TUHS

tuhs@tuhs.org

29 participants
6439 discussions

by jnc＠mercury.lcs.mit.edu

So, I have a chance to buy a copy of a Version 5 manual, but it will be a lot. I looked, and the Version 5 manual doesn't appear to be online. So while normally at the price this is at, I would pass, it might be worth it for me to buy it, and scan it to make it available. But, I looked in the "FAQ on the Unix Archive and Unix on the PDP-11", and it says: 5th Edition has its on-line manual pages missing. ... Fortunately, we do have paper copies of all the research editions of UNIX from 1st … [View More]

10 years

Re: [TUHS] sync; sync; sync; halt (was: Re: Illumos ))

by jnc＠mercury.lcs.mit.edu

> From: Tom Ivar Helbekkmo > There was no fancy I/O order juggling, so everything was written in the > same chronological order as it was scheduled. > ... > What this means is that the second sync, by waiting for its own > superblock writes, will wait until all the inode and file data flushes > scheduled by the first one have completed. Ah, I'm not sure this is correct. Not all disk drivers handled requests in a 'first-come, first-served' order (i.… [View More]

10 years, 1 month

Illumos )

by Larry McVoy

Yo Jacob, I'm ex-sun but I don't know too much about Illumos. Care to give us the summary of why I might care about it? On Wed, Dec 31, 2014 at 01:16:00AM -0500, Jacob Ritorto wrote: > Hey, thanks, Derrik. > I don't mess with Linux much (kind of an Illumos junkie by trade ;), but > I bet gcc would. I did out of curiosity do it with the Macintosh cc (Apple > LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)) and it throws > warnings about our not type-defining … [View More]functions because you're apparently > supposed to do this explicitly these days, but it dutifully goes on to > assume int and compiles our test K&R stuff mostly fine. It does > unfortunately balk pretty badly at the naked returns we initially had, > though. Wish it didn't because it strikes me as being beautifully simple.. > > thx again for the encouragement! > jake > > > On Wed, Dec 31, 2014 at 1:02 AM, Derrik Walker v2.0 <dwalker(a)doomd.net> > wrote: > > > On Wed, 2014-12-31 at 00:44 -0500, Jacob Ritorto wrote: > > > > > > > > P.S. if anyone's bored enough, you can check out what we're up to at > > > https://github.com/srphtygr/dhb. I'm trying to get my 11yo kid to > > > spend a little time programming rather than just playing video games > > > when he's near a computer. He'a actually getting through this stuff > > > and is honestly interested when he understands it and sees it work -- > > > and he even spotted a bug before me this afternoon! Feel free to > > > raise issues, pull requests, etc. if you like -- I'm putting him > > > through the git committing and pair programming paces, so outside > > > interaction would be kinda fun :) > > > > > > > > > P.P.S. We're actually using 2.11bsd after all.. > > > > > I'm curious, will gcc on a modern Linux system compile K&R c? > > > > Maybe when I get a little time, I might try to see if I can compile it > > on a modern Fedora 21 system with gcc. > > > > BTW: Great job introducing him to such a classic environment. A few > > years ago, my now 18 year old had expressed some interest in graphics > > programming and was in awe over an SGI O2 I had at the time, so I got > > him an Indy. He played around with a bit of programming, but > > unfortunately, he lost interest. > > > > - Derrik > > > > > > _______________________________________________ > > TUHS mailing list > > TUHS(a)minnie.tuhs.org > > https://minnie.tuhs.org/mailman/listinfo/tuhs > > > _______________________________________________ > TUHS mailing list > TUHS(a)minnie.tuhs.org > https://minnie.tuhs.org/mailman/listinfo/tuhs -- --- Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm [View Less]

10 years, 1 month

Re: [TUHS] Less -- was Termcap vs terminfo

by Doug McIlroy

> when you - say - run less to display a file, it switches to a dedicated > region in the terminal memory buffer while printing its output, then > restores the buffer to back where you were to begin with when you exit > the pager Sorry for veering away from Unix history, but this pushed one of the hottest of my buttons. Less is the epitome of modern Unix decadence. Besides the maddening behavior described above, why, when all screens have a scroll bar, should a pager do its own … [View More]

10 years, 1 month

SVN of CSRG Releases

by Warren Toomey

Hi all, I came across this last week: http://svnweb.freebsd.org/ It's a Subversion VCS of all the CSRG releases. I'm not sure if it has been mentioned here before. Cheers, Warren

10 years, 1 month

Re: [TUHS] Termcap vs terminfo

by David Barto

<much discussion about quadratic search removed> All I remember (and still support to this day) is that I’ve got a TERMCAP=‘string’ in my login scripts to set termcap to the specific terminal I’m logging in with. Long ago this made things much faster. Today I think that it is just a holdover that I’m not changing due to inertia, rather than any real need for it. David — David Barto david(a)kdbarto.org

10 years, 1 month

Fixed Unix v5 bug!

by Mark Longridge

> Noel Chiappa > The change is pretty minor: in this piece of code: > > case reboot: > termall(); > execl(init, minus, 0); > reset(); > > just change the execl() line to say: > > execl(init, init, 0); I patched init in v5 and now ps shows /etc/init as expected, even after going from multi to single to multi mode. Looks like init.c was the same in v5 and v6.

