Date: Mon, 16 Dec 1996 23:16:12 -0800 (PST) From: Doug Russell <drussell@internode.net> To: Bill Fenner <fenner@parc.xerox.com>, current@freebsd.org Subject: Re: sysinstall REALLY needs a "reset FTP state" option, or something Message-ID: <1.5.4.16.19961217001848.34d7cec6@internode.net>
next in thread | raw e-mail | index | archive | help
At 08:06 PM 12/16/96 PST, Bill Fenner wrote: >I just spent about 15 minutes carefully choosing which distributions to >install, and then said "go". I came back an hour later, and it was 87% >done with bin. Another hour later, and it was still 87% done with bin. >The FTP connection had hung somehow. It's *really* frustrating to have >two choices: stay hung, or reboot. Is there any way that a control-C while >ftp'ing could allow another option of disconnecting and reconnecting to >the same server? (Or, even better, a keepalive so that a connection that >hasn't transferred a byte in an hour times out and you get the ftp >reselection menu...) That is a good suggestion, especially for people doing things over a (relatively) slow like, eg. a dialup PPP. While we are talking about the install program, I have found another little bug. (Oh, and I still haven't tried to upgrade to 2.2-ALPHA to test that possible partition table clobbering bug on other machines, by the way... Just like everyone else, as soon as I have a few free minutes I will... ) :-) I noticed this one because I store (part of) the FreeBSD tree on one of the machines in my house, which makes installing to a machine on the local network very fast and convenient. However, I currently don't have the entire packages directory for 2.2-ALPHA on that box, so, here's what happens. If I select an FTP install for my bin, XFree, etc. etc. (basic system) from my server machine, things install correctly. I get to the final config menu, and try to install a package which doesn't exist on my server, so I switch to, say ftp.freebsd.org on the media menu. When I try to install the package, it still tries to get it from my local server. The only way I could switch servers was to exit sysinstall and restart. It's really not THAT big of a deal anymore, since Sysinstall works pretty much correctly now (you can re-run it later and add a package, for example, and it actually works. Compared to the way things were back when I was running 1.x, this is pretty good! :-) Somethings just a little screwey in there. Sorry I can't give more detail, but it was a couple days ago, and I never really paid much attention to it, because it was fairly simple to work around. Somebody might want to look into it though. I also had a problem installing a package from the Networking menu on the final config/options menu. I inadvertantly tried to get Apache from my local server (which did not yet have the file at the time), before I switched ftp servers to ftp.freebsd.org. (the networking menu does seem to use the new FTP settings when you change them, it's just the "PACKAGES" one that doesn't work as far as I can tell...) I then installed a bunch of other packages off the network menu (from ftp.freebsd.org), but it would NOT let me re-try Apache, it would always pop up with a "can't fetch package" message, never even trying to fetch it from ftp.freebsd.org (the SD light on the outgoing modem never blinked). I don't know if it was still looking on server, or if it just assumed it couldn't find it. Maybe if I have a few minutes (ya, right) to myself I'll actually look into it myself. :-) Sorry for the long-winded message, I've been awake FAR too long. Hopefully you can understand what I'm trying to say. :-) Later...... <Doug>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1.5.4.16.19961217001848.34d7cec6>