Re: Using legacy sysinstall to upgrade live system
As Mark Newton wrote ... dannyman wrote: The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p 1. boot single-user 2. dd if=/some/dir/boot.flp of=/dev/da0s1b 3. reboot 4. When boot1 gives you the 5-second paused baton, press any key 5. enter da(0,b) at the Boot: prompt Us FreeBSD people can pretend we can do miniroot installs too :-) Not completely. You also need a standalone 'disklabel' before you can use a factory fresh disk. Like SunOS 3.x etc used. -- | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Sat, Aug 14, 1999 at 12:29:42PM +0200, Sheldon Hearn wrote: On Fri, 13 Aug 1999 17:51:10 MST, dannyman wrote: Uhmmm, what if we don't have a floppy drive? Then you probably have a CDROM drive or a network interface, both of which can be used to get sysinstall onto your machine. :-) The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p Or, the real point of it is, that aside from "make world from source" there is no good way to update an existing system without doing something lame like having to boot ... off ... a floppy ... uncompressing kernel ... please wait ... But, on to my original question, has anybody been looking at a more "user friendly" "upgrade the darn thing *REAL EASY*" kind of setup? maybe invoke a networked pkg_add to run the latest sysinstall w dependencies? -dman -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
dannyman wrote: The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p 1. boot single-user 2. dd if=/some/dir/boot.flp of=/dev/da0s1b 3. reboot 4. When boot1 gives you the 5-second paused baton, press any key 5. enter "da(0,b)" at the Boot: prompt Us FreeBSD people can pretend we can do miniroot installs too :-) [ admittedly, I haven't tried this since before the new boot blocks were committed, but it worked perfectly last year... ] - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Sat, Aug 14, 1999 at 12:29:42PM +0200, Sheldon Hearn wrote: On Fri, 13 Aug 1999 17:51:10 MST, dannyman wrote: Uhmmm, what if we don't have a floppy drive? Then you probably have a CDROM drive or a network interface, both of which can be used to get sysinstall onto your machine. :-) The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p Or, the real point of it is, that aside from make world from source there is no good way to update an existing system without doing something lame like having to boot ... off ... a floppy ... uncompressing kernel ... please wait ... But, on to my original question, has anybody been looking at a more user friendly upgrade the darn thing *REAL EASY* kind of setup? maybe invoke a networked pkg_add to run the latest sysinstall w dependencies? -dman -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
dannyman wrote: The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p 1. boot single-user 2. dd if=/some/dir/boot.flp of=/dev/da0s1b 3. reboot 4. When boot1 gives you the 5-second paused baton, press any key 5. enter da(0,b) at the Boot: prompt Us FreeBSD people can pretend we can do miniroot installs too :-) [ admittedly, I haven't tried this since before the new boot blocks were committed, but it worked perfectly last year... ] - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Mon, 16 Aug 1999 17:48:22 MST, dannyman wrote: The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p Presumably you saw the posted trick about dd'ing the floppy image to your swap partition and booting off _that_? :-) But, on to my original question, has anybody been looking at a more user friendly upgrade the darn thing *REAL EASY* kind of setup? maybe invoke a networked pkg_add to run the latest sysinstall w dependencies? Your original question? I started this thread. ;-) The best answer someone who is neither omniscient nor omnipresent can give you is I expect I'd be surprised to find that anybody was working on such a thing. Assume that further silence on the issue confirms that feeling. I've seen lots of people come up with ideas that they felt were good and worthy of lots of argument, but the ideas always seem to be all talk(1) and no diff(1). ;-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Fri, 13 Aug 1999 17:51:10 MST, dannyman wrote: Uhmmm, what if we don't have a floppy drive? Then you probably have a CDROM drive or a network interface, both of which can be used to get sysinstall onto your machine. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
Oh, that's incredibly cute. I've gotta remember that one. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: childrens-justice.org Tired of the broken divorce system in the United States and what it's doing to our kids? SIGN the online petition for equal parental - and children's - rights at the above URL. Make a difference in a kid's life today. Real-time chat now available from the above web page On Sat, Aug 14, 1999 at 10:00:29AM -0700, Nick Sayer wrote: dannyman wrote: Uhmmm, what if we don't have a floppy drive? Do the old SunOS trick: 1. Boot single user. 2. dd the boot floppy image to your swap partition. 3. Reboot, specifying wd(0,b)/kernel (or appropriate). ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Sat, 14 Aug 1999, Nick Sayer wrote: dannyman wrote: Uhmmm, what if we don't have a floppy drive? Do the old SunOS trick: 1. Boot single user. 2. dd the boot floppy image to your swap partition. To really do the ScumOS trick, you should just assume that the swap partition is sd(0,0,0)b. GRRR! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Fri, 13 Aug 1999 17:51:10 MST, dannyman wrote: Uhmmm, what if we don't have a floppy drive? Then you probably have a CDROM drive or a network interface, both of which can be used to get sysinstall onto your machine. :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
dannyman wrote: Uhmmm, what if we don't have a floppy drive? Do the old SunOS trick: 1. Boot single user. 2. dd the boot floppy image to your swap partition. 3. Reboot, specifying wd(0,b)/kernel (or appropriate). ? smime.p7s Description: S/MIME Cryptographic Signature
Re: Using legacy sysinstall to upgrade live system
Oh, that's incredibly cute. I've gotta remember that one. -- -- Karl Denninger (k...@denninger.net) Web: childrens-justice.org Tired of the broken divorce system in the United States and what it's doing to our kids? SIGN the online petition for equal parental - and children's - rights at the above URL. Make a difference in a kid's life today. Real-time chat now available from the above web page On Sat, Aug 14, 1999 at 10:00:29AM -0700, Nick Sayer wrote: dannyman wrote: Uhmmm, what if we don't have a floppy drive? Do the old SunOS trick: 1. Boot single user. 2. dd the boot floppy image to your swap partition. 3. Reboot, specifying wd(0,b)/kernel (or appropriate). ? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Sat, 14 Aug 1999, Nick Sayer wrote: dannyman wrote: Uhmmm, what if we don't have a floppy drive? Do the old SunOS trick: 1. Boot single user. 2. dd the boot floppy image to your swap partition. To really do the ScumOS trick, you should just assume that the swap partition is sd(0,0,0)b. GRRR! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, Aug 11, 1999 at 12:07:41AM -0700, Jordan K. Hubbard wrote: The use of /stand/sysinstall to do a live upgrade has always been discouraged, though it's not outright disallowed since I believe in every man's right to blow his feet off if he really wants to. Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. Uhmmm, what if we don't have a floppy drive? I suggested my colleague score /stand/sysinstall off one of my 3.2 systems so he could upgrade his 3.1. Has there been though put in to making a net-able upgrade set, maybe you have a sysinstall which pops the new kernel in to place, reboots into sysinstall like a floppy, and then gets ready to upgrade. Maybe we could use an MFS floppy? Might be a fun project to take on ... can one reboot into an MFS partition, or how hard would it be to try a "reboot system into upgrade floppy" without trashing the underlying system, in case the user wanted to bail ... maybe a kernel that chroot's itself into an /upgrade directory? Thoughts? -dman -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, Aug 11, 1999 at 12:07:41AM -0700, Jordan K. Hubbard wrote: The use of /stand/sysinstall to do a live upgrade has always been discouraged, though it's not outright disallowed since I believe in every man's right to blow his feet off if he really wants to. Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. Uhmmm, what if we don't have a floppy drive? I suggested my colleague score /stand/sysinstall off one of my 3.2 systems so he could upgrade his 3.1. Has there been though put in to making a net-able upgrade set, maybe you have a sysinstall which pops the new kernel in to place, reboots into sysinstall like a floppy, and then gets ready to upgrade. Maybe we could use an MFS floppy? Might be a fun project to take on ... can one reboot into an MFS partition, or how hard would it be to try a reboot system into upgrade floppy without trashing the underlying system, in case the user wanted to bail ... maybe a kernel that chroot's itself into an /upgrade directory? Thoughts? -dman -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
The use of /stand/sysinstall to do a live upgrade has always been discouraged, though it's not outright disallowed since I believe in every man's right to blow his feet off if he really wants to. Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, 11 Aug 1999 00:07:41 MST, "Jordan K. Hubbard" wrote: Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. Gotcha. So you'd be interested in diffs that teach sysinstall to bleat if an Upgrade is requested for a release for which the instance of sysinstall was not designed? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, 11 Aug 1999 17:08:10 CST, Wes Peters wrote: It's OK to let the users shoot their feet off, but they may not know they're about to shoot their feet off. Giving them an alert would be polite. I'll feel more comfortable about letting them shoot their feet off if you can point out _any_ way in which it might be beneficial for them to do so. :-) later, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Thu, Aug 12, 1999 at 01:10:44AM +0200, Sheldon Hearn wrote: I'll feel more comfortable about letting them shoot their feet off if you can point out _any_ way in which it might be beneficial for them to do so. :-) I suggest that it would be beneficial for you to let them shoot off their feet... I have used legacy sysinstall to upgrade a live multiuser system before and will probably do so again. In my dictionary, "bleet" translates to "warn". Just make sysinstall bleet as you originally offered and everyone will be happy. :-) Hmm... "bleet"'s not in esr's hacker dictionary. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, 11 Aug 1999 20:34:59 -0400, Tim Vanderhoek wrote: I suggest that it would be beneficial for you to let them shoot off their feet... I have used legacy sysinstall to upgrade a live multiuser system before and will probably do so again. Hair-raising. :-) Anyway, I've snuffled around in the code and I think I'd have to teach sysinstall what release it was built for before producing as comprehensive a warning as Wes was talking about. That'd be easy if I knew how VAR_RELNAME gets initialized. My take on the code made me think it's via kern.osrelease, but that doesn't seem to be the case. I've attached the diff I have on hand, but I'd obviously like to know how to do this properly. Hmm... "bleet"'s not in esr's hacker dictionary. My original spelling was "bleat". Ciao, Sheldon. Index: options.c === RCS file: /home/ncvs/src/release/sysinstall/options.c,v retrieving revision 1.62 diff -u -d -r1.62 options.c --- options.c 1999/08/05 19:50:26 1.62 +++ options.c 1999/08/12 01:04:16 @@ -95,7 +95,10 @@ #define TAPE_PROMPT"Please enter the tape block size in 512 byte blocks:" #define NEWFS_PROMPT "Please enter newfs(8) parameters:" -#define RELNAME_PROMPT "Please specify the release you wish to load or\n\"none\" for a generic release install:" +#define RELNAME_PROMPT "Please specify the release you wish to load or " \ +"\"none\" for a\ngeneric release install. Using an installed version " \ +"of sysinstall\nto install or upgrade to later releases is not " \ +"recommended." #define BPKG_PROMPT"Please specify the name of the HTML browser package:" #define BBIN_PROMPT"Please specify a full pathname to the HTML browser binary:" #define EDITOR_PROMPT "Please specify the name of the text editor you wish to use:" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
The use of /stand/sysinstall to do a live upgrade has always been discouraged, though it's not outright disallowed since I believe in every man's right to blow his feet off if he really wants to. Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, 11 Aug 1999 00:07:41 MST, Jordan K. Hubbard wrote: Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. Gotcha. So you'd be interested in diffs that teach sysinstall to bleat if an Upgrade is requested for a release for which the instance of sysinstall was not designed? Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
Sheldon Hearn wrote: On Wed, 11 Aug 1999 00:07:41 MST, Jordan K. Hubbard wrote: Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. Gotcha. So you'd be interested in diffs that teach sysinstall to bleat if an Upgrade is requested for a release for which the instance of sysinstall was not designed? Something like: +-- Doh! ---+ | | | You are trying to upgrade to FreeBSD 3.2 using a | | FreeBSD 2.0.5 installation program. This is doomed | | to fail. Please download the FreeBSD 3.2 install| | disk set, create install floppies, and run the | | upgrade from the 3.2 installation program. | | | | ++ +--+ | | | Cancel | | I feel lucky | | | ++ +--+ | | | +---+ would certainly be of value. It's OK to let the users shoot their feet off, but they may not know they're about to shoot their feet off. Giving them an alert would be polite. -- Where am I, and what am I doing in this handbasket? Wes Peters Softweyr LLC http://softweyr.com/ w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, 11 Aug 1999 17:08:10 CST, Wes Peters wrote: It's OK to let the users shoot their feet off, but they may not know they're about to shoot their feet off. Giving them an alert would be polite. I'll feel more comfortable about letting them shoot their feet off if you can point out _any_ way in which it might be beneficial for them to do so. :-) later, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Thu, Aug 12, 1999 at 01:10:44AM +0200, Sheldon Hearn wrote: I'll feel more comfortable about letting them shoot their feet off if you can point out _any_ way in which it might be beneficial for them to do so. :-) I suggest that it would be beneficial for you to let them shoot off their feet... I have used legacy sysinstall to upgrade a live multiuser system before and will probably do so again. In my dictionary, bleet translates to warn. Just make sysinstall bleet as you originally offered and everyone will be happy. :-) Hmm... bleet's not in esr's hacker dictionary. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, 11 Aug 1999 20:34:59 -0400, Tim Vanderhoek wrote: I suggest that it would be beneficial for you to let them shoot off their feet... I have used legacy sysinstall to upgrade a live multiuser system before and will probably do so again. Hair-raising. :-) Anyway, I've snuffled around in the code and I think I'd have to teach sysinstall what release it was built for before producing as comprehensive a warning as Wes was talking about. That'd be easy if I knew how VAR_RELNAME gets initialized. My take on the code made me think it's via kern.osrelease, but that doesn't seem to be the case. I've attached the diff I have on hand, but I'd obviously like to know how to do this properly. Hmm... bleet's not in esr's hacker dictionary. My original spelling was bleat. Ciao, Sheldon. Index: options.c === RCS file: /home/ncvs/src/release/sysinstall/options.c,v retrieving revision 1.62 diff -u -d -r1.62 options.c --- options.c 1999/08/05 19:50:26 1.62 +++ options.c 1999/08/12 01:04:16 @@ -95,7 +95,10 @@ #define TAPE_PROMPTPlease enter the tape block size in 512 byte blocks: #define NEWFS_PROMPT Please enter newfs(8) parameters: -#define RELNAME_PROMPT Please specify the release you wish to load or\n\none\ for a generic release install: +#define RELNAME_PROMPT Please specify the release you wish to load or \ +\none\ for a\ngeneric release install. Using an installed version \ +of sysinstall\nto install or upgrade to later releases is not \ +recommended. #define BPKG_PROMPTPlease specify the name of the HTML browser package: #define BBIN_PROMPTPlease specify a full pathname to the HTML browser binary: #define EDITOR_PROMPT Please specify the name of the text editor you wish to use: To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
