From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Distro discusion
Date: Mon, 25 Sep 2000 19:14:14 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0009251904360.6271-100000@localhost.localdomain> (raw)
In-Reply-To: <005501c0276a$faa7ee20$1e059ed8@wang>
Personally, the biggest thing that I believe is important on a
distribution is good documentation on where files are placed. Having said
that, I think it is past time for the distributions to discuss this and
commit to following a standard (or two). Certainly there will be
differences in such things as init scripts. After all Slackware uses a BSD
style init (more or less) while RedHat uses a SystemV ini (more or less).
There are advantages to both of them, and that isn't the point. The thing
is that RedHat does place some config files in strange places. If there
was one place to put a given file it would make Linux overall
stronger. There could still be room for each to do its thing for
improvement. (For instance once you say that all init scripts will reside
in rc.d you can choose to follow the redhat method of a directory for each
run level and one for the actual scripts. Or you could decide to place
them all in the /etc/rc.d dir.)
Actually, documentation is the biggest weakness I see in Linux. The fact
is that much of the documentation is great if you already know what your
doing. Some of it is great, and some is lousy. Sometimes knowing whre to
look though can be a major task in the first place. One master document
giving direction on where to look for all network functions would be
nice. One covering all disk subsystems would also go a long way.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Seek simplicity -- and distrust it.
Alfred North Whitehead
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
New user encountering problems Jerry Robinette
` Gorgotek Systems
` Kirk Wood
` Jacob Schmude
` Brent Harding
` Geoff Shang
` Brent Harding
` Jacob Schmude
` Kirk Wood
` Brent Harding
` Jacob Schmude
[not found] ` <Pine.LNX.4.21.0009231155110.1013-100000@localhost.localdom ain>
` Brent Harding
` Victor Tsaran
` Brent Harding
` Victor Tsaran
` Kerry Hoath
` Kirk Wood
` Victor Tsaran
` Kirk Wood [this message]
` Distro discusion Chris Nestrud
` Kirk Wood
` Gene Collins
` Victor Tsaran
` Jacob Schmude
` Brent Harding
` Victor Tsaran
` Brent Harding
` New user encountering problems Brent Harding
` HOWTOs (was Re: New user encountering problems) Jacob Schmude
` New user encountering problems Jacob Schmude
` William F. Acker WB2FLW +1-303-777-8123
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0009251904360.6271-100000@localhost.localdomain \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).