I might be wrong, but I believe that the spread of malaria is largely due to badly constructed houses into which the fly is able to enter through cracks during night. If the money went into establishing better living conditions in the affected areas, the threat of malaria in those areas would be lesser, as well as having obvious additional benefits for the people living there.
Plan 9 failed simply because it fell short of being a compelling enough improvement on Unix to displace its ancestor. Compared to Plan 9, Unix creaks and clanks and has obvious rust spots, but it gets the job done well enough to hold its position. There is a lesson here for ambitious system architects: the most dangerous enemy of a better solution is an existing codebase that is just good enough.
I think all operating system providers are going to walk into this sooner or later. Sooner if they have a big user base already, later if they serve a niche. At some point people will be happy with what they have, and the software industry will have to come up with more ways to waste CPU cycles to get them to upgrade to the next big thing.
To suggest there is no difference is not only untrue, but vaguely insulting to the project.
That would be insulting myself since I'd like to see myself as a contributor to it.
I think that you misunderstand me. Security is, in the end, in the hands of the administrator, no matter what the operating system might be. If security is your main issue, then by all means choose OpenBSD if you think it'll save your day. Personally, I picked OpenBSD because it was small, fully featured, quick to install and easy to maintain. If you say it'll save me from evil, hey, that's even better.
Code and bug-fixes are shared between the BSD projects, and none of them takes security lightly. Any security-related bug found in a project will be fixed in the others, where applicable. The OpenBSD code audits does find and fix bugs, not all security-related, and that all good.
You are right that OpenBSD provides sane defaults, and I hope the other BSDs do the same. I just don't like the "NetBSD is for portability, OpenBSD is for security"-thing. They're both portable and secure. In the wrong hands, they are both as secure as an unboiled egg.
(By the way, OpenBSD did not come from FreeBSD, Theo started it in '95 when he got kicked out of the NetBSD core team after a fallout with some of its members.)
OpenBSD for security, NetBSD for portability and FreeBSD for diffusion in the wider world (ie, comparable to Linux).
Bollocks!
If your playground is i386-type systems, like it is in the case of the OP, and if he has some common sense, then the three operating systems are more or less the same in terms of security and software availability. He should just pick the one he finds most fun/simple to administrate.
It's really not at all that hard to install all the BSDs, one after the other, and try them out. There's not that many of them... and what better way to get to learn the systems?
All the BSD projects have excellent documentation, easily accessible from their respective web sites. They all have good mailing lists for users who can both RTFM and RTFFAQ but who still gets stuck with problems.
Honestly, if you rely on other people's opinions on what operating system to choose for personal use, you will get a system that you think you'd like, instead of a system that you feel comfortable with.
Other interesting tidbits: Swedish youth were more than twice as likely to select the right choice for the size of the US population, where the options were "between 10 and 50 million", "between 150 and 350 million", "between 500 and 750 million", "between 1 billion and 2 billion" or "I don't know".... Hardly a difficult question. Even so, only 55% of the Swedish youth (who did best on this question) got it right.
Since we can safely assume that the *BSD developers are running their own OS, this implies that the 5 developers are very, very productive!
I think that you even can assume that at least two of those five developers are running more than their own BSD, and maybe even a Linux distribution on the side.
Now that sounds even stranger. The telescope wasn't even built back then... Put the word "from" in the appropriate place to make it better, or start talking about distance and how far away the objects are instead.
Unfortunately, this won't work on XP (which has no DOS box), so you're forced to use notepad or something which will append.txt to the end of any file, and then you have to go into explorer and rename it, hope to god that the user won't get scared by the "if you change the file extention, this file name not be usuable anymore" warning, and so on.
Just name it "Uninstall.pky" (including the double quotes) in Notepad.
I never thought that I would give a Windows tip... shudder...
Re:Business Models or "Developers, developers!"
on
Minitel Hits Twenty
·
· Score: 1
A stretch of about 30 years. The internet is 1.5 times the age of minitel.
I think the author confused Internet and World Wide Web, a not too common thing to do.
Will email, if charged per-piece, be any different?
How would that be implemented in a secure and reliable way? In the MUA or in the MTA? How would mailing lists be treated? How would you get everyone to use it (and not start using e-mail by ftp, http, or some other tunnel)? Would there be a threshold that you had to pass before the charge was applied? Where to place that threshold and would it be in bytes or in number of e-mails?
Slashdot Mirror
Do you really need to patent the software to sell a good product nowadays?
RFC 1178 addresses this.
I might be wrong, but I believe that the spread of malaria is largely due to badly constructed houses into which the fly is able to enter through cracks during night. If the money went into establishing better living conditions in the affected areas, the threat of malaria in those areas would be lesser, as well as having obvious additional benefits for the people living there.
Just my 2p.
Also, it was hard to get money from companies, and almost everything seems to have come from caring individuals: message here
... until someone builds a easy-to-carry and effective laser/microwave-based weapon...
That's the most innovative use of Rubik's cube I've seen in a while! Bravo! I also like the use of the VCR eject feature.
You can't compare percentages like that and come to the conclusion that women are leaving the IT market without mentioning the actual numbers...
For a BSD solution, try pkgsrc.
Don't forget bgpd. Together, they make the guys that bought Cisco boxes look pretty dumb.
That would be insulting myself since I'd like to see myself as a contributor to it.
I think that you misunderstand me. Security is, in the end, in the hands of the administrator, no matter what the operating system might be. If security is your main issue, then by all means choose OpenBSD if you think it'll save your day. Personally, I picked OpenBSD because it was small, fully featured, quick to install and easy to maintain. If you say it'll save me from evil, hey, that's even better.
Code and bug-fixes are shared between the BSD projects, and none of them takes security lightly. Any security-related bug found in a project will be fixed in the others, where applicable. The OpenBSD code audits does find and fix bugs, not all security-related, and that all good.
You are right that OpenBSD provides sane defaults, and I hope the other BSDs do the same. I just don't like the "NetBSD is for portability, OpenBSD is for security"-thing. They're both portable and secure. In the wrong hands, they are both as secure as an unboiled egg.
(By the way, OpenBSD did not come from FreeBSD, Theo started it in '95 when he got kicked out of the NetBSD core team after a fallout with some of its members.)
Bollocks!
If your playground is i386-type systems, like it is in the case of the OP, and if he has some common sense, then the three operating systems are more or less the same in terms of security and software availability. He should just pick the one he finds most fun/simple to administrate.
It's really not at all that hard to install all the BSDs, one after the other, and try them out. There's not that many of them... and what better way to get to learn the systems?
All the BSD projects have excellent documentation, easily accessible from their respective web sites. They all have good mailing lists for users who can both RTFM and RTFFAQ but who still gets stuck with problems.
Honestly, if you rely on other people's opinions on what operating system to choose for personal use, you will get a system that you think you'd like, instead of a system that you feel comfortable with.
I don't think that the email addresses has to be valid, or even present. The person signing a key only has to be sure of who the key belongs to.
The correct answer is "I don't know", right?
Green Hills Software, Inc. has registered INTEGRITY 5.0 PPC as conforming to the 1003.1-2003 System Interfaces Product Standard.
Coincidence?
Closed-source projects have the same issue.
I think that you even can assume that at least two of those five developers are running more than their own BSD, and maybe even a Linux distribution on the side.
Now that sounds even stranger. The telescope wasn't even built back then... Put the word "from" in the appropriate place to make it better, or start talking about distance and how far away the objects are instead.
Sure, go ahead! That's what the MirBSD people did after all...
Just pick one of the BSDs and try it out. Noone knows what's best for you but yourself.
Just name it "Uninstall.pky" (including the double quotes) in Notepad.
I never thought that I would give a Windows tip... shudder...
I think the author confused Internet and World Wide Web, a not too common thing to do.
You didn't read the license, did you?
How would that be implemented in a secure and reliable way? In the MUA or in the MTA? How would mailing lists be treated? How would you get everyone to use it (and not start using e-mail by ftp, http, or some other tunnel)? Would there be a threshold that you had to pass before the charge was applied? Where to place that threshold and would it be in bytes or in number of e-mails?