From owner-freebsd-stable@FreeBSD.ORG Thu Oct 26 11:42:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAD1B16A403 for ; Thu, 26 Oct 2006 11:42:22 +0000 (UTC) (envelope-from joe@joeholden.co.uk) Received: from claire.ber.rewt.org.uk (claire.ber.rewt.org.uk [217.160.200.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 392AC43D5F for ; Thu, 26 Oct 2006 11:42:20 +0000 (GMT) (envelope-from joe@joeholden.co.uk) Received: from localhost (localhost [127.0.0.1]) by claire.ber.rewt.org.uk (Postfix) with ESMTP id 9A7B9140036B; Thu, 26 Oct 2006 12:42:18 +0100 (BST) X-Virus-Scanned: Scanned at claire.ber.rewt.org.uk Received: from claire.ber.rewt.org.uk ([127.0.0.1]) by localhost (claire.ber.rewt.org.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rwns-qkCbPoJ; Thu, 26 Oct 2006 12:42:09 +0100 (BST) Received: from [10.2.1.120] (cpvirtual.operatelecom.com [62.232.41.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: joe) by claire.ber.rewt.org.uk (Postfix) with ESMTP id A10A21400343; Thu, 26 Oct 2006 12:42:09 +0100 (BST) Message-ID: <45409F10.4020806@joeholden.co.uk> Date: Thu, 26 Oct 2006 12:42:08 +0100 From: Joe Holden Organization: joe@joeholden.co.uk User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: "SiteRollout.com" References: <002c01c6f8f2$7656c550$0200a8c0@pc1> In-Reply-To: <002c01c6f8f2$7656c550$0200a8c0@pc1> X-Enigmail-Version: 0.94.1.0 OpenPGP: id=13A6D1E7 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6CC696BFE639DC4E58C6C521" Cc: freebsd-stable@freebsd.org Subject: Re: Three FreeBSD 6 questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2006 11:42:23 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6CC696BFE639DC4E58C6C521 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable SiteRollout.com wrote: > I'm new to this list, so here's a hello, how are you to everyone on the= > list! Welcome! > I'm coming to FreeBSD from a Linux background, so whilst some things ar= e > pretty similar, some things are pretty different. Excellent! > 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= : > =20 > FreeBSD server4.domain.info 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Sat Sep= 23 > 13:52:48 UTC 2006 root@server4. > > domain.info:/usr/src/sys/i386/compile/SERVER4 i386 You would be running -RELEASE, which is a snapshot of -STABLE at a particular point in time (Someone correct me if i'm wrong). > And which file do I change to use a different release, and how must I u= pdate > the system to pull in this latest release? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html is a good starting point, I recommend you read the handbook entirely at least once! > 2.) I'm a bit confused as to updating the system. As I understand, ther= e are > 3 areas which require updates: > =20 > i. Ports > ii. Security updates > iii. Kernel updates > =20 > I know how to perform the first two, but for kernel updates I can't see= n 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 up2dat= e? The "kernel" updates are all part of the cvsup process, as its including in -src, you base system and kernel must always be in line, its not "modular" like Linux is. > 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 tho= ught > it was due to overheating. However cooling was all good, so after furth= er > investigation and googling I diagnosed the problem as being the backgro= und > fsck which for some reason was failing, causing the server to shutdown = and > upon reboot requiring a manual fsck. > =20 > 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 fi= x > 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? A= nd > why has the background fsck been failing? Where can i find further info= ? > =20 > Any help with these questions would be greatly appreciated. > =20 > Regards, > Suhail. Thanks, Joe --------------enig6CC696BFE639DC4E58C6C521 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFQJ8TdQJXshOm0ecRAk40AJ9vdokTJkcxh+9Uz1f3mEoku7qAtQCffnf3 z532J3CzICLXsonqKQ4Ct7A= =5nfK -----END PGP SIGNATURE----- --------------enig6CC696BFE639DC4E58C6C521--