> http://www.osnews.com/story/25556/Understanding_the_bin_sbin_usr_bin_usr_sb…
Cute, but most of the history is wrong.
The distinction between /bin and /usr/bin is true - / held the things
need to boot the system. Other things were on /usr.
The Berkeley guys did NOT invent shared libraries. Shared libraries as
we know them came originally from Sun, on SunOS 4.x for sure, possibly
on SunOS 3.x. (Larry?) Many commercial vendors adopted the design (Ultrix,
I think, and maybe others) and finally around 4.4 they found their way into
"pure" BSD.
/home and /opt came into the picture circa 1989 with SVR4 when Berkeley,
AT&T and Sun (and maybe a few others?) got together to standardize the
layout and make diskless booting possbile and reasonable with NFS sharing
of home directories. /sbin & /usr/sbin came into the picture at this
point also, to hold executables that until then had lived in /etc. The
idea was that /etc should only have per-machine configuration files.
The general point of the article and of some of the postings, that the
proliferation doesn't make a lot of sense today, is well taken. The
Bell Labs guys themselves recognized this when they did Plan 9.
The problem is even worse on 64 bit Linux systems, which can handle
two different architectures. /lib and /lib64 confuse a lot of the
older 'configure' programs.
Personally, I hate reading articles by "experts" where 85% of the facts
are wrong. I lived through all of it, and I know better... :-)
Arnold
I've received a link http://manpages.bsd.lv/history.html claiming to
be about man pages; in fact, it's a lot more than that, including the
prehistory of troff. Interesting stuff.
Greg
--
Sent from my desktop computer
Finger grog(a)FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
Hi. I announced this in comp.lang.awk in December and tried to BCC
the TUHS list but it didn't seem to happen. Here's the announcement
I posted.
Arnold
-----------------------------------------------
From: arnold(a)skeeve.com (Aharon Robbins)
Newsgroups: comp.lang.awk
Subject: AWKCC source now available
Date: Fri, 16 Dec 2011 12:27:39 +0000 (UTC)
Message-ID: <jcfdfr$qt9$1(a)dont-email.me>
[ BCC to TUHS list, Brian Kernighan & Chris Ramming ]
awk 'BEGIN { print "Sherman, set the wayback machine for 1988" }'
Hello All.
This note is to announce that through the valiant efforts of Brian Kernighan,
Alcatel-Lucent has been persuaded to make the source for awkcc available.
It can be found at:
https://open-innovation.alcatel-lucent.com/projects/awkcc
You have to register (no cost) before being able to download, but
it's easy. The license terms are at the site. It's a straightforward
"for personal use" kind of license.
For those who don't know, awkcc is an adaptation of Unix awk to translate
nawk programs into C. It was originally implemented by Chris Ramming (then
at Bell Labs, although no longer) circa 1988, and the source dist includes
some doc that Chris wrote.
Given how fast machines are these days, this program is mostly of
historical interest. But it's nice to have this bit of Unix / awk history
generally available. And, if you really need to turn an awk program into
C, this may provide a starting point.
Enjoy!
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
P.O. Box 354 Home Phone: +972 8 979-0381
Nof Ayalon Cell Phone: +972 50 729-7545
D.N. Shimshon 99785 ISRAEL
Hi All.
I announceced this some years ago but it's been renewed, so I'll announce
it again.
In 2004 sometime I downloaded all the comp.sources stuff I could from
uunet.uu.net, which was still making it available for anonymous ftp.
I've made a tarball of it available from http://www.skeeve.com/Usenet.tar.bz2
Warren, if you don't have this in the TUHS archives, maybe you could add it?
Thanks,
Arnold
Hi,
For those who want to refresh old memories.
Hans Bezemer has made big progress as far as performance of qemu is
concerned. His specific experience concerns Coherent, but other old
unixes could use it.
Details can be found in comp.os.coherent news group
http://groups.google.com/group/comp.os.coherent/topics
The older tuhs message can be mentioned :
http://minnie.tuhs.org/pipermail/tuhs/2008-July/001815.html
I have also noticed , that Coherent boots well and is very fast in
newest virtualbox 4.1.8, running in XP.
Dell Optiplex 755 was used with Core 2 Duo.
Details can be found in forums for "Other quests"
http://www.virtualbox.org
It suggests , that other old Unixes could benefit in new virtualbox.
Regards
Andrzej
A long time ago at the University that I graduated from. . .
Shell scripts had just added the ability to have functions in them, so I wrote a script to do some processing of files that I had, and then logged off to let it run in the background.
The shell script was named 'A'.
In the script was a function, named 'A'
When the script ran, instead of calling 'A' the function, it called 'A' the script, and you can see where this goes from here.
2 days later I received an email from the admin (thankfully a friend) who enclosed the 'ps -axl' output from the machine. It showed thousands of copies of my script running and a load that indicated that the machine was useless for almost everything.
With the admonishment: "Don't ever do this again."
I haven't.
David
David Barto
barto(a)kdbarto.org
barto(a)ucsd.edu
On Mon, Dec 26, 2011 at 8:15 PM, Dave Horsfall <dave(a)horsfall.org> wrote:
> On Tue, 27 Dec 2011, Warren Toomey wrote:
>> Yes, a good reminder on the power that programming brings us. A question
>> though: what command would "bring the system down"?
>
> It's right here: "Programmers were free to poke around to see and directly
> manipulate what was in the computer's memory."
http://minnie.tuhs.org/pipermail/unix-jun72/2008-May/000250.html
> -- Dave
--
Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
Hi,
I wonder if someone has an early version of top lying around? I'd
like to try getting it to work on my ZEUS clone. I'd start with
1.0 from 1984 if possible ;)
Regards, Oliver