Still running…

Might have to newfs this one and say screw it.

-Lightningcrash

Now if they only made baby clothes with Quake logos…

-LightningCrash

So I get everything in the board. I use a spring-screw heatsink mounting system that I bought. It works great.

Now I lay my computer down and just set the board on top of the chassis, supported by the motherboard box. I move the power cables over. I move the GT 220 over and plug the HDMI in. I use some RAM of mine I had extra (part of the 8GB DDR2-800 I got for $90 back in the day)

I hit the power button with a screwdriver…. Fans spin up, C&Q is bumping the CPU fan, but….      nothing.

So at this point I’m guessing the E7200 is the problem.

I have made arrangements with a [H]ard|Forum member to purchase his E6750, I will soon try that and report back. I have taken some Ibuprofen for the headache.  

Until next time!

-LightningCrash

I place the chip in my D975XBX, and the system doesn’t boot.

I put my old processor back in, and two pushpins on my heatsink break.

So I bundle up the wife and kids and run out to buy a new heatsink at Bestbuy. The heatsink does not make contact with the chip when attached. I don’t know what the crap was wrong with it, I tried it several different times, different directions until I finally realized it uses the same pin setup as my old heatsink.

So I pull two pushpins from the new heatsink to replace the broken ones on the old heatsink. One more pushpin is on its way to breaking, so I replace it too. I plop down on my laptop and look up my board revision’s C2D support. Well, I’m at revision 302 and I need 303 or 304 to be C2D-compatible at all. Even then, only the E6xxx series seem to work (and some E4xxx series). Definitely no E7200.

So I put the old CPU (a Pentium D 950) back into the unit and get it all seated. System boots up and I’m back up.

At least I’m right back where I started, and it only cost me $60 to not go anywhere.

-LightningCrash

Many people just forget that xargs can fork processes, to multithread an otherwise slow operation.

If you have a directory full of WAV files you want to encode and a quad core, fork that.

ls *.wav|xargs -n1 -P4 -i lame -h {} {}.mp3

rename ’s/\.wav//g’ *.mp3

The -P option is for the maximum number of processes. The -n option is to limit to 1 argument per xargs call.  The -i option gives us the {} substitution. Xargs will substitute the filename for {}. This means we get an output file called blah.wav.mp3, so I added the Perl utils rename step.

xargs has many uses with forking, and you could probably even use a VAAPI-enabled mencoder to transcode a whole directory of files this way.

Just don’t fork yourself or you’ll go blind.

Until next time!

-LightningCrash

It would really be the next logical step in police data collection. Take a warrant for arrest, pull phone records for $30, intercept the guy on his way home from his dealer’s house.
This wouldn’t be a burden placed upon the police, or even the NSA. It would be a money-maker for the telcos.
Lat/Lon can be packed as a 32-bit integer, unix timestamp is a 32-bit signed integer. Add in the telephone number and we’ll just call it 128 bits per reading.
Minutes in a day, 1440, so 1440×128 = 184,320 bits. 23,040 bytes per day.
As you can see, data warehousing for this is next to nothing. An 8GB disk could hold 372,827 days worth of GPS readings.
A day’s worth of GPS data for 30M users would be 675GB raw, before decompression and deduplication.
That would be a pretty tall order for a small business, but if you add in a few hundred legal spying data purchases every day, it would pay for itself pretty quickly.

You’d need a small cluster of servers and you would likely need good SAN hardware. They already store more information than this about the calls that you make. They already have the infrastructure in place.

So is it feasible? Yes, without a doubt.

Until next time!

-LightningCrash

I had a folder full of files that I wanted to rename, but I wanted to test things out first. I had settled for making a temporary directory and just symlinking to the files that I wanted to modify. I would run my tests, look at the link names, then delete and recreate the links.

Well, that is no more. `rename` has an option -n, for “No Act”, that will not actually rename the files. Instead, it will just print the filenames that matched and what they would have been renamed to.

Perfect!

Anyway, as the old saying goes, RTFM!
-LightningCrash

I hope to get a few more articles up soon, including finishing the series on find-fu.

Peace!

-LightningCrash

Now for the second installment of your `find` fu mastery! We are going to cover four principles today:

1. Learning to use object types
2. Using command execution
3. Using `find` to delete files
4. Limiting search depth

With no further ado,

1. Using object types in `find`

In the Linux/Unix filesystems there are more things than plain old regular files. Among then are symbolic links, directories, named pipes, block devices, character devices, and sockets. `find` will let you specify these items.

