A friend recently bought a Chumby.  If you haven’t heard of them, a Chumby is basically a network-aware clock.  Those who follow my blog may remember that I posted an article with this idea some time ago.  I’d like to think that I had the idea and the Chumby folks took it from me, but I don’t hold it against them.  I should have gotten off my butt and developed the product myself instead of sitting around waiting for someone else to do it so I could complain.

At any rate, it’s given me plenty of entertainment value.  The guy who bought it can’t help but mention it to everyone he sees, and I take every chance I get to call it his “Chubby” rather than Chumby.  It’s amazing how many different ways you can substitute Chubby for Chumby in normal conversation and have it end up funny.

He’s finally received his Chumby the night before Thanksgiving.  He’s promised to bring it to work on Monday, and we’re all supposed to be prepared to be amazed at it’s wonderfulness.  I’m not holding my breath.

I got to reminiscing with a couple fellow geeks today, and the subject turned to old proprietary UNIX’s, specifically those released by Hewlett Packard and Sun.  It doesn’t seem that long ago, but once I worked mainly with HP-UX.  We ran versions 9 and 10 on HP workstations and business-class servers.  I also was lucky enough, or unlucky enough, depending on how you look at it, to have worked with SunOS and Solaris.  At the time, they were two separate products – SunOS was the operating system and Solaris was the GUI frontend that you only loaded if you wanted or needed it. Continue reading »

It may be that prices on mainstream PC’s such as Dell and HP are getting so low that it’s less expensive to just buy a new machine than to do simple things like replace a failed hard drive or add more memory to support bigger apps.  It’s already happened with home printers, with the prices for the ink outweighing the printer price itself sometimes.  Printers are often snapped and glued together with no intention of them being opened back up for repair. Continue reading »

I wrote a short piece about OpenWRT and it’s apparent issues with WDS a few weeks ago.  Even though I was struggling with packet loss using WDS, I’m still a big fan of OpenWRT as a whole, mainly because I like anything that gives me an alternative to the mainstream.  I can load OpenWRT on an old WRT54G or certain other vendor/models, and have a whole new range of possibilities.

One idea I’ve had, that I’m not 100% sure can be done, is to create an alarm clock based on a WRT54G or equivalent device, running OpenWRT.  I have this idea of a clock with WRT54G internals, a basic LCD screen and integrated speaker.  The clock automatically DHCP’s an IP from a home LAN and the IP can be viewed through the LCD display.  Once it has an IP, it can be configured via web interface, where things are set up such as a network share where sound files are stored, time zone, etc…  Alarms would also be configured via web interface.

The idea is that once set up, the clock would be configurable for a wide range of alarm options.  It seems to me that people who sleep through their alarms or hit snooze buttons are doing so because they get used to the sound of their alarms and don’t really wake up all the way.  This clock would have a random mode where it grabs a sound file from the network share at random and blasts it out.  The owner could add their own sound files to the mix, remove others…  I even thought if it went over well enough, an online service could be had where the clocks would update their own sound files once a week or so to keep things fresh.  Maybe an ambulance siren one day, a rooster the next, a car crash, symbols, elephants trumpeting….  the possibilities are endless.

I look at it this way….  a WRT54G with OpenWRT already has a basic operating system.  It can sync time with an NTP server.  It has built-in wireless that can be used to connect to a home/business wi-fi LAN.  Scripts can be written for it that would connect to a network server for access to sound files.  The only missing pieces are basically an LCD display for a visible clock and an audio output for playing the sound files.

So, if someone thinks they can take my idea and turn it into reality, let me know.  Maybe we can make a bunch of money together! :)

I’m kind of a geek at heart, so years ago when I found out about OpenWRT, I had to use it somewhere, anywhere.  OpenWRT is an open-source third-party operating system built to run on consumer-grade broadband routers like the Linksys WRT54G wireless router.  If you’ve got some tech skills, it’s not too difficult to hack the Linksys to boot from tftp, and then provide the OpenWRT image via tftp server.  If things work out right, you get a Linksys on the outside, and OpenWRT on the inside.

OpenWRT is Linux-based, so there’s a shell interface and a limited web interface.  It’s limited, but that’s to be expected because the hardware itself is limited.  You can, however, do some cool stuff that the original vendor didn’t let you do, like assign the individual switch ports to vlans, run different dhcp servers for each vlan, firewall using iptables…  You’ve got much more direct control over the wireless functions as well.

I have been running 2 of these on my home network.  The first is my main router, and is configured for a few firewall pass-throughs to my internal machines.  It’s also set up for wireless.

When I decided to put another computer on the other side of the room, I at first installed a wireless adapter in that computer.  But then when I wanted to work on a customer’s computer on that same desk, I had no connectivity unless I installed a wireless adapter in their computer as well.  The simpler solution is to be able to hardwire to a network jack, since most computers already have network cards built-in.  For the heck of it, I decided to test out the WDS functionality of OpenWRT.  WDS is wireless distribution. 

Here’s the basic idea.  Configure your main WRT54G w/OpenWRT for WDS and give it a WEP key.  Set up another WRT54G w/OpenWRT for WDS and give it the same WEP key.  The two devices will bridge across the wireless connection and also act as AP’s on each end.  Set the SSID’s the same and you’ll move from one to another with a laptop or PDA fairly smoothly.  You’ve also got 4 LAN ports on that far-end device that are bridged all the way through the network, so you can plug in any hard-wired device on that far end as well.

Neat, huh?  Well… yeah, it IS.  The only problem is that I tend to see a lot of packet loss through the wireless when I have it set up this way.  I’ve strugggled with corrupted binaries on downloads to computers on the far end of the link.  I’ve done my research and haven’t been able to find a solution, but then again, it’s free software on a $50 router – can’t expect it to be iron-clad and gold-plated.

I’ve been talking to my boy about starting a new website, one that he can create content for.  Since he was little ( I guess he still is, since he’s only 7) he’s been either watching me use a computer or using one on his own.  He’s got an amazing array of knowledge about things [...]

It’s always said that kids try to emulate their parents, and my son is no exception.  All his life I’ve had jobs that require me to spend a lot of time in front of computer screens, and he definitely noticed.  I’d say his favorite thing, by far, is to spend Saturday morning at the computer, [...]

Man, all this talk about Usenet, trolls, Geek Code….  it just keeps the memories rushing back!  I remember so clearly having to compile every stupid application that people wanted to run.  Not Windows stuff, mind you – real apps run on Unix servers via telnet clients, character/curses-based.  Gopher, Archie, Wais, IRC.  There weren’t any handy [...]

I actually started creating my own Geek Code, as I never had one back “in the day”.  Quickly gave up, however, as several sections seemed completely irrelevant in today’s Geek world. Usenet is all but gone, and today’s modern Geek probably never saw OS/2 or VMS.  Maybe someone should rewrite the Code and replace those [...]

I had almost forgotten about the Geek Code…. Bookmark to:

© 2010 Virtual Adept Suffusion WordPress theme by Sayontan Sinha