And that gets to the point of answering the question "what ever happened to PXE?" - it got replaced by virtualised storage for booting virtual machines, running on a fat software hypervisor. It's still nifty though, and useful when you do it right.
ISPs siding with the public domain is a good step towards having governments listen to someone other than media corporations - hopefully plenty of people flock to this.
Basically Schmidt's quote can be better worded as saying "internet users shouldn't worry about privacy unless they're broadcasting something they have to hide".
Isn't it something like "Yo dawg, I heard you like to package Perl so I put a Perl packager in your Perl package so you can package Perl while you're packaging Perl packages" ?
In addition to all of that, there's a reason EM radiation of longer wavelengths is called "non-ionizing". Hint: it's because it's incapable of ionizing anything.
Don't worry, the damaged AM radio towers are being replaced by modern microwave dishes. The intercoms are saved!!
Not necessarily - for example, if you look at the PC boot sequence, people have been screaming that there are too many hard-coded sleep periods that don't get smaller as processors get faster. It's feasible there's similar locking problems (especially if it's associated with I/O) in a web app.
At least it fixed the bug in Frontier (at least on the Amiga) where hyperspace distances would overflow at 65536 light years, so you could get anywhere on a couple of tonnes of fuel (and within a couple of days) as long as you could find a star system 65536+(a very small amount) away and almost equidistant from your destination.
That was a stupid bug that ruined the gameplay (read: I only found out about it a few years ago, years after I'd stopped playing the game)
Depends who your customers are - most companies I've seen are scared shitless of using anything that doesn't have a brand name.
The only way you can "ensure getting paid" is by not giving the client any freedom (or source) at all - the whole point of the open business models is that the customer can pick up your code and go pay someone else to support it, and that's ironically why you can charge a premium.
Really, this "licensed codebase" is something different, and it's done all the time (like licensing a game engine to create your own game), all you need is a suitable NDA to keep anyone leaking the code to the public.
Depending on how valuable the source actually is, you could go the TrueCrypt/Firefox route and allow redistribution and modification, but use trademarks to protect your "official" version that has monetary value.
Slashdot Mirror
And that gets to the point of answering the question "what ever happened to PXE?" - it got replaced by virtualised storage for booting virtual machines, running on a fat software hypervisor. It's still nifty though, and useful when you do it right.
Sounds like you live in an adventure game... try not to go anywhere dark.
Whenever I see the word "Bungie" in type I always read it first as "Bungle"
ISPs siding with the public domain is a good step towards having governments listen to someone other than media corporations - hopefully plenty of people flock to this.
Basically Schmidt's quote can be better worded as saying "internet users shouldn't worry about privacy unless they're broadcasting something they have to hide".
Thread title is not -1 Redundant - it cannot be said enough.
...or you could just update the firmware
Isn't it something like "Yo dawg, I heard you like to package Perl so I put a Perl packager in your Perl package so you can package Perl while you're packaging Perl packages" ?
No, you have to: /lib/modules/*
sudo chABC -R
sudo mkinitnerves --all --spinal
then reboot
This is why neuroscience just isn't ready for the masses
In addition to all of that, there's a reason EM radiation of longer wavelengths is called "non-ionizing". Hint: it's because it's incapable of ionizing anything.
Don't worry, the damaged AM radio towers are being replaced by modern microwave dishes. The intercoms are saved!!
cf. Rocket Jump
This is why I like hanging out in a place less likely to be filled with Twilight fangirls :)
Not necessarily - for example, if you look at the PC boot sequence, people have been screaming that there are too many hard-coded sleep periods that don't get smaller as processors get faster. It's feasible there's similar locking problems (especially if it's associated with I/O) in a web app.
There're some things that Tux should just not be involved with... *shudder*
Ubuntu also comes with Firefox...
You forgot:
Eve: Boys, ready a unit for dispatch...
At least it fixed the bug in Frontier (at least on the Amiga) where hyperspace distances would overflow at 65536 light years, so you could get anywhere on a couple of tonnes of fuel (and within a couple of days) as long as you could find a star system 65536+(a very small amount) away and almost equidistant from your destination.
That was a stupid bug that ruined the gameplay (read: I only found out about it a few years ago, years after I'd stopped playing the game)
indubitably! ...
If they can't find the real MySQL, sounds like they need a unique identifier with an index...
(Warning: link contains strong language and vivid imagery.)
Excellent way to get people to RTFA :)
Yeah, I wonder how much of the difference is Windows+Nexuiz vs. Linux+Nexuiz, excluding the driver aspect.
The Aamazing Aardvark.
Depends who your customers are - most companies I've seen are scared shitless of using anything that doesn't have a brand name.
The only way you can "ensure getting paid" is by not giving the client any freedom (or source) at all - the whole point of the open business models is that the customer can pick up your code and go pay someone else to support it, and that's ironically why you can charge a premium.
Really, this "licensed codebase" is something different, and it's done all the time (like licensing a game engine to create your own game), all you need is a suitable NDA to keep anyone leaking the code to the public.
Depending on how valuable the source actually is, you could go the TrueCrypt/Firefox route and allow redistribution and modification, but use trademarks to protect your "official" version that has monetary value.
why oh why couldn't they have learned their lesson about backups and data availability with something silly like credit card information!?