* Octave Orgeron <unixconsole at yahoo.com> [2006-12-13 20:42]:
> I think it's a great idea to seperate the GNU commands into /usr/gnu.
> This keeps the /usr/bin,/usr/sbin, etc. namespaces clean as they
> should be. And with simple $PATH additions it gives users and
> developers the flexibility they need. All of the coretuils should be
> located in the /usr/gnu namespace. The g-commands should be symlinked
> into /usr/bin for ease of use. But the other commands should stay in
> the /usr/gnu area.
Can you expand on why you think /usr/bin/seq (as an example) is a
negative development?
> It would be nice to see a wider clean up of the commands and tools.
> For example, JDS/Gnome should reside under /usr/gnome, which currently
> only holds the share components. Considering that Java, CDE, Openwin,
> Perl, and apache are seperated this way it makes sense. Here is a list
> of items that should be cleaned up:
>
> /usr/sfw -> /usr/{bin,sbin,lib, etc.}
This change will happen as various components are updated.
> JDS/Gnome -> /usr/gnome
> MySQL -> /usr/mysql
> Postgres -> /usr/postgres
Don't have knowledge (beyond Alan's reply) regarding these. Stefan
T's looking at MySQL again, so maybe he has thoughts. (But they're
all a tad off topic for the GNU cases...)
> Some things are a little more difficult to determine the placement of,
> such as net-snmp, webmin, samba, and swat. But programming languages,
> desktop environments, major application suites, databases, web, etc.
> should be seperated.
If you go back in the various "Proposing /usr/gnu" threads in
tools-discuss, you'll see some commentary that components should be
easier to find. There are ways to have a balance of clean separation
with initial "entry binaries" in the default path (like /usr/perl5),
but they do appear different than other Unix-like OSes' implementation
choices...
- Stephen
--
Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems
stephen.hahn at sun.com http://blogs.sun.com/sch/
