Description of Problem: When doing a network (ftp) install, the installation procedure doesn't know about the end of disc1 and when to change to another mount point, so the installation fails (unless the server system manager does ugly and/or clever things). How Reproducible: 100% Steps to Reproduce: 1. mount -o loop <disc1> <mountpoint> (on server) 2. boot installation floppy and select ftp install 3. specify server and mount point, allow installation to proceed. At some point it simply hangs. Actual Results: Installation procedure hangs, repeatedly getting errors for non-existant kit. Expected Results: I would have expected the installation procedure to know when it has loaded all kits it can from disc1 and to ask for the location of disc2. Additional Information: When I asked an internal mailing list about this, the consensus was to simply copy both cd1 and cd2 to a common area and use it as the kit location. I was able to play some games instead by killing the ftpd daemon in the server and quickly unmounting the disc1 .iso image and mounting the disc2 .iso image. This way, when ftp timed-out on the machine on which I was doing the installation, the next invocation of ftp would access the same place, which would now have the files it needed to continue. Megan Gentry Former RT-11 Developer +--------------------------------+-------------------------------------+ | Megan Gentry, EMT/B, PP-ASEL | (work): gentry.com | | Unix Support Engineering Group | gentry.cpqcorp.net | | Compaq Computer Corporation | (home): mbg.com | | 110 Spitbrook Rd. ZK03-2/T43 | URL: http://world.std.com/~mbg/ | | Nashua, NH 03062 | "PDP-11 programmer - some assembler | | (603) 884 1055 | required." - mbg KB1FCA | +--------------------------------+-------------------------------------+
Hi Megan, The consensus is right. For network installs, a merged tree (ie RPMs from both CDs in one location) is necessary ... This is documented in the release notes. :) HTH, brock