From owner-freebsd-current Fri Feb 9 11:00:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA02819 for current-outgoing; Fri, 9 Feb 1996 11:00:03 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA02748 for ; Fri, 9 Feb 1996 10:59:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id LAA04176; Fri, 9 Feb 1996 11:52:55 -0700 Message-Id: <199602091852.LAA04176@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: "Jordan K. Hubbard" cc: current@freefall.freebsd.org Subject: Re: 2.2-960130-SNAP experiences In-reply-to: Your message of "Fri, 09 Feb 1996 05:19:41 PST." <19922.823871981@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Feb 1996 11:52:55 -0700 Sender: owner-current@FreeBSD.ORG Precedence: bulk Jordon, >> Installing 2.2-960130-SNAP via medium NFS fails during "Commit" phase. >> I tried installing 6 or 7 times, each dying in one of 2 places. > >Hmmm. I've done several successful NFS installs with this SNAP >between my two test machines, so I can only conclude it's some weird >local configuration issue! Not to say that it's not a bug in >-current, but I don't think it's anywhere in the installation (for >once.. :-). I agree. Someone suggested that I try setting "NFS slow" option, that I am overrunning the 8bit 8003 card. I will try that sometime today and let you know what happens. Suggest any other experiments now, b4 I populate the disk and cannot redo installs... About the installation, I am using 2 identical disks (hope to use CCD) and was pleased to see it deal with 2 disks. However I couldn't get it to use sd1s1a (ie, a root partition) on the second drive. It wanted to start with prtition e, NOT a. If I let it pick the sizes it did the good thing: abefg. But assigning each size always started with e! I just saw something disturbing last nite. I found that I can "rsh {any of several 2.1.0-R machines}" from the new 2.2-SNAP but if I "rsh {2.2-SNAP} from one of the 2.1-R machines it always hangs. For example: 2.1-REL % rsh 2.2-SNAP ls will do the 'ls', showing me everything in the 2.2-SNAP directory, but will then be hung, even '^c' won't die, have to kiil from another term. I can reproduce this 100% of the time, always the one direction only. This is with hardware that has run previous versions of FreeBSD for years. Any tests I can run for you??? A question, ld.so doesn't like my shared 2.1 executables. Can I build a compat21 package, or must all dynamic execs be rebuilt? Finally, I have been getting truncated "current-digest" mailings, anyone else seen this? -- Steve Passe | powered by smp@csn.net | FreeBSD