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