LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-27-2016, 08:50 PM   #16
Xsane
Member
 
Registered: Jan 2014
Posts: 150

Rep: Reputation: 112Reputation: 112

Quote:
Originally Posted by Linux.tar.gz View Post
I noticed it because I patch a system that must not write to hwclock.
So when I used sed on /etc/rc.d/rc.6 I noticed the typo.
This is an example of why I tried to convince Pat to move the clock handlers to their own rc script.

With the kernel initializing the System Clock at boot, anyone using ntpd (so that '11 minute mode' keeps the Hardware Clock refreshed) doesn't need the init script clock handlers. Turning them off by removing the exe bit on rc.clocks would allow faster boot times. While other users with sneakernet boxen which require init clock handlers could still use them.

GazL recently commented about the seemingly random nature of what does, or does not, receive an rc script. I think a good starting criteria would be if a large percentage of users may want a given service turned off, then an rc script for it would be justified. For example, I'd find it useful to easily inhibit crond from auto starting without hacking the init scripts.
 
Old 03-28-2016, 01:52 AM   #17
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,449
Blog Entries: 15

Rep: Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021
That changes the nature of the subject. Systems that must not write back to the hardware for whatever reason should be taken into consideration. Alternative init systems like OpenRC have scripts for setting the clock. It might be useful for Slackware but it's usefulness may need to be proven.
 
Old 03-28-2016, 06:18 AM   #18
GazL
LQ Guru
 
Registered: May 2008
Posts: 5,193
Blog Entries: 18

Rep: Reputation: 2914Reputation: 2914Reputation: 2914Reputation: 2914Reputation: 2914Reputation: 2914Reputation: 2914Reputation: 2914Reputation: 2914Reputation: 2914Reputation: 2914
Quote:
Originally Posted by Xsane View Post
I think a good starting criteria would be if a large percentage of users may want a given service turned off, then an rc script for it would be justified. For example, I'd find it useful to easily inhibit crond from auto starting without hacking the init scripts.
The way I see it:
  • If a user may want to start/stop or otherwise affect something during runtime then it should have a separate rc.*.
  • For things that a user may or may not want to happen but which only occur at startup/shutdown, I favour the rc.conf/rc.conf.local approach. I don't think the chmod [+|-]x approach is always the most appropriate.

I can understand Pat being concerned about a proliferation of rc.* files and its definitely something to keep in mind, but as one of very few remaining non-systemd distro we're now something of a flag bearer for sysvinit and too be quite frank our inconsistent 20 year old script designs aren't exactly good arguments to throw in the faces of the systemd crowd.

Too close to 14.2 now to do anything. Would be nice to have some sort of a revamp for 15.0, but just like how the different package-sets still persist but really don't make much sense any more, I can't see Pat making any big changes in this area. If anyone wants something like this, I think they're going to have to implement it as an external customisation project. If the modifications proved popular then Pat might be open to adopting them in future, but I wouldn't hold my breath on that.
 
1 members found this post helpful.
Old 03-28-2016, 06:44 AM   #19
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 480Reputation: 480Reputation: 480Reputation: 480Reputation: 480
I have to Agree with the OP. When creating patches or merging these simple white spaces cause additional work. I can see down the line one day as Pat has said before some day Slackware setup on the git hub.
As for usability yes the script could care less.

It is all Slackware.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] XFCE Desktop - Slackware 14 - Typo lkraemer Slackware 3 11-10-2012 11:02 AM
SSL version number typo in slackware.com repository clifford227 Slackware 3 04-01-2010 04:33 PM
fluxbox.SlackBuild in -current typo? wadsworth Slackware 9 11-13-2008 01:59 PM
Typo in slackware-current/source/a/lilo/liloconfig drumz Slackware 7 02-22-2008 12:53 PM
dhcpcd in current..minor concerns gravityworks Slackware 3 06-21-2006 06:22 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration