Passwords are probably the most annoying things that people have to deal with other than constant registration requests from every site we visit, which in turn breeds more passwords. A vicious cycle that leads to password reuse, and poor password policy.
I am both a geek and a sysadmin, therefor I know how important passwords are and how dumb password reuse is. To be honest though, I've been known to reuse weak passwords for logins I don't care about, that have nothing to do with my important information. Most trivial forums I do this with - because I don't care if my account there gets hacked, its not related to anything important. Sorry Ubuntu and RoosterTeeth forums if I randomly start posting ads for prada handbags.
I (foolishly) decided to try using the "Lastpass" password manager plugin for Firefox and Chrome (and I.E now I think) to manage my passwords. The interface is smooth, password generation easy. Lastpass even syncs the passwords via the ......Uh, "Cloud" so all my OS's and web browsers would be the same. This is about the point I should have /facepalm'd. But I didn't.
As a web dev, we require systems to handle our testing in as realistically a way as possible. Because I'm stuck in a Windows environment, I determined that a taste of Debian in a VirtualBox virtual machine would perform as an ideal testing environment. Going about and installing VirtualBox was painless, and so was getting Debian installed through the ISO.
Up until now, I had been using bridging for my internet access using the host machines connection but the virtual machine getting it's own IP address from the physical network. This made updating and installing through apt easy. I quickly discovered that mobility would be an issue though. As my laptop changed networks, it would get a new IP from that physical network. The rub came in when trying to keep Dreamweaver updated with the virtual machine's IP address. The developers working with Sun (now Oracle) had a feature called Host-only Networking which does exactly as the name describes. The host machine makes a virtual connection and includes itself and the virtual machines in a network logically separate from the outside world. This keeps the machine from changing networks (and thus IPs) wherever I go! Great in theory, but didn't work upon implementation.
Well hello there, how did the tubes treat you on your trip to this sad tale? Good? Excellent, now I must begin.
Like any good geek story, this one starts out with a command line and a slight overdose of mountain dew. I, being a generic geek have a large external hard disk with all my geeky treasures on it. Folders filled with .iso's, install files for most of my common used programs and a batch file to install them, large amounts of tech manuals and awesome background pictures featuring both penguins and lolcats (not really, I swear).
I had recently decided to reconfigure my thinclient with an external hard disk rather than the 8gb thumb drive I had been using. Easy task, I just need to burn the latest arch netinstall .iso to my thumbdrive. Quickest route != unetbootin, but rather dd, which I love. Mostly. Plugged in the hard disk and thumb drive, navigated to /media/Teh Disk/iso/linux/ and then:
time sudo dd if=arch_2010_04_x64.iso of=/dev/sdc
and I walked away to use the restroom (Remember, mountain dew overdose, it happens).
By the time I came back dd had finished, informing me that the iso had been burned as it were. Thumb drive transferred to the thinclient and hit the power button.
Error "operating system not found"