From Fedora Project Wiki
m (1 revision(s)) |
m (PackagingDrafts/InitDir moved to Archive:PackagingDrafts/InitDir: (no revisions since import from MoinMoin May 2008) Appears to already be applied to Packaging:SysVInitScript) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
In the past, some packages were putting files in /etc/init.d as well as /etc/rc.d/init.d. Without requiring a specific location, it makes it more difficult to use yum install against the initscript filename and path. Since /etc/init.d is the symlink (and because the Filesystem Hierarchy Standard does not mandate a location), the full directory is required. | In the past, some packages were putting files in /etc/init.d as well as /etc/rc.d/init.d. Without requiring a specific location, it makes it more difficult to use yum install against the initscript filename and path. Since /etc/init.d is the symlink (and because the Filesystem Hierarchy Standard does not mandate a location), the full directory is required. | ||
[[Category:Archived packaging guideline drafts]] | |||
Latest revision as of 21:05, 21 February 2009
Packages with initscripts must put any initscripts into /etc/rc.d/init.d.
In the past, some packages were putting files in /etc/init.d as well as /etc/rc.d/init.d. Without requiring a specific location, it makes it more difficult to use yum install against the initscript filename and path. Since /etc/init.d is the symlink (and because the Filesystem Hierarchy Standard does not mandate a location), the full directory is required.