In marketroid-speak, superior; implies a product imbued with exclusive magic by the unmatched brilliance of the company's own hardware or software designers.
In the language of hackers and users, inferior; implies a product not conforming to open-systems standards, and thus one that puts the customer at the mercy of a vendor able to gouge freely on service and upgrade charges after the initial sale has locked the customer in.
50m? There are plenty of cavities in Earth that are bigger than that. My local underground carpark, for example.
You are correct, but a car park isn't really underground, in the sense that it is supporting a lot of overburden. I didn't catch how deep these cavities were supposed to be and my number was for overburdens of ~1km.
So, on one hand, the caverns must be high enough so that the rock presure doesn't cause collapse, but must be deep enough so that the overburden is hard and strong enough to be supportive. Either way, 200 km cavities are just pretty hard to believe, even in Mars's lower gravity.
Of course, if it were true, it would be totally cool to visit them. This may be the reaction NASA intentended to achieve with their suppositions.
The channels have been filled in with sediment, they theorize. They're not just empty caverns in the rock.
But, if they were supposed to have once held water, they would still have to be self supporting. That is, unless one wants to theorize that the water pressure was constant and was helping to support the cavity (which is even harder to believe).
Even in Mars's (1/3 g?, I forget) gravity, I really doubt that a 200 km wide cavity could hold up. On Earth with good hard rock, 50 m is about all you get. What am I missing here?
I just grepped through Debian's great bug tracking pages (www.debian.org/Bugs). Here are some of the results:
Pending bugs: 13413
Forwarded upstream bugs: 1084
There are 702 grave, critical or important bugs (subset of pending) the rest ``normal'' or ``wishlist''.
This illustrates one more reason free/open software and processes are nice. We can find out just what is wrong with Debian, how it will effect our actuall use, and where we might help in fixing it.
In the case of MS bugs, the 65000 number is completely meaningless. Are their bugs show stoppers, or are many of them due to someone not liking the shade used to color a menu? Will the bug really hurt our use or are the applications we use uneffected? Is there any way to work around or fix these bugs, now today and with out waiting for MS? All these questions go unanswered.
I'm talking about negligence here, though. If you leave your loaded gun on the front step and somebody uses it to commit a crime, you can probably expect some repercussions.
I don't think so. The gun would be stolen. This offense would just be added onto the offense of using the gun in the commission of the crime. The only way leaving the gun could be negligence is if the gun owner aggreed (as part of the gun licence) to proper storage (which the front step certainly isn't). It may actually be part of getting a gun licence, I wouldn't know, but I doubt that a person putting a server on the net must agree to such a thing. I know I never have had to.
Similarly, leaving a system that has well-known and documented problems with easily available remedies on the Internet could be viewed as a form of negligence.
Ignoring what I said above, I would also find it hard to equate committing a crime with a gun to be similar to a DoS attack.
However, in theory I aggree with you. Both putting up insecure servers as well as storing a loaded gun on the front step is morally negligent, I just don't think you would win any lawsuits. Of course, with MickyDees getting sued for overly hot coffee, I could be proven wrong.
If your system is cracked, and then used to attack me, can I sue you for negligence? How else do we get companies to put proper practices in place?
Probably not.
This is a slippery slope. I feel one should blame the person who breaks the law not someone who innocently contributed to the possibility of the law being broken. To blame the owner of the cracked system used for a DoS attack is like blaming the owner of a stolen car for it's use in a bank robbery, or to blame the kids who wrote DeCSS for the (potential) piracy of DVDs.
Furthermore, in the case of cracked machines being used for DoS attacks, there is no contractual requirement for the owners of those machines to put secure servers onto the net, so I doubt your lawsuit would be successful. You would probably obtain better results by publicizing the need for server maintainers to be more aware of implications of an insecure machine.
After reading his claims that his work is ``past the scientific verification stage'' while it won't be until January that he ``will submit [his] findings to a premier [yet unamed] scholarly journal'' it makes me wonder how carefully he paid attention when he was attending Harvard and MIT (if he actually did). Peer review is at the heart of scientific verification.
Mr. Mills: just what grade did you get in your physics class?
Strangely, I would suggest just the opposite. I get the most pain when using keyboards which are too close to me. I prefer to have from my elbow to my wrist supported by the desk and wrist pad.
I think that it is more important to just pay attention to yourself. I started getting severe pains in both arms near the wrists (using the above position!). Consiously and slightly altering my exact possition eventually brough relief.
One thing for sure, however, is it is SCARY when you start getting these pains!
Debian itself takes security pretty seriously. Often it is Debian releasing a security related bug fix long before other big distributions. There was a recent bug fix which RH trumpeted but which had been fixed by Debian more than a year previously.
The only time I have had one of my Debian machines broken into is when I had failed to head the Debian Security Advisories.
In reality the entire scientific community is bunch of argumentative ego-maniacs (who will be first against the wall when the revolution comes)
While I agree somewhat with your first statement (I am part of this comunity so I know first hand), I think your second is childish and ignorant. With out this comunity of argumentative ego-maniacs you would not have been able to express your ``learned'' opinion in this/. forum.
suggested reading this nice document on "Time Paradox" dealing with the grandfather paradox etc, its just as much crap but it has nicer formatting and pretty side bar.
I see you have your priorities straight. Why don't you go watch TV, it has lots of pretty pictures for you. You'll like it.
Van Eck devices can read what's on your computer monitor from halfway down the street. (I heard that the CIA demonstrated this for Scott McNealy at Sun; they captured his password from a van in the company's parking lot.)
I first heard of Van Eck freaking (imaging of computer screens by detection of emitted radiation) and while at first I was skeptical, I was eventually convinced it would be possible (my laptop screen lets off a LOT of noise as windows or pointers are moved, so picking this up doesn't seem impossible).
However, in reading the above it seems to me that either McNealy has his password printed in plain text on the screen (I don't see why he would, all password entries I know of either don't show characters or just show `*'s), or somehow the demo applied Van Eck methods to something other than the screen (keyboard? memory??). Does anyone have details on this?
Almost true. Strangely, you can't select a URL in NS and paste it in to the window from which is was selected. You must paste it to another NS window (or plop it into the ``Location:'' bar).
We also used this scheme, (so far: ale, bock and stout) when we started populating our offices with Linux boxen in `94. In particular, the name ``bock'' has great room for upgrading as when the single CPU machine goes to a dual CPU, you can rename it ``duppel-bock''.
Version 8.6 is very stable, by Mac standards, and approaches that of the Unix world. I do tech support for an office of 30, and have iMacs, G3s and even older models, like the 4400s and 6500's that go days or weeks without crashes or involuntary restarts.
I recently bought a G4-400 w/ MacOS 8.6 for my wife. It is hardly stable. We find it locks up or the pointer freezes or acts erratic at a rate of almost once per hour.
As far as your claim that MacOS approaches Unix stability because your macs stay up for ``days or weeks'', I think you are implicitly denegrating Unix (although, I assume unintentionally). For Unix, anything less than an infinite uptime is considered a failure (ignoring down time due to things like new kernels or hardware installs). For the most part (for most of the stable kernels) and barring hardware problems, this has been true of for our Linux boxen.
I hope that one day MacOS does obtain this level of stability as it is a really cute platform to work on.
It's surprising but some locations in the ocean have water clear enough that the attenuation length is about 200m. For example, the DUMAND site off Hawai'i had water that was about that clear. For comparision 18megaohm (100% pure) water has an attenuation length of about 300m so its not that bad.
200m seems a stretch. The clearest SK has been is 80m - 100m, depending on how you measure it. I can't imagine ocean water being clearer than SK water. If you are correct, then it is indeed surprising.
The Internet is STILL a tiny club of culturally-elite, rich (compared to the rest of the world) burgoise representing everything despised by Marx. Despite our burgeoning population, we represent a tiny fraction of priveleged humanity trodding upon the backs of the repressed masses.
From the latest issue of Wired magazine (and my memory) something like 1/3 to 1/2 of US is online. Something like 1/4 to 1/3 of Jp is online. Most other countries had a smaller fraction online, but this is definitely not a tiny club and it is one which is growing rapidly.
And, much of the ``gifts'' of which you speak are written by poor students and academicians and not culturally-elite rich.
The Free Software culture is far from Communism. It more resembles Nepotism, with the talented, rich few giving away to the less-talented rich few -- yet all members of the same, elite club.
Nepotism is favoritism shown to family members. The free software culture is about the freedom for anyone to use and modify software. For the former, anyone can play, for the latter, admittedly one must be technically able.
I must agree with the comments noted in the review from others: The idea that the "gift culture" is communism is hogwash.
Chapter 11 is a titled "Writing a GtkWidget" and is well-written, but I question its usefulness to anyone but library developers.
I think encapsulating things into widgets is one of the primary strengths of any toolkit. Even if you are writing an app and not contributing to a library, writing widgets allows you to build a much more flexable program. I actually wish there was more, not less, focus on writing good widgets as well as subclassing and combining existing ones.
That said, I agree with most of the review. Besides numerous typos (which are undoubtably fixed or to be fixed in the online version) this book is extreamely useful for anyone learning GTK and GNOME programming.
This is just a guess, but it looks like the main thing they make is a 4 CPU PCI expansion board. So, if you have a single CPU mac with a PCI bus and you add one card you have 1 + 4 cpus. This also makes sense as they say at one place in their page that you can have 13 CPUs (1 + 3*4).
Here is a pic from their page which lead me to this assumption.
proprietary /adj./
I imagine this copter would auto-rotate if it ran out of fuel, just like any other. You would fall, but not like a brick, more like a leaf.
You are correct, but a car park isn't really underground, in the sense that it is supporting a lot of overburden. I didn't catch how deep these cavities were supposed to be and my number was for overburdens of ~1km.
So, on one hand, the caverns must be high enough so that the rock presure doesn't cause collapse, but must be deep enough so that the overburden is hard and strong enough to be supportive. Either way, 200 km cavities are just pretty hard to believe, even in Mars's lower gravity.
Of course, if it were true, it would be totally cool to visit them. This may be the reaction NASA intentended to achieve with their suppositions.
But, if they were supposed to have once held water, they would still have to be self supporting. That is, unless one wants to theorize that the water pressure was constant and was helping to support the cavity (which is even harder to believe).
Even in Mars's (1/3 g?, I forget) gravity, I really doubt that a 200 km wide cavity could hold up. On Earth with good hard rock, 50 m is about all you get. What am I missing here?
- Pending bugs: 13413
- Forwarded upstream bugs: 1084
There are 702 grave, critical or important bugs (subset of pending) the rest ``normal'' or ``wishlist''.This illustrates one more reason free/open software and processes are nice. We can find out just what is wrong with Debian, how it will effect our actuall use, and where we might help in fixing it.
In the case of MS bugs, the 65000 number is completely meaningless. Are their bugs show stoppers, or are many of them due to someone not liking the shade used to color a menu? Will the bug really hurt our use or are the applications we use uneffected? Is there any way to work around or fix these bugs, now today and with out waiting for MS? All these questions go unanswered.
But, I guess I am not saying anything new here.
I don't think so. The gun would be stolen. This offense would just be added onto the offense of using the gun in the commission of the crime. The only way leaving the gun could be negligence is if the gun owner aggreed (as part of the gun licence) to proper storage (which the front step certainly isn't). It may actually be part of getting a gun licence, I wouldn't know, but I doubt that a person putting a server on the net must agree to such a thing. I know I never have had to.
Similarly, leaving a system that has well-known and documented problems with easily available remedies on the Internet could be viewed as a form of negligence.
Ignoring what I said above, I would also find it hard to equate committing a crime with a gun to be similar to a DoS attack.
However, in theory I aggree with you. Both putting up insecure servers as well as storing a loaded gun on the front step is morally negligent, I just don't think you would win any lawsuits. Of course, with MickyDees getting sued for overly hot coffee, I could be proven wrong.
Probably not.
This is a slippery slope. I feel one should blame the person who breaks the law not someone who innocently contributed to the possibility of the law being broken. To blame the owner of the cracked system used for a DoS attack is like blaming the owner of a stolen car for it's use in a bank robbery, or to blame the kids who wrote DeCSS for the (potential) piracy of DVDs.
Furthermore, in the case of cracked machines being used for DoS attacks, there is no contractual requirement for the owners of those machines to put secure servers onto the net, so I doubt your lawsuit would be successful. You would probably obtain better results by publicizing the need for server maintainers to be more aware of implications of an insecure machine.
http://slashdot.org/comments.pl?sid=00/01/24/20242 33&cid=338
http://www.cs.nmsu.edu/~joshagam/css/
THE CRACKPOT INDEX (see #7)
Poor Mr. Mills quickly racks up the points.
After reading his claims that his work is ``past the scientific verification stage'' while it won't be until January that he ``will submit [his] findings to a premier [yet unamed] scholarly journal'' it makes me wonder how carefully he paid attention when he was attending Harvard and MIT (if he actually did). Peer review is at the heart of scientific verification.
Mr. Mills: just what grade did you get in your physics class?
I think that it is more important to just pay attention to yourself. I started getting severe pains in both arms near the wrists (using the above position!). Consiously and slightly altering my exact possition eventually brough relief.
One thing for sure, however, is it is SCARY when you start getting these pains!
The only time I have had one of my Debian machines broken into is when I had failed to head the Debian Security Advisories.
While I agree somewhat with your first statement (I am part of this comunity so I know first hand), I think your second is childish and ignorant. With out this comunity of argumentative ego-maniacs you would not have been able to express your ``learned'' opinion in this /. forum.
suggested reading this nice document on "Time Paradox" dealing with the grandfather paradox etc, its just as much crap but it has nicer formatting and pretty side bar.
I see you have your priorities straight. Why don't you go watch TV, it has lots of pretty pictures for you. You'll like it.
Maybe he meant to use the scotch to help start a fire with the blanket. A workable short term solution....
I first heard of Van Eck freaking (imaging of computer screens by detection of emitted radiation) and while at first I was skeptical, I was eventually convinced it would be possible (my laptop screen lets off a LOT of noise as windows or pointers are moved, so picking this up doesn't seem impossible).
However, in reading the above it seems to me that either McNealy has his password printed in plain text on the screen (I don't see why he would, all password entries I know of either don't show characters or just show `*'s), or somehow the demo applied Van Eck methods to something other than the screen (keyboard? memory??). Does anyone have details on this?
Almost true. Strangely, you can't select a URL in NS and paste it in to the window from which is was selected. You must paste it to another NS window (or plop it into the ``Location:'' bar).
We also used this scheme, (so far: ale, bock and stout) when we started populating our offices with Linux boxen in `94. In particular, the name ``bock'' has great room for upgrading as when the single CPU machine goes to a dual CPU, you can rename it ``duppel-bock''.
I recently bought a G4-400 w/ MacOS 8.6 for my wife. It is hardly stable. We find it locks up or the pointer freezes or acts erratic at a rate of almost once per hour.
As far as your claim that MacOS approaches Unix stability because your macs stay up for ``days or weeks'', I think you are implicitly denegrating Unix (although, I assume unintentionally). For Unix, anything less than an infinite uptime is considered a failure (ignoring down time due to things like new kernels or hardware installs). For the most part (for most of the stable kernels) and barring hardware problems, this has been true of for our Linux boxen.
I hope that one day MacOS does obtain this level of stability as it is a really cute platform to work on.
-Brett.
... allow us to finally observe proton decay by 2050.
200m seems a stretch. The clearest SK has been is 80m - 100m, depending on how you measure it. I can't imagine ocean water being clearer than SK water. If you are correct, then it is indeed surprising.
BTW, who are you?
From the latest issue of Wired magazine (and my memory) something like 1/3 to 1/2 of US is online. Something like 1/4 to 1/3 of Jp is online. Most other countries had a smaller fraction online, but this is definitely not a tiny club and it is one which is growing rapidly.
And, much of the ``gifts'' of which you speak are written by poor students and academicians and not culturally-elite rich.
The Free Software culture is far from Communism. It more resembles Nepotism, with the talented, rich few giving away to the less-talented rich few -- yet all members of the same, elite club.
Nepotism is favoritism shown to family members. The free software culture is about the freedom for anyone to use and modify software. For the former, anyone can play, for the latter, admittedly one must be technically able.
I must agree with the comments noted in the review from others: The idea that the "gift culture" is communism is hogwash.
Agreed.
I think encapsulating things into widgets is one of the primary strengths of any toolkit. Even if you are writing an app and not contributing to a library, writing widgets allows you to build a much more flexable program. I actually wish there was more, not less, focus on writing good widgets as well as subclassing and combining existing ones.
That said, I agree with most of the review. Besides numerous typos (which are undoubtably fixed or to be fixed in the online version) this book is extreamely useful for anyone learning GTK and GNOME programming.
Thanks Havoc!
That should be ``... envy the cosmonauts'', eh?!
This is just a guess, but it looks like the main thing they make is a 4 CPU PCI expansion board. So, if you have a single CPU mac with a PCI bus and you add one card you have 1 + 4 cpus. This also makes sense as they say at one place in their page that you can have 13 CPUs (1 + 3*4).
Here is a pic from their page which lead me to this assumption.