Strav's blog

Yet another thing that drives me nuts about XP. I'm sick of having to tell the system over and over that I actually DO want to run the program that I just executed. This will prevent that dialog box from popping up every time you try to run a new file on the system.


Run gpedit.msc, and go to
Local Computer Policy
 ->User Configuration
  ->Administrative Templates
   ->Windows Components
    ->Attachment Manager
Enable "Default risk level for file attachments"
Enable "Inclusion list for low risk file types"
Add the file extensions that you want to open without being bothered.

I'll update this list if I make additions to it.

Ack!!!! I finally figured out why udev wasn't working on the laptop. It turns out that the symlink I made from the /etc/udev/rules.d directory to the network.rules file was named 010_network_rules. That '_' before the 'rules' in the symlink needed to be a '.' so apparently the file was never read by udev. Such a simple solution to something which has consumed many hours, not to mention the elevated stress levels. Ah well, at least it's working again. Now I can get back to moving over to the new wireless router.

Doing a chroot with udev is a little trickier than it was before udev. Here are the steps:

mount /dev/sda1 /mnt/linux/boot
mount -t none /dev /mnt/linux/dev -o bind
chroot /mnt/linux/boot
mount /proc
mount /sys

Well, the last two evenings have been interesting. It's been difficult getting to the server from the internet due to ongoing DDOS attacks on the nameservers (ns2.zoneedit.com and ns3.zoneedit.com). I'm going to check into what is involved in adding a secondary nameserver.

I recently had a need to duplicate some directory structures - not the files within the directories - just the directory tree itself. Rather than sifting through and spending hours trying to recurse through the directories by hand, I went to work finding a better way. Find does a good job of listing out the tree:

find /var/opt/ -type d

Combine that with sed and you can create a script to create the directories.

find /var/opt -type d | sed 's/old_dir/new_dir/' | sed 's/.*/mkdir -p "&"/'

It's even possible to use ssh to retrieve the directory structure from a different machine with:

ssh user@system "command"

Put it all together and you get

ssh user@system "command" | find /var/opt -type d | sed 's/old_dir/new_dir/' | sed 's/.*/mkdir -p "&"/'

Finally, you can pipe that output to sh and run it on the fly rather than creating scripts to do it.

ssh user@system "command" | find /var/opt -type d | sed 's/old_dir/new_dir/' | sed 's/.*/mkdir -p "&"/' | sh

Very handy - particularly in my new role on the Tech Services team!