From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kernel panic on manually built kernel
Date: Mon, 8 Nov 2010 21:15:40 +0000 [thread overview]
Message-ID: <D109E9CD-F46A-46F7-9330-8E1E0F0D6770@stellar.eclipse.co.uk> (raw)
In-Reply-To: <4CD839D2.5060206@gmail.com>
On 8/11/2010, at 5:56pm, Dale wrote:
> ...
> I have not been able to get grub to see the LABELS yet but I'm going to post fstab so that you have a example that is known to work and not from a guide:
>
> /dev/disk/by-label/boot /boot ext2 noatime 1 2
> /dev/disk/by-label/root / reiserfs defaults 0 1
> /dev/disk/by-label/swap none swap sw 0 0
> /dev/disk/by-label/portage /usr/portage ext3 defaults 0 1
> /dev/disk/by-label/home /home reiserfs defaults 1 1
> /dev/disk/by-label/data /data reiserfs defaults 0 1
I'm not paying enough attention to know whether your above fastab works or not, but /dev/disk/by-label/* seems a relatively ugly way of doing things. I'm pretty sure it's not intended that you use that format, and I have no idea whether it's supposed to work that way.
All the guides say to use the word "LABEL". That's not a variable or anything - it's the literal word you're supposed to use.
I have no idea why a guide should be considered unreliable, but the below is not fabricated - it is from an actual working system:
$ grep -ve ^# /etc/fstab
LABEL=boot /boot ext2 noauto,noatime 1 2
LABEL=/ / ext4 noatime 0 1
LABEL=swap none swap sw 0 0
/dev/cdrom /mnt/cdrom auto noauto,ro,users 0 0
LABEL=space /mnt/space ext4 noatime 0 3
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
$
To me this seems cleaner than your format, and it's certainly fewer characters!
Stroller.
next prev parent reply other threads:[~2010-11-08 21:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 16:34 [gentoo-user] kernel panic on manually built kernel dhk
2010-11-04 16:45 ` Dale
2010-11-04 18:12 ` covici
2010-11-04 18:19 ` dhk
2010-11-04 18:36 ` Yohan Pereira
2010-11-04 18:39 ` covici
2010-11-04 16:52 ` Alan McKinnon
2010-11-04 17:00 ` dhk
2010-11-04 17:08 ` Neil Bothwick
2010-11-04 17:36 ` dhk
2010-11-04 19:25 ` Alan McKinnon
2010-11-05 9:29 ` dhk
2010-11-05 9:43 ` Alan McKinnon
2010-11-04 19:51 ` Neil Bothwick
2010-11-05 9:47 ` dhk
2010-11-05 10:30 ` Alan McKinnon
2010-11-05 10:33 ` Neil Bothwick
2010-11-05 11:36 ` dhk
2010-11-05 19:31 ` [gentoo-user] " walt
2010-11-04 20:41 ` [gentoo-user] " Stroller
2010-11-04 19:24 ` Alan McKinnon
2010-11-05 15:52 ` Volker Armin Hemmann
2010-11-08 10:28 ` Coert Waagmeester
2010-11-08 10:48 ` dhk
2010-11-08 11:05 ` Coert Waagmeester
2010-11-08 17:56 ` Dale
2010-11-08 21:15 ` Stroller [this message]
2010-11-08 21:34 ` Dale
2010-11-08 21:43 ` Stroller
2010-11-08 22:34 ` Dale
2010-11-08 22:39 ` Neil Bothwick
2010-11-08 22:47 ` Dale
2010-11-09 0:05 ` Stroller
2010-11-08 15:50 ` Volker Armin Hemmann
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=D109E9CD-F46A-46F7-9330-8E1E0F0D6770@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--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