On Tue, 29 Aug 2006 01:52:22 +0200, Andy Feldman <[EMAIL PROTECTED]>
wrote:
On 8/28/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
Having a standard place where media mounts is a good thing, so that
users
know where to look and such things can be integrated in gui, like
placing
icons on desktop or similar. I really don't know where such directory
should be called or placed in GoboLinux, but I use /Mount for that.
I also use /Mount... isn't that the default location for the automatic
mount points after a Gobo install? It's not *just* removable media I
guess, but it does include it.
Same goes for files used by servers such as Apache and Subversion.
Perhaps
defining what /Files or /Depot are used for could help here. As it is
now
they aren't well defined imo. I use /Files for such, on my server.
Having
this defined would also help recipe creation, making it possible to
provide stub configuration files, that actually works out of the box,
and
that the users can find the newly installed files, i.e. apaches default
htdocs.
As I understood it, /Files is used for system files (i.e. -- the user
won't have any direct interaction with them, but it will be used by
system tools).
That's how I've understood it as well and that's what I think of apache
server root, SVN repositories etc to be. The user never directly interact
with those files but uses some sort of client to get them (web browser,
svn client etc). Sometimes one might want to edit the htdocs in webroot,
but that's no users job but the webmaster's job.
Actually even the users htdos lies under /Files, but the users interact
with them through a symlink in their home directory. This has two reasons.
First the user can set whatever permissions on their directory, without
have to worry that the webserver can read their htdocs and secondly (and
most important) this is a preparation for having the home directory
encrypted. If the user is not logged on the encrypted file system isn't
mounted and the webserver can't read the htdocs. Actually the users htdocs
could be under /Depot as well, but thinking of them as they are served by
apache and having them with the other htdocs felt natural.
/Depot is for the user to actually put files.
My /Files:
Codecs, Compile, Descriptions, Documentation, Fonts, Fortunes,
Plugins. I have very little cause to manually enter any of those
directories. Codecs, for example, is populated (if I choose) during a
Compile of MPlayer. Any changes to Fonts and the various other things
could be considered system configuration.
I have got the same structure as you, but on my server I also got WWW,
SVN, MySQL and Trac.
My /Depot:
Backups, Docs, Downloads, Packages, WWW, Wallpapers. WWW, Docs and
Packages were there by default, and Packages especially I don't
interact with so I would choose to put it in /Files by default. The
other directories contain my files that don't fit naturally in my
/Users dir, because they aren't associated with my user account. (This
is a single-owner computer, so I don't need to separate for example my
backups from anyone else's.)
I don't have WWW or backup here, but instead I have Media, which contains
my music and film.
You're right that it is not easy to tell which of those would host
Apache-type files (although currently it is /Depot by default).
I think that /Files should be default, as I said above, the users never
directly interact with the htdocs.
Other stuff:
"A package to be installed in /opt must locate its static files in a
separate /opt/<package> or /opt/<provider> directory tree, where
<package> is a name that describes the software package [...]."
Describe /Programs alright. The only difference is they seem to assume
only a single level of folders for /opt/<package>/bin.
Yes, that describes /Programs alright. But then, to have it the "correct"
way could be to have an /opt directory, like /usr is now, and that
symlinks with the name and version are created to point to the
corresponding program, i.e. /opt/HTTPD-2.0.59 -> /Programs/HTTPD/2.0.59,
just to have the single level directories in /opt. This is not even a
suggestion but just an idea on how it could be "solved".
Other directories like /boot and /mnt seem like a good idea to me.
/mnt points to /Mount/Temp ("for a temporarily mounted filesystem"),
and /boot to /S/K/B. /srv points to wherever the WWW directory resides
by default (currenty /Depot, although if /srv pointing to /Depot seems
nonsensical I would argue that it's WWW which should move.) /etc/opt
points to /etc, /home points to /Users... And it doesn't make a
difference to native Gobo users if it's hidden.
Agree with you fully on all this, and I really like the idea of
/Mount/Temp for temporarly mounts instead of having them directly in
/Mounts, with an addition: /root should point to /Users/<superuser name>
(I have actually installed a program requiring the existance of /root).
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
