On Fri, May 02, 2008 at 05:25:00PM -1000, Tim Newsham wrote: Yay, it works! :login: root root # ls -l total 6 43 sdrwr- 2 bin 620 Jan 1 00:00:00 bin 42 sdrwr- 2 sys 250 Jan 1 00:00:00 dev 44 sdrwr- 2 bin 110 Jan 1 00:00:00 etc 46 sdrwrw 2 sys 30 Jan 1 00:00:00 tmp 45 sdrwr- 2 sys 20 Jan 1 00:00:00 usr # chdir bin # date Fri Jan 1 00:00:24 Amazing work from all of you! Congrats, Warren

Its not easy to think of what's next in the excitement, but here goes a shot: - I don't see any mount utility in the s2 bits, we'll need one. - we should get the /usr stuff onto the rk03 disk and get it mounted - we should see how hard it is to get the serial ttys working. It sounds like getting a hack working in simh might not be too hard, but to get it integrated back in they probably want something robust. Perhaps having 1ed around will give someone the motivation to get dc11 support in simh? - I thought "as" wouldn't work, but it seems to be trying to run it. If possible we should investigate what is necessary to get the system to build its own kernel and its own tape. - we should investigate the original boot process and see how much of it would be possible to restore and determine if its worth the effort. - there's a bunch of file fragments in the 1972_stuff that might prove useful. It sounds like Warren has started to think about how to triage these. This might be a bit of effort. - at some point we should probably put together some kind of package for others who want to run the system in simh. I'm not really sure what this should look like and perhaps its a bit early to talk about it... Maybe two sets - a set of rf0 and rk0 images with a kernel that can run instantly, and a set with a cold kernel, a normal kernel and a tape image? any thoughts? anything I missed? Tim Newsham http://www.thenewsh.com/~newsham/

On Fri, May 02, 2008 at 10:12:59PM -0600, Warner Losh wrote: The 1e manual says: If the 1st argument represents the path name of an executable file, it is invoked; otherwise the string "/bin/" is prepended to the argument. In this way the standard commands, which reside in "/bin" are found. The 3e manual extends the above: If no such command is found, the string "/usr" is further prepended (to give "/usr/bin/command") and another attempt is made to execute the resulting file. (Certain "overflow" commands live in "/usr/bin".) If the "/usr/bin" file exists, but is not executable, it is used by the shell as a command file. That is to say it is executed as though it were typed from the console. Manuals for 4e, 5e and 6e all say the above. The 7th Edition manual is the first to say: The shell parameter $PATH defines the search path for the directory containing the command. Each alternative directory name is separated by a colon (:) The default path is :/bin:/usr/bin. If the command name contains a / then the search path is not used. Otherwise, each directory in the path is searched for an executable file. If the file has execute permission but is not an a.out file, it is assumed to be a file containing shell commands. Cheers, Warren

On Fri, May 02, 2008 at 05:47:47PM -1000, Tim Newsham wrote: The asm code to init.s is here: http://minnie.tuhs.org/UnixTree/1972_stuff/s1/frag2.html sys mount; rk1; usr sys mount; rk2; ssys sys mount; rk3; crp rk1: </dev/rk1\0> rk2: </dev/rk2\0> rk3: </dev/rk3\0> usr: </usr\0> ssys: </sys\0> crp: </crp\0> Looks like we can use it to write a simple mount.s. Warren