From owner-freebsd-stable Fri Jul 21 14:15:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from grey.cloud.rain.com (c1029014-a.bvrtn1.or.home.com [24.12.160.67]) by hub.freebsd.org (Postfix) with ESMTP id 31BB837C021 for ; Fri, 21 Jul 2000 14:15:12 -0700 (PDT) (envelope-from trost@cloud.rain.com) Received: (qmail 12041 invoked from network); 21 Jul 2000 21:15:11 -0000 Received: from localhost.cloud.rain.com (HELO cloud.rain.com) (@127.0.0.1) by localhost.cloud.rain.com with SMTP; 21 Jul 2000 21:15:11 -0000 To: freebsd-stable@FreeBSD.ORG Subject: Re: problems upgrading to 4.1-RC2 References: <4450.964211629@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12037.964214110.1@cloud.rain.com> Date: Fri, 21 Jul 2000 14:15:10 -0700 Message-ID: <12038.964214110@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to both you and John Baldwin for the quick replies! "Jordan K. Hubbard" writes: I don't think proxies work for HTTP installs right now. Oh yes they do! I upgraded two machines that way today. > 3. Go to the "options" menu from the root menu, try to set the > "media type", and sysinstall will ultimately panic. Might just > remove the option to set media type from the options menu. I need more details. Set the media type to what? Exactly where does it "ultimately panic?" Yes, sorry. Alas, I have forgotten the details. On the other hand! Doing nothing unusual on my laptop (a Fujitsu Lifebook 635Tx with a Linksys PCMCIA card using the ed0 driver), I kept having a sysinstall panic on something like "set_variable2." I would select what to install and the disks as usual, then select an HTTP proxy install. I might use DHCP, or might go manually, but either way, immediately after the screen to configure the interface, I would get a dialog saying "trying to contact ftp.freebsd.org" and the panic message at the bottom of the window. I finally managed to permute the problem away by *either* not going directly for "custom" in the what-to-install screen, or by not specifying a name server (I was never specifying a default route, 'cause there ain't one). This one was a killer -- I was beginning to suspect that upgrading wasn't going to be possible. > 5. No XFree86. I've already mentioned this to John Baldwin. Normal for early snapshot releases; packages and XFree86 don't always show up until later in the process. Perhaps, but John was talking about spiffy new binaries in his announcement. In a completely different vein -- I sendpr'd a bug for the 4.0 prerelease that *still* hasn't been fixed: i386/16770, "cc -aout foo.c" doesn't work. I haven't heard back on i386/16722, either, which I reported at roughly the same time. By the by, how widely are the release candidates going to be mirrored? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message