For instance, if I am looking for the baseq3 directory of my Quake3 installation, I can do the following:

find / -type d -name 'baseq3'

If I am looking for all symbolic links in a directory, I can do the following:

find . -type s

If I am looking for only files, I can specify ‘-type f’. This is handy by itself, but becomes more useful as you are executing commands for each of your search results. Which brings us to…

2. Using Command Execution

This is probably one of the most useful things that `find` has to offer. This is also one of the easiest ways to screw up your system and/or your day’s work. You have to be careful with this. Fortunately, `find` puts options in to help with that. We’ll cover those in a moment after we give some basics of command execution in `find`.

I have a directory full of PHP source code and I want to issue a find/replace on every file in the entire hierarchy to change a setting. The setting’s value is 12345 and I want to change it to 67890. You use the -exec option , put your command in, substitute the filename with {}, and put \; to denote the end of the command. Let’s take a look:

find ./ -type f -exec perl -pi -e 's/12345/67890/g' {} \;

This works great, except how do I know I’m not executing something that I don’t want to? Well,`find` has this covered with the ‘ok’ option.

find ./ -type f -ok perl -pi -e 's/12345/67890/g' {} \;

This will now prompt you to OK everything that is done, line by line. Useful for if you’re going to do something where you’d like to know which files it’s operating on. However, `find` will truncate part of the command if it’s too long, so you don’t get to see exactly what it’s doing. You can always put an echo in front of your commands to see them in their entirety before you execute them.

`find` also has an -execdir and -okdir command, which operate in a different manner. -execdir operates as if you `cd` into the directory and then run the command. This can be handy if you don’t want to do the filename substitution with {}, maybe you want to run something inside every directory. If you have a directory full of source called src, and maybe you want to run the `make` command to compile everything, you could issue a `find` statement like so:

find ./src -type d -execdir make all \;

This is a bit messy but it illustrates my point.

 3. Using `find` to delete files

Speaking of dangerous operations, here’s another one you need to be very, very careful with.

But the easiest way to illustrate this would be to say maybe you downloaded a package for installation that contained a number of files that you do not want at all. Some shared packages come with .nfo files, .txt, .installs, .sfx, .subs, all sorts of unwanted garbage that you rarely want. Let’s allow `find` to delete that garbage, shall we?

I’m going to make these .sfx files disappear…

cd ~/Downloads/package/


find ./ -type f -name '*.sfx' -delete

Ta-da!

:jokerface:

4. Limiting Search Depth

So maybe you want to only go one directory deep. Maybe you don’t want to descend into any directories with your search. Maybe you want to search a filesystem without having `find` hop onto other drives in its search. `find` has got you covered like a fire team.

Descend only one directory:

find ./ -maxdepth 1

Don’t descend at all:

find ./ -maxdepth 0

Don’t search on filesystems or drives other than the current one:

find ./ -xdev

The above is particularly useful if you have a jump drive of some sort mounting in an inappropriate place.

Wrapping up.

Can you snatch the pebble from your filesystem’s hand?

We train again later, grasshopper.

-LightningCrash

Introduction:

Among the tools you will use on a Linux system, few are more valuable than the find utility from findutils. Forget search bars: This is a more highly tailored search system that can help you find exactly what you’re looking for with great ease. It will also permit you to perform operations upon the files that you find, delete them, or just list them. If you do more than just browse the Internet with your Linux box, you need some sort of proficiency with find.

Basics:
Find, at its simplest, will list everything in the filesystem beneath your current directory. This includes files, directories, symbolic links, FIFOs, sockets, and more other crap than you probably care to know about. Over 95% of your usage is going to be finding files and directories, so we’ll focus there.
If you open up a terminal and type
cd
find
You’ll receive a list of everything in the filesystem below your current directory.
Let’s limit that some. Let’s search for files that end in mp3.
find -name '*.mp3'

But wait, I know I had a file that ended in .MP3, why didn’t it show up? Well, the -name test is case sensitive. -iname is not. Let’s do the same thing with iname.

find -iname '*.mp3'

Ahh, there it is.
I want to search my videos directory for the video of my friend’s birthday party. I know it was named Fred-something. Now I can introduce a directory in the search.

find ~/Videos/ -name '*Fred*'

Hah. Fred is silly.

Well, that’s the most basic that you’ll get with find, grasshopper. Now you must prove your skills to the sensei!

Well, sort of. You just have to wait for the next part of the series.

-LightningCrash

(This is the first part in a three part series. Read part two here.)