* [Unix-jun72] Missing commands @ 2008-05-03 8:48 Warren Toomey 2008-05-03 11:23 ` Brad Parker 0 siblings, 1 reply; 6+ messages in thread From: Warren Toomey @ 2008-05-03 8:48 UTC (permalink / raw) I thought I would quickly make a list of commands we have, commands that are missing, and out-of-the-ordinary commands. Below, if a command has no comment, it's a V1 command that we have. Notes follow. I have not tried to list the missing /etc and /usr/... commands yet. /bin ---- : V2 cmd, 0405 binary ar as V2 binary b missing bas bcd missing boot missing cal cat cc V2 binary chball ? no idea check chmod chown cmp cp date db dbppt missing dc df ds V2 binary dsw dtf missing du echo V2 cmd, 0405 binary ed exit V2 cmd, 0405 binary fc V2 binary find V2 binary form goto V2 cmd, 0405 binary hup missing if V2 cmd, 0405 binary lbppt missing ld V2 binary ln login V2 cmd, 0405 binary ls mail maki V2 binary mesg mkdir mkfs mount mv nm V2 binary od pr rew rkd missing rkf missing rkl missing rm rmdir roff sdate missing sh size V2 binary skip ? no idea sort stat strip V2 binary stty V2 cmd, 0405 binary su sum tap tm tty type un V2 binary wc who write /etc ---- as2 V2 binary getty V2 cmd, 0405 binary glob init msh suftab uids I have a quote from dmr somewhere (I can't find it), but to paraphrase: early UNIX was under a constant state of development. We would tidy up now and then, write a new manual, then get back to development. The 1st Edition UNIX manual is dated November 3, 1971. The 2nd Edition UNIX manual is dated June 12, 1972. 1st Edition (1e) only used 0405 a.out files. 2nd Edition (2e) only used 0407 a.out files. I would guess that the executables that we have from the s2 tape are from a snapshot halfway between 1e and 2e, and at that point in time the kernel could execute both varieties. This would explain why some V2 commands are 0405 style, and some are 0407 style. Despite the dates on the PDF commentary where we got the kernel source, the kernel has to be around 1e, not much later. The kernel only knows about 0405 a.out files, and is missing all of the system calls new to 2e: hog, kill, makdir (renamed from 1e mkdir), smdate and sync. So: kernel is around 1e, Nov 1971 or close; executables are somewhere between 1e and 2e, but before June 1972 as we have 0405 and 0407 ones. Cheers, Warren ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Unix-jun72] Missing commands 2008-05-03 8:48 [Unix-jun72] Missing commands Warren Toomey @ 2008-05-03 11:23 ` Brad Parker 2008-05-03 11:39 ` Warren Toomey 0 siblings, 1 reply; 6+ messages in thread From: Brad Parker @ 2008-05-03 11:23 UTC (permalink / raw) Warren Toomey wrote: >I thought I would quickly make a list of commands we have, commands that >are missing, and out-of-the-ordinary commands. Below, if a command has >no comment, it's a V1 command that we have. Notes follow. I have not tried >to list the missing /etc and /usr/... commands yet. > ... >mkfs Where is this? I don't have it in my v2 bits. Like to try it on the rk. -brad ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Unix-jun72] Missing commands 2008-05-03 11:23 ` Brad Parker @ 2008-05-03 11:39 ` Warren Toomey [not found] ` <345.1209815083@mini> 0 siblings, 1 reply; 6+ messages in thread From: Warren Toomey @ 2008-05-03 11:39 UTC (permalink / raw) On Sat, May 03, 2008 at 07:23:45AM -0400, Brad Parker wrote: > >mkfs > Where is this? I don't have it in my v2 bits. Like to try it on the rk. > -brad Whups, that should have been marked as missing, sorry. Warren ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <345.1209815083@mini>]
[parent not found: <20080503121126.GA83961@minnie.tuhs.org>]
[parent not found: <1041.1209816979@mini>]
* [Unix-jun72] Missing commands [not found] ` <1041.1209816979@mini> @ 2008-05-03 12:31 ` Warren Toomey 2008-05-03 12:42 ` Warren Toomey 2008-05-03 18:06 ` Tim Newsham 0 siblings, 2 replies; 6+ messages in thread From: Warren Toomey @ 2008-05-03 12:31 UTC (permalink / raw) On Sat, May 03, 2008 at 08:16:19AM -0400, Brad Parker wrote: > The simh setup was wrong; you need to use > > set rk0 enabled > attach rk0 rk3.dsk > > Once I did that I could check the image I made with your program. I have > not mounted it yet, however. It checks fine. > > Tim - where did you get the files you used to make your tape image? Can > you tar up that directory and check it in? I can't find init anywhere. > I must be confused. On the s2 tape in /etc/init. Thanks Brad. Warren ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Unix-jun72] Missing commands 2008-05-03 12:31 ` Warren Toomey @ 2008-05-03 12:42 ` Warren Toomey 2008-05-03 18:06 ` Tim Newsham 1 sibling, 0 replies; 6+ messages in thread From: Warren Toomey @ 2008-05-03 12:42 UTC (permalink / raw) On Sat, May 03, 2008 at 08:16:19AM -0400, Brad Parker wrote: > The simh setup was wrong; you need to use > > set rk0 enabled > attach rk0 rk3.dsk and #set rk3 enabled #att rk3 rk0.dsk I'm attaching my latest mkfs.c. It makes RF images fine, but for some reason I can't make a working RK image bigger than 2165 blocks. I must be overflowing something on the image. Cheers, Warren -------------- next part -------------- A non-text attachment was scrubbed... Name: mkfs.c.gz Type: application/x-gunzip Size: 5003 bytes Desc: not available URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20080503/9d949139/attachment.bin> ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Unix-jun72] Missing commands 2008-05-03 12:31 ` Warren Toomey 2008-05-03 12:42 ` Warren Toomey @ 2008-05-03 18:06 ` Tim Newsham 1 sibling, 0 replies; 6+ messages in thread From: Tim Newsham @ 2008-05-03 18:06 UTC (permalink / raw) >> Tim - where did you get the files you used to make your tape image? Can >> you tar up that directory and check it in? I can't find init anywhere. >> I must be confused. The process for making the tape image is: - get s2.tar.gz from TUHS PDP11 distributions (under research) - extract somewhere like /tmp/s2 (if elsewhere, you must edit tools/mktape.py) - build a tape with the files you want: tools/mktape.py /tmp/s2/bin/* /tmp/s2/etc/* you can add any files you want, but it will make up uid/permission for files it doesnt "know" about. It has a table of files and permissions baked into it that came from the TUHS archive. The tool strips off "/tmp/s2" from the paths right now, so if you put s2 in a different location you'll have to alter that path or you'll have to build the tape from within that subdirectory using relative paths. Tim Newsham http://www.thenewsh.com/~newsham/ ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2008-05-03 18:06 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2008-05-03 8:48 [Unix-jun72] Missing commands Warren Toomey 2008-05-03 11:23 ` Brad Parker 2008-05-03 11:39 ` Warren Toomey [not found] ` <345.1209815083@mini> [not found] ` <20080503121126.GA83961@minnie.tuhs.org> [not found] ` <1041.1209816979@mini> 2008-05-03 12:31 ` Warren Toomey 2008-05-03 12:42 ` Warren Toomey 2008-05-03 18:06 ` Tim Newsham
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).