From: Jesse Pollard <jesse@cats-chateau.net>
To: John Lash <jkl@sarvega.com>, Michael Lothian <s0095670@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Catch 22
Date: Wed, 14 Jan 2004 10:50:32 -0600 [thread overview]
Message-ID: <04011410503200.32256@tabby> (raw)
In-Reply-To: <20040114090137.5586a08c.jkl@sarvega.com>
On Wednesday 14 January 2004 09:01, John Lash wrote:
> On Wed, 14 Jan 2004 14:40:03 +0000
>
> Michael Lothian <s0095670@sms.ed.ac.uk> wrote:
> > Just thaought I'd let you know about my experiences with Mandrake using
> > the 2.4 and 2.6 kernels on my new hardware which is primaraly a Asus
> > A7V600 (KT600) Motherboard and Radeon 9600XT
> >
> > Under 2.4 my ATA hard drak is mounted under /dev/hda where as under 2.6
> > is /dev/hde so there is no wasy way to switch between them with lilo and
> > /etc/fstab needing to be changed
>
> At least in this case, you should be able to use volume labels for the
> filesystems instead of the actual device names. Check out tune2fs -L. You
> then reference the volume label in your fstab.
>
> With lilo, you can specify that boot disk and root disk on the command
> line. Also you can point lilo to a different config file using lilo -C. Not
> seamless but should allow you to bounce back and forth w/o editing
> files....
>
> Sorry, I'm not familiar with the rest.....
Also you can use a MBR lilo that only boots one or more partitions, then
have Lilo installed on each partition to select a specific kernel related
to that particular partition. This way you no longer have to update a
single point of failure - only update the lilo configuration on a specific
partition when changes are needed.
You avoid altering the MBR and the other partition.
next prev parent reply other threads:[~2004-01-14 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 14:40 Catch 22 Michael Lothian
2004-01-14 15:01 ` John Lash
2004-01-14 16:50 ` Jesse Pollard [this message]
2004-01-14 17:03 ` Rudo Thomas
2004-01-14 17:14 ` Randy.Dunlap
2004-01-14 18:16 ` John Lash
2004-01-14 18:42 ` Paulo Marques
2004-01-14 20:01 ` Lech Szychowski
2004-01-15 0:37 ` Michael Lothian
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=04011410503200.32256@tabby \
--to=jesse@cats-chateau.net \
--cc=jkl@sarvega.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0095670@sms.ed.ac.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.