Re: Etch to Lenny, two kernel options now, why?
- From: "Douglas A. Tutty" <dtutty@xxxxxxxxxxxxx>
- Date: Wed, 16 Jan 2008 09:39:18 -0500
On Wed, Jan 16, 2008 at 01:39:51PM +0100, ???????????????????? ??. ???????????????? wrote:
Quoth Andre:
I recently moved to Lenny from Etch via dist-upgrade. Now I got two
kernel options in grub available for boot. Doesn't a dist-upgrade mean
that the old kernel is quite useless with the new system (with all its
new libraries and stuff)? If so, how do I get rid off Etch's leftovers?
No, the Kernel doesn't depend on those libraries. Evenything you need to boot a
machine is in /boot and /lib/modules/`uname -r`. From then on, any init-process
may get called, which will most likely depend on _a lot_ of libs, but that's
fine.
There's and advantage to having some kind of static-linked shell (at
least). There used to be busybox static and now there's sash. You
would start it (and bypass the standard lib-dependant init scripts with
a kernel command line that contains:
init=/bin/sash
Doug.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: Etch to Lenny, two kernel options now, why?
- From: Александър Л. Димитров
- Re: Etch to Lenny, two kernel options now, why?
- References:
- Etch to Lenny, two kernel options now, why?
- From: Andre
- Re: Etch to Lenny, two kernel options now, why?
- From: Александър Л. Димитров
- Etch to Lenny, two kernel options now, why?
- Prev by Date: Re: How to filter out mailing list spam with bogofilter
- Next by Date: Re: Logging a kernel panic (remotely)
- Previous by thread: Re: Etch to Lenny, two kernel options now, why?
- Next by thread: Re: Etch to Lenny, two kernel options now, why?
- Index(es):
Relevant Pages
|