Gentoo Archives: gentoo-user

From: Mick <michaelkintzios@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] /dev/sda* missing at boot
Date: Sat, 20 Aug 2011 13:30:32
Message-Id: 201108201429.17095.michaelkintzios@gmail.com
In Reply to: Re: [gentoo-user] /dev/sda* missing at boot by David W Noon
1 On Saturday 20 Aug 2011 13:59:42 David W Noon wrote:
2 > On Sat, 20 Aug 2011 03:48:18 -0500, Dale wrote about "Re:
3 > [gentoo-user] /dev/sda* missing at boot":
4 >
5 > [snip]
6 >
7 > >I wish you could convince the devs of that. I already have /var on
8 > >its own and was planning to put /usr on its own. I'm not now tho.
9 > >Looks like /, /boot, /home and that's it for the OS part. It
10 > >downright sucks.
11 >
12 > I have also been following the discussion on gentoo-dev, although I
13 > currently only lurk there. I was going to register and post with a
14 > suggestion that everything should be on the root partition; that way we
15 > could rename it C: and be compliant with the "industry standard".
16 >
17 > However, it gets worse: one cannot safely fsck a partition or logical
18 > volume once it has been mounted. As things currently stand, there are
19 > no statically linked fsck modules for ext2/3/4, as static linkage was
20 > dropped from e2fsprogs about 3 years ago. This means for fsck to run
21 > inside an initramfs or intrd, the image will have to contain glibc,
22 > libpthread and a whole slew of other large libraries in order to run
23 > e2fsck with dynamic linkage. The initramfs will end up being *many*
24 > times larger than the kernel itself. [On my systems, the vmlinuz file
25 > is only about 1.8 megs, and glibc alone makes that look really puny.]
26 >
27 > Welcome to progress.
28
29 This is madness. Is there anything we can do to stop it?
30 --
31 Regards,
32 Mick

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-user] /dev/sda* missing at boot Pandu Poluan <pandu@××××××.info>
Re: [gentoo-user] /dev/sda* missing at boot Alan McKinnon <alan.mckinnon@×××××.com>