I was just in a hotel last week and had put my laptop in the room safe. I entered my 6 digit code and locked the safe. Two days later, I tried to open it and it wouldn't take my pin. I called the hotel staff and a maintenance guy came to my room with a small 10-key pad that had an LCD display. He plugged an RJ45 cable into a port on the bottom of the locking device, entered 2468#, then 1357#, and the safe opened. After it was open, it flashed LO-BAT, so that explains why it lost my combination.

If it's as easy as having one of those pin pads, why even have the safe in the room?

http://sourceforge.net/projects/linuxwacom/forums/forum/236871/topic/4686734

The Wacom Inkling shows up as a drive with WPI files on it. It should work just fine in Linux since the heavy lifting is all done on the pen. And I didn't spend very long looking either.

The firmware thing was what caused me to start recommending other server manufacturers. The Sun hardware was actually really nice, well designed, and very stable. The ILOM was great since it was so tightly integrated with the hardware and yet completely out of band, and was included with the server at no real additional cost.

Then Oracle bought Sun and turned off firmware support unless you had an active support contract. That was a big *fuck you* to everyone who bought a bunch of Sun hardware and only kept support on a few critial units. I know firmware updates aren't free to make, but that's the price of good customer service.

Oracle, you've lost my business.

I thought the same thing. I would imagine they already had equipment to deal with 35mm film, and it was easier to transfer it to 35mm to feed that equipment rather than retrofitting the equipment to take a larger source.

I'm surprised they MANUALLY advanced each frame through the little shutter contraption. Don't any of these guys have a bag of Legos they could automate that process with???

YouTube has a much better video than the one linked in the article that contains the process they went through and talks about the capture and projection intended by the inventor.

You don't buy Cisco because of the features, you buy Cisco because of TAC. At 2:30 AM when you have 96 phone lines down, the call center opens in 3 hours, and you're getting call supervision with no voice traffic, you call TAC. I got an engineer out of their Sydney office on the phone in 14 minutes, and we had the problem resolved within an hour. (It was a telco provisioning problem.) Having someone on hand to support a problem 24 hours a day, and a supply chain that can send a part out in 4 hours is a safety net worth paying for.

Just to be clear, the Harry Potter series isn't available in eBook format. JK won't allow it for some reason.

If the magnetic poles move any farther, future generations may not be able to operate the things as they were intended. :)

Not to be a total ass, but a map doesn't actually show you where you are. You have to determine your own location on the map.

I agree that a map won't fail in the same ways a GPS unit will fail, but your argument isn't really a fair argument. An outdoor GPS works in the rain, a map gets wet and turns to mush. A GPS takes much less room to store more map data. A GPS won't have small tears at the edges and folds.

Each method for location has its' own strengths and weaknesses. Use the correct tool for the job.

I literally just opened the box of my first Arduino board about 15 minutes ago. I installed the IDE, plugged it into my computer, loaded the drivers, and sent a few sample programs to the tiny board with -zero- problems.

With an out-of-the-box experience like that, it's no wonder the darn thing is so popular.

I'm in a small (9 site) business that uses Cisco gear for all the interconnect. Cisco's have some glorious uptime, but little me has found 3 different bugs in IOS simply dealing with the day to day activities of our shop. Access lists that won't apply to a policy (standard ACL only, the extended ACL applied just fine), spurious items in the running config that change throughout the day by themselves, SIP session handling causing the call to be dropped *before it was answered*...

Yes, Cisco's have great uptime, and yes, we'll stick with them, but not because they're perfect - we stick with Cisco because of TAC. When the shit hits the fan, TAC has your back. I've never had a better experience with a technical support team than I've had with TAC. Sure it might take some time to get through to second level or even third level, but those guys know their stuff and will do what it takes to get things functional. I literally have a private IOS build sitting on my core router right now ready to go live this weekend to fix a bug.

Looks like you may have changed the stereo out before disconnecting power which is a Bad Idea (TM) when installing new car stereos. Agreed that it's stupid to require a dealer visit to reset a light, though.

Sounds more like a hooker that's double-booked to me.

I've been through 9.10, 10.4, and 10.10 on a ThinkPad X200 with Chromium 6.x and just updated to Chrome 7 (not Chromium) today and everything is working perfectly. Maybe it's your DPI settings on your monitor? My ThinkPad has a fixed LCD resolution and DPI...

That used to be true on the older 1900 gear, but all the new 2960's have it. Even the 3500's had it in the later CatOS stack. It doesn't interfere with relaying as long as you're trusting the correct port upstream. You can even configure a router to relay DHCP requests to remote DHCP servers and PXE servers at the same time for remote-boot services without onsite servers.

In any case, many of the network-based threats that are out have mitigation procedures available, as long as someone's willing to spend the time/effort/energy/money to implement them. It all winds up being a balance between reliability and cost, as usual.