If you were to implement such a system, along with some sort of QoS monitor (a la Mozilla), you might be able to analyze the data from all the different builds and more easily figure out which kernel modules were interfering with each other and causing the instabilities in 2.4.x (the Kernel of Pain).
A solution has been proposed that is a hybrid of Napster and Gnutella; basically, it is a Gnutella-like network of volunteer-run Open-Nap-type servers. Most users would run as an end node, which would merely query, upload and download; a few, however, would run index servers, where all the searching would take place. End nodes would run as a client/server relationship to one (or more) of the indexing nodes, each of which would network with a few other indexing nodes. The result would be a file-sharing network nearly as efficient as Napster with the robustness of Gnutella.
I think Mr. Robertson should send an email to everyone whose information is being sent to Microsoft, warning them of the disclosure.
While he's at it, he should also provide a link to a poll on his website, asking whether any of those people had been initially confused when researching the new OS.
I think the results would be staggeringly positive, and I suspect they would make an impression on the judge.
(Better include a unique code with each email; wouldn't want Microsoft to stack the deck yet again...)
Two changes to this configuration would make it perfect, IMO...
No onboard video and an AGP slot on the opposite side of the board...
And for the case, a separate power supply module.
The result would be even more compact, and the components would be even smaller. Swap the A/C power module for one supplied by 12 volts, and you've got the perfect box for your vehicle.
I'd love it!...But it's not gonna happen any time soon. Running extra fiber while digging in the stuff you're using is relatively cheap, compared to the equipment you need to actually light it up. Otherwise it'd already be utilized.
Prices on the equipment needed are still coming down, though, thanks to new technology and economies of scale. So give it a few years, and your wishes may come true.
Really? I'm surprised. There are some applications where being able to allocate a big chunk of disk space for a buffer is important, and writing zeroes over it would slow things down. Are you sure there aren't any functions for doing so, hidden in the OS?
There are other reasons for keeping passwords in encrypted form as well, though such exploits are mostly limited to when people have physical access to the box. Not as likely, but still a good reason to routinely encrypt passwords.
There's a very good reason not to store passwords in plaintext -- even if the file containing the passwords has restricted permissions.
Adam decides to change one of the passwords. Adam loads the password file in vi, makes the change, exits, and walks away from his console, happy.
Bill, a guest-class user who wants higher-level access for nerfarious purposes, creates a file in/tmp and blindly allocates disk space. He then closes it and reads what it contains.
Well, when Adam saved the password file and closed, vi did the following: It created a new file containing the revised information, then deleted the old file, and finally renamed the new file to match the original file. The space allocated by the original file was released to be reused. When Bill allocated space for his temp file, he happened to get the same space the original file used -- and its contents.
Bill identifies the file fragment as having belonged to a password file. While one password was changed, there may be others which haven't; or the format of the password used may allow Bill to make some educated guesses about Adam's new one.
While this form of attack isn't always successful, password data can be exploited; and the more passwords on the system that aren't encrypted, the more likely one may be discovered. In other words: Routinely encrypt passwords!
I have a 1 gig microdrive, it came with my camera. Let me tell you, the amount of space is fantastic. I haven't had to delete anything in months. It's almost too much for a digicam.
There is one thing I don't like about it, though; it's much slower than flash memory. I've found it tends to restrain me from shooting quickly. Sometime soon I'll probably get a 256M flash card and move the microdrive into a compatible MP3 player.
> this looks like a ploy to try to get Linux Newbies
> to switch over because it has some fancy styling
> and Wine installed.
And this is such a bad thing? Linux could use a bigger user base. And a nice, standard distribution where the rest of the OS is tuned to WINE's operation is attractive to people dependent on Win32 apps.
The problem is the public money. While it may be a noble idea to set up enormous institutions to teach kids and give intellectuals a place to roost, it's also inappropriate to take my cash, via the Internal Revenue Service, to fund such an undertaking, whether or not I've approved of it. Just because people voted for the politicos who decided to spend my tax money on it doesn't make it right.
So let the universities profit from their intellectual property. Maybe they'll eventually make enough so that I, and the rest of the country, no longer have to subsidize them.
My cable company has been offering 4 HD channels (HBO East and West, SHO East and West) for free for some time, and when I decided to add a computer to my entertainment center, I took the plunge and bought a 35" Zenith HDTV/VGA monitor. It was a discontinued, slightly battered store demo, for "only" a thousand dollars. I grabbed it.
Well, I must report that HDTV is certainly all it is cracked up to be. Although the 4:3 ratio monitor squishes some display modes a bit when it letterboxes them (I suppose to get better vertical resolution), the difference in picture clarity is phenomenal. I'd have to say it equates with the difference between VHS and DVD.
The only that really irks me about the Zenith monitor is its inability to handle VGA at 800x600, despite its being able to display much higher HD resolutions. I think Zenith might've improved that in their newer models, though.
This isn't much different from the system already in use in the United States, where the metalized strips in our currency are encoded magnetically. The proposed system for the Euro is potentially more secure, given that information couldn't be read nor written without the correct codes, but is just as big a problem with regards to privacy.
Having credit card data available on your system is a huge potential problem; any security hole might be exploited, and even if none of the card #s are misused, it would make your customers very unhappy.
I'd recommend transferring the card numbers to another machine via a logging-type channel; in other words, send the card number and billing data to a logger on a machine with no other servers running. The fewer open ports, the less chance of the machine being exploited. An application on that machine could then read the log and insert the appropriate information into its database, and perform the billing functions as needed.
Slashdot Mirror
http://ars.userfriendly.org/cartoons/?id=20020120
We've got the technology; the bugs, the transmitters, the surveillance airplanes...
What do the Chinese have? Wen-Ho Lee?
I guess the Chinese are winning... -_-
If you were to implement such a system, along with some sort of QoS monitor (a la Mozilla), you might be able to analyze the data from all the different builds and more easily figure out which kernel modules were interfering with each other and causing the instabilities in 2.4.x (the Kernel of Pain).
A solution has been proposed that is a hybrid of Napster and Gnutella; basically, it is a Gnutella-like network of volunteer-run Open-Nap-type servers. Most users would run as an end node, which would merely query, upload and download; a few, however, would run index servers, where all the searching would take place. End nodes would run as a client/server relationship to one (or more) of the indexing nodes, each of which would network with a few other indexing nodes. The result would be a file-sharing network nearly as efficient as Napster with the robustness of Gnutella.
> Don't you remember how Microsoft engaged in
> blatant ballot stuffing
Yeah, that's why I added the last line to my original post. By adding a unique code for each email sent, they'd be able to control the results.
But I wasn't aware an email alert had already been sent. Thanks.
http://www.nyfairuse.org/law_is_copyrighted.xhtml1 b.asp
http://www.thompsonhine.com/news/nl/ebus_march200
Would this mean that all the source for software the NSA and CIA have been using would be made public?
:-)
Now that would be something I'd like to see...
I think Mr. Robertson should send an email to everyone whose information is being sent to Microsoft, warning them of the disclosure.
While he's at it, he should also provide a link to a poll on his website, asking whether any of those people had been initially confused when researching the new OS.
I think the results would be staggeringly positive, and I suspect they would make an impression on the judge.
(Better include a unique code with each email; wouldn't want Microsoft to stack the deck yet again...)
Two changes to this configuration would make it perfect, IMO...
No onboard video and an AGP slot on the opposite side of the board...
And for the case, a separate power supply module.
The result would be even more compact, and the components would be even smaller. Swap the A/C power module for one supplied by 12 volts, and you've got the perfect box for your vehicle.
I'd love it! ...But it's not gonna happen any time soon. Running extra fiber while digging in the stuff you're using is relatively cheap, compared to the equipment you need to actually light it up. Otherwise it'd already be utilized.
Prices on the equipment needed are still coming down, though, thanks to new technology and economies of scale. So give it a few years, and your wishes may come true.
Heh. Finally, the fabled machine code operators can be implemented...
HCF - Halt and Catch Fire
XOI - Execute Operator Immediately
Really? I'm surprised. There are some applications where being able to allocate a big chunk of disk space for a buffer is important, and writing zeroes over it would slow things down. Are you sure there aren't any functions for doing so, hidden in the OS?
There are other reasons for keeping passwords in encrypted form as well, though such exploits are mostly limited to when people have physical access to the box. Not as likely, but still a good reason to routinely encrypt passwords.
There's a very good reason not to store passwords in plaintext -- even if the file containing the passwords has restricted permissions.
/tmp and blindly allocates disk space. He then closes it and reads what it contains.
Adam decides to change one of the passwords. Adam loads the password file in vi, makes the change, exits, and walks away from his console, happy.
Bill, a guest-class user who wants higher-level access for nerfarious purposes, creates a file in
Well, when Adam saved the password file and closed, vi did the following: It created a new file containing the revised information, then deleted the old file, and finally renamed the new file to match the original file. The space allocated by the original file was released to be reused. When Bill allocated space for his temp file, he happened to get the same space the original file used -- and its contents.
Bill identifies the file fragment as having belonged to a password file. While one password was changed, there may be others which haven't; or the format of the password used may allow Bill to make some educated guesses about Adam's new one.
While this form of attack isn't always successful, password data can be exploited; and the more passwords on the system that aren't encrypted, the more likely one may be discovered. In other words: Routinely encrypt passwords!
I have a 1 gig microdrive, it came with my camera. Let me tell you, the amount of space is fantastic. I haven't had to delete anything in months. It's almost too much for a digicam.
There is one thing I don't like about it, though; it's much slower than flash memory. I've found it tends to restrain me from shooting quickly. Sometime soon I'll probably get a 256M flash card and move the microdrive into a compatible MP3 player.
> this looks like a ploy to try to get Linux Newbies
> to switch over because it has some fancy styling
> and Wine installed.
And this is such a bad thing? Linux could use a bigger user base. And a nice, standard distribution where the rest of the OS is tuned to WINE's operation is attractive to people dependent on Win32 apps.
The problem is the public money. While it may be a noble idea to set up enormous institutions to teach kids and give intellectuals a place to roost, it's also inappropriate to take my cash, via the Internal Revenue Service, to fund such an undertaking, whether or not I've approved of it. Just because people voted for the politicos who decided to spend my tax money on it doesn't make it right.
So let the universities profit from their intellectual property. Maybe they'll eventually make enough so that I, and the rest of the country, no longer have to subsidize them.
Then again, maybe pigs CAN fly.
Wasn't the Cult of the Dead Cow going to be releasing some software that did exactly this? Whatever happened to the project?
Can I get this for my Linksys hardware in a firmware update?
My cable company has been offering 4 HD channels (HBO East and West, SHO East and West) for free for some time, and when I decided to add a computer to my entertainment center, I took the plunge and bought a 35" Zenith HDTV/VGA monitor. It was a discontinued, slightly battered store demo, for "only" a thousand dollars. I grabbed it.
Well, I must report that HDTV is certainly all it is cracked up to be. Although the 4:3 ratio monitor squishes some display modes a bit when it letterboxes them (I suppose to get better vertical resolution), the difference in picture clarity is phenomenal. I'd have to say it equates with the difference between VHS and DVD.
The only that really irks me about the Zenith monitor is its inability to handle VGA at 800x600, despite its being able to display much higher HD resolutions. I think Zenith might've improved that in their newer models, though.
This isn't much different from the system already in use in the United States, where the metalized strips in our currency are encoded magnetically. The proposed system for the Euro is potentially more secure, given that information couldn't be read nor written without the correct codes, but is just as big a problem with regards to privacy.
Having credit card data available on your system is a huge potential problem; any security hole might be exploited, and even if none of the card #s are misused, it would make your customers very unhappy.
I'd recommend transferring the card numbers to another machine via a logging-type channel; in other words, send the card number and billing data to a logger on a machine with no other servers running. The fewer open ports, the less chance of the machine being exploited. An application on that machine could then read the log and insert the appropriate information into its database, and perform the billing functions as needed.
If you're going to do sousveillance on the Government, you might wind up like Jim Bell.
And then we'll have gibibytes (gibby-bytes), tebibytes (tabby-bytes), and pebibytes (oh, forget it)?
As if there isn't geeks are made fun of...
I was wrong. Doh!
The price on the website cited for the 1G USB drive is $700, not $900.