| 1 |
On 3/10/12 7:50 PM, Rich Freeman wrote: |
| 2 |
> Well, I'm trying not to take sides in that war. Unless we want to |
| 3 |
> patch the living daylights out of upsteam it seems almost moot. |
| 4 |
|
| 5 |
It is not a matter about siding. If our boot process requires glib or |
| 6 |
dbus we are sore idiots if we aren't either of them available by that time. |
| 7 |
|
| 8 |
Luckily we do not *need* that at boot time but we can use daemons |
| 9 |
leveraging it after the file system hosting them is mounted. |
| 10 |
|
| 11 |
Same could be said for udev rules. If udev by itself can survive on the |
| 12 |
bare / till we mount our filesystem we are fine, if it does need to |
| 13 |
access the pci-id database we have either to provide it in a way or another. |
| 14 |
|
| 15 |
> I'm not even so much interested in making dracut easy to use. I'd |
| 16 |
> just appreciate it if there were even a single sentence written on |
| 17 |
> each of its modules and options, let alone some kind of coherent guide |
| 18 |
> to how to make it all work. |
| 19 |
|
| 20 |
That would be great. |
| 21 |
|
| 22 |
> There is a guide out there, but it hasn't really kept pace with the |
| 23 |
> very rapidly evolving tool, and it doesn't really cover all the |
| 24 |
> nuances. |
| 25 |
|
| 26 |
Ouch. |
| 27 |
|
| 28 |
> Another useful thing would be to update our official RAID+LVM guide so |
| 29 |
> that when you're done following it your system will boot. |
| 30 |
|
| 31 |
indeed. |
Archives