Date: Sun, 3 Dec 1995 14:16:08 -0500 From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: freebsd-bugs@freefall.FreeBSD.org, freebsd-hackers@freefall.FreeBSD.org Subject: Can't install 2.1 over SL/IP (bummer) Message-ID: <199512031916.OAA17606@ponds.UUCP>
next in thread | raw e-mail | index | archive | help
I've finally found the time to try a 2.1 install on my laptop. (I tried it on my 4meg machine, at work; Jordan will be happy to here I have gotten a replacement for it, and will no longer need 1.2meg floppies, or 4meg configurations again. But, just F.Y.I. it didn't boot.) Anyway, I've tried several alternative mechanisms to get things working via SL/IP (on a direct connection) but the install script always tells me that sl0 isn't configured, and says I have to straighten it out in the "Network configuration" menu. First - There is no obvious way to reach the "Network configuration" menu, as it isn't listed. I suppose that is a reference to the menu where you fill in your hostname, etc... Second - when I go to the holographic shell, I find that, in fact; sl0 is configured, and the slattach is properly running. I can run mount_nfs to get something actually mounted. This means that the sysinstall script is incorrect in saying sl0 isn't working. How does it determine something isn't working? On the debugging screen, after the slattach I got: DEBUG: Command "slattach -s 19200 /dev/cuaa0' returns status of 0 DEBUG: Switching back to VTY1 and then I get the message on VTY1 indicating the "The device sl0 is not configured..." [By the way, I was able to "sneak" in a proper ifconfig for sl0 when entering the slattach command, I simply typed: ifconfig sl0 130.96.3.1 130.96.3.116; slattach -s 19200 /dev/cuaa0 in the window.] My situation is: 1) A laptop wired to a 19200 cable. 2) No gateway or default or nameserver routes I tried to get to a situation where I could edit the install script, but when you mount the boot floppy, all you can get to is the one 'kernel' file, where everything is compiled into the MFS... So, I have no good fix for this problem (I was able to work around the problem before by clever editing of the sysinstall script after bouncing into the emergency fix-up shell, but that has gone away.) So, I'm at a loss this go-'round. I can't install 2.1 on my laptop (unless, I suppose, I wrote everything to floppies.) Does anyone have a suggestion? Also, I'd like to argue for the return of the "emergency shell" which I found very helpful in the past (something like, pressing cntrl-A could get you the emergency shell, if it could be done...) - Thanks - - Dave Rivers -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512031916.OAA17606>