"Donn Cave" <donn@xxxxxxxxxxx> wrote: > This is probably more obvious to someone who already knows what it > means, > but somewhere I hope it's documented in a little more detail. Like, > what does "system-wide" mean - if I'm writing an install script, how > do > I know what is system-wide and what isn't? > > If there's really a point in creating a new, competing platform- > specific > install location, it's important for that purpose to be described as > unambiguously as possible. Otherwise you can end up with something > that > was started with good intentions, but actually makes life worse by > splitting stuff more or less at random between two locations. > (Really > I think that outcome is nearly guaranteed, but I hope I'm wrong.) /boot/system is for the system, and only for the system. You don't alter it. /boot/common is for *any* resources you add that are shared between users. /boot/home/ is the playfield for the one user there currently is. Bye, Axel.