Skip to Content.
Sympa Menu

sm-grimoire-bugs - [SM-Grimoire-Bugs] [Bug 9636] Master bug - all init scripts should have a consistent naming scheme

sm-grimoire-bugs AT lists.ibiblio.org

Subject: SourceMage Grimoire Bug List

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-grimoire-bugs AT lists.ibiblio.org
  • Subject: [SM-Grimoire-Bugs] [Bug 9636] Master bug - all init scripts should have a consistent naming scheme
  • Date: Sun, 28 Aug 2005 13:20:33 -0700 (PDT)

http://bugs.sourcemage.org/show_bug.cgi?id=9636


jblosser-smgl AT firinn.org changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |jblosser-smgl AT firinn.org




------- Additional Comments From jblosser-smgl AT firinn.org 2005-08-28 13:20
-------
Why would we add a prefix to an init script name? The only effect I can see
that this has is making it more difficult for admins to find an init script,
since the name is guaranteed to not match what any other distribution has.

We have a standards doc that says that we use standard names for anything
found
in http://www.lanana.org/lsbreg/init/init.txt, and prefix any others with
smgl-, but frankly don't even understand why we add the smgl- to any of them.
Even if the scripts are home grown the services/daemons aren't, and from a
sysadmin perspective I don't care who wrote the init script, if I'm looking
for
it I'm looking for it by the name of the service or daemon it provides.
LANANA's argument is that all init scripts should use names from that list to
avoice conflicts, and that's somewhat valid, but I don't think the smgl-
prefix
buys us anything there that we wouldn't get just being careful to avoid
conflicts. Two spells with an smgl-foo script are going to conflict in any
case.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page