I used the following beep sequence to remotely play "Happy birthday" for a friend at his office through VPN.
beep -f 261.6 -n -f 261.6 -n -f 293.7 -n -f 261.6 -n -f 349.2 \ -n -l 500 -f 329.6 -n -f 1 -n -f 261.6 -n -f 261.6 -n -f 293.7 \ -n -f 261.6 -n -f 392.0 -n -l 500 -f 349.2 -n -f 1 -n -f 261.6 \ -n -f 261.6 -n -f 523.2 -n -f 440.0 -n -f 349.2 -n -f 329.6 \ -l 200 -n -f 293.7 -n -f 1 -n -f 523.2 -n -f 523.2 -n -f 440.0 \ -n -f 349.2 -n -f 392.0 -n -f 349.2
Since I first learned of rsync, copying files
have not been the same. If you do not know
rsync, you should read up
on it now.
Though I like
rsync I have always been a little bothered that there
was seemingly no way of forcing
rsync to count the total number of
files before transferring them, thus making the --progress option
partially useless. This time I did some research, and found that if
rsync is newer than version 3.1.0 there is an
From the rsync manual page:
--info=FLAGS This option lets you have fine-grained control over the information output you want to see. An individual flag name may be followed by a level number, with 0 meaning to silence that output, 1 being the default output level, and higher numbers increasing the output of that flag (for those that support higher levels). Use --info=help to see all the available flag names, what they output, and what flag names are added for each increase in the verbose level. Some examples: rsync -a --info=progress2 src/ dest/ rsync -avv --info=stats2,misc1,flist0 src/ dest/ Note that --info=name's output is affected by the --out-format and --itemize-changes (-i) options. See those options for more information on what is output and when. This option was added to 3.1.0, so an older rsync on the server side might reject your attempts at fine-grained control (if one or more flags needed to be send to the server and the server was too old to understand them). See also the "max verbosity" caveat above when dealing with a daemon.
--info=progress2 i get the following kind of output:
receiving incremental file list 0 0% 0.00kB/s 0:00:00 (xfr#0, ir-chk=1001/71529) Documents/development/projects/C/linux/cdcat/src/gcdCat/src/.deps/ 0 0% 0.00kB/s 0:00:00 (xfr#0, ir-chk=1000/71612) Documents/development/projects/C/linux/cdcat/src/gcdCat/src/CVS/ 0 0% 0.00kB/s 0:00:00 (xfr#0, ir-chk=1000/73443) Documents/ebooks/Humble bundle/ 0 0% 0.00kB/s 0:00:00 (xfr#0, ir-chk=1014/73485)
Which seem what I have wished for.
I will walk through copying a bootable Windows 7 installation from a VirtualBox VM to real iron.
- Insert an external hard drive in the USB port and share it with your Windows 7 VM.
- Ask windows to make a system image "Control Panel -> Back up your computer -> Create system image", and save it to the external hard drive.
- Boot the Windows 7 install disk, click through, and select "Repair windows installation". The drives that you do not put on the exclude list, will be repartitioned and formatted, so make sure to exclude everything you want to keep.
- Let it chew on your backup, and when done, boot Windows.
On Gentoo I needed to point the configure script at libbfd.so. On my
system it is in
./configure --prefix=/usr/local/ --with-bfd=/usr/lib/binutils/x86\_64-pc-linux-gnu/2.22/
I have found this tool indespensible, when finding unforseen errors in complex makefiles.
Generated on 2018-05-03 01:14:21.924635