Skip to main content

autovacuum in the real world


Any sysadmin who runs postgresql (or sqlite) knows he should vacuum once in a while. You didn't ? Probably because nowadays, there's an autovacuum function. But what about the Real World (you know, the big room with the blue ceiling) ?

After years of manually vacuuming the floors, I now got myself an autovacuumer to take care of my office space: the iRobot Roomba 560. This robot can drive around on the floor and cleans it. After having cleaned the room, it automatically returns to the dock where it recharges the battery.

Aside from the "cool" factor, it really does a good job. I've seen comments from people who claim that a vacuum cleaner can't run on batteries for an hour, even proving their point with calculations, but don't be fooled: the Roomba is not a vacuum cleaner like the one you already own. First, doesn't suck dirt through a 3 meter tube. Second, it isn't even a vacuum cleaner in the strictest sense: it uses brushes to pick up most of the dirt, then using a small DustBuster style vacuum engine for the finishing touch.

Overall verdict: I should have bought one sooner !
Labels:

Comments

XXX said…
Interesting stuff, this "iRobot Roomba 560". The questions that immediately pop into my mind:
- Does it run Linux?
- Can I put my own kernel on it?
- Can I ssh to the device?
- Does it run PERL?
9/1/09 17:57
Anonymous said…
Het zou kunnen ...
http://www.hackingroomba.com/
9/1/09 20:26
Unknown said…
Now that you've been using that Roomba for almost two months, what are your experiences with it? Are you still as happy with it as you were when you just got it?

I guess you're better placed now to give your insight on some of it's shortcomings?

I might buy one myself, but I fear it won't be able to get under my sofa. How tall is it, actually ?
1/3/09 14:51
Bert de Bruijn said…
@Pieter: zeker, nog altijd zeer tevreden. Ik weet ondertussen beter welke objecten ik best opzij zet voor het stofzuigen, en hoe mijn kat reageert wanneer de Roomba zijn werk doet :-) Een Scooba staat nog op het verlanglijstje...
23/4/09 15:15
Post a Comment

Popular posts from this blog

Volkswagen UHV bluetooth touch adapter & its problems

My Volkswagen car has the "universal cellphone preparation" UHV built-in. This is the main part of a car kit, but requires an additional adapter for connecting to a cellphone. At first, I was using an adapter for my good old Nokia 6310, even after I changed to the Nokia E71. Connecting was easy: pair the phone with the "VW UHV" bluetooth entity, and done. This has the phone connected to the car kit at all times, so even non-call-related functions use the car audio system (e.g. voice recognition). But progress will have its way, no matter what happens. So in comes the "bluetooth touch adapter". Instead of a phone-specific adapter, this is a small touchscreen device that slots into the UHV dashboard mount. Connecting a phone is very different now: the Bluetooth Touch Adapter connects to the "VW UHV" device via bluetooth the phone connects to "Touch Adapter" device, also via bluetooth The device doesn't allow step 2 if step 1 didn'...
12 comments
Read more

Reset lost root password on vSphere ESXi 6.7

VMware's solution to a lost or forgotten root password for ESXi is simple: go to  https://kb.vmware.com/s/article/1317898?lang=en_US  and you'll find that "Reinstalling the ESXi host is the only supported way to reset a password on ESXi". If your host is still connected to vCenter, you may be able to use Host Profiles to reset the root password, or alternatively you can join ESXi in Active Directory via vCenter, and log in with a user in the "ESX Admins" AD group. If your host is no longer connected to vCenter, those options are closed. Can you avoid reinstallation? Fortunately, you can. You will need to reset and reboot your ESXi though. If you're ready for an unsupported deep dive into the bowels of ESXi, follow these steps: Create a bootable Linux USB-drive (or something else you can boot your server with). I used a CentOS 7 installation USB-drive that I could use to boot into rescue mode. Reset your ESXi and boot from the Linux medium. Ident...
Post a Comment
Read more

GEM WS2 MIDI System Exclusive structure and checksums

MIDI is the standard for communication between electronic music instruments like keyboards and synthesizers. And computers! While tinkering with an old floppy-less GEM WS2 keyboard, I wanted to figure out the structure of their System Exclusive memory dumps. SysEx is the vendor-specific (and non-standard) part of MIDI. Vendors can use it for real-time instructions (changing a sound parameter in real-time) and for non-real-time instructions (sending or loading a configuration, sample set, etc.). In the GEM WS2, there's two ways of saving the memory (voices, globals, styles and songs): in .ALL files on floppy, and via MIDI SysEx. The .ALL files are binary files, 60415 bytes long. The only recognizable parts are the ASCII encoded voice and global names. The SysEx dumps are 73691 bytes long. As always in MIDI, only command start (and end) bytes have MSB 1, and all data bytes have MSB 0. The data is spread out over 576 SysEx packets, preceded by one SysEx packet with header informat...
23 comments
Read more