From: aps@ieee.org (Armando Stettner)
Subject: [TUHS] history of sbin?
Date: Thu, 31 Jan 2013 22:24:02 -0500 [thread overview]
Message-ID: <DC8B1F73-C48F-4A0E-A8FC-866FC611908C@ieee.org> (raw)
In-Reply-To: <B42FA21C-5386-4CD3-ACB0-6D6F46AF886C@ieee.org>
I stand corrected: UNIX-wizards....
Thanks, Ron. :)
Begin forwarded message:
> From: Armando Stettner <aps at ieee.org>
> Subject: Re: [TUHS] history of sbin?
> Date: January 31, 2013 9:02:06 PM EST
> To: "ramble1035 @dslextreme.com" <ramble1035 at dslextreme.com>
> Cc: tuhs at tuhs.org
>
> This all reminds me of UNIX-gurus on Usenet.... :)
>
> decvax!aps
>
>
> Begin forwarded message:
>
>> From: "ramble1035 @dslextreme.com" <ramble1035 at dslextreme.com>
>> Subject: Re: [TUHS] history of sbin?
>> Date: January 31, 2013 8:53:16 PM EST
>> To: tuhs at tuhs.org
>>
>> Based on some vague recollections of early days at Sun... I seem to recall that one of the main differences between /bin and /sbin was that the /sbin binaries were all built with static libraries rather than shared. I heard /sbin described as "single-user bin"...
>>
>> I don't know when /sbin first appeared, though.
>>
>> -- Chris
>>
>>
>> On Thu, Jan 31, 2013 at 5:41 PM, Warren Toomey <wkt at tuhs.org> wrote:
>> On Thu, Jan 31, 2013 at 06:06:15PM -0600, Jeremy C. Reed wrote:
>> > http://lists.busybox.net/pipermail/busybox/2010-December/074114.html
>>
>> A few inaccuracies:
>>
>> When the operating system grew too big to fit on the first RK05 disk
>> pack (their root filesystem) they let it leak into the second one,
>> which is where all the user home directories lived (which is why
>> the mount was called /usr). They replicated all the OS directories
>> under there (/bin, /sbin, /lib, /tmp...) and wrote files to those
>> new directories because their original disk was out of space.
>> When they got a third disk, they mounted it on /home and relocated
>> all the user directories to there so the OS could consume all the
>> space on both disks and grow to THREE WHOLE MEGABYTES (ooooh!).
>>
>> Research Unix never had /sbin nor /home, and the tale of the third disk
>> doesn't ring any bells to me.
>>
>> 7th Edition has /usr/dmr and /usr/ken, not /home/dmr nor /usr/home/dmr :)
>>
>> Cheers,
>> Warren
>> _______________________________________________
>> TUHS mailing list
>> TUHS at minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
>>
>> _______________________________________________
>> TUHS mailing list
>> TUHS at minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20130131/0aed610f/attachment.html>
next prev parent reply other threads:[~2013-02-01 3:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 0:06 Jeremy C. Reed
2013-02-01 1:28 ` Random832
2013-02-01 1:37 ` Warner Losh
2013-02-01 1:41 ` Warren Toomey
2013-02-01 1:53 ` ramble1035 @dslextreme.com
2013-02-01 2:01 ` Larry McVoy
2013-02-01 2:02 ` Armando Stettner
2013-02-01 3:09 ` Larry McVoy
2013-02-01 3:24 ` Armando Stettner [this message]
2013-02-01 2:03 ` [TUHS] 1974 CACM Paper, was " Warren Toomey
2013-02-01 2:14 ` Warren Toomey
2013-02-01 2:34 ` [TUHS] 1974 CACM Paper Warren Toomey
2013-02-01 2:54 ` [TUHS] history of sbin? Warren Toomey
2013-02-01 4:58 Norman Wilson
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=DC8B1F73-C48F-4A0E-A8FC-866FC611908C@ieee.org \
--to=aps@ieee.org \
/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).