On some other OS there is a need to have a custom kernel to support your hardware since their default kernels are pretty slim. Most OpenBSD users have no need to configure their kernel to make some hardware work. The GENERIC kernel is just fine where all drivers considered stable/reliable are enabled.
Some packages are ancient, but much of the ports tree is not. If you want to run the most updated packages, then you have to use -current. Note that not all updates makes it before code freeze, like the case with KDE for 3.7. KDE released 3.4 after code freeze for upcomming OpenBSD 3.7
I use OpenBSD for desktop, and for my needs it's very nice.
I don't understand why you undermine OpenBSD improvements in security. They made their improvements painlessly available for their users, and it works. What's so bad about that? It's not perfect, but sure beats "not used at all".
Thanks for playing. Perhaps you should come back once you understand what I wrote?
Why don't you just leave the telnet mentality behind and enter the age of ssh? Once upon a time one used su to make it harder for a packet sniffer to get the root password in a telnet session, but with ssh that is not the case. If you are worried that someone can get the root password while using ssh you have more serious problems to deal with, like you are rooted in the first place or using ssh authentication agent in an unsecure way.
Not permitting root logins does not give much added security, but probably gives you some much needed sense of security?
The summary covers two completely unrelated topics. One is the USPTOs rejection of Microsoft's attempt to extort the digital camera/USB stick makers (which is really what patenting FAT was about). The other story is about how Microsoft Office will never appear on Linux - so what, we don't want it.
Yes, and most posters did not understand that the important news in this is the rejection of some patent(s) related to FAT(32 only?). FAT (in it's various forms) is a fileformat that is supported on multiple OS, and is used to transport data from one OS to another. I for one use it when I transfer data via memory stick between Windows and OpenBSD. I could not care less about Microsoft Office on BSD/Linux, but Microsoft stopping me from using a well know fileformat for transporting data is an entierly another matter.
Don't work in cubicles, ever. Working in cubicles is the sure sign that you're not working for a successful company.
I worked at Google. We had cubicles. Good thing this guy came along to tell me it wasn't a successful company or I never would have known.
The problem with cubicles is that it's (usually) a noisy environment that makes it hard to concentrate, except for a few minutes. The efficiency and error-rate is lower in such environments.
Bugger, there is a missing "not" in my post. Here is the correct one:
Actually, several bugs in various ports was found because of this new allocator, as a search in the ports@ will show you. This does not imply, of course, that running Electric Fence will not find even more bugs.
I don't think the BSD allocator will reveal more software bugs unless the programmers have not tested with Electric Fence.
Actually, several bugs in various ports was found because of this new allocator, as a search in the ports@ will show you. This does not imply, of course, that running Electric Fence will find even more bugs.
Indeed, its a good step forward. Quite a few bugs in aplications in the OpenBSD ports tree was fixed because of this. A benefit for non-OpenBSD users as well.
1. OpenBSD already makes use of NX-bit protection (they call it W^X).
2. OpenBSD previously implemented stack protection (propolice + other stuff).
3. OpenBSD even implements W^X on non-NX-bit i386 through other techniques.
The last point is important since most i386 machines don't have the NX-bit, and that will be the case for many years to come.
SSH in as user, then su. Adds an extra layer of security to get through, provided there's no easy writable suid file and any root apps are kept up to date, and that kind of attack is harder to automate.
An extra layer with questionable benefit, assuming that your root password is strong in the first place.
Why the hell do they allow root logins over SSH in the first place?
Yeah, much better with a bunch of sudo-users so instead one root password you now have bunch of them. Besides, they should disable password login in any case.
And why should "Trusted Computing" be a problem for NSW? They (presumably) will have their needed applications running on *BSD/Linux, they'll use a standard format for exchanging documents with citizens (or offer several formats). If Microsoft et al is stupid enough to try hindering citicens from reading those documents on Windows, Microsoft will be in trouble.
Depends on who their members are, especially the more influential ones. If they are mostly authors whose books get published at 50,000 copies, then they have every reason to prefer the current system with gate keepers. It prevents competition.
Most books, like most music, that so many are so extremely keen on downloading, is mostly junk. Yes, the McDonalds of writing/music: Unite in extending the concept if "junk food". Most with a small audience has something to say, and they often tell it well.
They provide binary-only management tools for the RAID cards, and refuse to release good enough documentation to make a good open source alternative. This does not imply that Linux sucks, but that these vendors sucks.
It's for good reason OpenBSD (in the FAQ says) decided to disable Adaptec RAID support in GENERIC kernel i.e. whats considered reliable. The OpenBSD developers have mellowed somewhat later on since the FAQ entry about the removal of the Adaptec aac RAID driver from GENERIC is changed, to paraphrase (the original) "The aac driver is removed due to unreliability. What part of _unreliable_ is unclear to you?". Now it's just a "non-starter" in the FAQ.-)
The "American Dream" is the notion that anybody, if they work hard enough, will strike it rich.
The dream might have been true once, but not anymore. Today it's an illusion, a type of propaganda, to accept the status quo: That the very rich becomes ever more rich at the expense of the rest. Many have two jobs, but can't really makes end meets. They work hard, but they will never strike it rich. No Western country has such an uneven distribution of wealth and capital, and is so rich at the same time. But still the poor is left to fend for themselves as best as they can as recent events so tragically shows.
I've been running completely open-source soft RAID for years on Red Hat linux. My backup server, which uses the same basic idea as dirvish, uses a couple of terabytes of RAID10. There are even multiple RAID implementations freely available, although you are typically restricted by your choice of kernels.
You zealots never seem to realize your conception of the system you disdain is necessarily going to be incorrect, because you aren't going to spend the time required to really understand it. Concentrate on cheerleading you chosen religion's good points and stop trying to point out the other guy's bad points, that way you can show some real insight.
Dude, cool down, and read my post again. I was not talking about software RAID, but software to manage RAID cards. RAID card manufacturers, with LSI as an exception, does not give documention unless it's under NDA or similar. If they have some application to control the RAID card it's typically a Windows and/or Linux binary.
You're not particulary informed, it seems.
The RAID support in OpenBSD is very good, and what they've added is a unified RAID management system that will be expanded to more cards in the future. There is no LVM support in OpenBSD, thus it can't be redone. Yo seem to have heard that SMP support in OpenBSD is fairly recen,t kudos to you.
A critical importance of is, of course, stability and relability and then I don't want to be hold hostage to some binary-only shoddy RAID managment software running on Linux.
I don't have faith in the EU lasting. I don't have faith in Russia's solvency. I don't have faith in this project.
Well, the right-wing nutties currently in charge in USA agrees. It's foretold in the Most Holy of Printed Acid-Free Paper that there will be a Second Roman Empire run by a hexor that insists on leaving His mark 666 everywhere. Bloddy spammer.
How many applications does one need anyway? That's my desktop machine, which runs OpenBSD 3.7, with fluxbox, gkrellm, links-2, firefox, etc.
I don't really understand the people that chooses an OS because of the number applications available. What's is important is that the applications that you, as a user needs, are available.
How many applications does one need anyway? That's my desktop machine, which runs OpenBSD 3.7, with fluxbox, gkrellm, links-2, firefox, etc.
I don't really understand the people that chooses an OS because of the number applications available. What's is important is that the applications that you, as a user needs, are available.
Why don't the security conscious just use OpenBSD?
Some really clueless moderator modded you down as flamebait, go figure. I any case, the Linux kernel has had about 20-30 of local root exploits in the last year, and clearly the Linux kernel leaves something to be desired in this regard. It's also understandable that this happens due to the huge amount of new code, and the focus on performance (but not stability).
Slashdot Mirror
Some packages are ancient, but much of the ports tree is not. If you want to run the most updated packages, then you have to use -current. Note that not all updates makes it before code freeze, like the case with KDE for 3.7. KDE released 3.4 after code freeze for upcomming OpenBSD 3.7
I use OpenBSD for desktop, and for my needs it's very nice.
I don't understand why you undermine OpenBSD improvements in security. They made their improvements painlessly available for their users, and it works. What's so bad about that? It's not perfect, but sure beats "not used at all".
Thanks for playing. Perhaps you should come back once you understand what I wrote?
Why don't you just leave the telnet mentality behind and enter the age of ssh? Once upon a time one used su to make it harder for a packet sniffer to get the root password in a telnet session, but with ssh that is not the case. If you are worried that someone can get the root password while using ssh you have more serious problems to deal with, like you are rooted in the first place or using ssh authentication agent in an unsecure way.
Not permitting root logins does not give much added security, but probably gives you some much needed sense of security?
This is not 1995 anymore.
Yes, and most posters did not understand that the important news in this is the rejection of some patent(s) related to FAT(32 only?). FAT (in it's various forms) is a fileformat that is supported on multiple OS, and is used to transport data from one OS to another. I for one use it when I transfer data via memory stick between Windows and OpenBSD. I could not care less about Microsoft Office on BSD/Linux, but Microsoft stopping me from using a well know fileformat for transporting data is an entierly another matter.
The problem with cubicles is that it's (usually) a noisy environment that makes it hard to concentrate, except for a few minutes. The efficiency and error-rate is lower in such environments.
$ cd /tmp
$ cat > rtfm.c
#include stdio.h
int main () { printf("RTFM\n"); }
$ cc rtfm.c
rtfm.c:1:10: #include expects "FILENAME" or
$
Hmh, perhaps "man cc" will give you some hints ;-)
Actually, several bugs in various ports was found because of this new allocator, as a search in the ports@ will show you. This does not imply, of course, that running Electric Fence will not find even more bugs.
Actually, several bugs in various ports was found because of this new allocator, as a search in the ports@ will show you. This does not imply, of course, that running Electric Fence will find even more bugs.
Indeed, its a good step forward. Quite a few bugs in aplications in the OpenBSD ports tree was fixed because of this. A benefit for non-OpenBSD users as well.
1. OpenBSD already makes use of NX-bit protection (they call it W^X).
2. OpenBSD previously implemented stack protection (propolice + other stuff).
3. OpenBSD even implements W^X on non-NX-bit i386 through other techniques.
The last point is important since most i386 machines don't have the NX-bit, and that will be the case for many years to come.
An extra layer with questionable benefit, assuming that your root password is strong in the first place.
Yeah, much better with a bunch of sudo-users so instead one root password you now have bunch of them. Besides, they should disable password login in any case.
And why should "Trusted Computing" be a problem for NSW? They (presumably) will have their needed applications running on *BSD/Linux, they'll use a standard format for exchanging documents with citizens (or offer several formats). If Microsoft et al is stupid enough to try hindering citicens from reading those documents on Windows, Microsoft will be in trouble.
Most books, like most music, that so many are so extremely keen on downloading, is mostly junk. Yes, the McDonalds of writing/music: Unite in extending the concept if "junk food". Most with a small audience has something to say, and they often tell it well.
Hey, man pages are for free, so why can't I make some quick bucks?
Sincerely (sort of)
Mr O'Reilly
Yeah, I know, I should not read /.
It's for good reason OpenBSD (in the FAQ says) decided to disable Adaptec RAID support in GENERIC kernel i.e. whats considered reliable. The OpenBSD developers have mellowed somewhat later on since the FAQ entry about the removal of the Adaptec aac RAID driver from GENERIC is changed, to paraphrase (the original) "The aac driver is removed due to unreliability. What part of _unreliable_ is unclear to you?". Now it's just a "non-starter" in the FAQ .-)
The dream might have been true once, but not anymore. Today it's an illusion, a type of propaganda, to accept the status quo: That the very rich becomes ever more rich at the expense of the rest. Many have two jobs, but can't really makes end meets. They work hard, but they will never strike it rich. No Western country has such an uneven distribution of wealth and capital, and is so rich at the same time. But still the poor is left to fend for themselves as best as they can as recent events so tragically shows.
You zealots never seem to realize your conception of the system you disdain is necessarily going to be incorrect, because you aren't going to spend the time required to really understand it. Concentrate on cheerleading you chosen religion's good points and stop trying to point out the other guy's bad points, that way you can show some real insight.
Dude, cool down, and read my post again. I was not talking about software RAID, but software to manage RAID cards . RAID card manufacturers, with LSI as an exception, does not give documention unless it's under NDA or similar. If they have some application to control the RAID card it's typically a Windows and/or Linux binary.
Read the commentary to the OpenbSD 3.8 song.
A critical importance of is, of course, stability and relability and then I don't want to be hold hostage to some binary-only shoddy RAID managment software running on Linux.
Well, the right-wing nutties currently in charge in USA agrees. It's foretold in the Most Holy of Printed Acid-Free Paper that there will be a Second Roman Empire run by a hexor that insists on leaving His mark 666 everywhere. Bloddy spammer.
I don't really understand the people that chooses an OS because of the number applications available. What's is important is that the applications that you, as a user needs, are available.
How many applications does one need anyway? That's my desktop machine, which runs OpenBSD 3.7, with fluxbox, gkrellm, links-2, firefox, etc.
I don't really understand the people that chooses an OS because of the number applications available. What's is important is that the applications that you, as a user needs, are available.
Some really clueless moderator modded you down as flamebait, go figure. I any case, the Linux kernel has had about 20-30 of local root exploits in the last year, and clearly the Linux kernel leaves something to be desired in this regard. It's also understandable that this happens due to the huge amount of new code, and the focus on performance (but not stability).