It is about the use of another group, similar to "install", with the
directories /etc/rc.d/...
I found that it could be useful in order to prevent a software
installation to install a service without being allowed by the
root user. The root user has to add the package user to that
group (let's name it "bootscripts") in order to make it able to
install files in the etc/rc.d directories.
Hmm, it sounds sensible, but so far I'm unable to see how different this
would be to pkg-usr approach. Right now I think have what you seem to
aiming at implemented. I'm following the hint, and have a user called
bootscripts. Under /usr/src/bootscripts I have two directories, lfs and
blfs, which are nothing more than decompressed tarballs from LFS and
BLFS. rc.d and everyhing below is owned by this user... and that's it
really, just works as you might expect.
So - is this what you have in mind or am I missing something?
Kind regards.
PS: AFAIK it's very rare that some package tries to write to /etc/rc.d.
I have gnome running with print and sane servers, and still I have yet
to come across one.
--
David Ciecierski
Want control, education, and security from your operating system?
Hardened Linux From Scratch
http://www.linuxfromscratch.org/hlfs
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
