Excuse me? Do you actually comprehend what you read?
Since when does "not much progress" equal "no progress".
Including a firewall with windows, while being some progress, is unfortunately progress in the wrong direction. People thinking that they are protected by enabling the Windows firewall is a joke. How many *default* holes are there in the preloaded config.
Why don't you just go ahead and use whatever you'd like, and never know for sure just *what* you mean, while I use the term that means exactly what it's supposed to.
I will be able to carry my meaning through in conversation and documentation, while others will scratch their heads and wonder just what exactly you meant.
Please recall that using terms like megabyte, gigabyte when discussing storage does NOT mean 2^xx - it means exactly what it says, 10^xx.
A 500GB drive does NOT contain 500GiB or 500x1024x1024x1024, it contains 500x1000x1000x1000 bytes. Say what you want, but the numbers prove out.
And even then, that's not exactly true. For in the 3.5" floppy medium, the 1.44MB meant 1.44 * 1024 * 1000 - so where's the consistancy?
Just because everyone does (or a lot of people do) something, doesn't make it right.
The metric system is all base 10. The binary system is all base 2.
The only 'proper' way to measure binary, is with a binary based system, not a decimal based system.
By using these terms exclusively, how many people would be hoodwinked by the storage industry?
Hell, how many people get their brand new 512MB or 1024MB flash memory devices home, only to find out that they are really 487MiB, or 975MiB in size.
Whether or not you like to be told you're wrong by using the misleading terminology matters not. It's a statement of fact, that it's incorrect terminology, regardless of historical usage, or in this case, mis-usage.
As far as sounding ridiculous, how would you like to use the long hand version of terabinarybytes? I know I'd sure hate to type that out, so tebibytes works just fine for me.
It's a great little gadget, with loads of promise. I use it to hold ghost images of my windows systems, and digital archives. The latest opensource firmware's unlock this neat little slug to allow it to do so much more than just disk sharing.
Oh - first thing you should do when you get it, (as long as you don't care about warranty that is), is de-underclock it back to it's fully rated speed.
By default, Linksys ships it with the speed cut in half, literally.
What's really funny, is that the cantonrep site that held the story, has actually caused a hellacious amount of damage way beyond anything the poor kid did.
Whether intentional or not, their story, coupled with our outrage - probably caused the poor server to have a meltdown.
Who's going to jail from the paper? Oh wait - freedom of the press right?
Poor school district jerks. Who the hell do they think they are? They're acting like grade school bullies. "We'll show him how we deal with jokes." sheesh - what a bunch of dick-heads. I mean that literally. Here's a bunch of supposedly intelligent adults, trying to scare the crap out of a kid. Yeah the poor sob is 18, so he's legally no longer a kid, but neither are these dorks. I wonder how many illegal, or immoral actions we can pin on the school representatives, as well as the local constabulary.
Let's see, reckless actions, nearly causing a virtual riot. Intimidation, threats, unwarranted arrest. I'd say the poor prosecuting attorney in this matter has just ended any hope of a political career.
Anyone want to e-mail Leno or Letterman and let them take pot-shots at these idiots?
It's valid, and yet invalid - all rolled into one.
No they aren't many different distros, only 2.
Windows 1.x -> ME are all different versions of windows management systems based on MSDOS.
Windows NT 3.x -> 2003 are all different versions of windows management systems based on NT.
So only 2 distros, with lots of versions.
Now Linux has had how many distros? I've read as high as 90, and no, I haven't done the research myself to come up with my own answer, but I know personally of at least 20.
Add to that the BSD distros, of which I know of 3 personally.
Then they lumped in 4 completely different Operating systems - not even distributions. AIX, Solaris, HP-UX and MacOSX - all of these are true UNIX operating systems - not the complete list by far - Tru-64, Centix, C-TIX, the pre-caldera UNIXWare, OpenServer, Xenix, UNIX, etc...
Remember, Linux ISN'T UNIX. So why the hell would they lump them together. Here's why - it's the only way they could get the numbers to add up to anything close to a large margin above the count from the 2 distros of Windows.
Except that now, there are whole lines of human stem cells that did not require aborted fetal tissues. So that whole avenue of stem cell research objection is null and void.
So if you still object to stem cell research, then yes, I'd consider you a hardliner. Next objection please.
HP-UX, AIX, Solaris, Mac OSX, OpenBSD, FreeBSD, NetBSD and the 4 score and 7 variants of Linux, even, dare I say it, some SCO stuff added into the mix.
Hmmm - somewhere on the neighborhood of let's pick a good round number, say 20 *nix variants, versus 1 os.
20 to 1, and only 3 times the number of vulnerabilities - that's approximately.15 vulnerabilities for the average *nix distro for every 1 vulnerability in Windows. That changes the numbers dramatically. Showing a 6.66 to 1 (Oh, my - the number of the beast - how'd that get in there - could it by Bill Satan perhaps?) ratio of Windows vulnerabilities to 1 *nix variant.
Interesting how numbers can be skewed now, isn't it.
Oh - and users aren't allowed to modify their environments. ie - their home directories are read only. There is a sub-directory below their home directory where they can dork with stuff, but only there. They aren't allowed to modify their.profile /.bash_profile. They aren't allowed to write scripts in their home directories either. Their PATH variables are READ-ONLY, and disallow./ Then again, most of our users are running financial software, and we cannot allow *customizations* for individual users.
In the environment that I manage, only the admins have sudo priveleges for any kind of system command.
Developers that need to run certain programs as other users (such as the userids that certain application services run as) we write scripts that can only be modified by root, and then give the individual users rights to run them. The scripts are written to disallow break-outs (like interrupt, kill, etc).
The admin users do not have access to the root account - unless the machine is down, and root access is needed to bring it up. Then we get the root passwords out of a lockbox, that requires management to get access to them.
The rest of the time, the admin users execute commands as needed via sudo. Any time an admin uses the sudo -s parameter, they have to add an entry to a log book as to why, what commands were run, and for what reason. All other commands run from sudo, are logged, and the log entries record to the equivelent of WORM storage.
If a user needs something changed, they submit a request to their supervisor, who then passes it on their manager. Management has to read, understand and approve the request, before forwarding on to the admins to have the work done. If it passes admin checks and approvals, then they can get it done. If it doesn't pass, then a discussion is started, as to why they thought they needed it, and their reasons behind it. Sometimes the users make silly requests because that's the only way they could think of to get something done. Usually one of the admins can come up with a better solution that solves the user's problem, without doing something odd to the rest of the system.
If a developer needs something done, the request has to pass a peer review before the request is ever submitted to the admins. Once submitted the process flows through very much like the user requests.
So in short, users NEVER get sudo access, developers rarely get sudo access, and when they do, it's very restricted to scripts they cannot modify. All sudo access records are written to media that once written, cannot be changed.
By definition, DAC's would NOT be illegal. Because they convert digital to analog.
What I think would be made illegal, is all the movie and music studios, that take analog microphone, instrument and video input, then convert it to digital.
As you stated, the world we live in IS analog.
Isn't it ironic, that the RIAA and MPAA would promote a law that would make the equipment they use to make a living, illegal?
RIAA, MPAA - I'm laughing at your superior intellect. Care to try for a rematch?
I think what he's stating, is that MS will just decide to STOP providing product and services to ANY EU country. At which point, MS believes that the EU will back down, cowering and repeating the mantra of "Sorry, so sorry" over and over again.
The only problem with carbon dating, is the maximum timeline it can be used for. It cannot be used to go back to the beginning of time, only a very small percentage of it.
It requires that sunlight was hitting the entire planet for all of the time that the Earth was around.
Now given the story of Genesis and the flood, that would mean that the firmament, made up of water, surrounded most of, if not the entire earth from the time of creation, until the flood - this would mean that sunlight only struck the earth at the polar regions where the firmament would have been thinned out enough to allow sunlight through.
Given this, there would be nothing that would have been hit with sufficient sunlight to give accurate readings prior to the flood, except at the polar regions.
After the flood, the entire planet was in the path of the sunlight and could start building up quantities of carbon-14 in their makeup.
Slashdot Mirror
Excuse me? Do you actually comprehend what you read?
Since when does "not much progress" equal "no progress".
Including a firewall with windows, while being some progress, is unfortunately progress in the wrong direction. People thinking that they are protected by enabling the Windows firewall is a joke. How many *default* holes are there in the preloaded config.
I tell you what.
Why don't you just go ahead and use whatever you'd like, and never know for sure just *what* you mean, while I use the term that means exactly what it's supposed to.
I will be able to carry my meaning through in conversation and documentation, while others will scratch their heads and wonder just what exactly you meant.
Please recall that using terms like megabyte, gigabyte when discussing storage does NOT mean 2^xx - it means exactly what it says, 10^xx.
A 500GB drive does NOT contain 500GiB or 500x1024x1024x1024, it contains 500x1000x1000x1000 bytes. Say what you want, but the numbers prove out.
And even then, that's not exactly true.
For in the 3.5" floppy medium, the 1.44MB meant 1.44 * 1024 * 1000 - so where's the consistancy?
Just because everyone does (or a lot of people do) something, doesn't make it right.
The metric system is all base 10.
The binary system is all base 2.
The only 'proper' way to measure binary, is with a binary based system, not a decimal based system.
By using these terms exclusively, how many people would be hoodwinked by the storage industry?
Hell, how many people get their brand new 512MB or 1024MB flash memory devices home, only to find out that they are really 487MiB, or 975MiB in size.
Whether or not you like to be told you're wrong by using the misleading terminology matters not. It's a statement of fact, that it's incorrect terminology, regardless of historical usage, or in this case, mis-usage.
As far as sounding ridiculous, how would you like to use the long hand version of terabinarybytes? I know I'd sure hate to type that out, so tebibytes works just fine for me.
Parsed the list a little better.
.016 bugs per distro, per bug in windows.
.032 bugs per linux distro vs. 1 bug per windows distro.
350 Linux
7 BSD
1 Solaris
1 HP-UX
1 AIX
----
360 Distinct Linux/UNIX Distributions/Variants
With 6 times the bugs listed, divided by 360 that's only
Now factor that windows is 2 distros, that's
That appears to change the results a tad.
For each bug found in Linux/Unix, there's 32 in Windows.
Update...
I did a little research, and according to www.distrowatch.com, there are 359 distinct Linux distributions (as of 1/6/2006)
Have you ever messed around with Linksys's NSLU2?
It's a great little gadget, with loads of promise.
I use it to hold ghost images of my windows systems, and digital archives.
The latest opensource firmware's unlock this neat little slug to allow it to do so much more than just disk sharing.
Oh - first thing you should do when you get it, (as long as you don't care about warranty that is), is de-underclock it back to it's fully rated speed.
By default, Linksys ships it with the speed cut in half, literally.
That's one reason why I married a shorter woman.
Tebibytes - the proper term for measuring binary storage, as opposed to terabytes.
LOL - Try converting your movie collection to digital storage, for a media center system.
3.5 TiB and climbing.
What's really funny, is that the cantonrep site that held the story, has actually caused a hellacious amount of damage way beyond anything the poor kid did.
Whether intentional or not, their story, coupled with our outrage - probably caused the poor server to have a meltdown.
Who's going to jail from the paper? Oh wait - freedom of the press right?
Poor school district jerks. Who the hell do they think they are? They're acting like grade school bullies. "We'll show him how we deal with jokes." sheesh - what a bunch of dick-heads. I mean that literally. Here's a bunch of supposedly intelligent adults, trying to scare the crap out of a kid. Yeah the poor sob is 18, so he's legally no longer a kid, but neither are these dorks. I wonder how many illegal, or immoral actions we can pin on the school representatives, as well as the local constabulary.
Let's see, reckless actions, nearly causing a virtual riot. Intimidation, threats, unwarranted arrest. I'd say the poor prosecuting attorney in this matter has just ended any hope of a political career.
Anyone want to e-mail Leno or Letterman and let them take pot-shots at these idiots?
It's valid, and yet invalid - all rolled into one.
No they aren't many different distros, only 2.
Windows 1.x -> ME are all different versions of windows management systems based on MSDOS.
Windows NT 3.x -> 2003 are all different versions of windows management systems based on NT.
So only 2 distros, with lots of versions.
Now Linux has had how many distros? I've read as high as 90, and no, I haven't done the research myself to come up with my own answer, but I know personally of at least 20.
Add to that the BSD distros, of which I know of 3 personally.
Then they lumped in 4 completely different Operating systems - not even distributions.
AIX, Solaris, HP-UX and MacOSX - all of these are true UNIX operating systems - not the complete list by far - Tru-64, Centix, C-TIX, the pre-caldera UNIXWare, OpenServer, Xenix, UNIX, etc...
Remember, Linux ISN'T UNIX. So why the hell would they lump them together. Here's why - it's the only way they could get the numbers to add up to anything close to a large margin above the count from the 2 distros of Windows.
It appears that they may have actually been implementing more than one bad accounting practice.
Why limit yourself to just one.
Except that now, there are whole lines of human stem cells that did not require aborted fetal tissues. So that whole avenue of stem cell research objection is null and void.
So if you still object to stem cell research, then yes, I'd consider you a hardliner.
Next objection please.
Multiple versions of course, yet one OS.
.15 vulnerabilities for the average *nix distro for every 1 vulnerability in Windows. That changes the numbers dramatically. Showing a 6.66 to 1 (Oh, my - the number of the beast - how'd that get in there - could it by Bill Satan perhaps?) ratio of Windows vulnerabilities to 1 *nix variant.
HP-UX, AIX, Solaris, Mac OSX, OpenBSD, FreeBSD, NetBSD and the 4 score and 7 variants of Linux, even, dare I say it, some SCO stuff added into the mix.
Hmmm - somewhere on the neighborhood of let's pick a good round number, say 20 *nix variants, versus 1 os.
20 to 1, and only 3 times the number of vulnerabilities - that's approximately
Interesting how numbers can be skewed now, isn't it.
I understand irony just fine.
You were apparently inept at your attempt at being ironic.
Pot calling the kettle black?
that would be "you're kidding, right?"
and the response would be "you're illiterate right?"
LOLAYIAAPFASES
Oh - and users aren't allowed to modify their environments. ie - their home directories are read only. There is a sub-directory below their home directory where they can dork with stuff, but only there. They aren't allowed to modify their .profile / .bash_profile. They aren't allowed to write scripts in their home directories either. Their PATH variables are READ-ONLY, and disallow ./
Then again, most of our users are running financial software, and we cannot allow *customizations* for individual users.
In the environment that I manage, only the admins have sudo priveleges for any kind of system command.
Developers that need to run certain programs as other users (such as the userids that certain application services run as) we write scripts that can only be modified by root, and then give the individual users rights to run them. The scripts are written to disallow break-outs (like interrupt, kill, etc).
The admin users do not have access to the root account - unless the machine is down, and root access is needed to bring it up. Then we get the root passwords out of a lockbox, that requires management to get access to them.
The rest of the time, the admin users execute commands as needed via sudo. Any time an admin uses the sudo -s parameter, they have to add an entry to a log book as to why, what commands were run, and for what reason. All other commands run from sudo, are logged, and the log entries record to the equivelent of WORM storage.
If a user needs something changed, they submit a request to their supervisor, who then passes it on their manager. Management has to read, understand and approve the request, before forwarding on to the admins to have the work done. If it passes admin checks and approvals, then they can get it done. If it doesn't pass, then a discussion is started, as to why they thought they needed it, and their reasons behind it. Sometimes the users make silly requests because that's the only way they could think of to get something done. Usually one of the admins can come up with a better solution that solves the user's problem, without doing something odd to the rest of the system.
If a developer needs something done, the request has to pass a peer review before the request is ever submitted to the admins. Once submitted the process flows through very much like the user requests.
So in short, users NEVER get sudo access, developers rarely get sudo access, and when they do, it's very restricted to scripts they cannot modify. All sudo access records are written to media that once written, cannot be changed.
Woot - and now redundant for throwing my opinion of the modding in the face of the modder.
I think I smell a rat - a dirty stinking, karma burning, mod-opathic rat.
(Amazing what happens when you have Karma to burn, isn't it)
By definition, DAC's would NOT be illegal.
Because they convert digital to analog.
What I think would be made illegal, is all the movie and music studios, that take analog microphone, instrument and video input, then convert it to digital.
As you stated, the world we live in IS analog.
Isn't it ironic, that the RIAA and MPAA would promote a law that would make the equipment they use to make a living, illegal?
RIAA, MPAA - I'm laughing at your superior intellect. Care to try for a rematch?
WTF?
I get modded down for stating the truth?
LOL - Whatever.
Must have been an MS employee sneaking around here.
No.
I think what he's stating, is that MS will just decide to STOP providing product and services to ANY EU country. At which point, MS believes that the EU will back down, cowering and repeating the mantra of "Sorry, so sorry" over and over again.
No.
They'll just raise the prices of their software to increase their profits by 4.8Million a day.
Dongles anyone? Interposed between computer and device that override the repsonses to answer back as an *APPROVED* device for the non approved one.
DUH
Next idea please.
Here's one - track down those that traffic in the pirated goods, and arrest them.
Quit treating customers as criminals.
The only problem with carbon dating, is the maximum timeline it can be used for.
It cannot be used to go back to the beginning of time, only a very small percentage of it.
It requires that sunlight was hitting the entire planet for all of the time that the Earth was around.
Now given the story of Genesis and the flood, that would mean that the firmament, made up of water, surrounded most of, if not the entire earth from the time of creation, until the flood - this would mean that sunlight only struck the earth at the polar regions where the firmament would have been thinned out enough to allow sunlight through.
Given this, there would be nothing that would have been hit with sufficient sunlight to give accurate readings prior to the flood, except at the polar regions.
After the flood, the entire planet was in the path of the sunlight and could start building up quantities of carbon-14 in their makeup.