Lord... Whats a qubit?

it is more of who than a what...Qubit is Q*Bert's Chinese cousin.

hrm, well they changed their name (in 1961) to the "New Democratic Party" from the "New Party"..they seem to like the "New" name.

heh. I did come back to check to see if you responded.

HP tends to do the tall enter key...so the pipe key is to the left of that.

watch out for the consumer level laptops from HP...they are fairly cheaply made (pavilion line).

the probooks are much better quality....but you do pay for it.

other than that...great machines.

(non ac this time :))

when ever I think of BIND8, I think of my .sig:

refusing to interviews if the interviewer isn't willing to "properly" refer to GNU/Linux or conflates Free and Open Source Software... Arguably such people are the ones who might most benefit from his message. Appearing on stage next to a banner might produce the opportunity to talk about why he disagrees with such things... talking to a reporter who conflates "Free" and "Open Source" might provide an opportunity to talk about the difference. Both could be done in a non-confrontational way that none the less shows what he believes and why.

did you see the part where rms asks that the journalists actually attend his talk? and the references he gives to the GNU website talking about the difference between Free Software and Open Source software?
by the time he finishes his speech, he has spoken at length on the differences. why repeat it to a journalist?

pfft...this is clearly a slashvertisement for Linus' divelog!

haha, yep...I hear ya on the mod points thing.

it has always made me feel more connected to /.

I agree...I don't really see why these games need "winners" and "losers"...they shouldn't even keep score...and at the end of the games...whats with the cold handshakes...why not HUG!

DVD's have DRM also. Your argument doesn't hold any water.

that is because his argument is not licensed to hold water in your region. if you were in the proper region, and paid the appropriate licensing fees you would see that the water is indeed held.

Now, there well may be technical reasons why a reboot is a bad idea, but this article doesn't present any.

hrm, the article states: ...If you shrug and reboot the box after looking around for a few minutes, you may have missed the fact that a junior admin inadvertently deleted /boot and some portions of /etc and /usr/lib64 due to a runaway script they were writing. That's what was causing the segfaults and the wonky behavior. But since you rebooted the server without digging into the problem, you've made it much worse, and you'll soon boot a rescue image -- with all kinds of ponderous work awaiting you -- while a production server is down.

and:
In many cases, it's extremely important not to reboot, because the key to fixing the problem is present on the system before the reboot, but will not be immediately available after. The problem will recur, and if the only known solution is to reboot, then the problem will never be fixed unless or until someone decides not to reboot and instead tries to find the root of the problem.

and while I disagree with this one slightly..as the problem may still be present after a reboot..I defintely agree with what the author is saying...find the actual root of the problem, and fix it..don't just cross your fingers and hope a reboot will fix the problem.

Also the author never mentions preserving uptime of the server as a goal..he does mention a few times patching in place..which will mean killing services, effectively making that particular server unavailable.