TUHS February 2012

tuhs@tuhs.org

23 participants
13 discussions

by norman＠nose.cita.utoronto.ca

I've assembled some notes from old manuals and other sources on the formats used for on-disk file systems through the Seventh Edition: http://www.cita.utoronto.ca/~norman/old-unix/old-fs.html Additional notes, comments on style, and whatnot are welcome. (It may be sensible to send anything in the last two categories directly to me, rather than to the whole list.)

1 year, 6 months

32V, 3BSD and 4.0BSD on VAX-11/780

by nao

Hi, I successfully made SIMH VAX-11/780 emulator run 32V, 3BSD and 4.0BSD. Details are on my web site (thogh rather tarse): http://zazie.tom-yam.or.jp/starunix/ Enjoy! Naoki Hamada nao(a)tom-yam.or.jp

7 years, 10 months

Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split

by A. P. Garcia

http://www.osnews.com/story/25556/Understanding_the_bin_sbin_usr_bin_usr_sb…

11 years, 8 months

Re: [TUHS] why the leading under score added to function names?

by arnold＠skeeve.com

Hi All. This is interesting. It shows that (apparently) early on, assembler was viewed as the primary programming language. It also shows the consequences a small, apparently local decision can have: here we are 40+ years later and GCC on Windows is still preprending underscores to function names! In 15 minutes I helped the guy at work solve a problem he'd been working on for two days! Thanks everyone, Arnold > From: Brantley Coile <brantley(a)coraid.com> > To: Dave Horsfall <dave(a)horsfall.org> > Date: Mon, 20 Feb 2012 18:34:26 -0600 > Cc: The Eunuchs Hysterical Society <tuhs(a)tuhs.org> > Subject: Re: [TUHS] why the leading under score added to function names? > > correct. we could link to assembler code with _entry points and not i> worry about symbol collisions in the rest of the code. > > iPhone email > > On Feb 20, 2012, at 6:23 PM, "Dave Horsfall" <dave(a)horsfall.org> wrote: > > > On Mon, 20 Feb 2012, arnold(a)skeeve.com wrote: > > > > [...] > > > >> I'm pretty sure this dates back to PDP-11 days. I'm wondering "why?". > >> Why did the C compiler prepend an underscore to function names? > > > > Sure was the PDP-11 :-) I vaguely recall that it was to make sure that > > user functions did not conflict with predefined assembler functions, as > > that would be a pain to diagnose (much like having swap overlap root). > > > > -- Dave

11 years, 9 months

[Unix-jun72] Invitación a conectarnos en LinkedIn

by Sergio Pedraja

LinkedIn ------------ Me gustaría añadirte a mi red profesional en LinkedIn. -Sergio Sergio Pedraja IT Security Administrator / Information Security Manager en Savings Bank Santander y alrededores, España Confirma que conoces a Sergio Pedraja: https://www.linkedin.com/e/-p9hg1j-gyzit23b-16/isd/6035310103/YCHqBtRa/?hs=… -- Estás recibiendo invitaciones a conectar. Haz clic para darte de baja: http://www.linkedin.com/e/-p9hg1j-gyzit23b-16/pQvcBySBaffs0LLhMMtx8DQb3x_CT… (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, EE.UU.

11 years, 9 months

Invitación a conectarnos en LinkedIn

by Sergio Pedraja

LinkedIn ------------ Me gustaría añadirte a mi red profesional en LinkedIn. -Sergio Sergio Pedraja IT Security Administrator / Information Security Manager en Savings Bank Santander y alrededores, España Confirma que conoces a Sergio Pedraja: https://www.linkedin.com/e/-amg4ei-gyzit20d-4/isd/6035310080/f1t_FAOT/?hs=f… -- Estás recibiendo invitaciones a conectar. Haz clic para darte de baja: http://www.linkedin.com/e/-amg4ei-gyzit20d-4/IES2kw2WbAK2tgMLcf1q-MI/goo/tu… (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, EE.UU.

11 years, 9 months

Invitación a conectarnos en LinkedIn

by Sergio Pedraja

LinkedIn ------------ Me gustaría añadirte a mi red profesional en LinkedIn. -Sergio Sergio Pedraja IT Security Administrator / Information Security Manager en Savings Bank Santander y alrededores, España Confirma que conoces a Sergio Pedraja: https://www.linkedin.com/e/-9arw1o-gyzisxbk-15/isd/6035309375/9Ym-js9F/?hs=… -- Estás recibiendo invitaciones a conectar. Haz clic para darte de baja: http://www.linkedin.com/e/-9arw1o-gyzisxbk-15/_SZkCeK7HqzqROuy9YxIdtKYnud5R… (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, EE.UU.

11 years, 9 months

why the leading under score added to function names?

by arnold＠skeeve.com

Hi All. Recently at work I helped someone figure out that when working with ld, the name of a function "foo" gets turned into "_foo" by the compiler. (It took this old-timer 15 minutes to solve a problem he had been working on for two days!) I'm pretty sure this dates back to PDP-11 days. I'm wondering "why?". Why did the C compiler prepend an underscore to function names? Thanks, Arnold

11 years, 9 months

Yet Another Kernel Description Document

by Warren Toomey

All, I've just received from Poul-Henning Kamp a document entitled "UNIX Program Description", dated January 1976 and written by the UNIX Support Group. It contains detailed descriptions of the functions inside a Unix kernel. Given the date and the USG origin, I'm guessing that the system described is PWB/1.0. Can anybody confirm this at all? The URL is http://minnie.tuhs.org/Archive/PDP-11/Distributions/usdl/unix_program_descr… but I'll move it if it turns out not to be about PWB. I love how new documents and artifacts keep appearing! Thanks phk. Cheers, Warren

11 years, 9 months

Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split

by Hendrik Jan Thomassen

If I recall well the /sbin directory first appeared in HP/UX, and the name stood for 'Static binaries'. Its reason for existence was that with the introduction of shared libraries the file with the C-library had become a single point of failure. Therefore this sbin was introduced to hold Statically linked executables for the most important commands needed to fix a broken system (sh, ls, mv, cp, find, tar, fsck etcetera). With this directory earlier than /bin in his PATH the administrator could at least restore a working libc.so file. And, while we are at it, the name 'executable' was not commonly used: they were called 'binaries' (except in IBM mainframe terminology were they were called 'load modules'). Only much later the habit of /sbin = System binaries emerged. An important reason to split /bin vs. /usr/bin and /lib vs. /usr/lib etc. was that the root file system had to be kept small. The fsck program, while at work, builds tables. If possible, they stay in memory, but if memory runs out fsck writes them to disk. However, you don't want them to be written to an untrusted/unchecked file system, and certainly not to the file system currently under repair. Since the root file system has to be checked before the others, it had to be small enough so ensure that fsck could run memory-based only. Therefore: the /bin, /lib and other root-fs based directories held the minimal stuff needed for booting and for repairs/restores, while all the rest had to go into the "overflow" directories /usr/bin, /usr/lib etc (and, obviously, /usr was a separately mounted partition). Remember: those were the days that every reboot included a full fsck on all your partitions. -- Hendrik-Jan Thomassen <hjt(a)ATComputing.nl> AT Computing 6546 BE Nijmegen NL Fax +31 24 352 72 92 info(a)atcomputing.nl www.atcomputing.nl 'If you think education is expensive, then try ignorance.'

11 years, 10 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

TUHS February 2012