Win9x was designed for/on 486s, so were the older WMs.. the newer versions of KDE and Gnome were designed for/on faster machines (like the ones using Windows XP today). You need to relate Gnome/Ximian/KDE to WindowsXP and some of the older window managers to Win9x.
I'll agree with you that alot of these newer linux window managers are too slow, but I think this lies inherent in the nature of linux. There's many ways to do the same thing (take gtk/qt , etc for example) And everything has to be compatible with everything else so naturally programs will take up more ram and run slower (most noticibly in the window manager), but if we're dealing with a uniformed standard where there's only one way to do most things (windows) then alot of functionality is cut off.
I think it would be fine if everyone could agree on a uniformed standard for linux, and then progress from there. But then linux would become another windows and taht's the last thing we want.
At 99 dollars, I've got cash to blow to be the first on the block to get a cool gadget. If it sucks, I'll sell it to some jackoff like myself on e-bay for 85 plus 20 shipping.
You can... but who the hell would want to? Buy a bunch of used pentiums or 486s from your local computer shop for a third of the price, and you've got something that not even 30 of these running together would do.
Re:maybe the best server OS is not the best PDA OS
on
Linux PDA Part Deux
·
· Score: 2, Insightful
Scalability! It's really exciting to see that Linux can be scaled down to reliably run on something like this. It's really neat that an OS can be written to run on 15mhz hardware with 8 megs of ram or a 60 ghz beowulf cluster with terabytes of ram.
Instead of GPS, I think we should work on developing IPS (Interstellar Positioning System) We could do it with current GPS technology, just face the dishes away from the Earth... lose something on accuracy and we'd need a new coordinate system for space, but hey, we're gonna need it anyway in a few hundred years.
Wow, that's what I'm talkin bout. I don't care if it's done before, it's something I'd always wanted, but never bothered to look for/write. This is great
Why would microsoft agree to this? It doesn't make any sense. They won't lose anything if they give out the software (they own it, it costs them next to nothing to duplicate). They will also be seen as in alliance with the open source people. They'll actually lose money if they have to buy all that extra hardware. Seems like RedHat is just trying to make borg look bad.
If I remember correctly, they did a kind of similar thing when the Exxon Valdez oil ship crashed... I think there was some bacteria that had been engineered to live off oil, and so they dropped some bacteria on the oil and that cleaned up much of it. This is from my freshman biology class, so I'm not quite sure if it's accurate.
I'd like to point out that whatever the government's intentions may be, it's near impossible to prevent DOS attacks on any form of computing platform. I personally think that if the goal is to keep government communications going, then this is a better idea than trying to develop protocols for Internet 2 that will be invulnerable to DOS attacks.
The creators of video games are artists.
on
Are Videogames Art?
·
· Score: 1
The creators of video games are artists, their brush is a keyboard and a mouse, their paint is electrons. Their canvas is a hard drive. What they develop out of these tools can take the breath away from anyone. Video game worlds are expansive, alluring, and wonderful worlds that can rival our own. Video game creators are developing a new kind of interactive art that astounds everyone.
Just because something is different from the norm doesn't make it not art. It makes it different. If people didn't agree with this then people like Van Gogh, Picasso, etc. would never have been considered artists.
Ok, first off, I really do think that we need to catalog these worms, but it doesn't seem useful to me to have 50,000+ slashdot readers cataloging the same vulnerability. Second, the best way to secure a system is to write secure code. Although many of these attacks are original and new, most of them could be avoided if programmers just learned some secure coding practices (eg. not using strcpy(), I swear, that must account for 90% of root compromises) Also, maybe sysadmins should pay a little more attention to keeping their system secure. Set up your system securely to begin with, and then it's not that hard to check securityfocus.com once a day to see if there are new vulnerabilities in the daemons that you run. If there are, install the patch. It's that simple, really.
The fact that I don't specialise in intrusion detection doesn't mean that I didn't do anything. You should really do your research before making accusations that i didn't do anything. If you want to read something I've done, pick up the latest issue of 2600 and read my article entitled "Myths about TCP spoofing". Besides, I think an article specializing in how to write secure code might be better... or an article about how to patch your system as soon as a new vulnerability is announced. There's absolutely no reason to announce to 50,000+ slashdot readers "Let's all catalog the log entries of the same worm!" Especially when there are people who have set up boxes all over the internet to serve only this function.
I completely disagree on this one, there are tons of ways to get root on any given system, and all different kinds of command sequences... and if you've ever heard of a polymorphic virus, it may utilise many of these different ways to obtain root on a system, and randomize the order in which they are used. That's just one of the many things that these worm writers can think of.
My point was, we're improving the IDS rules and filters after the fact, rendering it useless to most new worms. Improving IDS rules and building better filters DOES improve the security of the server (that's what Intrusion Detection Systems are for, most IDS's I know don't JUST detect an intrusion, but also kick out possible intruders) And although checking your logs is good to see if you were the intended target of the attack, if you're even a half-assed sysadmin, you should be able to tell if you've been infected with a worm. My point was that it does very little to help against new worms, because, contrary to popular belief the people who write these worms are pretty clever.
It makes me angry that everyone decides to beef up security and write analytical articles about how to maintain security AFTER THE FACT. The problem is, that although this seems like a good idea now, fingerprinting probably won't help for the next series of attacks, because they will be different in nature.
Either a motion sensor or a program that will compare the last image taken to the one before that, if they are the same, it's just a pointer, or something like that... 90kb down to 4 bytes should save plenty of space.... just a thought.
You would be suprised how readily you can find routers (important ones!!) that use default passwords... try writing a little perl script that will traceroute to slashdot, cut up the output, and goes through a database of default passwords (this site has one), or even just cisco/cisco or enable/cisco in a telnet connection (99% of the time to port 23). I would be willing to bet that if it takes 10 hops to get there, 4 of them will use default passwords. AND THIS IS ON THE BACKBONE!!! Just imagine the number of routers sitting on the edge of a corporate network as their principle gateway that use default passwords. Scary. Very scary.
You neglected to explain that at least one computer must be on for you to use this. While this may be OK for the/. crowd, it just doesn't cut it for the typical consumer.
Slashdot Mirror
Win9x was designed for/on 486s, so were the older WMs.. the newer versions of KDE and Gnome were designed for/on faster machines (like the ones using Windows XP today). You need to relate Gnome/Ximian/KDE to WindowsXP and some of the older window managers to Win9x.
I'll agree with you that alot of these newer linux window managers are too slow, but I think this lies inherent in the nature of linux. There's many ways to do the same thing (take gtk/qt , etc for example) And everything has to be compatible with everything else so naturally programs will take up more ram and run slower (most noticibly in the window manager), but if we're dealing with a uniformed standard where there's only one way to do most things (windows) then alot of functionality is cut off.
I think it would be fine if everyone could agree on a uniformed standard for linux, and then progress from there. But then linux would become another windows and taht's the last thing we want.
LOTR has been at the top spot on IMDB since at least friday. That's 2 days after it's release... wow.
At 99 dollars, I've got cash to blow to be the first on the block to get a cool gadget. If it sucks, I'll sell it to some jackoff like myself on e-bay for 85 plus 20 shipping.
You can... but who the hell would want to? Buy a bunch of used pentiums or 486s from your local computer shop for a third of the price, and you've got something that not even 30 of these running together would do.
Scalability! It's really exciting to see that Linux can be scaled down to reliably run on something like this. It's really neat that an OS can be written to run on 15mhz hardware with 8 megs of ram or a 60 ghz beowulf cluster with terabytes of ram.
Just DAYS after I ordered my PowerPlay III PDA. Oh well, what're you gonna do? Does anyone have any links to reviews of the PowerPlay III? Thanks.
don't forget terrorists!
Fuck you all mother fuckers! Slashdot is the trashiest site on the internet! Haha, lets see you sue me for libel.
Instead of GPS, I think we should work on developing IPS (Interstellar Positioning System) We could do it with current GPS technology, just face the dishes away from the Earth... lose something on accuracy and we'd need a new coordinate system for space, but hey, we're gonna need it anyway in a few hundred years.
Wow, that's what I'm talkin bout. I don't care if it's done before, it's something I'd always wanted, but never bothered to look for/write. This is great
for the Attack Of The Clones!
Why would microsoft agree to this? It doesn't make any sense. They won't lose anything if they give out the software (they own it, it costs them next to nothing to duplicate). They will also be seen as in alliance with the open source people. They'll actually lose money if they have to buy all that extra hardware. Seems like RedHat is just trying to make borg look bad.
If I remember correctly, they did a kind of similar thing when the Exxon Valdez oil ship crashed... I think there was some bacteria that had been engineered to live off oil, and so they dropped some bacteria on the oil and that cleaned up much of it. This is from my freshman biology class, so I'm not quite sure if it's accurate.
I'd like to point out that whatever the government's intentions may be, it's near impossible to prevent DOS attacks on any form of computing platform. I personally think that if the goal is to keep government communications going, then this is a better idea than trying to develop protocols for Internet 2 that will be invulnerable to DOS attacks.
The creators of video games are artists, their brush is a keyboard and a mouse, their paint is electrons. Their canvas is a hard drive. What they develop out of these tools can take the breath away from anyone. Video game worlds are expansive, alluring, and wonderful worlds that can rival our own. Video game creators are developing a new kind of interactive art that astounds everyone.
Just because something is different from the norm doesn't make it not art. It makes it different. If people didn't agree with this then people like Van Gogh, Picasso, etc. would never have been considered artists.
Why only digital play? What about the radio? Seems to me that the record companies shouldn't get any money except from record sales.
Ok, first off, I really do think that we need to catalog these worms, but it doesn't seem useful to me to have 50,000+ slashdot readers cataloging the same vulnerability. Second, the best way to secure a system is to write secure code. Although many of these attacks are original and new, most of them could be avoided if programmers just learned some secure coding practices (eg. not using strcpy(), I swear, that must account for 90% of root compromises) Also, maybe sysadmins should pay a little more attention to keeping their system secure. Set up your system securely to begin with, and then it's not that hard to check securityfocus.com once a day to see if there are new vulnerabilities in the daemons that you run. If there are, install the patch. It's that simple, really.
The fact that I don't specialise in intrusion detection doesn't mean that I didn't do anything. You should really do your research before making accusations that i didn't do anything. If you want to read something I've done, pick up the latest issue of 2600 and read my article entitled "Myths about TCP spoofing". Besides, I think an article specializing in how to write secure code might be better... or an article about how to patch your system as soon as a new vulnerability is announced. There's absolutely no reason to announce to 50,000+ slashdot readers "Let's all catalog the log entries of the same worm!" Especially when there are people who have set up boxes all over the internet to serve only this function.
I completely disagree on this one, there are tons of ways to get root on any given system, and all different kinds of command sequences... and if you've ever heard of a polymorphic virus, it may utilise many of these different ways to obtain root on a system, and randomize the order in which they are used. That's just one of the many things that these worm writers can think of.
My point was, we're improving the IDS rules and filters after the fact, rendering it useless to most new worms. Improving IDS rules and building better filters DOES improve the security of the server (that's what Intrusion Detection Systems are for, most IDS's I know don't JUST detect an intrusion, but also kick out possible intruders) And although checking your logs is good to see if you were the intended target of the attack, if you're even a half-assed sysadmin, you should be able to tell if you've been infected with a worm. My point was that it does very little to help against new worms, because, contrary to popular belief the people who write these worms are pretty clever.
It makes me angry that everyone decides to beef up security and write analytical articles about how to maintain security AFTER THE FACT. The problem is, that although this seems like a good idea now, fingerprinting probably won't help for the next series of attacks, because they will be different in nature.
I still don't see the "tremendous improvement" of perl 6 over perl 5 in practical use. IMHO nothing has really changed between the two versions.
Either a motion sensor or a program that will compare the last image taken to the one before that, if they are the same, it's just a pointer, or something like that ... 90kb down to 4 bytes should save plenty of space.... just a thought.
You would be suprised how readily you can find routers (important ones!!) that use default passwords... try writing a little perl script that will traceroute to slashdot, cut up the output, and goes through a database of default passwords (this site has one), or even just cisco/cisco or enable/cisco in a telnet connection (99% of the time to port 23). I would be willing to bet that if it takes 10 hops to get there, 4 of them will use default passwords. AND THIS IS ON THE BACKBONE!!! Just imagine the number of routers sitting on the edge of a corporate network as their principle gateway that use default passwords. Scary. Very scary.
You neglected to explain that at least one computer must be on for you to use this. While this may be OK for the /. crowd, it just doesn't cut it for the typical consumer.