From: pepe@naleco.com (Pepe)
Subject: [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split
Date: Sat, 4 Feb 2012 20:34:17 +0100 [thread overview]
Message-ID: <000901cce373$fc2e2ad0$50651bac@naleco.com> (raw)
"Jose R. Valverde" <jrvalverde at cnb.csic.es> said:
> Beyond that, the original articles and comments complained also about
> directory naming (/bin /etc /lib) as "unintuitive". I fail to
> understand in
> what way is it easier for someone new to a computer to learn a "/bin
> /etc /var /lib" alien terminology and what it means, than to learn
> "System Config Libraries
> etc..." or "Windows Windows32 Windows64 Temp Users and Settings,
> etc..."
In SCO Xenix/UNIX, the home directory is usually mounted on /u.
I was amused the first time I saw it.
next reply other threads:[~2012-02-04 19:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 19:34 Pepe [this message]
2012-02-04 21:05 ` Lyndon Nerenberg
-- strict thread matches above, loose matches on Subject: below --
2012-02-05 8:38 Hendrik Jan Thomassen
2012-02-05 10:13 ` Jaap Akkerhuis
2012-02-05 17:15 ` Warner Losh
2012-02-02 23:16 Norman Wilson
2012-02-02 23:37 ` Carl Lowenstein
2012-02-02 23:58 ` John Cowan
2012-02-01 9:26 arnold
2012-02-02 13:35 ` Tim Bradshaw
2012-02-02 13:49 ` Larry McVoy
2012-01-31 19:16 A. P. Garcia
2012-01-31 19:27 ` Warner Losh
2012-02-01 11:12 ` Jose R. Valverde
2012-02-01 17:35 ` Warner Losh
2012-02-02 13:32 ` Random832
2012-02-02 17:24 ` Warner Losh
2012-02-02 17:36 ` John Cowan
2012-02-02 18:10 ` Warner Losh
2012-02-02 21:14 ` Dave Horsfall
2012-02-02 21:49 ` Warner Losh
2012-02-02 22:29 ` Tim Newsham
2012-02-02 22:47 ` Warner Losh
2012-02-02 22:59 ` Lyndon Nerenberg
2012-02-02 23:33 ` Warner Losh
2012-02-02 22:53 ` Lyndon Nerenberg
2012-02-02 23:35 ` Warner Losh
2012-02-03 11:10 ` Tim Bradshaw
2012-02-03 15:22 ` Jose R. Valverde
2012-02-03 16:06 ` Ronald Natalie
2012-02-03 16:09 ` Steve Nickolas
2012-02-02 17:40 ` Warner Losh
2012-02-02 18:02 ` Tim Newsham
2012-02-02 13:45 ` Tim Bradshaw
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='000901cce373$fc2e2ad0$50651bac@naleco.com' \
--to=pepe@naleco.com \
/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 NNTP newsgroup(s).