Three FreeBSD 6 questions
pj at smo.de
Thu Oct 26 12:14:23 UTC 2006
> Two questions to kickstart my participation on this list:
> 1.) How exactly do I know whether I am running the STABLE or CURRENT
> release, as when I run uname I can only see the following relevant info:
> FreeBSD server4.domain.info 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Sat Sep 23
> 13:52:48 UTC 2006 root at server4.
> <mailto:root at server4.e-webhost.info:/usr/src/sys/i386/compile/SERVER4>
> domain.info:/usr/src/sys/i386/compile/SERVER4 i386
You are running 6.0-RELEASE. The current release is 6.1 - 6.2 is coming
CURRENT is bleeding-edge development - you perhaps won't run it on a
production server as it may crash at some point in time due to new
> And which file do I change to use a different release, and how must I update
> the system to pull in this latest release?
You use cvsup(1) to update your local source-tree (and the
ports-collection). In cvsup's configuration file(s), you specify what
`version' of FreeBSD (RELEASE, STABLE, CURRENT) you want. ;)
> 2.) I'm a bit confused as to updating the system. As I understand, there are
> 3 areas which require updates:
> i. Ports
> ii. Security updates
> iii. Kernel updates
> I know how to perform the first two, but for kernel updates I can't seen to
> find a consistent unified method with talk of the "traditional" way and the
> "latest" way. What is the best way to keep my FreeBSD 6.x system up2date?
> 3.) One of my new FreeBSD 6.0 servers went down recently. This was odd as
> the actual server was hardly busy, but filesystem errors came up when
> booting up the server. After running fsck, server would be up for about an
> hour and then go down again. This kept happening and so I initially thought
> it was due to overheating. However cooling was all good, so after further
> investigation and googling I diagnosed the problem as being the background
> fsck which for some reason was failing, causing the server to shutdown and
> upon reboot requiring a manual fsck.
> I've fixed this by disabling the background fsck and forcing the bootup fsck
> in /etc/rc.conf. At least then if the server goes down again it will fix
> itself with a full fsck when booting up. My question is whether this is
> okay, and has anyone experienced this same problem with their system? And
> why has the background fsck been failing? Where can i find further info?
Have you tried fscking your disks in single-user mode?
And as Joe already said: Read The Handbook - it answers a lot of
questions (if not all). :) You should have a local copy of it in
More information about the freebsd-stable