Bug#3143: sysvinit init.d/network script buglet
Ian Jackson said:
> Miquel van Smoorenburg writes ("Bug#3143: sysvinit init.d/network script buglet"):
> ...
> > While on the subject, I think that marking these startup scripts as
> > config files is wrong. The configuration should be in seperate files,
> > for example in /etc/sysconf (or whatever).
>
> Marking just the scripts as conffiles and having them contain the
> configuration is OK for scripts which aren't edited by the postinst,
> though it's nicer to have flags the user can change in a separate
> file.
>
> Certainly all of the scripts in /etc should be marked as conffiles, so
> that the user can edit them if they want to. We should just avoid
> forcing most of them to do so.
It would be nice if things were set up like on many vendor unix boxes, with
startup scripts in /sbin/init.d/, and configuration files in /etc/rc.config.d/
or similar, with configuration file names corresponding to script names. That
way, the script doesn't have to be edited. Then, if a new script has new
configuration variables in it, the config file could be altered to contain the
new variables (disabled -- unless the postinst sets them up interactively).
--
Scott Barker
Linux Consultant
scott@galileo.cuug.ab.ca
http://www.cuug.ab.ca:8001/~barkers/ (under construction)
[ I try to reply to all e-mail within 5 days. If you don't ]
[ get a response by then, I probably didn't get your e-mail ]
[ (we have a sometimes sporadic connection to the internet) ]
"Science cannot stop while ethics catches up - and nobody should expect
scientists to do all the thinking for the country."
- Elvin Stackman
Reply to: