[Bug 446653] Review Request: coda - Coda distributed file system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: coda - Coda distributed file system


https://bugzilla.redhat.com/show_bug.cgi?id=446653





------- Additional Comments From adam@xxxxxxxxxxxxx  2008-05-19 10:34 EST -------
(In reply to comment #7)
> I've already solved this by creating /coda if it doesn't exit in %post, and
> owning it through %ghost. This IMHO is better, because even a coda-filesystem
> package might need an update one day, and then you still have a problem.

Ok, that sounds good.

> 
> >  * Use coda-client as the service name for the client, this is more intuitive
> > and follows how the Debian packages are.
> > 
> 
> This deviates from upstream, and makes it harder to use things like the coda
> howto and other documents together with the packages.

This is true, but isn't /usr/coda really ugly? Also, when I say "Debian
packages", I don't mean official packages (there aren't any), but the Debian
packages that upstream makes for download. If you look at debian/ in the
standard tarball, you will see the initscript and other files that use the
FHS-style paths and the "coda-client" named service.

More importantly, Coda predates Linux and the FHS. The config file allows for
the customization of directories to fit a particular system. The defaults are
generic, and not really correct for a modern Linux system. The defaults given in
the debian directory should be closer to what a Linux system today should have.

> 
> >  * Split out gcodacon
> 
> Why?
> 

This is optional, but useful for avoiding dependences on Gtk.

> >  * Ship a venus.conf that sets the coda directories to places in /var/log,
> > /var/run, etc
> 
> I've moved the entire venus cache, logs etc to /var/lib/coda by adding a
> /usr/coda symlink which points to /var/lib/coda
> 

See above. I don't think /usr/coda should exist on Fedora. /coda is bad enough!
(But unavoidable.)


> > Something needed but have not done yet:
> >  * Add /etc/udev/makedev.d/99-coda.nodes with contents "cfs0"
> 
> This is not necessary the venus initscript loads the coda kernel module and then
> the nodes get created automatically by udev

This is a race condition, yes? Or are you calling udev-settle? makedev.d avoids
the race condition, and is what fuse does (which is similar to coda in some ways).

> 
> p.s.
> 
> As you may have seen I've written new sysv style initscript scripts for these
> packages which fully follow the Fedora / RH initscript conventions. I would like
> to share these with upstream, what would be the best place to submit these?
> 

http://www.coda.cs.cmu.edu/trac

Pull from git and file some tickets!

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

_______________________________________________
Fedora-package-review mailing list
Fedora-package-review@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-package-review

[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]