Gentoo Archives: gentoo-dev

From: Matthew Summers <quantumsummers@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: Let's redesign the entire filesystem!
Date: Wed, 14 Mar 2012 16:29:44
Message-Id: CAET+hMSuDgmfZ_yy_+-jn-5Umb0_dnanUzcWvUKMkw9KEM3mYQ@mail.gmail.com
In Reply to: Re: [gentoo-dev] Re: Let's redesign the entire filesystem! by Greg KH
1 On Wed, Mar 14, 2012 at 10:22 AM, Greg KH <gregkh@g.o> wrote:
2 > On Wed, Mar 14, 2012 at 03:08:27PM +0000, Ciaran McCreesh wrote:
3 >> On Wed, 14 Mar 2012 08:04:31 -0700
4 >> Greg KH <gregkh@g.o> wrote:
5 >> > Not always, no, it isn't obvious that something didn't start up
6 >> > correctly, or that it didn't fully load properly.  Some programs later
7 >> > on recover and handle things better.
8 >>
9 >> So why not work on fixing those things, since they're clearly symptoms
10 >> of a larger "oops, we have too much coupling" problem, instead of
11 >> forcing a workaround onto large numbers of users?
12 >
13 > I seriously doubt there are a "large number" of users here that have
14 > this issue.
15 >
16
17 The majority of users should not encounter any difficulty due to this
18 issue. Those that are doing special things that require careful
19 mounting, etc should be sufficiently competent to deal with this issue
20 without any trouble at all, especially given the various solution
21 paths.
22
23 > And even if there is, again, there is a simple solution that Gentoo
24 > provides for this issue, see the earlier initrd solution that we support
25 > today.
26 >
27
28 Gentoo provides a solution with genkernel, dracut provides a solution,
29 even the linux kernel itself provides a solution (in my view the
30 easiest solution at that).
31
32 > I'll go back to lurking now, and getting stuff done, like everyone else
33 > on this thread should be doing, instead of complaining (this is -dev,
34 > not -users...)
35 >
36 > greg k-h
37 >
38
39 Oh, please Greg, do continue to stay engaged, I enjoy your perspective
40 very much.
41
42 I just wanted to drop this simple fact in there. This has been coming
43 for several years now AND the linux kernel has been using an initramfs
44 for every boot, every time for a long time now, all 2.6 and up as I
45 understand it. If the initramfs is empty, well the kernel is smart
46 enough to fall back on "legacy" boot process.
47
48 If you care to read about it, its all contained locally if your kernel
49 source in the file
50 linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt
51
52 Its a great read, sure to entertain and enlighten. It saved my bacon a
53 few times when mdadm switched to the new metadata format. Once I began
54 to learn about what the initramfs made possible, entire new worlds of
55 possibility appeared (and I was not even on drugs!).
56
57 It's actually something of a surprise to me that there are people
58 upset about this change, since it cleans things up a bit while also
59 giving people that want and/or need it, a great deal of power and
60 control over the boot process that was not nearly as easy before.
61
62 I do believe Gentoo, as a community/volunteer-run and super-power-user
63 distribution, should be careful, a bit wary, and seriously consider
64 the decisions made by our corporate colleagues (we do have the mandate
65 to maintain our independence). However, simply because RHEL, SUSE, etc
66 are corporation controlled distributions does not mean they are bad or
67 trying to control/ruin the rest of the distros.
68
69 Anyway, I merely thought I would place my commentary on this situation
70 here for posterity. Since I have an opinion, I thought I would share
71 it for better or worse.
72
73 --
74 Matthew W. Summers
75 Gentoo Foundation Inc.

Replies

Subject Author
Re: [gentoo-dev] Re: Let's redesign the entire filesystem! Joshua Kinard <kumba@g.o>