Re: Re: Disk Cloning
On 28 Sep 2009 15:02, Giorgos Keramidas keram...@ceid.upatras.gr wrote: On Mon, 28 Sep 2009 01:14:44 -0500, Chris rac...@makeworld.com wrote: Greetings, Please suggest a cloning method comparable to Clonezilla. Preferably fast, no need to install a base OS, easy to clone and restore. Of course, the key is fast. Clonezilla does a nice job with OS's other than *BSD (It uses dd (iirc)) and that takes forever (at least when cloning - have not tried a restore). Some specs I'm using to compare: A typical restore/save currently with other OS's using CloneZ takes about 12 minutes with a simple boot from CD. The restored/imaged drive is 400 meg sata. A dump restore of a 400 MB system should be *very* fast. Copying files from a read-only USB flash disk easily reaches speeds of more than 20 MB/sec on my laptop. This means that 400 MB of data should take around 20 seconds to copy from an external USB disk. If you can attach both disks at the same time, eg the source disk as ad0 and the target disk as ad1, it should take less than 2-3 minutes to: * Enter single user mode * Partition and mount ad1 under /mnt * Use dump(8) to save data from ad0 and restore(8) to copy them over to ad1. Even if you cannot attach both disks at the same time, but you can access the source disk over the network, it should be possible to: * Install the target disk on the target host (host2). * Boot from a rescue image (CD-ROM, DVD-ROM or USB). * Bring up a network interface to access the source host (host1). * Partition the ad0 disk of the target host (host2). The standard fdisk(8), bsdlabel(8) or gpart(8) utilities can do this. * Tunnel dump over ssh: host2# cd / host2# ssh opera...@host1 'dump -0a -C32 -L -f - /' | restore -rf - I might add that if network speed is an issue, it may be worth adding a gzip in there; host2# ssh opera...@host1 'dump -0a -C32 -L -f - / | gzip' | gunzip | restore -rf - Just be careful where you put the quotes! Dump is excellent, especially the -L flag for a live filesystem. I can't believe how few OSes don't have snapshot functionality; it's absolutely essential for me. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re: Dump/Restore?
On 14 Sep 2009 02:50, Chris Maness ch...@chrismaness.com wrote: On Sun, Sep 13, 2009 at 6:15 PM, Chris Maness ch...@chrismaness.com wrote: I level 0 dump of my server. I lost a file that I need back. Is it possible to use restore like tar and explode it into a directory instead of a pristine partition/mount? Or even better, is it possible to just extract a single file without exploding the whole tape dump? Sorry if the question seems stupid. Chris KQ6UP Sorry, I was reading the restore man from my mac, and it was not as clear. The restore does not seem to work from my mac (this is where my backup dumps reside as I have two massive HDs). I guess the mac restore would only work with HFS+ and not UFS. I guess the only way would be to move the massive dump file back over to the FreeBSD server. Thanks, Chris KQ6UP ___ Try using NFS or cat over ssh, something like $ ssh my_mac 'cat dumpfile' | restore -if - restore treats the file as a tape, so it doesn't pull any bytes until you ask it to. This should be the least network intensive way of doing it Good luck! Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re: Dump/Restore?
On 14 Sep 2009 22:38, Richard Mahlerwein mahle...@yahoo.com wrote: --- On Mon, 9/14/09, Polytropon free...@edvax.de wrote: From: Polytropon free...@edvax.de Subject: Re: Dump/Restore? To: mahle...@yahoo.com Cc: freebsd-questions@freebsd.org, Chris Maness ch...@chrismaness.com Date: Monday, September 14, 2009, 4:37 PM On Mon, 14 Sep 2009 05:45:01 -0700 (PDT), Richard Mahlerwein mahle...@yahoo.com wrote: In the restore : prompt you can add to add it to the restore list. Works with folders, too. Excuse me, just a little terminology note: FreeBSD has directories, not folders. It doesn't have sheets of papers instead of files, too. :-) Pie on my face. I work too much with multiple operating systems. *sigh* BTW, I also work and develop heavily with a (non BSD, non-open source) document imaging and workflow management software, so you probably will, at some point, see me confuse files and sheets of paper. I will not mind a gentle reminder just like the above when I do that . :) Yeah, unfortunately I still think of 'folders', and am continually wrong-footed by the term 'directory' in a graphical environment, even after years of GNU and FreeBSD use. I have all sorts of strange habits that many will recognise as symptoms of multi-booting and running servers. There's no shame in that! Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re: Dump/Restore?
On 14 Sep 2009 23:14, Polytropon free...@edvax.de wrote: On Mon, 14 Sep 2009 22:02:49 +, utis...@googlemail.com wrote: Yeah, unfortunately I still think of 'folders', and am continually wrong-footed by the term 'directory' in a graphical environment, even after years of GNU and FreeBSD use. Just imagine if the Xerox Alto and its first GUI wouldn't have been invented in the US, but in Germany. Then we would refer to ring binders or lever arch folders, or ordners or actenordner (the german word is der Ordner or der Akten- ordner). Surely, this would be the default symbol: http://www.officexl.de/kopierpapier/images/ordner.jpg And all paper sizes defaults would refer to DIN A4 in the first place... what a beautiful imagination! :-) I have all sorts of strange habits that many will recognise as symptoms of multi-booting and running servers. There's no shame in that! Please don't get me wrong: There are correct places to use the term folder, eg when talking about mail folders (which can be represented as files (mbox) or directories with files (MH) on the disk level). But in the case discussed, directory is the correct term. There's no need to change proven terminology just because some company indoctrinates you to do so. :-) How important it is to use the correct terminology is when users start asking you questions about their modems (refers to PC), their TV and their brains (refers to speakers), or start complaining that the file system is too big (refers to the icon size in the file manager used), and want the same pictures at home as I have them at work (refers to the OS). To sum it up in quite your own words: I have all sorts of strange habits that many will recognise as symptoms of asperger's syndrome. There's no shame in that! :-) Certainly no shame in that, but also one should be corrected on errors of terminology. Sorry if I didn't make that clear (I didn't!). I merely meant to point out that the best of us make terminological errors, and that it's all part of our 'diversity'. However, you were still right to correct the term IMO. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re: Automatic screen lock when leaving desk
On 14 Jul 2009 21:43, Chad Perrin per...@apotheon.com wrote: On Tue, Jul 14, 2009 at 05:32:01PM +0200, Frederique Rijsdijk wrote: Hi, I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? Why does it have to be automatic? Something like xlockmore or slock can be tied to a keyboard shortcut, such as ++. If for some reason you require automatic locking, though, you could perhaps set up some kind of Bluetooth connection detection if you have a Bluetooth enabled cellphone in your pocket (or something else that would work as a Bluetooth token) and if your computer has the right hardware. I imagine writing a daemon in Perl or Ruby that checks for loss of a Bluetooth connection would be easier than getting Bluetooth working in the first place might be, depending on the state of Bluetooth support in FreeBSD. I'm not really well-versed in the ephemera of what is used to determine inactivity on a computer, but if it's reasonably easy (or if there's a Perl module for it), that seems like the obvious way to handle it -- though of course that may present problems, such as false positives on detecting inactivity when watching a movie on the computer or something like that. Although it would ravish your cellphone's battery Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
