From owner-freebsd-stable Sun Mar 22 10:21:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03413 for freebsd-stable-outgoing; Sun, 22 Mar 1998 10:21:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dog.farm.org (gw-hssi-2.farm.org [209.66.103.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03400 for ; Sun, 22 Mar 1998 10:20:58 -0800 (PST) (envelope-from dog.farm.org!dk) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id KAA19841; Sun, 22 Mar 1998 10:24:12 -0800 (PST) Date: Sun, 22 Mar 1998 10:24:12 -0800 (PST) From: Dmitry Kohmanyuk Message-Id: <199803221824.KAA19841@dog.farm.org> To: mike@smith.net.au (Mike Smith) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Help! Upgrade 2.2.5-RELEASE to 2.2-STABLE. Newsgroups: cs-monolit.gated.lists.freebsd.stable Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In article <199803140337.TAA03072@dingo.cdrom.com> you wrote: > > I think I'll have to join Paul in questioning whether this breakage is > > going to make 2.2.6 a support nightmare. I don't want this to become > > another ``unknown login class root''-style hailstorm. :-( > If you update /sbin/mount at the same time, it's a no-op. I got bitten > by the two different "dedicated" disk types issue though; that hurt. > The fix is still being tested in -current, but I haven't heard any > complaints about it, so I was planning to bring it over tonight. So, does this change work with BSD-partitioned disks (not Micro$oft- partitioned?) I have 4 production 2.2-x boxes all set in this mode (so no need to bother with BIOS geometry...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message