From owner-freebsd-stable  Sat Dec 19 19:10:33 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA24532
          for freebsd-stable-outgoing; Sat, 19 Dec 1998 19:10:33 -0800 (PST)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from ccsales.com (ccsales.com [216.0.22.30])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24527
          for <freebsd-stable@FreeBSD.ORG>; Sat, 19 Dec 1998 19:10:31 -0800 (PST)
          (envelope-from randyk@ccsales.com)
Received: from ntrkcasa (pool98.hiper.net [216.0.22.98])
	by ccsales.com (8.9.1/8.9.0) with SMTP id TAA15044;
	Sat, 19 Dec 1998 19:10:39 -0800 (PST)
Message-Id: <3.0.5.32.19981219190923.04b0b8c0@ccsales.com>
X-Sender: randyk@ccsales.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Sat, 19 Dec 1998 19:09:23 -0800
To: Lomag <support@lomag.net>, freebsd-stable@FreeBSD.ORG
From: "Randy A. Katz" <randyk@ccsales.com>
Subject: Re: FreeBSD 3.0-STABLE
In-Reply-To: <367C5978.B1242AD4@lomag.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Check your hardware settings. I've had 3.0 working for over 6 months
now...no problems through current. I've had it running on over 8 machines,
2 of which are production machines.


At 08:57 PM 12/19/98 -0500, Lomag wrote:
>Can someone please cue me in as when 3.0-stablr branch
>will be ready? I'm forced to use 3.0-current and its
>very unstable, stays up for about 10 days, after that
>things just go haywire. I have to use 3.0 to support
>my UW2 scsi card and Seagate Cheetah hard drives.
>If anyone can please tell me so I know when to expect
>it to upgrade asap.
>
>Regards,
>Mark Skurzynski
>support@lomag.net
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-stable" in the body of the message
>
>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message