From: Dale <dalek1967@bellsouth.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Date: Sun, 20 Jul 2008 14:25:18 -0500 [thread overview]
Message-ID: <4883911E.8000207@bellsouth.net> (raw)
In-Reply-To: <g602l6$1q6$1@ger.gmane.org>
Nikos Chantziaras wrote:
> Mick wrote:
>> [...]
>> What would be the recommended way of upgrading from the /dev/hd to
>> /dev/sd then? I have held back doing this because I didn't have the
>> time to mess about with it. If I were to configure a new kernel
>> without legacy ATA drivers, how would I know what my devices will be
>> seen as in advance, so that I can change my /etc/fstab before I reboot?
>
> The way I do it, is to label my partitions. If your partitions aren't
> labeled yet, you can do so with 'tune2fs'. If your /dev/hda1 is your
> root (/), /dev/hda2 your /home and /dev/hda3 your swap, you can label
> them with:
>
> tune2fs -L GentooRoot /dev/hda1
> tune2fs -L GentooHome /dev/hda2
> mkswap -L GentooSwap /dev/hda3
>
> Then edit /etc/fstab and change the mount points from:
>
> /dev/hda1 ...
> /dev/hda2 ...
> /dev/hda3 ...
>
> to:
>
> /dev/disk/by-label/GentooRoot
> /dev/disk/by-label/GentooHome
> /dev/disk/by-label/GentooSwap
>
> As reference, here the relevant entries in my own /etc/fstab:
>
> /dev/disk/by-label/GentooRoot / ext3 noatime 0 1
> /dev/disk/by-label/GentooSwap none swap sw 0 0
> /dev/disk/by-label/Suckage /windows/C ntfs-3g noatime 0 0
>
> As you can see this even works for NTFS; you use the label you gave
> the drive in Windows.
>
> After you've done these changes, it doesn't matter the least anymore
> what the actual device name is. You can even move the harddisk to
> another computer (actually I'm doing exactly that) that totally
> results in a re-ordering of /dev/sd* entries and it will still mount
> correctly.
>
>
>
Question, if I were to label mine and then boot from a Gentoo or any
other bootable CD, would those labels still be there?
Dale
:-) :-)
next prev parent reply other threads:[~2008-07-20 19:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 18:51 [gentoo-user] mount: "special device /dev/hdc does not exist". What does this mean? Alan Mackenzie
2008-07-19 19:06 ` [gentoo-user] " Nikos Chantziaras
2008-07-19 21:12 ` Alan Mackenzie
2008-07-19 21:29 ` Nikos Chantziaras
2008-07-20 14:52 ` Mick
2008-07-20 19:11 ` Nikos Chantziaras
2008-07-20 19:25 ` Dale [this message]
2008-07-20 19:33 ` Nikos Chantziaras
2008-07-20 19:58 ` Dale
2008-07-20 20:27 ` Nikos Chantziaras
2008-07-20 21:10 ` Dale
2008-07-20 21:20 ` Dale
2008-07-20 23:25 ` Nikos Chantziaras
2008-07-20 20:12 ` Mick
2008-07-20 23:35 ` Nikos Chantziaras
2008-07-21 6:56 ` Neil Bothwick
2008-07-20 15:05 ` Alan Mackenzie
2008-07-20 17:22 ` Mick
2008-07-20 18:49 ` Alan Mackenzie
2008-07-20 18:48 ` Neil Bothwick
2008-07-20 20:10 ` Nikos Chantziaras
2008-07-20 18:54 ` [gentoo-user] Solved!!! [Re: mount: "special device /dev/hdc does not exist"] Alan Mackenzie
2008-07-19 19:11 ` [gentoo-user] mount: "special device /dev/hdc does not exist". What does this mean? Daniel Pielmeier
2008-07-19 21:41 ` Alan Mackenzie
2008-07-19 21:53 ` Daniel Pielmeier
2008-07-19 19:13 ` [gentoo-user] " Miernik
2008-07-19 21:22 ` Alan Mackenzie
2008-07-19 21:33 ` Graham Murray
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=4883911E.8000207@bellsouth.net \
--to=dalek1967@bellsouth.net \
--cc=gentoo-user@lists.gentoo.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