Smaller Vista installations

Posted on January 29th, 2008 in Technology, Windows Admin by Rodney

If you’re none too happy with the massive footprint of Windows Vista, why not give vLite a go? This small application allows you to selectively remove (with a nice GUI) Windows Vista components you’re not normally allowed to remove, prior to the installation of Vista (which is image based).

Components you can remove include the MSN installer, Windows Media Player and just about all others, letting you get back to a core OS. Furthermore, you can use it to slipstream installation ISOs & use the standard Windows unattended installation tools with it, so you can perform a mass deployment of your cut-down OS.

Failed linux software RAID.

Posted on January 28th, 2008 in Howtos, Linux Admin by Rodney

Ok, the second problem I got with my power drop was the failure of the software RAID running on the VMWare host CentOS box. This can be seen as follows:

[root@selene ~]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdb1[2](F) sda2[0]
155227904 blocks [2/1] [U_]

(The (F) after the sdb1[2] is a bad thing, by the way, implying something failed).

Now, to fix this, I will need to rebuild the RAID (and also have some faith in the power supply, while I am doing it).

More detail can be picked up as follows:

[root@selene ~]# mdadm -D /dev/md0
/dev/md0:
Version : 00.90.01
Creation Time : Fri Mar 16 07:53:50 2007
Raid Level : raid1
Array Size : 155227904 (148.04 GiB 158.95 GB)
Device Size : 155227904 (148.04 GiB 158.95 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Mon Jan 28 15:43:15 2008
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

UUID : 870a8c32:61f98f07:8433c71a:2d84006c
Events : 0.4444326

Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 0 0 – removed

2 8 17 – faulty /dev/sdb1

Uh oh, something has failed out of the RAID… Looks like we need to bring it back in. We do this as follows.

We know that /dev/sdb1 is the one which has failed out, so let’s bring it back in as follows:

[root@selene ~]# mdadm /dev/md0 –remove /dev/sdb1
mdadm: hot removed /dev/sdb1
[root@selene ~]# mdadm /dev/md0 –add /dev/sdb1
mdadm: hot added /dev/sdb1

Now we can see it’s rebuilding, again by using mdstat:

[root@selene ~]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdb1[2] sda2[0]
155227904 blocks [2/1] [U_]
[>....................] recovery = 0.1% (226560/155227904) finish=57.0min speed=45312K/sec
unused devices:

So that’s it. Just keep an eye on the recovery and watch it as it goes. You can do this by just running mdstat (as above) a few times every 15 minutes or so, to see how far along it’s gotten.

Good luck!

P.S. For the record, my RAID-1 with 2*160GB IDE drives (47% full) took around an hour.

YUM segmentation fault

Posted on January 28th, 2008 in Howtos, Linux Admin by Rodney

Because I mainly use this blog to remind myself of fixes for things that crop up from time to time, here is the next one.

Recently, I was performing a yum update on a VMWare guest OS, running Fedora 7, when the power dropped (the device was on a UPS – ironically the only thing to fail was the UPS… guess it’s had its day). Anyway, when it came back up, it couldn’t complete the yum update, due to a segmentation fault.

Anyway, the way to fix this problem is pretty simple. Just go to the bash and enter:

rpm –rebuilddb (that’s two hyphens).

This should correct the issue.

Cya!

Vista SP1 RC available for download

Posted on January 23rd, 2008 in Technology by Rodney

If you’re feeling suicidally optimisitic and want to try to improve the performance of your Vista install (or just plant to do some pre-deployment testing):

Vista SP1 RC is available for download.

Good luck.

Vista, we hardly knew you…

Posted on January 21st, 2008 in Ramblings by Rodney

It’s official – Vista is the new ME.

Microsoft have announced the release date for Windows 7, just a year after Vista’s release. Even Microsoft seem to have given up hope for the widely unpopular operating system.

As much as I wanted to love Vista, I just couldn’t. Too many bugs pervade the system, network performance is atrocious and the file system is terribly slow. Plus the 64 bit version has poor support, even from Microsoft themselves.

Vista Ultimate Extras have been a complete joke – nothing more than a few pathetic backgrounds and screen savers, for all that extra money (and now with a new version of Plus! coming out, Ultimate has basically been canned as well).

So I’m looking forward to Windows 7 and hoping that unlike with Vista, they don’t rush the job and actually do deliver on the promises (which include a genuinely new kernel and filesystem, although what this means for backwards compatibility is yet to be seen).

mDNSResponder.exe & Adobe

Posted on January 8th, 2008 in IT Security by Rodney

Just today I was going to click on one of my taskbar shortcuts and, through being a little too quick for my own good, missed and clicked on the shortcut to the CMD prompt. I figured, while it’s open, I’ll have a look at what is using my network, just to check nothing is there which shouldn’t be.

A strange thought process, I know but that’s how I think (apparently).

Anyway, using netstat -anb, you’re able to see what programs are accessing the network from your Windows machine and on what port.

In my case, I was a little surprised, to say the least, to see mDNSResponder.exe happily listening away on my computer. Having no idea what it was, I thought I’d run a quick Google to see what comes up. All the first hits indicate it’s related to iTunes – a product I don’t use.

Always thinking the worst, I dug a little deeper. It turns out the product is used for generic music sharing and for reasons not quite clear, is installed whenever you update or install any Adobe products, now days. Sure enough, my Acrobat Reader ran an update just last night.

So it seems Adobe didn’t just deem it fit to install additional and unrelated software on my computer, all in the name of updating Acrobat Reader but also deemed it fit to create a service, with a misleading name (Windows Bonjour!) and set it to run automatically, providing information about my music preferences to whoever may be listening (i.e. Adobe).

While Adobe claim this product is used to provide information only to other computers on a local network, the service is configured allow connections from 0.0.0.0:0 (i.e. unrestricted), when surely they could have restricted it to the local subnet, only, if that was genuinely their intent. So if you don’t have a firewall installed, any computer in the World can connect to you and find out about the music you have on your computer.

This kind of reprehensible behaviour on the behalf of companies like Adobe really does need to stop. Having a highly used, common-place “free” product, like Acrobat Reader, which has widespread adoption, isn’t carte blanche to simply do whatever the hell you want with the chumps (customers) who support you.

All this hot on the heels of Adobe being caught out installing Spyware on people’s computers, only last month. In this example, Adobe tried to hide the connections to remote machines by using a known Spyware company, with a registered domain name of 2o7.net (that’s an “o” as in “ooh” by the way, not a zero). They then used a name 192.168.112.2o7.net, in the hope that people would gloss over the connection and assume it was part of their local area network.

However management at Adobe really don’t seem to be heading in the right direction, these days, as their software continues to bloat and continues to raise eyebrows with very unusual inclusions. I suspect this trend will continue, as Adobe really seem to be going out of their way to lose friends, in the industry.

P.S.
You can find a few tools online to remove this product, however I wouldn’t use any of them, as they’re all unsigned, unknown .exe files. If you have a similar program installed and don’t want it, simply find the offending service, stop it (using the Windows Services MMC snap-in, or by clicking start > control panel > administrative tools > services) and then remove it, from the CMD prompt with “sc delete {service name}” (if the service name has a space in it, surround the name with quotation marks).