From: Paulo Marques <pmarques@grupopie.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: John Lash <jkl@sarvega.com>,
s0095670@sms.ed.ac.uk, linux-kernel@vger.kernel.org
Subject: Re: Catch 22
Date: Wed, 14 Jan 2004 18:42:51 +0000 [thread overview]
Message-ID: <40058DAB.30802@grupopie.com> (raw)
In-Reply-To: 20040114091456.752ad02d.rddunlap@osdl.org
Randy.Dunlap wrote:
> On Wed, 14 Jan 2004 09:01:37 -0600 John Lash <jkl@sarvega.com> 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....
>
> Does anyone know the reason for this (ATA ident/naming change)?
>
> I do *not* see this and I'm also using Mandrake (v9.0, not later).
>
I guess the problem is that, by default, Mandrake creates an extended partition
when installed, where all the other partitions go.
Whenever I install Mandrake, I'm always careful to switch to "Expert" mode and
configure the partitions to be primary by hand to avoid this kind of problems.
If you are a corageous hacker, you can always:
- boot from a CD distribution (knoppix, etc.)
- run fdisk on your hard drive
- take note on the cylinders being used by the partitions,
- delete the partitions on the extended partition, and the extended partition
itself
- create the partitions again as primary using the *exact* same cylinders
- write the partition to disk
- reboot
Probably you'll have to adjust fstab to use the new partitions, but at least 2.4
and 2.6 should both agree that you have an hda :)
I don't know if you'll need to run lilo again before rebooting, but I would do
that just to be on the safe side. To do that:
- mount /dev/hda somewhere (/mnt/disk or something)
- # cd /mnt/disk
- edit etc/lilo.conf to always use /dev/hda
- # chroot . lilo
I hope this helps,
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
next prev parent reply other threads:[~2004-01-14 18:43 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
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 [this message]
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=40058DAB.30802@grupopie.com \
--to=pmarques@grupopie.com \
--cc=jkl@sarvega.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox