> Alan, > > Ok, so if /etc/init.d is the standard, why is that the symlink on the newer > systems, rather than the other way around? What kind of things would break > if /etc/init.d was the real directory and the older convention used a > symlink?
I don't recall the details, but Red Hat did try what you suggest. I think it was in rawhide. I didn't get caught up in that one, but people did complain about things that didn't work. > > Mark Post > > -----Original Message----- > From: Alan Cox [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 26, 2002 6:21 PM > To: [EMAIL PROTECTED] > Subject: Re: SSHD at boot > > > > No sure about that, you should read the LSB docs for builds, certainly has > > changed. Right, SuSE did place a symlink there for the RH RPM's But > > calling this "Standard" is a little far, Solaris and system V are > > /etc/init.d But, anybody can make a standard I guess, just have to get > > people to follow it is the trick or be a monopoly like Microsoft and > > change an RFC because you want to put stupid hooks into it for your own > > selfish pleasure, and demand that people use it :~0) > > The standard is /etc/init.d. Which is why RH has a symlink there. Older RH > used /etc/rc.d/init.d and it wouldnt be appropriate to break old third > party apps > -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
