<br><br><div class="gmail_quote">On Sun, Jun 20, 2010 at 8:32 AM, Keith Richie <span dir="ltr"><<a href="mailto:disturbed1976@gmail.com">disturbed1976@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Sun, Jun 20, 2010 at 8:15 AM, Robert Kelsen <<a href="mailto:rkelsen@optusnet.com.au">rkelsen@optusnet.com.au</a>> wrote:<br>
>> That's not the "Slackware way" of init. Slackware uses a BSD-like init.<br>
><br>
> Well, I wasn't expecting such a politically charged response.<br>
><br>
><br>
> Then why are there all of these /etc/rc.d/rc*.d directories?<br>
><br>
> People who say that Slackware's init is "BSD-like" should go and install<br>
> a *BSD before making this comment.<br>
><br>
>> I vote for not using this for SlackBuilds on <a href="http://slackbuilds.org" target="_blank">slackbuilds.org</a>.<br>
><br>
> You vote against a symlink? You'd rather keep manually editing rc.local?<br>
> _______________________________________________<br>
> SlackBuilds-users mailing list<br>
> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
> FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
><br>
><br>
<br>
</div></div>Let's see -<br>
A single rc.blah file, and edit rc.local{shutdown}.<br>
or<br>
A single rc.blah, with a link to init.d, then links from that linked<br>
link to different run levels, a K{ill} link to stop the script in the<br>
proper run levels, and a S{tart} link to start the script in the<br>
proper run levels, along with figuring out the K/S number to get the<br>
order correct.<br>
<br>
I'm not entirely sure which one is easier to manage, maintain, and update ;-)<br></blockquote><div><br></div><div>I think you've made the case very well and agree completely. I think the current Slackware method is just fine.</div>
<div><br></div><div>By the way, regarding the original poster's "<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">People who say that Slackware's init is "BSD-like" should go and install</span></div>
<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">a *BSD before making this comment." comment: I have run both FreeBSD (which I found too buggy as a desktop system; its reputation for solidity was earned on servers) and OpenBSD (which is a rock-solid system, but technically behind Linux -- e.g., no unified buffer cache, crude SMP support -- and noticeably slower; I ran it for almost a year before tiring of the nastiness and rudeness of the developer community -- to everyone -- which takes its behavioral cues from Theo de Raadt). Slackware is very similar in spirit to OpenBSD. Both place value on conceptual simplicity and the result is that you configure them by editing things like rc.local. Both systems are easy and straightforward to administer. I would hate to see Slackware go the sys V route, which I always found cumbersome.</span></div>
<div class="gmail_quote"><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div class="gmail_quote"><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">/Don<br>
</span></font><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
<br>
"Then why are there all of these /etc/rc.d/rc*.d directories?"<br>
</div>To provide compatibility to those proprietary packages that like to<br>
unnecessarily complicate things. At least Virtual Box gets this right.<br>
<div><div></div><div class="h5">_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
</div></div></blockquote></div><br>