public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: mount: "special device /dev/hdc does not     exist". What does this mean?
Date: Sun, 20 Jul 2008 22:33:02 +0300	[thread overview]
Message-ID: <g603tg$4sf$1@ger.gmane.org> (raw)
In-Reply-To: <4883911E.8000207@bellsouth.net>

Dale wrote:
> 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
>> [...]
> 
> Question, if I were to label mine and then boot from a Gentoo or any 
> other bootable CD, would those labels still be there?

The labels are part of the file system; they're always there.  For 
example, when booting the 2007.0 LiveDVD (which uses the legacy drivers, 
meaning /dev/hd* instead of /dev/sd*) the labels are there and I can 
mount /dev/disk/by-label/GentooRoot just fine.




  reply	other threads:[~2008-07-20 19:33 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
2008-07-20 19:33             ` Nikos Chantziaras [this message]
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='g603tg$4sf$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --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