1 |
On Fri, Aug 05, 2011 at 08:25:19AM -0500, Matthew Summers wrote: |
2 |
> This, at least to me, seems like an excellent opportunity to nicely |
3 |
> document what can be done with an initramfs (in basic and advanced |
4 |
> forms, as there are some really fancy things one can do with |
5 |
> initramfs's), and how Gentoo is recommending their usage in the cases |
6 |
> outlined by Robin and others. |
7 |
|
8 |
I'm all in favor of documenting what an initramfs does (or at least what it |
9 |
is supposed to do), how it works, how to create one, how to debug issues |
10 |
while booting with one, etc. |
11 |
|
12 |
That said, I'm a bit hesitant to describing that we "recommend" it |
13 |
regardless of the situation. What is wrong with describing when? At least |
14 |
inform our users that the udev rules have evolved to more than just "detect |
15 |
and mknod" scripts and that they are now relying on files and binaries |
16 |
available in other locations, like /usr and /var. |
17 |
|
18 |
How does the tool that creates an initramfs know which files to copy from |
19 |
/usr and /var anyhow? |
20 |
|
21 |
Also, how well does this play with all our profiles (so not only the popular |
22 |
architectures)? What about SELinux and/or grSecurity's RBAC model? Are these |
23 |
supported throughout the initramfs? |
24 |
|
25 |
Wkr, |
26 |
Sven Vermeulen |