I was just at a ftp server that grabbed my IP and reverse-resolved my name even though I was logged in "anonymously". This could be used to track me too.
Enterprise Edition is the High End do-everything version. Standard Edition is a fraction of the price.
Even still, $10,000 is nothing compared to the hardware and staff to run it. There are plenty of companies that spend more than $10,000 a month on their help desk.
I just wish I knew how much our companies subscription to the Burgandy CD's cost:)
The Win32 API basically is the operating system. So of course you need to access the Operating System for an application to work.
Whether you need to go through the overhead of a windowing system and message dispatch queue just to ping another machine(as the original poster implied) is another story.
Have you slashdotters forgot? Einstein worked for the belly of the beast, the patent office.
I'm calling for the open source movement to boycott all of Einstein's theories, their practical applications, and any other theories or applications derived from his original work.
I'm also starting an open source project called "Absolutly" that will attempt to do a clean room implementation of Relativity.
You're actually paying the money for the third-party software from Adaptec. Older versions of EZ CD Creator generate a blue-screen on Win2K. It's actually a pretty good deal compared to buying EZ-CD and Direct CD straight from Adaptec.
I just want to know why you need a shockwave menu to pop up when you insert blank media.
The idea of using a hash function like MD5 rather than bona-fide encryption like blowfish for passwords is that it's literally impossible to decrypt the result. The only way to get someones password is to run it though the hash function and see if the result matches their hash. Sure, someone can run random strings through the hash function and find a match with someone's password, but they'll only be able to get access to that account.
With an encryption function, if someone figures out the key, they could concievably decrypt everyone else's password. This doesn't mean blowfish is insecure for passwords though. When the crypt() function uses blowfish, it actually jumps through alot of hoops (like using your password as the encyryption key, that way you would need to know the password to decode it) so that the result is impossible to decrypt.
I'm think you can change the SA's (or any) without having to know the old one. This assumes you have physical access to the machine, and didn't hardcode the password into any apps.
Since you usually have to fill out 25-odd documents, try just not returning one or two (like the NDA, noncompetitive). Theres a reasonable chance it'll slide by the HR department(especially if its a company where every job grade has different forms to fill out) and you can just play dumb if they call you asking about it.
They already tried to pull the plug on it once, but the outcry from corporate customers was too great. And with Compaq, where there's support contracts, there's business.
I've been expecting for about a year the announcement "OpenVMS is Open Source" as an excuse for Compaq dump it.
No, I'm not going to declare it the greatest computer ever, but one of the cool features it did have was a Recoverable Ram Disk. It could survive a power outage or even flipping the power off manually. There were even hacks for the game units based on the amiga (since they had no disk drive) where you would use a bootable CD, rebuild the OS on an RRD, and then flip the power switch and actually have it BOOT off of the RRD.
Not to mention the fact that in the real world, it's not really a viable option to recompile programs/kernels every other week or even shut the server down more than once a month.
I've read the license. The big thing is that BSD is not parasitic like GPL. As long as you reproduce the BSD License in the source file and a readme file you can do whatever you want with it.
It's very possible to meet all the criteria of the BSD license, and release a new package under the GPL. You say :
this is based on a package developed by XXX. Code developed by XXX is licensed under the following conditions [Insert BSD Here] All modifications are Copyright logistix Licensed under GPL blah blah blah.
Where it gets tricky is that even though the modifications are under the GPL, you don't need to say where they are ( i.e. I added line 11848 and fixed a typo in line 43929 ) anyone who gets this isn't going to be able to strip out your changes and revert to the BSD License, so in effect they'll be forced to use the GPL License for their modifications (since it's parasitic), unless they revert to the original BSD source package.
Don't get me wrong, That'd be lame, but it could (and probably has) been done.
I think the whole point of the BSD license (minus legalese) is just saying "Look, this is based on software that you can get the source code for. If you don't think it's been changed too much, these are the people who made the original. Do whatever the hell you want with it."
Once again, it's important to make the distinction between making your own backups for protection and downloading a 'backup' copy. They're two totally different things.
It's the same with.mp3's. There's a difference between ripping your own and downloading a 'backup' for a CD you ( may or may not ) already own.
It's the same with buying/selling a 'backup' copy of software on e-bay (which I don't think you can do anymore) instead of making your own backup.
It's also illegal to redistribute your own personal 'backup' copy which is what these ROM sites are doing.
Granted, most people don't have the equipment to backup ROM's, but that's your problem.
While we're on the subject, does anyone have any documentation that the 'you're only allowed to keep a ROM for 48 hours' rule, or is that an urban myth?
The BSD License allows you to relicense however you want as long as you indicate that it was based on BSD source. You can relicense under GPL and just put a header in the source code and a readme that indicates 'this uses code from FreeBSD project' without having to specify exactly what code is from the BSD project.
Anyone who works with your codebase has to abide by the GPL, even if they change previously BSD'd source code. If they don't want to they can go back to the original BSD source, since you told them where it is.
There will be no peripherals, It'll all be attached directly to the brain. These devices just create an artifical layer between what we want to do and doing it. HUD's and whatnot are nice because they're within technological reach now, but they just go to show that less is more.
Then there will be no 'low-resolution' or '800 different buttons' accessing anything will happen on an instinctual level. You don't have to think 'I want to move my index finger down to press the a key on my keyboard to type' You just do it.
Of course this won't happen in our lifetimes, so it's irrelevant.
I was just at a ftp server that grabbed my IP and reverse-resolved my name even though I was logged in "anonymously". This could be used to track me too.
And no, it wasn't IIS.
stack <int> S;
stack S;
Enterprise Edition is the High End do-everything version. Standard Edition is a fraction of the price.
:)
Even still, $10,000 is nothing compared to the hardware and staff to run it. There are plenty of companies that spend more than $10,000 a month on their help desk.
I just wish I knew how much our companies subscription to the Burgandy CD's cost
The Win32 API basically is the operating system. So of course you need to access the Operating System for an application to work.
Whether you need to go through the overhead of a windowing system and message dispatch queue just to ping another machine(as the original poster implied) is another story.
<HTML>
<HEAD>
<!-- By Viewing this source code, you agree to the following conditions: ...
A company owned by VA Linux has it's IP stolen, and suddenly slashdot believes that information doesn't want to be free :)
Have you slashdotters forgot? Einstein worked for the belly of the beast, the patent office.
I'm calling for the open source movement to boycott all of Einstein's theories, their practical applications, and any other theories or applications derived from his original work.
I'm also starting an open source project called "Absolutly" that will attempt to do a clean room implementation of Relativity.
The CD-ROM works fine without that disk.
You're actually paying the money for the third-party software from Adaptec. Older versions of EZ CD Creator generate a blue-screen on Win2K. It's actually a pretty good deal compared to buying EZ-CD and Direct CD straight from Adaptec.
I just want to know why you need a shockwave menu to pop up when you insert blank media.
The idea of using a hash function like MD5 rather than bona-fide encryption like blowfish for passwords is that it's literally impossible to decrypt the result. The only way to get someones password is to run it though the hash function and see if the result matches their hash. Sure, someone can run random strings through the hash function and find a match with someone's password, but they'll only be able to get access to that account.
With an encryption function, if someone figures out the key, they could concievably decrypt everyone else's password. This doesn't mean blowfish is insecure for passwords though. When the crypt() function uses blowfish, it actually jumps through alot of hoops (like using your password as the encyryption key, that way you would need to know the password to decode it) so that the result is impossible to decrypt.
Just replace banner ads an cached pages with ones that google gets paid for.
I'm think you can change the SA's (or any) without having to know the old one. This assumes you have physical access to the machine, and didn't hardcode the password into any apps.
Did these companies do any contract work with the government?
Since you usually have to fill out 25-odd documents, try just not returning one or two (like the NDA, noncompetitive). Theres a reasonable chance it'll slide by the HR department(especially if its a company where every job grade has different forms to fill out) and you can just play dumb if they call you asking about it.
Especially if it's the marketing people that came up with:
DSL comes through a tiny little phone line, Cable comes through a big ass cable line
(at least on my machine)
try this.
Reboot Linux, login, type free.
startx, open xterm, type free.
quit X windows, type free.
Don't open X windows or reboot for a week.
Type free.
It'll still be using 90 megs just to run. Sure, I can kill processes manually, but you can do that on NT too.
Compaq wished VMS was dead.
They already tried to pull the plug on it once, but the outcry from corporate customers was too great. And with Compaq, where there's support contracts, there's business.
I've been expecting for about a year the announcement "OpenVMS is Open Source" as an excuse for Compaq dump it.
No, I'm not going to declare it the greatest computer ever, but one of the cool features it did have was a Recoverable Ram Disk. It could survive a power outage or even flipping the power off manually. There were even hacks for the game units based on the amiga (since they had no disk drive) where you would use a bootable CD, rebuild the OS on an RRD, and then flip the power switch and actually have it BOOT off of the RRD.
That's just crazy.
Not to mention the fact that in the real world, it's not really a viable option to recompile programs/kernels every other week or even shut the server down more than once a month.
I've read the license. The big thing is that BSD is not parasitic like GPL. As long as you reproduce the BSD License in the source file and a readme file you can do whatever you want with it.
It's very possible to meet all the criteria of the BSD license, and release a new package under the GPL. You say :
this is based on a package developed by XXX. Code developed by XXX is licensed under the following conditions [Insert BSD Here] All modifications are Copyright logistix Licensed under GPL blah blah blah.
Where it gets tricky is that even though the modifications are under the GPL, you don't need to say where they are ( i.e. I added line 11848 and fixed a typo in line 43929 ) anyone who gets this isn't going to be able to strip out your changes and revert to the BSD License, so in effect they'll be forced to use the GPL License for their modifications (since it's parasitic), unless they revert to the original BSD source package.
Don't get me wrong, That'd be lame, but it could (and probably has) been done.
I think the whole point of the BSD license (minus legalese) is just saying "Look, this is based on software that you can get the source code for. If you don't think it's been changed too much, these are the people who made the original. Do whatever the hell you want with it."
I really just wanted to see if all your petty, offtopic, know-it-all posts deserved a default Score:2, or if you just slipped :)
Once again, it's important to make the distinction between making your own backups for protection and downloading a 'backup' copy. They're two totally different things.
.mp3's. There's a difference between ripping your own and downloading a 'backup' for a CD you ( may or may not ) already own.
It's the same with
It's the same with buying/selling a 'backup' copy of software on e-bay (which I don't think you can do anymore) instead of making your own backup.
It's also illegal to redistribute your own personal 'backup' copy which is what these ROM sites are doing.
Granted, most people don't have the equipment to backup ROM's, but that's your problem.
While we're on the subject, does anyone have any documentation that the 'you're only allowed to keep a ROM for 48 hours' rule, or is that an urban myth?
The BSD License allows you to relicense however you want as long as you indicate that it was based on BSD source. You can relicense under GPL and just put a header in the source code and a readme that indicates 'this uses code from FreeBSD project' without having to specify exactly what code is from the BSD project.
:)
Anyone who works with your codebase has to abide by the GPL, even if they change previously BSD'd source code. If they don't want to they can go back to the original BSD source, since you told them where it is.
GPL's for commies anyway
There will be no peripherals, It'll all be attached directly to the brain. These devices just create an artifical layer between what we want to do and doing it. HUD's and whatnot are nice because they're within technological reach now, but they just go to show that less is more.
Then there will be no 'low-resolution' or '800 different buttons' accessing anything will happen on an instinctual level. You don't have to think 'I want to move my index finger down to press the a key on my keyboard to type' You just do it.
Of course this won't happen in our lifetimes, so it's irrelevant.