1 |
On March 18, 2012 at 2:52 PM "Canek Peláez Valdés" <caneko@×××××.com> |
2 |
wrote: |
3 |
|
4 |
> On Sun, Mar 18, 2012 at 11:44 AM, Tanstaafl <tanstaafl@×××××××××××.org> |
5 |
wrote: |
6 |
> |
7 |
> [snip] |
8 |
> |
9 |
> > Ok, I have never used genkernel, and have no desire to... |
10 |
> > |
11 |
> > I have no idea what dracut is or how to use it... |
12 |
> > |
13 |
> > I have a remote system that has /usr on a separate partition. |
14 |
> > |
15 |
> > So... |
16 |
> > |
17 |
> > How do I find out if I am actually *using* an initramfs right now (I |
18 |
know it |
19 |
> > is built into the kernel), and |
20 |
|
21 |
ls -l /boot/ will tell you. |
22 |
|
23 |
There is a difference between an initrd (initial RAM disk) image (simple) |
24 |
and an initramfs (initial RAM filesystem) (complicated). Gentoo used to |
25 |
have a script called mkinitrd. It was removed before I migrated to Gentoo, |
26 |
but I should look in attic to see if it's still there. To date I've found |
27 |
no one in Gentoo who will even discuss it. |
28 |
|
29 |
Slackware has used mkinitrd for ions, and it still works very efficiently |
30 |
there. Of course, Eric Hameleers understands the script, and Slackware's |
31 |
init scripts, and maintains mkinitrd. Maybe in Gentoo somebody "upstream" |
32 |
scared people with initramfs, like they're doing with this horrible systemd |
33 |
idea, and whoever maintained mkinitrd just cowered in the corner and |
34 |
dropped the ball. Who knows? |
35 |
|
36 |
The bottom line is that "officially" Gentoo has abandoned initrd for |
37 |
initramfs. You can write a script to make an initrd, as people do all the |
38 |
time. But don't look for official Gentoo support for it. |
39 |
|
40 |
It seems to me after a year around Gentoo that things get so complicated, |
41 |
and upstream gets to "force" things on Gentoo (such as systemd), because |
42 |
there are just too many different developers. All are human with different |
43 |
opinions, so you wind up with people going off in different directions with |
44 |
no cohesive ability to stand against upstream. IOW, we're too forked within |
45 |
Gentoo. |
46 |
|
47 |
For instance, the maintainer of ConsoleKit in Gentoo (Gnome herd guy) says |
48 |
he doesn't care about systemd, he's maintaining ConsoleKit and it's not |
49 |
going anywhere. (We'll see...) |
50 |
|
51 |
Anyway ... for more on Gentoo's initramfs read |
52 |
http://en.gentoo-wiki.com/wiki/Initramfs |
53 |
|
54 |
> > If I am not, how do I do this without using genkernel? Is dracut the |
55 |
*only* |
56 |
> > other option? Is it easy/trivial to set one up manually? |
57 |
|
58 |
> |
59 |
> On March 18, 2012 at 2:52 PM "Canek Peláez Valdés" <caneko@×××××.com> |
60 |
prattled: |
61 |
> |
62 |
> udev is going to be unmasked, not stabilized. By the time udev gets |
63 |
> into x86/amd64, hopefully the documentation necessary will be ready. |
64 |
|
65 |
That's you telling the world what an asinine idea this drastic change is |
66 |
... when it's the stable version, which most of the unsuspecting Gentoo |
67 |
userbase will emerge, "hopefully the documentation necessary will be |
68 |
ready." Par for the Poettering course. |
69 |
|
70 |
> You can suscribe to bug 407959 |
71 |
> (https://bugs.gentoo.org/show_bug.cgi?id=407959), which tracks the |
72 |
> documentation changes necessary. Right now the only blocker is 408691 |
73 |
> (https://bugs.gentoo.org/show_bug.cgi?id=408691), but I'm sure it will |
74 |
> be joined by more bugs in the near future. |
75 |
> |
76 |
> Devs are already working on the documentation. If you have a test |
77 |
> spare machine, you can help them, and the whole Gentoo comunity. |
78 |
> |
79 |
> Regards. |
80 |
> -- |
81 |
> Canek Peláez Valdés |
82 |
|
83 |
udev is already unmasked, and stabilized at 171-r5 now... |
84 |
You need to explain what you mean ... you're probably talking about |
85 |
udev-181 |
86 |
|
87 |
Please don't encourage people who don't understand what's happening to test |
88 |
nefarious software ideas. There is nothing about this that's going to "help |
89 |
the whole Gentoo community." |
90 |
-- |
91 |
Happy Penguin Computers >`) |
92 |
126 Fenco Drive ( \ |
93 |
Tupelo, MS 38801 ^^ |
94 |
662-269-2706; 662-491-8613 |
95 |
support at happypenguincomputers dot com |
96 |
http://www.happypenguincomputers.com |