en-us http://www.keithwatanabe.net/index.php Keith Watanabe's Website http://www.keithwatanabe.net/blogs/2004/3/13/91540508929191c8a466dc1bad8804c7.html Sat, 13 Mar 2004 02:34:43 -0700 http://www.keithwatanabe.net/blogs/2004/3/13/91540508929191c8a466dc1bad8804c7.html http://www.keithwatanabe.net/blogs/2004/5/11/811ae67b903b10dab03b0f19bf3dbb37.html Tue, 11 May 2004 21:26:22 -0600 http://www.keithwatanabe.net/blogs/2004/5/11/811ae67b903b10dab03b0f19bf3dbb37.html http://www.keithwatanabe.net/blogs/2004/5/11/96fed81b37a3469d135dcbdc3c516f4d.html $compressedfile.tar.gz if you're doing this from a script rather than command line, you have to note that you'll need to change directories into parent directory of the directory you want to tar up. For instance: cd /home/mydir; /usr/bin/tar -cvf - important_dir | gzip -c > important_dir.tar.gz In this case, you can put something like this into crontab if you need to do a nightly backup.]]> Tue, 11 May 2004 21:30:50 -0600 http://www.keithwatanabe.net/blogs/2004/5/11/96fed81b37a3469d135dcbdc3c516f4d.html http://www.keithwatanabe.net/blogs/2005/6/27/7d6f1e9f41cd0ac663b898b8ac6dfe4a.html Mon, 27 Jun 2005 15:33:54 -0600 http://www.keithwatanabe.net/blogs/2005/6/27/7d6f1e9f41cd0ac663b898b8ac6dfe4a.html http://www.keithwatanabe.net/blogs/2005/9/13/3a62cbf01d43c842dd635d1c297c42fa.html 2) copy files 3) mkisofs -r -o cd_image where: cd_image is the name of the file you want to create for burning as a data file. 4) cdrecord -scanbus (shows your device driver for your cd recorder) 5) note the node (e.g. 0,0,0) 6) cdrecord -v speed=16 dev=0,0,0 -data cd_image (creates the cd from the cd_image you generated) 7) note: use -overburn in case you are a little over the warning amount.]]> Tue, 13 Sep 2005 23:40:23 -0600 http://www.keithwatanabe.net/blogs/2005/9/13/3a62cbf01d43c842dd635d1c297c42fa.html http://www.keithwatanabe.net/blogs/2005/12/6/557f70ea8de17899feb9cc19cd235995.html to get a listing of users. but the handy dandy piece is fuser -k. that'll send a SIGKILL signal to those processes. unfortunately, that still didn't resolve my issue. those processes (namely automount and xine) still persisted. so the next thing to try was umount -l on the external drive. that's a lazy umount that somehow allows you to unmount a device and let the processes, etc. accessing that device get cleaned up later. so in the end, that saved my ass. on the side, xine has really pissed me off. on core 1, it worked beautifully. somehow the upgrades caused some issues that cause problems with the process. i suggest not using xine for playing dvds. other formats don't show this issue though.]]> Tue, 06 Dec 2005 01:40:25 -0700 http://www.keithwatanabe.net/blogs/2005/12/6/557f70ea8de17899feb9cc19cd235995.html http://www.keithwatanabe.net/blogs/2008/1/28/cfe181ec2bae0e8094aebc7d208f3e93.html patch utility. Actually, I got to work with a combination of the unix utilities diff and patch. I've found various good tutorials on the subject to get me started. Right now, I'm doing some simple patch creation. In the easiest form, you can create a patch from two files using diff like this:

diff -c original_file new_file > patch.diff

Apparently, the "-c" options allows for some context based mode that will allow the patch program to have an easier time patching your code. Also, the order of running the diff is critical. If you do this in the wrong order, patch will just give you a warning message and create a kind of backup file with the .orig extension.

Using the patch file, you would do something like this:

patch original_file -i patch.diff

The "-i" option tells patch the input file (i.e. the patch file).

You can also diff directories in creating a patch. I didn't succeed very well at that, but I'll put up my results once I become an expert in that area.

With Subversion, you can perform even more powerful patches by using Subversion's diff utility and comparing the repository items against a file or even directories. I had some issues getting this to work, but I think my biggest issue was the ordering of the diff. I kept getting the .orig extensions, signifying that patch did not work as expected. Well, I'll try again another day as I really want to become an expert at these subject matters.

On a side note, it's a real bitch mastering so many different technologies. You learn one tool, then you find out that you have to learn around 10 more related ones. On a positive note, I'm getting to the point where I feel very comfortable with a large number of tools. These are just another feather in my cap.]]> Mon, 28 Jan 2008 06:55:36 -0700 http://www.keithwatanabe.net/blogs/2008/1/28/cfe181ec2bae0e8094aebc7d208f3e93.html