Date: Wed, 14 Jun 1995 13:51:01 -0500 (CDT) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: phk@ref.tfs.com (Poul-Henning Kamp) Cc: paul@freebsd.org, terry@cs.weber.edu, hackers@freebsd.org Subject: Re: LIST PING Message-ID: <199506141851.NAA17965@brasil.moneng.mei.com> In-Reply-To: <199506141707.KAA06511@ref.tfs.com> from "Poul-Henning Kamp" at Jun 14, 95 10:07:52 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > A *drop off* in traffic? > > > > > I thought my mail connection was screwed, you mean it really is > > this quiet? > > Yes, people sit tight for some days and listen for other peoples results, > make their backups (Insert floppy #127...) and then they plunge in and > all hell breaks loose... One hopeful so far: news.sol.net took the plunge and is happily chugging away under 2.0.5-RELEASE. It was locking about once a week under 2.0R due to VM problems, and I blew my stack on Sunday and did a hack and slash upgrade. I installed 2.0.5-R on a virgin 660MB SCSI-I disk, on a different box, planning basically to drop it in place of the old root disk and see what happened. Since the install box did not have two SCSI controllers or 7GB of disk on it, I was unable to allow sysinstall handle the details for me. I didn't figure this would be much of a problem. I got it installed, without too much ado, got an appropriately configured and tuned kernel installed, and went down to install the disk on news.sol.net. I had lots of problems with the slice code and trying to maintain my old partitions. I eventually got fed up and had to re-fdisk and re-disklabelled all the disks. Maybe my mistake was not reading the documentation carefully enough.... it was sorta ugly. :-( And, after having to "feel" my way through that process, maybe somebody can outline the canonical way to take a given SCSI disk, get it DOS partitioned, and get it disklabelled correctly. I had major problems with FreeBSD fdisk not writing specified geometries (not sure if it was updating the disk and not updating the in-core copy, sorta seemed like it after I finally managed to get it to work)... it was sorta wierd, but I attributed it to my cluelessness with the slice stuff. But, as I said, I may have missed some documentation - it was just sort of frustrating. The procedure for setting up disks correctly seems to be a bit of a moving target (I understand why, but it doesn't make it any easier for those of us who do it only somewhat frequently). Hardware config: Currently: 486DX/33, 32MB RAM, AHA1542B with 7 SCSI-I drives, AHA1542CF with 2 SCSI-II disks. VGA card going bad. SMC Elite 8013. Soon: 486DX4/100 (ASUS SP3G), 64MB RAM, NCR PCI's, etc. I don't have the board yet so I can't verify that this system works under 2.0.5R... In any case, the system is back up and running, and has yet to crash (3 days up). I wouldn't consider it a wild success story - yet - but if it lasts another week without crashing, or at least crashes and reboots, it's an improvement! :-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506141851.NAA17965>