Contributed by dhartmei on from the favorable-reviews dept.
Not a week goes by without a new computer security bulletin being issued. The problem is particularly acute on servers, and diligent system administrators face an endless (and often thankless) task watching for security alerts and downloading the relevant patches as soon as these become available. Not surprisingly, a lot of sysadmins would kill for an operating system in which the code was carefully audited in advance so that vulnerabilities were squashed before they could be exploited. In the following article, we explore OpenBSD, an operating system built from the ground up with security in mind. Though not suitable for every taste, OpenBSD will no doubt save many system administrators gray hairs. Even for those not running a server, this is a very stable and powerful OS and you don't necessarily need to be paranoid (though it helps) to enjoy using it.
(Comments are closed)
By Anonymous Coward (208.252.48.163) on
I'm all for praising OpenBSD for what it's good at, but this is the case with any operating system, OpenBSD included: http://www.openbsd.org/errata.html
By James Nobis (64.244.122.155) on http://www.quelrod.net
By Dunceor (130.243.30.36) on
By Anonymous Coward (142.166.105.70) on
He got a few details in X installation a little muddled. He forgot 'X -configure' as a means to set up X, and you really don't need to add 'nolisten tcp' to anything since this is the default when X is launched from xdm (which he seems to have missed entirely).
Personally I don't find fdisk and disklabel all that confusing -- but in fairness I can barely remember when OBSD installs seemed new and strange.
I'd love to see somebody cover a 'simple' printer setup for your typical inkjet user using lpd, ghostscript, and a couple of script filters. Somehow this has never found it's way into the FAQ or as an example setup in printcap. It probably belongs there.
Comments
By SH (82.182.103.172) on
Comments
By Chris (139.142.208.98) on
Comments
By SH (82.182.103.172) on
Nope, you are wrong about this for i386. From OpenBSD FAQ Install section 4.5.2 we have
"Setting up disks in OpenBSD varies a bit between platforms. For i386 and macppc, disk setup is done in two stages. First, the OpenBSD slice of the hard disk is defined using fdisk(8), then that slice is subdivided into OpenBSD partitions using disklabel(8)."
Add to this that both of the man pages for fdisk and disklabel talks alot about partitions and how to edit them. Same goes for the output of the programs when installing OpenBSD. So, partitioning can be confusing the first few times.
/SH
By Anthony (192.208.10.217) on
By Peter Hessler (208.201.244.164) spambox@theapt.org on
Subscribe at http://mailman.theapt.org/listinfo/sfobug
Archives at http://marc.theaimsgroup.com/?l=openbsd-newbies&r=1&w=2
(Not sponsered by the OpenBSD project, just by the San Francisco OpenBSD Users Group)
By goon (220.253.49.128) goonmailALPHATANGOnetspaceDELTAnetDELTAau on http://slashdot.org/~goon
in *Obtaining OpenBSD* and installing there's no mention made of just downloading a base install and burning it to CD. While it is desirable to buy the official release there's nothing stopping you grabbing what you need and delaying the purchase
there is some emphasis in using obsd as a desktop and the lack of GUI pf tools ~ but nothing about how using the system in cli mode is pretty easy.
a useful inclusion might be the obsd package distro watch link, which I use to see what the focus of an OS really is.