Re: [SLE] < RANT > *5
From: plain (kanenas_at_hawaii.rr.com)
Date: 02/19/04
- Previous message: Sid Boyce: "Re: [SLE] Reiser4"
- In reply to: Trey Gruel: "Re: [SLE] < RANT > *5"
- Next in thread: David Barnes: "Re: [SLE] < RANT > *5"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: suse-linux-e@suse.com Date: Wed, 18 Feb 2004 21:39:17 -1000
On Wednesday 18 February 2004 11:43, Trey Gruel wrote:
> On Wed, 18 Feb 2004, Steven T. Hatton wrote:
> > On Wednesday 18 February 2004 03:42 pm, Paul Cooke wrote:
> > > and that's where it's /supposed/ to go... /local/ to your system. If
> > > you want it otherwise, then you've got to go and edit the resources to
> > > point to usr/ share instead.
> >
> > To be pedantic, it means local to your site. Typically stuff that would
> > be shared by several systems on a local network, more or less. I'm
> > several revs back on this. And haven't looked at it in years, so things
> > may have changed. But this is the gospel of /supposed to/ for Linux file
> > systems.
> >
> > The way I read the document years ago, suff such as the KDE is in the
> > correct place on a SuSE box. Gnu wants to put everything in usr/local.
> > Which isn't all that problematic because SuSE leaves that pretty much
> > alone. IIRC, /usr/share is actually for apps shared on the box, not the
> > network, but I would have to review to be sure.
>
> i've used plenty of systems where the entire /usr tree (not including the
> /usr/local subtree which was usually empty anyway) was mounted from a
> remote machine via nfs. on most of them, everything not required to be
> local was an nfs mount.
>
> as it stands now, i install anything i compile from source in /usr/local
> which i have as a separate partition so i can upgrade my distro without
> worrying that it might overwrite something i installed myself.
>
> i'm glad that suse puts /opt to good use keeping major components like kde
> and gnome separate from the rest of the system so /usr/bin doesn't become
> the overcrowded nightmare it is in redhat.
>
> --
> trey
Every time my 15 year old tried to goof off by inventing yet another way to do
one of his chores, he was met with the simple truth that, the mundane things
in life would be better off if they remained mundane. The same advice should
be given to all open software developrs. While it is true that the originator
of this thread was -as he himself plainly said- "ranting", there is still a
lesson or two to be learned by this "ranting". Lesson one should be the
realization that it is a ridiculocity to a: have each app choose an arbitrary
file installation path AND b: lack the simple capacity to deal with stuff
installed in not the expected path. these two issues alone probably account
for a third or more of NEWBIE problems. Another third or so of the NEWBIE
problems lie with the "comprehensive" incomprehensiveness of "full"
distributions like SuSE. A very simple example of that is the almost total
failure of yast in installing a samba printer! Just going "by the book" in
the system i am writing this post from, has resulted in a setup under which
my SuSE 9.0 can see the windoze machine where the printer is installed, alas,
it will not print there. The maddening thing is that, after installation of
an xp and a windoze 2k virtual machine in my vmware 4.0 (want a story on that
too?, i got one!), BOTH doze vm's can see not only my SuSE system, but by
going "through" it they reach the xp machine with the printer AND the printer
installed in the xp machine!!!! BUT NOT MY NATIVE SuSE 9.0 OS!!!! All
advertising and all indications of Yast had made it clear that the printer
"was" available! Well, it was *not*! It took quite a bit of work and a bunch
of "cryptic" (for a NEWBIE) commands as root to correct the situation! If
SuSE can not find that printer as simply as 'windoze", then it should not
advertise that it can...
It is less than a third of the issues that a NEWBIE comes up against that
should require help from a wonderful forum like this. Unfortunately, in a day
or two, there will be yet another samba printer or sound thread. Yes, i got
them both working thanks to this forum, however, if linux is to mount any
sort of a threat to ms, i should not have had to use this forum, packman,
mplayerhq.hu (nice and complete mplayer setup) and so on for some of the
really basic stuff.
AGAIN, PLEASE NOTE, i am talking about NEWBIES...
and, unfortunately, I am asking open software developers to keep it simple,
concistent and flexible with the inconcistensies of others.
As much as some dislike that species, if it is going to happen, it is the
NEWBIES who will make linux grand.
imitris
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
- Previous message: Sid Boyce: "Re: [SLE] Reiser4"
- In reply to: Trey Gruel: "Re: [SLE] < RANT > *5"
- Next in thread: David Barnes: "Re: [SLE] < RANT > *5"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
