public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.6.5-1.358 and Fedora
Date: Tue, 05 Oct 2004 15:21:58 -0500	[thread overview]
Message-ID: <41630266.7070402@pbl.ca> (raw)
In-Reply-To: <20041005194208.GE11254@devserv.devel.redhat.com>

Arjan van de Ven wrote:
> On Tue, Oct 05, 2004 at 09:46:18PM +0200, Jesper Juhl wrote:
> 
>>On Tue, 5 Oct 2004, Arjan van de Ven wrote:
>>
>>
>>>If Richard overwrote his modules anyway he must have hacked the Makefile
>>>himself to deliberately cause this, at which point... well saw wind
>>>harvest storm ;)
>>>
>>
>>While I lack specific Fedora knowledge and thus can't provide exact 
>>details for it I'd say it should still be pretty simple to recover. On 
>>Slackware I'd simply boot a kernel from the install CD and tell it to 
>>mount the installed system on my HD, then you'll have a running system and 
>>can easily clean out the broken modules etc and install the original ones 
>>from your CD and be right back where you started in 5 min. Surely 
>>something similar is possible with Fedora, reinstalling from scratch (as 
>>he said he did) seems like massive overkill to me.
> 
> 
> yeah there is rescue mode for that reason on the first cd

Actually, FC2 has an CD called rescue CD.  All he needed to do (if he 
toasted his working kernel) was to boot from it, and reinstall the 
kernel package from the first CD (rpm -Uhv --force 
kernel-2.6.5-1.358.i686.rpm or i586, force is needed to push things a 
bit since system thinks the same version of package is already installed).

I'd be quite interested to find out how he managed to toast his working 
kernel.  Not an easy task.  Actaully it is, but requires some manual 
work, it can't be done by just typing make this, make that.  There were 
some steps he "forgot" to mention ;-).

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7

  reply	other threads:[~2004-10-05 20:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 18:17 Linux-2.6.5-1.358 and Fedora Johnson, Richard
2004-10-05 18:34 ` Arjan van de Ven
2004-10-05 19:15 ` Jesper Juhl
2004-10-05 19:29   ` Arjan van de Ven
2004-10-05 19:46     ` Jesper Juhl
2004-10-05 19:42       ` Arjan van de Ven
2004-10-05 20:21         ` Aleksandar Milivojevic [this message]
2004-10-05 19:52       ` Neil Horman
2004-10-05 20:38       ` Johnson, Richard
2004-10-05 20:55         ` Jesper Juhl
2004-10-05 21:00         ` Aleksandar Milivojevic
2004-10-05 20:34     ` Johnson, Richard
2004-10-07  8:00   ` Sander
2004-10-05 21:48 ` David van Hoose

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41630266.7070402@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox