[TUHS] User maintained programs in the Second Edition

[TUHS] User maintained programs in the Second Edition

[Doug McIlroy]

> Does anyone remember whether at the time these were installed in the
> system-wide /bin directory,

Those that I remember were in /usr/bin. 

Doug

[TUHS] User maintained programs in the Second Edition

[Diomidis Spinellis]

On 23/12/2016 04:28, Doug McIlroy wrote:
 >> Does anyone remember whether at the time these were installed in the
 >> system-wide /bin directory,
 >
 > Those that I remember were in /usr/bin.

So was "/usr/bin" initially only for user-contributed binaries, or was 
it from its inception a place for binaries that were not essential for 
system boot and could not fit in the root partition?

The second reason is the one that is popularly documented e.g.:

http://lists.busybox.net/pipermail/busybox/2010-December/074114.html
http://askubuntu.com/questions/130186/what-is-the-rationale-for-the-usr-directory

[TUHS] User maintained programs in the Second Edition

[Joerg Schilling]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

Diomidis Spinellis <dds at aueb.gr> wrote:

> On 23/12/2016 04:28, Doug McIlroy wrote:
>  >> Does anyone remember whether at the time these were installed in the
>  >> system-wide /bin directory,
>  >
>  > Those that I remember were in /usr/bin.
>
> So was "/usr/bin" initially only for user-contributed binaries, or was 
> it from its inception a place for binaries that were not essential for 
> system boot and could not fit in the root partition?

From the talk from Stephen Bourne around 1990 at the Sun User Group meeting, 
/usr/bin started with user contributed binaries only.

Later the directory was aquired by the system after many of the user 
contributed programs have been integrated into UNIX.

At that time people started to use /usr/local and in order to interrupt this 
chain of bad naming, /opt/<vendor>/bin has been introduced.

Jörg

-- 
 EMail:joerg at schily.net                  (home) Jörg Schilling D-13353 Berlin
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/

[TUHS] User maintained programs in the Second Edition

[Clem Cole]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2316 bytes --]

below...

On Fri, Dec 23, 2016 at 5:27 AM, Joerg Schilling <schily at schily.net> wrote:

> Diomidis Spinellis <dds at aueb.gr> wrote:
>
> > On 23/12/2016 04:28, Doug McIlroy wrote:
> >  >> Does anyone remember whether at the time these were installed in the
> >  >> system-wide /bin directory,
> >  >
> >  > Those that I remember were in /usr/bin.
> >
> > So was "/usr/bin" initially only for user-contributed binaries, or was
> > it from its inception a place for binaries that were not essential for
> > system boot and could not fit in the root partition?
>
> From the talk from Stephen Bourne around 1990 at the Sun User Group
> meeting,
> /usr/bin started with user contributed binaries only.
>
> Later the directory was aquired by the system after many of the user
> contributed programs have been integrated into UNIX.

​Right - that follows what I had been told.   So /usr/local (for locally
compiled) and /usr/ucb (to differentiate from Research programs) were
introduced, which worked when UNIX was a source release.​

​Many makefiles in USENIX tapes use the /usr/local convention for new
programs but it failed to deal with binary distributions from ISV's ​




>
>
> At that time people started to use /usr/local and in order to interrupt
> this
> chain of bad naming, /opt/<vendor>/bin has been introduced.

​Almost right --- This was one of the things the /usr/group gave us.   IIRC
it was Heinz Lyclamia that proposed it BTW.   Before IEEE P1003 (aka POSIX)
the burgeoning industry folks started to talk about how to deal with the
plethora of almost, but not quite the same UNIX flavors.   The 1985
/usr/group API was the result (which would begat POSIX but that's a
different story).

Heinz was the pushing an ABI not an API.   He was sure UNIX would never be
able to compete with VMS or the like and get ISV's to the table without
one.  Two of the things he insisted that we consider was where to install
vendors code and /usr/opt/vendor was born (** /opt would come later **)​.
It was put in /usr because symlink did not yet exist AND people agreed that
the root file system should be as small as possible.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20161223/06ce5618/attachment-0001.html>

[TUHS] User maintained programs in the Second Edition

[Diomidis Spinellis]

The Second Edition manual has a section titled "User Maintained 
Programs" listing the following utilities and games: basic, bc, bj, cal, 
chash, cre, das, dli, dpt, moo, ptx, tmg, and ttt.  In the Introduction, 
the reader is asked to consult their authors for more information.

Does anyone remember whether at the time these were installed in the 
system-wide /bin directory, or whether they were only available in their 
owners' home directories?

[TUHS] User maintained programs in the Second Edition

[Joerg Schilling]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

Diomidis Spinellis <dds at aueb.gr> wrote:

> Does anyone remember whether at the time these were installed in the 
> system-wide /bin directory, or whether they were only available in their 
> owners' home directories?

From what I remember from a talk from Stephen Bourne at a Sun user group 
meeting in 1990, user maintained programs have been installed in /usr/bin.

Stephen Bourne after some time wrote a cron job that checked whether an update
in a binary also resulted in an updated man page and otherwise removed the 
binary. This is why these programs have man pages.

Jörg

-- 
 EMail:joerg at schily.net                  (home) Jörg Schilling D-13353 Berlin
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/

[TUHS] User maintained programs in the Second Edition

[SPC]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]

2016-12-22 10:22 GMT+01:00 Joerg Schilling <schily at schily.net>:
> Diomidis Spinellis <dds at aueb.gr> wrote:
>
>> Does anyone remember whether at the time these were installed in the
>> system-wide /bin directory, or whether they were only available in their
>> owners' home directories?
>
> From what I remember from a talk from Stephen Bourne at a Sun user group
> meeting in 1990, user maintained programs have been installed in /usr/bin.
>
> Stephen Bourne after some time wrote a cron job that checked whether an update
> in a binary also resulted in an updated man page and otherwise removed the
> binary. This is why these programs have man pages.
>
> Jörg
>
> --
>  EMail:joerg at schily.net                  (home) Jörg Schilling D-13353 Berlin
>        joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
>  URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/

Impressive. Everything has a reason, that's clear. A primitive but
more or less effective security measure for new software installations
:-)

Gracias | Regards - Saludos | Greetings | Freundliche Grüße | Salutations

--
Sergio Pedraja
--
twitter: @sergio_pedraja | skype: Sergio Pedraja
--
http://plus.google.com/u/0/101292256663392735405
http://www.linkedin.com/in/sergiopedraja
http://spedraja.wordpress.com
-----
No crea todo lo que ve, ni crea que está viéndolo todo
-----
"El estado de una Copia de Seguridad es desconocido
hasta que intentas restaurarla" (- nixCraft)

[TUHS] User maintained programs in the Second Edition

[Dave Horsfall]

On Thu, 22 Dec 2016, Joerg Schilling wrote:

> Stephen Bourne after some time wrote a cron job that checked whether an 
> update in a binary also resulted in an updated man page and otherwise 
> removed the binary. This is why these programs have man pages.

An effective way of enforcing compliance :-)  I like it.

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."