Date: Thu, 15 Jun 1995 02:32:48 +0100 From: "Jordan K. Hubbard" <jkh@freebsd.org> To: Robert Watson <rwatson@clark.net> Cc: bugs@freebsd.org Subject: Re: originally a newsgroup post, but news server here isn't working Message-ID: <1394.803179968@whisker.internet-eireann.ie> In-Reply-To: Your message of "Wed, 14 Jun 1995 20:38:17 EDT." <Pine.SOL.3.91.950614203752.3747C-100000@clark.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> on my system. Admittadly it's a 386sx20 w/4megs of ram, but that's > supposedly the min platform line or such. Egads. I suppose I should be happy that there are people like you around to keep us honest, though frankly you're all also a big pain in the butt! :-) :-) Anyway, all joking aside, on to the reported problems. > 1) sysinstall has problems with memory -- first it started killing its > own processed (hadn't set up swap yet, hadn't given me a chance, but was This *is* with the latest 2.0.5R "UPDATES" boot floppy? As Gary announced on the <announce@FreeBSD.org> mailing list, we initially made a mistake with 4MB machines and overflowed our maximum allowable kernel size. Gary pared things back down again at the last moment and stuck a boot boot floppy in place. If it's still dying WITH that floppy, then we definitely want to know about it as it means that the problem hasn't been fixed! > 2) Having the ppp installation line go down trashes the installation > program, locking up the ppp dialer and not letting you reload a further Sorry, I expect a reliable line for now and will continue to do so for the forseeable future - coding defensively for this isn't actually all that easy, and there are bigger problems I'd prefer to focus on solving anyway. Heck, 2.0R didn't even *support* a ppp installation, so I figured one that works on a reliable line was still a fair step up from none at all! :) > to an hour (assuming that would be enough.) When I got back, it had > installed fine, but the system froze shortly afterwards when I tried to > abort part of sysinstall. (pressing ctrl-c results in a reboot of Sorry, you can't really abort it effectively right now - I don't hold and process signals at checkpoints, though I may perhaps add this at some other point. > Xconfig program confused, as it suggested /dev/tty00 as a possible mouse > device, but there wasn't one (after linking random tty files to > /dev/mouse, I eventually found /dev/ttyid0 for the mouse on com1.) This is because they've been renamed for 2.0.5 (which really should be documented in a "Changes" doc someplace - argh!). /dev/cuaa0 is the ticket. > Boot assistance would be great -- I have a 230 meg FreeBSD slice on wd1 > (a maxtor 540 drive) and a 130 meg dos slice on wd0 (130 meg maxtor > drive) and a 270 meg and 40 meg slice on wd1 again. (eg., freebsd should > boot off of wd(1,a)/kernel -- which it did one installation, only the > sysinstall program never installed all of the binary installation that > time ;). Try a reinstall with the latest, if you haven't already done so, and select the boot manager option. Try to also be sure of each step in advance; sysinstall isn't very fault-tolerant right now and it works fairly well in most instances if you say just the right things to it. :-) Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1394.803179968>