On 12/23/2011 07:44 AM, Thomas Jeunet wrote:
On Fri, Dec 23, 2011 at 06:19, Barry Grumbine<[email protected]> wrote:
On Thu, Dec 22, 2011 at 3:29 PM, Corey<[email protected]> wrote:
On 12/21/2011 06:46 PM, Stuart Henderson wrote:
On 2011-12-21, Corey<[email protected]> wrote:
On 12/20/2011 11:16 AM, Stuart Henderson wrote:
Then afterwards, can I check out the -current branch from CVS as
I do with -stable? i.e. # cvs -d$CVSROOT checkout -P src
Or am I not supposed to fetch& build -current at all? Would it
You can checkout src if you want, but you don't have to,
you can just install the binary sets just as you would for a release
be safer to just download the /snapshots/i386/install50.iso every
couple weeks and do a fresh install every time? I guess I will
There's really no need for fresh installs, upgrades work very well
No need for install*.iso either, just download a new bsd.rd and
boot that from the boot loader (boot /bsd.rd) and do a network
upgrade install
Out of curiosity, is this more efficient and/or less loading on the
servers than downloading the iso (assuming one installs all sets)?
Doesn't make a lot of difference server-side but I know it's a lot
easier for me to boot a different kernel and point it at a (possibly
locally mirrored or pre-downloaded) set of files than it is to
download an iso, burn a cd and boot from it - I imagine this is
the case for most people.
Ah...ok. I'm usually following -current on only one or two machines, so I
never really thought of setting up a local mirror (though there may be
other
advantages to doing that). How do you keep your local file mirror in sync
with newer kernels/snapshots? Or do you do the local repo and the kernel
somewhat independently, and just try new kernels (and read release notes)
and see if stuff breaks?
C
Hi there,
I just wanted to chime in with an alternate perspective. I've been
running snapshots for two or three years now. Here's my procedure:
1. download installXX.iso
2. mount installXX.iso (http://openbsd.org/faq/faq14.html#MountImage)
3. cp /mnt/5.0/i386/bsd.rd /
4. cp -R /mnt/5.0 /
5. reboot
6. boot> boot bsd.rd
7. Upgrade
For "Location of sets?" type "disk"
For "Is the disk partition already mounted?" say "yes"
8. After reboot use sysmerge and pkg_add -ui
This works very nicely for me.
I came across this method two or three years ago when I got tired of
burning CDs.
Also, I pay attention to when the latest snapshot packages were built,
and try to pick a snapshot close to that date.
BTW, this works for release->release, release->snapshot,
snapshot->snapshot, I even successfully went from i386 to amd64 once,
but I guarantee that is an unsupported move... haven't had the huevos
to try it yet, but I think I could even get away skipping a release
(eg. 4.8->5.0).
If you use sysmerge and pay attention to the upgrade instructions
(http://openbsd.org/faq/upgrade50.html) life is good. sysmerge kicks
some serious ass..
-Barry
For the record, i use a similar method.
1. snapdl (in ports, sysutils/snapdl)
For "Path to download sets? (or 'pretend' )" type "/5.0/amd64"
(adjust accordingly version and arch)
2. reboot
3. boot> boot /5.0/amd64/bsd.rd
4. Upgrade
For "Location of sets?" type "disk"
For "Is the disk partition already mounted?" say "yes"
5. After reboot use sysmerge and pkg_add -ui
By the way, the following diff would save me one keystroke but I don't
know how many use external disk or store upgrade sets on another disk
than the one used to boot.
Index: install.sub
===================================================================
RCS file: /cvs/src/distrib/miniroot/install.sub,v
retrieving revision 1.655
diff -u -p -r1.655 install.sub
--- install.sub 22 Nov 2011 14:02:14 -0000 1.655
+++ install.sub 23 Dec 2011 13:41:33 -0000
@@ -1447,7 +1447,7 @@ install_cdrom() {
}
install_disk() {
- ask_yn "Is the disk partition already mounted?"
+ ask_yn "Is the disk partition already mounted?" y
if [[ $resp == n ]]; then
get_drive "disk" '$(bsort $(get_dkdevs))' \
'$(bsort $(rmel $ROOTDISK $(get_dkdevs)))' || return
Regards,
Cool, good ideas. I usually do the image mount of the installXX.iso as
Barry describes in a VM that has a USB stick as the main disk, do the
install/upgrade, copy the tarred sets over to it, then use it to go
upgrade any other machines I need to do. I was going to play with
setting up a DHCP/TFTP server in that USB stick image so I could plug it
into any handy machine (or use a VM), change a few network interface
settings, and netboot machines to be upgraded from it, but haven't
gotten around to that yet.
I'll investigate snapdl, but my preference usually is to use the
standard tools if they work adequately. I may have to set up that local
mirror :) Thanks guys for the info.
Heh -- I just wonder: how many other systems can you upgrade by
untarring sets to a running system? Try that with Windows :)
Corey
