Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On 2014-08-22, Maurice McCarthy m...@mythic-beasts.com wrote: Hi, /boot is found by block number and offset of its inode so I think the root partition should be copied using dd. It may be easier to installboot(8) after copying.
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On Sat, Aug 23, 2014 at 6:21 AM, Stuart Henderson s...@spacehopper.org wrote: It may be easier to installboot(8) after copying. Yeah I used installboot -- Don't eat anything you've ever seen advertised on TV - Michael Pollan, author of In Defense of Food
Cloning an OpenBSD system (and potential FAQ (4.15) error?)
Hi folks, I've done this a (n exaggerated) million times on Linux but I'm new at OpenBSD. Google found me a few options and I just want to see whether there are any more that I missed. FAQ 4.15 addresses this matter and says : Unfortunately, there are no known disk imaging packages which are FFS-aware However my googling turned up http://clonezilla.org/, and their FAQ claims that they understand UFS. More googling tells me that UFS and FFS are the same thing. However I have not yet tried Clonezilla. I have also found this : http://www.ualberta.ca/~antoine/clone/openbsd.html Also looks promising. I like the looks of the latter since it seems to allow me to run the first part on a live system, to make a copy of that system (can anyone confirm that?). I'd much rather not have to take it down to make the image since I don't have to do that when I clone Linux. And my production systems will be happier that way :-) Clonezilla looks to be all-singing-all-dancing, but seems to require me to boot from their CD or USB in order to make a copy of my original system (can anyone confirm or refute?). Not a massive issue in my DEV rack but not ideal in production. In Linux the way I do systems is to boot the target system in Live Linux (Ubuntu), and then partition the HD(s) the way I want, and mount them up under /mnt/target/ with that being my root. Then run rsync locally to copy the master live system into /mnt/target. Use a couple of options to tell it what not to copy. Works awesome. The above perl scripts from U Alberta seem to be at least a bit similar to this procedure. Are there any options I am missing that I should look at? Has anyone used the above methods and can comment on how well they work or whether or not I should just avoid one or the other? thanks, -Alan -- Don't eat anything you've ever seen advertised on TV - Michael Pollan, author of In Defense of Food
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On Fri, Aug 22, 2014 at 10:04:28AM -0400, Alan McKay wrote: Hi folks, I've done this a (n exaggerated) million times on Linux but I'm new at OpenBSD. Google found me a few options and I just want to see whether there are any more that I missed. FAQ 4.15 addresses this matter and says : Unfortunately, there are no known disk imaging packages which are FFS-aware However my googling turned up http://clonezilla.org/, and their FAQ claims that they understand UFS. More googling tells me that UFS and FFS are the same thing. However I have not yet tried Clonezilla. I have also found this : http://www.ualberta.ca/~antoine/clone/openbsd.html Also looks promising. I like the looks of the latter since it seems to allow me to run the first part on a live system, to make a copy of that system (can anyone confirm that?). I'd much rather not have to take it down to make the image since I don't have to do that when I clone Linux. And my production systems will be happier that way :-) Clonezilla looks to be all-singing-all-dancing, but seems to require me to boot from their CD or USB in order to make a copy of my original system (can anyone confirm or refute?). Not a massive issue in my DEV rack but not ideal in production. In Linux the way I do systems is to boot the target system in Live Linux (Ubuntu), and then partition the HD(s) the way I want, and mount them up under /mnt/target/ with that being my root. Then run rsync locally to copy the master live system into /mnt/target. Use a couple of options to tell it what not to copy. Works awesome. The above perl scripts from U Alberta seem to be at least a bit similar to this procedure. Are there any options I am missing that I should look at? Has anyone used the above methods and can comment on how well they work or whether or not I should just avoid one or the other? thanks, -Alan What about automated installation and configuration management to do the rest? j.
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On Fri, 22 Aug 2014 10:04:28 -0400 Alan McKay alan.mc...@gmail.com wrote: Hi folks, Hi! I have also found this : http://www.ualberta.ca/~antoine/clone/openbsd.html Also looks promising. this seems to be helper/wrapper scripts around dump. dump(8) is the way to go. I usually do dump -0auf 140822var.dump0 /var for dumping /var in a file or dump -0auf - /var |nc -l 1 on source and restore -rf - |nc source 1 for cloning a partition over the network. I like the looks of the latter since it seems to allow me to run the first part on a live system, to make a copy of that system (can anyone confirm that?). I'd much rather not have to take it down to make the image since I don't have to do that when I clone Linux. And my production systems will be happier that way :-) This will work. I can confirm that. dump can dump from mounted as well as unmounted filesystems. Clonezilla looks to be all-singing-all-dancing, but seems to require me to boot from their CD or USB in order to make a copy of my original system (can anyone confirm or refute?). Not a massive issue in my DEV rack but not ideal in production. In Linux the way I do systems is to boot the target system in Live Linux (Ubuntu), and then partition the HD(s) the way I want, and mount them up under /mnt/target/ with that being my root. Then run rsync locally to copy the master live system into /mnt/target. Use a couple of options to tell it what not to copy. Works awesome. The above perl scripts from U Alberta seem to be at least a bit similar to this procedure. Are there any options I am missing that I should look at? Has anyone used the above methods and can comment on how well they work or whether or not I should just avoid one or the other? after restoring / copying the filesystems using dump/restore and fixing up /etc/fstab on the target system, you'll need to install boot. see installboot(8). Christopher -- http://gmerlin.de OpenPGP: http://gmerlin.de/christopher.pub F190 D013 8F01 AA53 E080 3F3C F17F B0A1 D44E 4FEE [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
Hi, /boot is found by block number and offset of its inode so I think the root partition should be copied using dd. See http://www.openbsd.org/faq/faq14.html sections 14.7 and 14.20 in particular. Can't help otherwise. Good Luck Moss
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
Wow, thanks for the responses so far! An ancilliary question : am I going to have any issues bringing it up in a VM? I know that for example NIC names will change so I'll have to rename hostname.bnx0 to hostname.em0 Any other gotchas?
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On Fri, Aug 22, 2014 at 10:22 AM, Jiri B ji...@devio.us wrote: What about automated installation and configuration management to do the rest? What is this? -- Don't eat anything you've ever seen advertised on TV - Michael Pollan, author of In Defense of Food
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On Fri, Aug 22, 2014 at 10:37 AM, sven falempin sven.falem...@gmail.com wrote: Openbsd is simple, you may easily script an install or use the automated install feature.IE a file containing the answer to the install process. And finally siteXX.tgz to push your own file. Oh OK I missed that. Yes, we do this actually. But I need to clone/move a system that was created outside of that infrastructure. I'm actually working towards pulling it into the automated installs and cloning/moving it is part of that. We've got a pretty slick system with svn and maven for doing this. Just one outlier that needs to be brought in. -- Don't eat anything you've ever seen advertised on TV - Michael Pollan, author of In Defense of Food
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On Fri, Aug 22, 2014 at 10:33 AM, Alan McKay alan.mc...@gmail.com wrote: no toher gotchas depends the vm and the machines but nothing more. vnconfig is cool, mount virtual disk, if your vm system allow raw format On Fri, Aug 22, 2014 at 10:22 AM, Jiri B ji...@devio.us wrote: What about automated installation and configuration management to do the rest? What is this? Openbsd is simple, you may easily script an install or use the automated install feature.IE a file containing the answer to the install process. And finally siteXX.tgz to push your own file. -- Don't eat anything you've ever seen advertised on TV - Michael Pollan, author of In Defense of Food -- - () ascii ribbon campaign - against html e-mail /\
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On Fri, Aug 22, 2014 at 10:28 AM, Christopher Zimmermann chr...@openbsd.org wrote: I usually do dump -0auf 140822var.dump0 /var for dumping /var in a file or dump -0auf - /var |nc -l 1 on source and restore -rf - |nc source 1 OK I want to try this so that I have better control of things and understand it all better On the restore side I guess I have to have the new /var mounted in the cwd where I run this command? e.g. mkdir /mnt/var chmod 0777 /mnt/var mount /dev/foo /mnt/var cd /mnt/var and shouldn't the restore/nc be the other way around? So now : nc source 1 | restore -rf - Also, I have the OpenBSD install CD booted and I exited to shell, but there does not seem to be an nc there. What are you booting on the restore side? And do you have the -l option on the correct end up there? I'm relatively new to nc as well but man page says that is listen for incoming connection -- Don't eat anything you've ever seen advertised on TV - Michael Pollan, author of In Defense of Food
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
On Fri, Aug 22, 2014 at 11:07 AM, Alan McKay alan.mc...@gmail.com wrote: Also, I have the OpenBSD install CD booted and I exited to shell, but there does not seem to be an nc there. What are you booting on the restore side? Looks like this problem is easily solved thus : http://livecd-openbsd.sourceforge.net/ Is that a trustworthy product? And the intricacies of dump/restore/nc I can work out on my own ... -- Don't eat anything you've ever seen advertised on TV - Michael Pollan, author of In Defense of Food
Re: Cloning an OpenBSD system (and potential FAQ (4.15) error?)
Clone worked great with the LiveCD booted in the destination, and dump/restore/nc I will be happy to document it for the FAQ if anyone wants it there. Not sure what the process is for that. And I will also be happy to update the FAQ regarding the aforementioned error. Now, I do have one problem with the cloned system, but I'll start a new thread for it.
