From owner-freebsd-chat Fri Feb 14 10:56:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA23920 for chat-outgoing; Fri, 14 Feb 1997 10:56:20 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA23914 for ; Fri, 14 Feb 1997 10:56:16 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id TAA14090; Fri, 14 Feb 1997 19:54:08 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id TAA16857; Fri, 14 Feb 1997 19:42:39 +0100 (MET) Message-Id: <3.0.32.19970214194239.00a08de0@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 14 Feb 1997 19:42:40 +0100 To: Net Access Manager From: Eivind Eklund Subject: Re: Unix Shell Accounts Cc: Joerg Wunsch , freebsd-chat@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:50 AM 2/12/97 +0000, Net Access Manager wrote: > >> As Net Access Manager wrote: >> >> > Erm, well if you try compling FreeBSD current you will find that it >> > says version 3.0 on the boot up message. >> >> Sure, but that doesn't mean it's released yet. >> >> j@uriah 370% uname -sr >> FreeBSD 3.0-CURRENT >> ^^^^^^^ >> >> Also, i for sure wouldn't put up a -current machine for public >> access... > >Well, actually we use a snap of -current for all our unix boxes as it is >more stable than V2.4 release and supports nis better -- we have uptimes >of over 2 weeks. Please tell us where you got 2.4-RELEASE - this might save the FreeBSD developers a LOT of work for all three of 2.2-RELEASE, 2.3-RELEASE and 2.4-RELEASE. :) (Joerg should be especially interested, as he presently is putting down a lot of work managing the final touches for 2.2-RELEASE) Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org