[Slackbuilds-users] rc-script permissions

Robby Workman rworkman at slackbuilds.org
Mon Mar 30 04:00:56 UTC 2009

On Wed, 11 Feb 2009 09:33:08 +0100
"Chris Abela" <chris.abela at maltats.com> wrote:

> Further to a discussion that ensued on a linuxquestions.org thread:
> http://www.linuxquestions.org/questions/slackware-14/virtualbox-2.1.2-slackb
> uild-699309/
> I noted that the permissions on rc-scripts installed by Slackbuild
> packages are not consistent. Moreover the default permissions are not
> documented by the specific slackbuilds README files. A solution might
> be one of the following:
> 1. Specify the default permissions on rc-scripts for all slackbuilds
> (say 7xx)
> 2. Specify that README files shall declare the default rc-scripts
> permissions.
> 3. Warn users that there are no rules in this regard and they should
> check them out themselves (if they exist).

I don't know if this got a reply or not before -- I'm finding a few
orphan threads in my inbox tonight -- but this is basically a "caveat
lector" type thing that's more or less inconsequential.  Anything that
installs an init script will still require the admin to call that init
script from rc.local or another stock rc script before it will actually
run, so the permissions on the package-supplied script are largely
irrelevant.   I can only recall one exception to this -- the shorewall
packages install an rc.firewall, and since rc.firewall *is* called from
the stock system scripts if it exists, then there may be a valid case
of special handling here.

The more important issue is keeping the current permissions on an
existing init script when the new one is installed.  For example, if
rc.blah already exists, then we want rc.blah.new to have the same
permissions.  Even though the admin will need to diff the two scripts
to see what changed, there's no sense in requiring extra work to verify
the permissions too.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090329/4732141c/attachment.asc>

More information about the SlackBuilds-users mailing list