Am Sat, 15 Oct 2011 12:31:24 +0100 schrieb Neil Bothwick <[email protected]>:
> On Sat, 15 Oct 2011 03:10:37 -0700, Canek Peláez Valdés wrote: > > > It's arbitrary (basically) on executables and libraries. If an > > script needs something more (from /var, lets say), then the rule > > should be written in such a way that it can be called after that > > directory is mounted. If you try to put the same restriction with > > *executables* (not data, like in the ALSA case), then you need to > > start moving every executable to /, because that's the only way to > > guarantee that it would be available aearly on boot time (if you > > don't use an initramfs and have /usr separated). > > Anything needed for early boot is already in /. The problem is that > udev is trying to run all its rules at that early stage, when it > should not. This currently causes some actions to fail because /usr > is not mounted yet. The solution is not to mount /usr early, because > that only deals with one case, but to make sure that udev does not > run actions until the full system is available. This has been stated > many times by several people in the previous threads. correct. > > >> It basically removes the need for a "pesky init* thingy", > > >> although for the life of me I cannot understand why someone will > > >> not see the technical advantages of actually using an > > >> initramfs. why would anyone *want* an initramfs? its a clumsy workaround for limitations that should be overcome with better solutions. > > > > > > We understand its advantages in some circumstances, but I cannot > > > understand why someone will not see the technical disadvantages of > > > actually using an initramfs. either you read your schopenhauer or you are good at spotting bad/unfair arguments ;) > > > > Care to explain? > > Again? It's already been covered many times before. You expect people > to blindly accept your POV that an initramfs is a good thing, yet > refuse to see the circumstances where others believe it is not. For > one thing, implementing this in a stable, running system without > interruption is a non-trivial task. > >
