Date: Tue, 18 Mar 1997 17:06:19 -0600 From: "Jeffrey J. Mountin" <sysop@mixcom.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: questions@freebsd.org Subject: Re: 2.2 Upgrading for idiots? Message-ID: <3.0.32.19970318170618.006ca9e4@mixcom.com>
next in thread | raw e-mail | index | archive | help
At 10:40 PM 3/17/97 -0800, Doug White wrote: >Absolutely not. That is why you need the boot floppy -- it'll replace >your existing binaries, which will do the equivalent of a "make all >install." When you get finished, you'll be booting a 2.2 GENERIC kernel, >and no doubt you'll want to restore your custom settings, thus #5. Great! And I just made some time to look over the system and see that most everything is updated. >I've done 5 or 6 upgrades the same way without any adverse effects. Later >this week, I'll do another round of 4 or so, bringing machines from 2.1.5 >to 2.2-960801-SNAP up to 2.2-RELEASE, as soon as it stabilizes. The first few upgrades I tried were dismal failures, something with sysinstall, which seems to have been fixed. >IMHO, you really must know what you are doing before building everything >from scratch. 99% of the population just wants to upgrade, not rebuild >everything and dedicate a 2GB disk to the job. The prescribed upgrade >instructions do this in the least painful way. If you're doing this, I >assume you're on hackers, stable, or current lists or have done this >before. OK, but I would imagine that it would be a good idea to recompile some of the packages, unless there is a new version. Some standard things I do as a package, usually from sysinstall. Others have been customized, so I keep the source out of the way of upgrades. >We've gone to the pain of doing this for you -- unless you have need to >build from edited source, save yourself and your computer some aspirin. Uh, no. Not really. 8-) >I upgraded my workstation from 2.1.6 (?) to 2.2-ALPHA without any real >trauma, so the change should be very simple. The sticky part is the >config file merging. They changed it for 2.2-GAMMA to make /etc/upgrade >instead of munging the files, and it is confusing some people because >suddenly, this glob of ipx stuff wants to start up... Sounds just like the upgrade to either 2.1.5(6?) and having to redo a half-dozen files in /etc and I don't see this as a problem. What I do have a problem with is the default mode for skeykeys, which should be treated just like master.passwd and spwd.db. Once it is set it doesn't get changed, but I do chmod a lot of things that users should not have execute rights for, let alone read. Easy enough to script this out. >Hope this helps. Of course, do what you feel is sufficient to upgrade >your system. It's your system, after all :) Like remembering to link perl -> perl5.003 Teensy little problem for a few customers. Thanks, ------------------------------------------- Jeff Mountin - System/Network Administrator jeff@mixcom.net MIX Communications Serving the Internet since 1990
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.32.19970318170618.006ca9e4>