|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
is openbsd really for me?
Ive been using openbsd since 3.3 but i admit that it doesnt mean that I know much about it at all. Basically what I do is that install latest version, update it to stable and install the packages that is needed, which so far has been a few imageconversions,archivers, sambaprograms,web and after that I never touch it cause I want stability and its been stable as rock. After 1-3 years i buy new hardware and do a complete install from scratch and move the needed. Ive jumped from 3.3->3.6->4.0
I havent kept on updating nor upgraded to latest version, which is a securityrisk, i know, but the thing is if i upgrade (and how) and something doesnt works like a charm im in a world of pain, because my lack of knowledge. I do not intend to learn every bit and pieces of how the system works, i dont care and is honestly not intrested.. I just feel safe with openbsd. Would I be better off with a linuxdist that has automatic updates? will be in same world of pain if it crashes. And now I need to add a torrentclient, which has to be updated to latest version or it wont work with a tracker im using. I also need to install a Direct Connect hub for me and my closest friends, which im not sure there is any packages at all for? About updates, i understand the securityrisk but at the same time, if you dont mess with a working system, that system can keep running forever. What do you think is better if you look at the security, openbsd not updated after inital install or linuxdist with automatic upgrades? and what do you think will be most stable system? Last edited by knasbas; 8th January 2009 at 03:31 PM. |
|
||||
I think that OpenBSD is probably not good choice for you right now since you are seeking some excitement.
OpenBSD is one of the most boring OS in existence. For the most part it just works rock stable and it is too safe so people can actually do their work instead of playing with OS. Occasional hick ups have been observed on OpenBSD running systems deployed by less than perfect users. We are currently having a pledge week at undeadly.org trying to rise some money which will help developers introduce some bugs and instabilities into the system. If you think you have a good idea about new bug you want to see in OpenBSD this is the time come out publicly with some money which will help developers implement your ideas. |
|
|||
Quote:
If you look at any system that is being actively kept up to date then at any one point in time, I would say that OpenBSD might be no better than <anything else>. BUT I would like to further qualify that statement by saying that it only applies to the basic install -- anything else you add (say, a torrent client) might not be as actively maintained -- it's a matter of upstream quality, no matter how actively you keep your system up to date -- and in that perspective I think it's safe to assume that OpenBSD trumps anything. (Isn't that why OpenBSD is slow to include all the latest bells and whistles, that they need to ensure it's up to par first, which takes time?) Sorry for the rant. You need to consider if you're focusing on security, stability, or features.
__________________
KlaymenDK -- 010\001\111 -- Last edited by KlaymenDK; 8th January 2009 at 05:33 PM. |
|
|||
Quote:
|
|
|||||||
Quote:
Quote:
Quote:
Quote:
Security is not something you buy, download, or install. Security is a process. A continuous process. Using the example I cited above, OpenBSD may be "secure by default" but has had two remote attack vectors exposed in its lifetime. How many unexposed ones exist now? No one knows about the third (or fourth..) until it is discovered, analyzed, and published. Is one there? No one knows for sure, but I'll guess that more will be uncovered over time.That's it for remote security issues. What about internal problems that affect security? From the beginning of the Project to present day, internal attack vectors are discovered, analyzed, published, and patched. For example, since support ceased for 4.0, there have been six serious security patches published.More security flaws will be found, and that continuous process to improve security will continue, through the life of the Project. Quote:
Quote:
Quote:
|
|
|||
I am so dissapointed that im almost speechless. Either my english is so bad that almost none understood what i wrote or asked or noone just cared cause it was more entertaining to explain to me about security and updates.
Do you think i do not know its meant to upgrade 3.6-3.7-3.8 and to keep all patches up to date? Why doesnt some understand "I do not intend to learn every bit and pieces of how the system works, i dont care and is honestly not intrested.."? I do understand that some people is spending alot of time and energy and is very dedicated to learn about their system and the flaws, but isnt it possible to keep openbsd safe without rtfm of every possible little command there is in unix? Why cant i have stability, security and features? and to tell me im confused, gees man thats really so low i wont even comment. |
|
|||
We understand, but it's simple.. if you do not care, why should we?
If you do not care about the systems you maintain, you probably shouldn't be maintaining anything. Quote:
|
|
||||
In terms of maintenance, you're going to get a lot more pain out of GNU/Linux than you would out of any BSD or SVRX Unix. I wouldn't migrate to GNU/Linux.
If you don't tinker, then a system can run infinitely, but you might be at a disadvantage running an older build. For example, a new version may have performance enhancements that may improve your productivity. To keep system up-to-date, you don't need to learn every single element of the Unix command line. You only need to know a few commands. On FreeBSD, you need to know five variations of the same command to update the system. I'm sure it's even simpler if you use binary updates. http://quickdc.sourceforge.net/ Check that link out for your dc needs.
__________________
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." MacBook Pro (Darwin 9), iMac (Darwin 9), iPod Touch (Darwin 9), Dell Optiplex GX620 (FreeBSD 7.1-STABLE) |
|
|||
Hi there,
people usually post for technical assistance, hence the nature of the replies you got. I will attempt a more holistic answer Are you sure what you want can be achieved in a single OS or single box (given that we are not programmers with loads of time on our hands)? As a sysadmin, I use OpenBSD for its exceptional security, stability and quality control (I use it for servers, firewalls and my workstations). For family & friends I have to use PC-BSD because I don't have the time to make a consumer-friendly environment out of OpenBSD. If I need the latest apps, gizmo, hardware or features, I find myself using Windows (client servers and desktop). But as you know, Windows security is an illusion (check f-secure's frontpage...), and stability & quality is compromised by the rapid pace of development and diversity of 3rd party apps. I think the combination you want can only be achieved by spending loads of time on compiling your own distribution It is a well known trade-of for design engineers and programmers that out of the triangle of quality, features & time-to-market, you can only have 2 at the same time Maybe there is a linux distro out there that fits your needs (Debian is most closely aligned to OpenBSD's ethos of quality control and security), but I won't spend time on Linux as I see it as being as much of a convoluted mess as windows is and it will be the next target for the malware industry (26,500 unique windows virus signatures per hour in November 2008...) |
|
||||||
Quote:
Quote:
Quote:
Quote:
If this is too much for you, choose a different OS. Quote:
Quote:
|
|
||||
Quote:
And that's not OpenBSD's fault- that's true for any operating system, any set of applications. Quote:
But it's also quite clear that you are also the system administrator of the machine, and system administrators must have a thorough understanding of what they are administrating, or pay someone else to. The prime example of this is any normal residential user's home system. They have absolutely zero knowledge of their operating system or applications, but they don't have anyone even semi-professional looking after their system. And so it gets hacked. If you take the same approach, you'll eventually have the same level of risk, regardless of what you use.
__________________
Network Firefighter |
Thread Tools | |
Display Modes | |
|
|