| 1 |
On Thu, 29 Mar 2012 14:35:36 -0400, Michael Mol wrote: |
| 2 |
|
| 3 |
> Fine. NFS clients. Samba clients. Crypto. SSHFS. NTFS-3g. Security |
| 4 |
> auditing. Virtualization tools. Perl, python or whatever is necessary |
| 5 |
> to handle some case which required scripting. X. Graphics loading |
| 6 |
> libraries. Cupsd, because some graphics library required by a |
| 7 |
> bootsplash expressed a dependency on cairo, which expressed a |
| 8 |
> dependency on something else, which expressed a dependency on cups. |
| 9 |
> |
| 10 |
> Perhaps crypto required a crypto daemon to be loaded, which required a |
| 11 |
> smartcard, or required auth from a serial port or network connection. |
| 12 |
> Perhaps an accurate clock is needed. Or perhaps a network policy |
| 13 |
> demands that a machine be authorized to boot, so an LDAP client is |
| 14 |
> required. |
| 15 |
> |
| 16 |
> It's easy to imagine entirely plausible circumstances which would |
| 17 |
> bloat initramfs size and maintenance. At some point in time, these |
| 18 |
> various things would normally be the simplest and most straightforward |
| 19 |
> way to reach a quick end to some problem or another for some poor guy |
| 20 |
> stuck in a private hell. And this initramfs crap increases the amount |
| 21 |
> of work he has to do to solve his unique case. |
| 22 |
> |
| 23 |
|
| 24 |
Setting up such a boot environment is decidedly non-standard and trying |
| 25 |
to put all that into a tool designed to get the core filesystem(s) loaded |
| 26 |
is ludicrous. But would you really want all of that available before init |
| 27 |
started to run? Mount / and /usr in the initramfs and run init. |
| 28 |
|
| 29 |
If you really need all that so early on, before /usr is mounted, maybe |
| 30 |
combining / and /usr is the cleanest approach. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Neil Bothwick |
| 35 |
|
| 36 |
Fer sail cheep, Windows spel chekcer, wurks grate |
Archives