Skip to Content.
Sympa Menu

sm-grimoire-bugs - [SM-Grimoire-Bugs] [Bug 14238] mountnetwork, smgl-default-remote-fs, etc ordered according to broken principles. Corrections supplied.

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 14238] mountnetwork, smgl-default-remote-fs, etc ordered according to broken principles. Corrections supplied.
  • Date: 22 Jan 2008 18:11:09 -0000

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





------- Additional Comments From eekee57 AT fastmail.fm 2008-01-22 12:11 -------
Garrr! I typed up a beautiful reply and my browser went and segfaulted.

Okay, in brief:

It's an okay workaround for sysadmins to do as you describe above, however
that's no good for distribution due to the variety of network file systems Out
There.

My new idea:

net-tools: remove mountnetwork

nfs-utils: remove NEEDS=+remote_fs from nfs and nfslock. add
PROVIDES=nfs_mount
to both. make new init script: smgl-mount-nfs with NEEDS=+nfs_mount

coda-client: remove NEEDS=+remote_fs from venus, and add PROVIDES=coda_mount.
make new init script: smgl-mount-coda with NEEDS=+coda_mount.

coda-server: remove NEEDS=+remote_fs from auth2 codafs and update


Also... I just grepped for +remote_fs in grimoire/*/*/init.d/* and found that,
like, everything needs it, so the smgl-mount-* scripts above should provide
it,
and maybe we shouldn't get rid of smgl-default-remote-fs too. It would be far
better if we could specify weak dependencies to init though, the presence of
smgl-default-remote-fs is confusing.

--
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