10 years, 1 month

Early Unix file system checks

by Mark Longridge

> Noel Chiappa: > Just out of curiousity, why don't you set the SR before you boot the machine? > That way it'll come up single user, and you can icheck/dcheck before you go > to multi-user mode. I prefer doing it that way, there's as little as possible > going on, in case the disk is slightly 'confused', so less chance any bit-rot > will spread... I actually do file system checks on v5 as it's the early unix I use the most: check -l /dev/rk0 check -u /dev/rk0 same for rk1, … [View More]

10 years, 1 month

Re: [TUHS] single user mode in v5 & v6

by jnc＠mercury.lcs.mit.edu

> From: Clem Cole > ps "knew" about some kernel data structures and had to compiled with > the same sources that your kernel used if you want all the command > field in particular to look reasonable. Not just the command field! The real problem was that all the parameters (e.g. NPROC) were not stored in the kernel anywhere, so if you wanted to have one copy of the 'ps' binary which would work on two different machines (but which were running the same version of the … [View More]kernel)... rotsa ruck. I have hacked my V6 to include lines like: int ninode NINODE; int nfile NFILE; int nproc NPROC; etc so 'ps' can just read those variables to find the table sizes in the running kernel. (Obviously if you modify a table format, then you're SOL.) > From: Ronald Natalie > The user structure of the currently running process is the only one > that is guaranteed to be in memory ... Any processes that were swapped > you could read the user structure so things that were stored there were > often unavailable (particularly the command name). Well, 'ps' (even the V6 stock version) was actually prepared to poke around on the swap device to look at the images of swapped-out processes. And the command name didn't come from the U area (it wasn't saved there in stock V6), 'ps' actually had to look on the top of the user stack (which is why it wasn't guaranteed to be accurate - the user process could smash that). > From: Clem cole > IIRC we had a table of sleep addresses so that ps could print the > actual thing you were waiting for not just an address. I've hacked my copy of 'ps' to grovel around in the system's symbol table, and print 'wchan' symbolically. E.g. here's some of the output of 'ps' on my system: TTY F S UID PID PPID PRI NIC CPU TIM ADDR SZ TXT WCHAN COMMAND ?: SL S 0 0 0-100 0 -1 127 1676 16 runout <swapper> ?: L W 0 1 0 40 0 0 127 1774 43 0 proc+26 /etc/init ?: L W 0 11 1 90 0 0 127 2405 37 tout /etc/update 8: L W 0 12 1 10 0 0 127 2772 72 2 kl11 - a: L W 0 13 1 40 0 0 127 3122 72 2 proc+102 - a: L R 0 22 13 100 0 10 0 3422 138 3 ps axl b: L W 0 14 1 10 0 0 127 2120 41 1 dz11+40 - 4 It's pretty easy to interpret this to see what each process is waiting for. Noel [View Less]

10 years, 1 month

Re: [TUHS] single user mode in v5 & v6

by jnc＠mercury.lcs.mit.edu

> From: Noel Chiappa > For some reason, the code for /etc/init .. bashes the command line so > it just has '-' in it, so it looks just like a shell. BTW, that may be accidental, not a deliberate choice - e.g. someone copied another line of code which exec'd a shell, and didn't change the second arg. > I fixed my copy so it says "/etc/init", or something like that. ... I > can upload the 'fixed' code tomorrow. The change is pretty minor: in this piece of code: … [View More] case reboot: termall(); execl(init, minus, 0); reset(); just change the execl() line to say: execl(init, init, 0); >> I'm not sure if unix of the v6 or v5 era was designed to go from multi >> user to single user mode and then back again. > I seem to recall there's some issue, something like in some cases > there's an extra shell left running attached to the console So the bug is that in going from single-user to multi-user, by using "kill -1 1" in single-user with the switch register set for multi-user, it doesn't kill the running single-user shell on the console. The workaround to that bug which I use is to set the CSWR and then ^D the running shell. In general, the code in init.c isn't quite as clean/clear as would be optimal (which is part of why I haven't tried to fix the above bug), but _in general_ it does support going back and forth. > From: Ronald Natalie > our init checked the switch register to determine whether to bring up > single or multiuser I think that's standard from Bell, actually. > I believe our system shutdown if you kill -1-1 (HUP to init). The 'stock' behaviour is that when that happens, it checks the switch register, and there are three options (the code is a little hard to follow, but I'm pretty sure this is right): - if it's set for single-user, it shuts down all the other children, and brings up a console shell; when done, it does the next - if it's set for 'reboot', it just shuts down all children, and restarts the init process (presumably so one can switch to a new version of the init without restarting the whole machine); - if it's not set for either, it re-reads /etc/ttys, and for any lines which have switched state in that file, it starts/kills the process listening to that line (this allows one to add/drop lines dynamically). > From: Clem Cole > it's probably worth digging up the v6 version of fsck. That's on that MIT V6 tape, too. Speaking of which, time to write the code to grok the tape... Noel [View Less]

10 years, 1 month

Jump to page:

2025

2024

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