From owner-freebsd-hackers Sun Jan 12 15:51:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA01902 for hackers-outgoing; Sun, 12 Jan 1997 15:51:42 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA01896 for ; Sun, 12 Jan 1997 15:51:38 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id PAA03743; Sun, 12 Jan 1997 15:51:19 -0800 (PST) To: Eivind Eklund cc: hackers@freebsd.org Subject: Re: Numerous minor with 2.1.6 In-reply-to: Your message of "Sun, 12 Jan 1997 15:53:57 +0100." <3.0.32.19970112155356.009c1100@dimaga.com> Date: Sun, 12 Jan 1997 15:51:18 -0800 Message-ID: <3739.853113078@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 1) After having loaded the kernel, just after starting "init" (sysinstall), > the system froze, but the VTYs worked. (Seems to have been an IO-area > conflict; it went away when I twiddled jumpers). Could be auto-detectable? I'm not sure about this one - none of my test systems exhibit this behavior. :( > 2) The description of proxy-FTP in the handbook leaves much to be desired; > I had a lot of work finding how to do it. (Suggestion for revised > handbook-entry sent to doc-mailing-list) - shorty: use options to set Which I'll take up, thanks. FWIW, I don't think that the Red Hat install even allows you to use a proxy server. :-) > 3) Many packages missed (I don't know exactly which, due to having set 'yes > to all non-critical questions') - no solution. (Except using ports to > install them afterwards) That was a bogus INDEX file - I think we've fixed that, though I'll go check. I know it's not the same on the CDROM. Perhaps I should send you a 2.1.6 CDROM to see how many of these problems persist there. :-) > 4) FreeBSD happily wrote a non-functioning boot-manager on my dangerously > dedicated disk. Solution: Don't do that. (I ended up bringing the box to > another location which already had a FreeBSD-machine, That's weird - how did you manage to get it to do that? That question should be skipped entirely when you choose the DD option; it was when I just tested it, anyway. Hmmmmm. > 7) The lynx port was 2.5FM - which no longer exist on the FTP sites > mentioned. Solution: I grabbed the -current ports collection, and Hmmm, that should be fixed somehow. > 8) The version of X downloaded is for 2.2 - it requires libc.so.3.0 > I've reported this to jmz@freebsd.org (maintainer for the port), but don't Really?? On ftp.cdrom.com, it's pointing at the 2.1-stable copies. Are you sure you followed the right link or installed it via sysinstall at initial installation time? > 9) SERIOUS: XFree86 _rebooted_ the box when /dev/mouse was linked to > /dev/mse0 and I ran a config with "Microsoft" as mouse protocol. /dev/mse0 Possible user error - did you enable the bus mouse in the kernel configuration menu? > 10) XFree86 3.2 would detect my Matrox Millenium 2064W, and all > documentation claim that the SVGA server support it - but it didn't work. Odd - it works just great with my same 2064W cards here. I've tested it several times. > This is more distribution-problems than I like. FreeBSD runs very nicely > once it is up, but I must admit to having had my share of problems getting > it up and running, which is unfortunate, as I would have liked to be able > to say it is easier than installing Linux :( I think it still is, you just seem to have had more than the usual amount of bad luck. :-) If you could get back to me on some of the "mystery problems" listed above, though, I'd appreciate it. Thanks! Jordan