From owner-freebsd-current Sat May 23 18:00:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01816 for freebsd-current-outgoing; Sat, 23 May 1998 18:00:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01786 for ; Sat, 23 May 1998 18:00:15 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA13941; Sat, 23 May 1998 18:00:36 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Tom Jackson cc: current@FreeBSD.ORG Subject: Re: panic: locking against myself (on very straight kernel) In-reply-to: Your message of "Sat, 23 May 1998 15:10:00 CDT." <19980523151000.43935@TOJ.org> Date: Sat, 23 May 1998 18:00:36 -0700 Message-ID: <13937.895971636@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Got this also with sysinstall. As far as I can see, /stand/sysinstall is > unuesable for setting slices and partitions. After I manually set a sd1s1e > partition, devfs/slice chokes on it. I've learned the hard way *NOT* to run > fsck on the partition when slice chokes on a partition ;-> Any attempt to use sysinstall with the new SLICE or DEVFS code is almost certainly doomed to fail since it has not been made aware of those additions, nor are their semantics 100% backwards compatible with the previous. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message