Linked by Thom Holwerda on Wed 20th Jun 2007 20:07 UTC, submitted by Valour
OpenBSD "If you're a software enthusiast who has never used OpenBSD before, you might enjoy installing it by yourself and figuring it out as you go. If, however, you're looking for a more practical approach to using OpenBSD 4.1 on a desktop or server machine, here's a quick guide to get you started in this spectacular operating system."
Permalink for comment 249468
To read all comments associated with this story, please click here.
Some small corrections
by Soulbender on Thu 21st Jun 2007 03:50 UTC
Member since:

"Default text editor: vi."

Not entirely true. Base also has mg, a small emacs-like editor.

"Type ls /dev/cd* to see other CD device nodes"

A better way to do this would be:
sysctl hw.disknames
disklabel cdX (X being whatever CD device you have)

"Packages are easier to upgrade when it comes time to switch to the next OpenBSD release; Ports are trickier to upgrade, and will take much longer to reinstall."

Not really since ports creates packages. It would only be a little but tricky if you had fiddled with the ports build options (something you usually should not do if you're a user).

"It's easier to find programs in Ports than it is the package database"

Install sqlports, a sqlite database of available ports/packages.

"export FETCH_PACKAGES=yes"

You should put "FETCH_PACKAGES=yes" in /etc/mk.conf and not export it in the shell. It's also useful to set "SUDO=sudo" in mk.conf so that you can build ports as an unprivileged user.
PKG_PATH can have multiple paths like so:

"Adding the Ports tree and OpenBSD source code"

Why add the source code?

"Enabling FreeBSD and Linux binary support"
Unless you really need this you should leave it off. Does anyone actually use the FreeBSD emulation?

"mv bsd"

Before you do this you should "mv /bsd /bsd.old".

Edited 2007-06-21 03:54

Reply Score: 4