Date: Sun, 24 May 1998 14:15:13 -0500 From: Tom Jackson <toj@gorillanet.gorilla.net> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: current@FreeBSD.ORG Subject: Re: panic: locking against myself (on very straight kernel) Message-ID: <19980524141513.32054@TOJ.org> In-Reply-To: <13937.895971636@time.cdrom.com>; from Jordan K. Hubbard on Sat, May 23, 1998 at 06:00:36PM -0700 References: <19980523151000.43935@TOJ.org> <13937.895971636@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 23, 1998 at 06:00:36PM -0700, Jordan K. Hubbard wrote: > > 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 I apologize for not being clear. These attempts to use sysinstall were under non-devfs/slice kernels. Sysinstall woulg get to the newfs stage and panic/hang at newfs sd1s1a. This was under smp kernel. Then tried it under a up kernel and got the same thing. This is a updated sysinstall btw. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980524141513.32054>