On Thu, Oct 15, 2009 at 7:16 AM, Michael T <[email protected]> wrote: > > Hello, > > Something that has always annoyed me about traditional init was the fact that > the scripts are kept under /etc, although nowadays they are almost never user > configuration files in the sense that they used to be, but scripts which come > with a package and are not intended to be changed by the user. Have you > considered changing this in upstart, and having package scripts go under, > say, /lib/init, with /etc/init only there for users to override defaults on a > case-by-case basis, if they so desire? > > This would also play nicer with dpkg's special handling of files which live > under /etc.
This seems like a replay of a previous email... The suggestion you're making makes absolutely no sense from a traditional Unix layout -- 99% of the time /lib and /usr/lib are reserved for system-provided shared and static _binary_ libraries [1]; jobfiles and upstart configuration files should continue to live in /etc in my opinion because these are configuration files and they shouldn't be changed unless the administrator has a particular use that necessitates the change. Thanks, -Garrett [1] The only contradiction I can think of to this paradigm at the moment is perl's and python standard libraries and site package directories, etc's modules. -- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
