dyer@spdcc.COM (Steve Dyer) (09/27/90)
I am developing a network install procedure for AIX PS/2 1.2 for our Athena enviroment, which doesn't use TCF at all. That is, each AIX PS/2 machine is a self-contained site with all its files resident. Essentially, operations staff simply want to bring up a machine using only a few floppies. It's been fairly easy to insinuate my changes into the stereotyped install procedure so far, and the procedure is fairly straightforward: boot from floppies using kernel with TCP/IP enabled use standard install diskette use customized "operating system" diskette (yes, one) mount (NFS or Athena RVD) an archival hierarchy of an installed system copy over machine-independent files (i.e., not those custom-created by the install procedure: /local/site, /local/filesystems...) Now at this point the resulting machine should look like a machine which has been installed from all 60+ floppies. And it does, sorta. However, when I boot from hard disk, it appears that /sitename is mounted read only (although "mount" doesn't report that.) Attempts to run fsck fail ("can't create pipe for first/second fsck"). And, as you know, it's impossible to unmount /sitename. The root is writable. Coming up on the maintenance disk, neither the root nor /sitename are "dirty"--that is, the install procedure unmounts and reboots cleanly and fsck's done from the maintenance disk don't report any modifications. I think I must be simply forgetting something simple. I was hoping that a Locus person might read this and quickly have a few suggestions. -- Steve Dyer dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer dyer@arktouros.mit.edu, dyer@hstbme.mit.edu
dyer@spdcc.COM (Steve Dyer) (09/28/90)
Nevermind. On the final installed system, /etc/fsck was somehow a link to /etc/dfsck instead of being a separate program of its own. /etc/fsck needs to run to check /generic/dev/sitename during the time that /sitename is mounted readonly. /etc/dfsck attempts to create pipes on /sitename and fails, causing the initial startup to fail (with /sitename still mounted r/o.) The fix was to ensure that /etc/fsck was correctly present on the final installed system. -- Steve Dyer dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer dyer@arktouros.mit.edu, dyer@hstbme.mit.edu