From: Jesper Juhl <juhl-lkml@dif.dk>
To: "Johnson, Richard" <rjohnson@analogic.com>
Cc: Arjan van de Ven <arjanv@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux-2.6.5-1.358 and Fedora
Date: Tue, 5 Oct 2004 22:55:21 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0410052247140.2913@dragon.hygekrogen.localhost> (raw)
In-Reply-To: <Pine.LNX.4.53.0410051635370.3240@quark.analogic.com>
On Tue, 5 Oct 2004, Johnson, Richard wrote:
> On Tue, 5 Oct 2004, 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.
> >
>
> Yeh? There is no place to get replacement modules from. They are
> somewhere on some RPM on one of the CDs,
That's not what I'd call "no place", that's "a place", and one you most
likely have available lying on your desk. Even if you don't have the CDs
any more you can always download the RPM you need from the net while
running in rescue mode.
> with no way to know. It's
> not like you could tar everything from the current root file-system.
>
Just like Slackware has a log of all packages and the files they contain
in /var/log/packages/ , so does RPM based distros like Fedora have their
rpm database. The 'rpm' tool can be used to search the database for
packages that contain a specific file, and once you know the RPM you need
you can easily find it on your CDs (even if you have no idea where to look
'find' should find it for you easily enough). Read through "man rpm" some
day, a package tool without a database of installed packages and the
files contained in those packages would be pretty useless.
--
Jesper Juhl
next prev parent reply other threads:[~2004-10-05 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 18:17 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
2004-10-05 19:52 ` Neil Horman
2004-10-05 20:38 ` Johnson, Richard
2004-10-05 20:55 ` Jesper Juhl [this message]
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=Pine.LNX.4.61.0410052247140.2913@dragon.hygekrogen.localhost \
--to=juhl-lkml@dif.dk \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjohnson@analogic.com \
/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
all inboxes | Powered by JetHome®