Article 4QV04 Slackware rc.d Script Update Project

Slackware rc.d Script Update Project

by
upnort
from LinuxQuestions.org on (#4QV04)
Introducing the Slackware rc.d Script Update Project!

This is intended to be a community project with a goal of helping Pat and the development team. Please participate and help if you are interested. :)

Please test!

Files: https://www.remembertheusers.com/files/15-rc.d.tar.xz (320KB -- exceeds LQ attachment limits).

Primary Goals

* Update Slackware rc.d scripts for consistency.

Secondary Goals

* Add variables/parameters to /etc/default text files.
* Introduce editable pauses and delays.
* Hope Pat merges the proposed changes.

Version 0.1

* Version 0.1: First proposed release -- not perfect, be gentle!
* First wave of changes are mostly cosmetic and editorial.
* Consistent heading declarations and comments.
* Consistent indentation.
* Convert tabs to 2 spaces.
* As applicable, scripts use the same Usage reminder format.
* Add variables and parameters to /etc/default text files.
* Remove trailing spaces.
* Remove consecutive empty lines.
* Not intended for any release other than 15.0.

New files

* /etc/default/haveged
* /etc/default/pause
* /etc/default/smartd
* /etc/default/sysctl
* /etc/default/syslogd

* /etc/rc.d/rc.firewall
* /etc/rc.d/rc.local_shutdown

To Do

* Test!
* Fix my overzealous typos.
* Fix anything I missed.
* Add comments to help study/understand scripts.
* Add stdout to help debug scripts.

Wish List

* Some scripts are inherited from upstream where Debian or Red Hat systems are presumed. The scripts do not match Slackware stdout. Massage these scripts into Slackware rc.d format?
* Update rc.inet1 debug_log function to support stdout.
* Add stdout color output option to the scripts (refer to Salix/Zenwalk).
* Add pkgtool/setup option to support toggling color output.
* Possible blasphemy :): change stdout double spacing after punctuation to single space. (Can the BDFL be retrained to type single spaces? ;))

Discussion/Questions

* Some scripts use #!/bin/bash and some use #!/bin/sh. While Slackware defaults to ln -s /bin/sh->/bin/bash, should all scripts be hard-coded to using /bin/bash to avoid "bashism" concerns?
* Possibly controversial: Convert various sleep times to variables. Please recommend something different.
* Do inet1.conf and wireless.conf need to be chmod 600? What meaningful security is provided?
* When a script runs restart (stop/start), is a 1 second pause necessary these days?

Notes/Comments

If changes are maintained within this thread then I agree to coordinate and merge. I do not have and have no desire to create an online repository account. I have no objections if somebody wants to do that or has an account and wants to host the project for community participation.

When are the scripts presented to Pat? Community vote?latest?d=yIl2AUoC8zA latest?i=GPuBy7lRtN8:RCaxe1I21Tg:F7zBnMy latest?i=GPuBy7lRtN8:RCaxe1I21Tg:V_sGLiP latest?d=qj6IDK7rITs latest?i=GPuBy7lRtN8:RCaxe1I21Tg:gIN9vFwGPuBy7lRtN8
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments