On 5/16/05, Declan Moriarty <[EMAIL PROTECTED]> wrote: > On Sun, May 15, 2005 at 09:56:32AM -0500, Dan McGhee enlightened us thusly > > I've built a couple of pakcages recently, hplip is one, that are not in > > the BLFS book. They want to put bootscripts into /etc/init.d. Of > > course, since I've followed the direction in both LFS and BLFS :), I > > don't have a directory like that. On the Mandrake side of my box, > > there's a link: > > > > /etc/init.d -->/etc/rc.d/init.d > > > > Until now I've used ' install [blah-blah] /etc/rcd./init.d' to work > > around this. > I presume you mean /etc/rc.d/init.d > > > > Are there any "up" or "down" sides to putting this link in? > > > If you don't have it, some things don't work :-) > > Somebody unix lot (RedHat? and mebbe others) did it this way, and users > of it write stuff that gets installed to /etc/init.d. So your startup > scripts end up there. All purists will tear their hair out until that > gets tidied strictly into the place FHS says it should be. This, in > fact, is what FHS is about; So the purists can whip the rest of us into shape > ;-).
Most programs just install a simple program you have to run at startup [like OpenSSH has sshd]. You are supose to use /etc/rc.d/init.d/template to make your own bootscript (; -- Nathan Coulson (conathan) ------ nathan at linuxfromscratch org conathan at gmail com -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
