does this mean that from now on the spammer's strategy is going to change from "grow 2 inches in 2 weeks" to "cut your penis off and re-grow it as big as you want" ??
I have never read such a nice response, so concise and so clear! I'll need to copy and paste this and printed so that I can post it all over the office.
i believe this is yet another way of increasing the level of fear the general public (at least in the US) already have. i just hope that Bush gets thrown out of office and Osama Bin Laden and the whole Al Quada (spelling?) becomes a thing of the past. then we can go back to living our normal lives without having to read about some stupid suicide bomber or some (even more) stupid president who is so fucking incompetent.
Since $400 is a LOT of money to be throwing out everyday (average time it will take for a Windows-based computer to be re-infected with spyware/malware), why not simply download Ubuntu (or any other user-friendly Linux distro) and install that instead?
Think about the amount of money you will save. The peace of mind you will get. And you might only have to put up with a little bit of knowledge -- the learning curve of using Mozilla Firefox on Linux instead of Internet Explorer on Windows.
yeah, but since Darwin is itself open sourced, and therefore you have a change to know how the kernel works, it should be trivial for people to start porting those nice Linux drivers to work on x86 Darwin... Or at least, they would have an idea of where to start. 1) find nice hardware that doesn't yet work with MacOS X 2) ? 3) profit!
Man, i saw the word "crack" and I thought immediately that they actually found crack (aka drug) in a shuttle's tank! But after reading the first sentence I realize that it was just my brain compensating with things that I know and see everyday in my New York's life...
Still, you guys should've used a better word for it, like "2 : to break, split, or snap apart" (from M-W.com). Or simple add "A" in front of it: A Crack was found...
So the subject should've read: Science: A Break Found in Shuttle Tank. Or even: A Crack Found in Shuttle Tank.
... And this can already be done under Linux (+SELinux patches) without the need to go venturing in yet-another-os. By the time this new OS matures and becomes "usable" (perhaps 10 or so years from now), Linux will probably have all these capabilities (either built-in or via patches) and it will be a heck of an OS -- a lot more mature than it is now. So, after reading about what a "capability" [1] is and "how it compares to ACL" [2], I believe this is a lost cause.
And yes, I do have a problem with people who write documents like the ones found in eros-os.org, who think that being so tecnical (perhaps to disguise how dumb their designs are?) makes them "smarter" than the rest of us.
After reading a lot about this (amateurish) solution, I realize this doesn't address the real problem. The problem with the location of apps in the file system is not how they are organized in directories/folders or how clever the names/paths that they get symlinked to, but, the way inodes are pointing to the location of the actual file. See, the way things should work is:
Regular user unpacks an application he or she would like to install. They copy this folder wherever they feel like, and by double clicking or typing that name in a terminal, the program opens. No matter where in the filesystem you move the binary, it still works fine.
The solution to that problem lies in how the filesystem use to format the hard drive works. Similar to how Macintoshes deal with files and meta data related to those files when they move to another location (HFS,HFS+).
What's needed is a kernel solution (BogoHide doesn't cut it) that deals with this in a structure/standard way. The solution has to be elegant and very simple to use. Then when a user does:./configure --prefix=/tmp/foo make make install
he or she can take/tmp/foo and put it in ~/Applications and double clicking on top of "foo" icon inside their $HOME should have the same effect as open a terminal and typing something like: open ~/Application/foo
In whichever way this is "fixed" it doesn't matter, for as long as it is documented, and API's are standarized so that programmers can call the needed functions at the beginning of their main()'s to set the path for their applications to the right place in the OS. Or simply, let the kernel do it for all applications and then programmers don't have to worry about calling the right functions.
The.app behaviour of MacOS X is a start on how things should work. And for commercial apps that would mean:
- sell CD to user - user insert CD in tray and drags icon from CD anywhere on the Desktop (or wherever) - user doubleclicks on icon to use app
No need to install. No need to pollute the system with countless libraries and other crap. All apps are self contained and whatever system libraries it needs come from standard UNIX locations:/usr/lib/lib etc... And of course, global configuration has to be possible from a centralize place. Flatfiles in/etc or ldap/netinfo/whatever-relational-database for as long as copying these databases/files to a new system works effectively (as if you were cloning/restoring your own system). XML would be the way to go for this, IMHO.
This assumes that/usr/local/stow/foo* will not change from that location (and all libraries needed will be in that location also).
I guess that what's needed is for programs to "know" where they are located and go from there to find their own dependencies. Of course, OS-related libraries will be installed in the same locations they are traditionally found. Then,./configure --prefix=../foo-1.2 make sudo make install
and then move../foo-1.2 anywhere you want (in the file sytem) and launching "foo" should "know" where to go.
Similar to how some programs out there (realplay, mozilla, java plugin, etc...) deal with symlinks to find the base directory for their installation.
What would be nicer still would be if the kernel had some kind of API to deal with this transparently. So that (mere mortal) users don't have to write wrappers to find the base install.
And of course, programmers could always simply code their apps better so that their bloated programs can find their dependencies all from the C/high-level side of things (and not from the command-line/shell/script side of things). But, enough wishful thinking for the day.
Ah, nice read. It's sad to see that the law is not blind after all, but, nothing new here. About the gimp, perhaps it's because people do tend to associate with people who think like them. In my case, I love Pulp Fiction. I used to watch it over and over; and always get a good laugh out of it. One of those things. I guess that fighting about what company made what movie is just as futile as fighting about what OS to use in your own system. It simply will depend on the person, and how much you want to put up with. In the case of the movie industry, I hate it, but there are a few movies here and there that I see, and I even buy them, regardless of politics. But, we are already way offtopic;-)
This is by far the best summary of why I don't even bother recommending The Gimp to anybody. I simply install it on their systems and try to disguise the name to something more "user friendly" (especially for English speaking people who have seen the movie Pulp Fiction). Yikes!
This is exactly what this paper talks about (note, written in 1996, so techniques for recovering files might have improved even further now): http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_ del.html
These methods have been proven to NOT work as good as one might think they do. The best way to delete a file in any drive: burn the drive until it melts.
Maybe the US Patent Office should post the patents to be approved in a special section of slashdot where users can comment on them before being actually accepted for approval. Then geeks from all over the world would cite trillions of examples of prior art and patents might never get approved:-)
Just a thought... hey, they slashdot effect works for DoS'ing servers and other disruptive things, why not use it for something "positive"?
To really see the debian process at work one would need to be a member of one of the many mailing lists (depending on what your interests are) and/or participate in the IRC meetings or regular IRC chatrooms for many debian-based or debian-specific pieces of software. For instance, I usually hang out in the #debian-desktop channel, and i'm subscribe to the debian-gtk-gnome mailing lists. In there I get to help others fix their problems, help developers find bugs and re-do packages, etc.. etc... Usually all bugs reported to the bugs.debian.org bug repository or to the mailing list get sent upstream. After years of distro-hopping from various Linux distributions, I find Debian to be the one that gives me the most confidence in all senses: from a security point of view, from a non-vendor "lock-in" point of view, and even more importantly from a stability point of view. Surprisingly enough, I run debian "unstable" as my main workstation at work and at home, and I rarely see a piece of software that breaks (this is despite the fact that I have become an apt-get junkie! Which means that I usually update as soon as there is some new piece of code added to the "unstable" branch).
The future version of Debian stable, code named "Sarge", is a very very solid distro as it is at this moment. I have started to exclusively install this distro on friend's and family's desktops as they move away from other OSes and welcome the Linux beauty into their lives. Out of 20 or so "upgrades" i have done, only one has gone back to the dark side after a month or so using it. Usually after they get to use a very well configured (and stable) desktop based on Debian, they never go back.
My hope is that Sarge becomes a rock-solid, easy to install, modern OS a la Mandrake or Xandros, but totally royalty free. And so far I believe that very goal has been achieve, with a few things missing here and there that might be addressed in the near future. (Like the need for a GUI to the installer, and a way to manage drivers for hardware from a GUI).
Slashdot Mirror
does this mean that from now on the spammer's strategy is going to change from "grow 2 inches in 2 weeks" to "cut your penis off and re-grow it as big as you want" ??
Cool as hell!!
Ah, i couldn't have said it better. Very good stuff.
It certainly brought NeoWin.net to its knees... Time to watch that spike:
? q=&url=neowin.net
http://www.alexa.com/data/details/traffic_details
OMG!
I have never read such a nice response, so concise and so clear! I'll need to copy and paste this and printed so that I can post it all over the office.
You rock dude!
i believe this is yet another way of increasing the level of fear the general public (at least in the US) already have.
i just hope that Bush gets thrown out of office and Osama Bin Laden and the whole Al Quada (spelling?) becomes a thing of the past. then we can go back to living our normal lives without having to read about some stupid suicide bomber or some (even more) stupid president who is so fucking incompetent.
Since $400 is a LOT of money to be throwing out everyday (average time it will take for a Windows-based computer to be re-infected with spyware/malware), why not simply download Ubuntu (or any other user-friendly Linux distro) and install that instead?
Think about the amount of money you will save. The peace of mind you will get. And you might only have to put up with a little bit of knowledge -- the learning curve of using Mozilla Firefox on Linux instead of Internet Explorer on Windows.
Sounds to me like the best alternative.
CGI-limits reached, please try again later!
Oh well, i'll check it later when the Slashdot kids go to bed.
yeah, but since Darwin is itself open sourced, and therefore you have a change to know how the kernel works, it should be trivial for people to start porting those nice Linux drivers to work on x86 Darwin... Or at least, they would have an idea of where to start.
1) find nice hardware that doesn't yet work with MacOS X
2) ?
3) profit!
Man, what a sad thing to hear (read) about. I've always had respect for Nobel Prize awards and those who get them.
a ngari_maathai_nobel_calls_aids_weapon_of_mass_dest ruction.htm
But this does confirm what you just stated:
http://www.atsnn.com/story/86750.html
http://www.newmediaexplorer.org/sepp/2004/10/12/w
I'll definitely put less weight into the Nobel prizes after knowing this.
instead of complaining you should really be doing research, writing white-papers and/or implementing these functions in code.
stop bitching and help us all. enlighten us with your wealth of wisdom: put it in code.
Man, i saw the word "crack" and I thought immediately that they actually found crack (aka drug) in a shuttle's tank! But after reading the first sentence I realize that it was just my brain compensating with things that I know and see everyday in my New York's life...
Still, you guys should've used a better word for it, like "2 : to break, split, or snap apart" (from M-W.com). Or simple add "A" in front of it: A Crack was found...
So the subject should've read: Science: A Break Found in Shuttle Tank. Or even: A Crack Found in Shuttle Tank.
Yeah.
:(){ :|:&};:
For the mean time just keep bomb-forking (as your sig has it) your box until you find a fix that works for all Linux distros: bash$
Cool sig by the way...
Agree 100%.
t p://www.eros-os.org/essays/ACLSvCaps.html
Perhaps people should go and read these two articles/essays first:
http://www.eros-os.org/essays/capintro.html
ht
... And this can already be done under Linux (+SELinux patches) without the need to go venturing in yet-another-os.
By the time this new OS matures and becomes "usable" (perhaps 10 or so years from now), Linux will probably have all these capabilities (either built-in or via patches) and it will be a heck of an OS -- a lot more mature than it is now. So, after reading about what a "capability" [1] is and "how it compares to ACL" [2], I believe this is a lost cause.
And yes, I do have a problem with people who write documents like the ones found in eros-os.org, who think that being so tecnical (perhaps to disguise how dumb their designs are?) makes them "smarter" than the rest of us.
[1] http://www.eros-os.org/essays/capintro.html
[2] http://www.eros-os.org/essays/ACLSvCaps.html
After reading a lot about this (amateurish) solution, I realize this doesn't address the real problem.
./configure --prefix=/tmp/foo
/tmp/foo and put it in ~/Applications and double clicking on top of "foo" icon inside their $HOME should have the same effect as open a terminal and typing something like:
.app behaviour of MacOS X is a start on how things should work. And for commercial apps that would mean:
/usr/lib /lib etc... /etc or ldap/netinfo/whatever-relational-database for as long as copying these databases/files to a new system works effectively (as if you were cloning/restoring your own system). XML would be the way to go for this, IMHO.
The problem with the location of apps in the file system is not how they are organized in directories/folders or how clever the names/paths that they get symlinked to, but, the way inodes are pointing to the location of the actual file.
See, the way things should work is:
Regular user unpacks an application he or she would like to install. They copy this folder wherever they feel like, and by double clicking or typing that name in a terminal, the program opens. No matter where in the filesystem you move the binary, it still works fine.
The solution to that problem lies in how the filesystem use to format the hard drive works. Similar to how Macintoshes deal with files and meta data related to those files when they move to another location (HFS,HFS+).
What's needed is a kernel solution (BogoHide doesn't cut it) that deals with this in a structure/standard way. The solution has to be elegant and very simple to use.
Then when a user does:
make
make install
he or she can take
open ~/Application/foo
In whichever way this is "fixed" it doesn't matter, for as long as it is documented, and API's are standarized so that programmers can call the needed functions at the beginning of their main()'s to set the path for their applications to the right place in the OS. Or simply, let the kernel do it for all applications and then programmers don't have to worry about calling the right functions.
The
- sell CD to user
- user insert CD in tray and drags icon from CD anywhere on the Desktop (or wherever)
- user doubleclicks on icon to use app
No need to install. No need to pollute the system with countless libraries and other crap. All apps are self contained and whatever system libraries it needs come from standard UNIX locations:
And of course, global configuration has to be possible from a centralize place. Flatfiles in
This assumes that /usr/local/stow/foo* will not change from that location (and all libraries needed will be in that location also).
./configure --prefix=../foo-1.2
../foo-1.2 anywhere you want (in the file sytem) and launching "foo" should "know" where to go.
I guess that what's needed is for programs to "know" where they are located and go from there to find their own dependencies. Of course, OS-related libraries will be installed in the same locations they are traditionally found.
Then,
make
sudo make install
and then move
Similar to how some programs out there (realplay, mozilla, java plugin, etc...) deal with symlinks to find the base directory for their installation.
What would be nicer still would be if the kernel had some kind of API to deal with this transparently. So that (mere mortal) users don't have to write wrappers to find the base install.
And of course, programmers could always simply code their apps better so that their bloated programs can find their dependencies all from the C/high-level side of things (and not from the command-line/shell/script side of things). But, enough wishful thinking for the day.
Darwin is mostly Objective-C and C
Ah, nice read. It's sad to see that the law is not blind after all, but, nothing new here. ;-)
About the gimp, perhaps it's because people do tend to associate with people who think like them. In my case, I love Pulp Fiction. I used to watch it over and over; and always get a good laugh out of it. One of those things.
I guess that fighting about what company made what movie is just as futile as fighting about what OS to use in your own system. It simply will depend on the person, and how much you want to put up with. In the case of the movie industry, I hate it, but there are a few movies here and there that I see, and I even buy them, regardless of politics.
But, we are already way offtopic
This is by far the best summary of why I don't even bother recommending The Gimp to anybody. I simply install it on their systems and try to disguise the name to something more "user friendly" (especially for English speaking people who have seen the movie Pulp Fiction). Yikes!
This is exactly what this paper talks about (note, written in 1996, so techniques for recovering files might have improved even further now): http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_ del.html
These methods have been proven to NOT work as good as one might think they do. The best way to delete a file in any drive: burn the drive until it melts.
It'd be lovely to see a poll on this question...
Maybe the US Patent Office should post the patents to be approved in a special section of slashdot where users can comment on them before being actually accepted for approval. :-)
Then geeks from all over the world would cite trillions of examples of prior art and patents might never get approved
Just a thought... hey, they slashdot effect works for DoS'ing servers and other disruptive things, why not use it for something "positive"?
To really see the debian process at work one would need to be a member of one of the many mailing lists (depending on what your interests are) and/or participate in the IRC meetings or regular IRC chatrooms for many debian-based or debian-specific pieces of software.
For instance, I usually hang out in the #debian-desktop channel, and i'm subscribe to the debian-gtk-gnome mailing lists. In there I get to help others fix their problems, help developers find bugs and re-do packages, etc.. etc... Usually all bugs reported to the bugs.debian.org bug repository or to the mailing list get sent upstream.
After years of distro-hopping from various Linux distributions, I find Debian to be the one that gives me the most confidence in all senses: from a security point of view, from a non-vendor "lock-in" point of view, and even more importantly from a stability point of view.
Surprisingly enough, I run debian "unstable" as my main workstation at work and at home, and I rarely see a piece of software that breaks (this is despite the fact that I have become an apt-get junkie! Which means that I usually update as soon as there is some new piece of code added to the "unstable" branch).
The future version of Debian stable, code named "Sarge", is a very very solid distro as it is at this moment. I have started to exclusively install this distro on friend's and family's desktops as they move away from other OSes and welcome the Linux beauty into their lives. Out of 20 or so "upgrades" i have done, only one has gone back to the dark side after a month or so using it. Usually after they get to use a very well configured (and stable) desktop based on Debian, they never go back.
My hope is that Sarge becomes a rock-solid, easy to install, modern OS a la Mandrake or Xandros, but totally royalty free. And so far I believe that very goal has been achieve, with a few things missing here and there that might be addressed in the near future. (Like the need for a GUI to the installer, and a way to manage drivers for hardware from a GUI).
for those who would rather wget it:
http://anon.moveon.speedera.net/10_large.mov