Like many others, I've become somewhat dependent on virtualization to reduce the number of computers and windows installs I have in my home. I recently took another stab at using open source virtualization, and I've had some success with WebVirtMgr, a libvirt-based VM management solution for Linux. This made me want to migrate some XP guests from vmware player to KVM, and I'm happy to say that this is relatively simple today once you figure out the precise sequence of events.
I needed a quick version of lspci for looking at some linux systems without pciutils, so I threw this one together in a couple of minutes.
It's very simple, it doesn't tell you what the devices are, but it does tell you what kind of devices they are and what their PCI ID is. Then you can go look that up online to figure out what they are. It wouldn't be a horrible stretch to add support for the pci.ids file, but it wasn't necessary for my purposes.
I just got a nice Samsung EVO 850 SSD, and therefore got the chance to remove two spinning disks from my PC. But in order to make this happen, I had to move Windows to the SSD I had in my PC already. So I mounted the new SSD and formatted it ext4, and transferred Linux without a hitch. Then I booted up and used gparted to transfer Windows to the old SSD I'd just vacated, and it wouldn't boot. I thought these problems were over? I used my Linux install (with vmware player) to fix the problem just as I had used it (with gparted) to copy Windows from one volume to another.
My LG E960, better known as the Google Nexus 4, decided to let me down. Around the same time, the radio stopped working properly and the digitizer stopped recognizing touches right in a fairly important spot — above the "e" key. Clearly it was time to take a right-hand turn and buy a new device from a different manufacturer. At just this moment, Amazon offered a discount on the second-generation (2014) Moto G, and the sale was made.
Short, short, short form: Before installing, install setfsb, then add a REG_EXPAND_SZ (named, perhaps, underclock) like this to the registry in
c:\programs\setfsb\setfsb.exe -w0 -s50 -q
Create victimless crimes, imprison people (ideally in privatized prisons from which the ruling class gets kickbacks, or which they own) and then demonize them when they are freed to increase recidivism, because incarcerating the same people over and over minimizes the chance that the voters will notice. This is the right hand of the devil.
This diatribe is a response to a discussion containing repeated assertations of "false equivalence" between the Democrats and Republicans. I don't believe that individual Democrats and Republicans are equivalent, and I don't even believe that left to their own devices, the people who make up these parties wouldn't go in different directions. I believe that we have a system that permits the corporations to juggle us between these two parties, reducing them to a distracting false front that distorts our view of the actual situation: corporate governance.
I recently became reinterested in pogoplug devices when they seemed to have come down to a fairly reliable ten to twenty dollars for the latest models, the kind with an SD slot. They're nice little ARM-based machines with a lovely case and pads for a 3.3 volt serial port. Now I wanted to add a little basic functionality to them when running Debian.
I picked up a Vertical Communications 7504-10 IP phone from a yard sale a little while ago on the assumption that since it was standards-based (SIP) that I'd be able to use it with Asterisk. Browsing around with google only revealed one thread where someone claimed that you could make the phones work, but said nothing about getting into the phone in the first place. But as it turns out, it's actually quite easy to configure these phones to work with an arbitrary SIP provider.
Once I bought a dockstar, and was mightily annoyed by it. Eventually new Pogoplugs came out, and I invested a whopping nine bucks in a used pogoplug mobile. After having it deregistered by support, I tried installing ArchLinuxARM on it. This produced a brick with a flashing green light, so do not try to install Arch for ARM on this device. It's probably possible to make it work, but the default install instructions don't work. Further, the revert process didn't work either! Seems like their u-boot is broken for this device.