From owner-freebsd-current Wed Jan 31 01:54:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA06310 for current-outgoing; Wed, 31 Jan 1996 01:54:07 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA06161 for ; Wed, 31 Jan 1996 01:52:30 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA11608 for ; Wed, 31 Jan 1996 10:51:24 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA10111 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 10:51:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id KAA20195 for freebsd-current@FreeBSD.org; Wed, 31 Jan 1996 10:26:23 +0100 (MET) From: J Wunsch Message-Id: <199601310926.KAA20195@uriah.heep.sax.de> Subject: Re: invalid primary partition table: no magic To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 31 Jan 1996 10:26:22 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601310338.OAA11342@godzilla.zeta.org.au> from "Bruce Evans" at Jan 31, 96 02:38:58 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org Precedence: bulk As Bruce Evans wrote: > > >uriah # vnconfig -c /dev/rvn0 fooimage > >uriah # Jan 30 23:51:48 uriah /kernel: vn0: invalid primary partition table: no magic > For emulating physical disks that don't have partition tables or labels, > don't use the `-s labels' option to vnconfig. Well, what about those that are about to get a label the next second? New vn devices are often created by dd'ing the appropriate amount of data out of /dev/zero. And why is it printed in the cited case, with an cd9660 image? I haven't used -s labels. I think it should at least go away for vn devices. Anybody playing with vn is expected to know what (s)he's doing. It's annoying enough with non-bootable physical disks that are dangerously dedicated, but i could perhaps live with that. People in Usenet are often more confused by this message. That's why i would like to have it an option. Any disk without the magic should simply (and silently, unless told otherwise) be considered an unsliced disk. To refine my proposal: use a sysctl-changeable variable, defaulting to "off" unless bootverbose is in effect. This way, we could ask the < 5 % people that experience problems in this area to turn on bootverbose. (All Usenet questions i've seen about this weren't errors, but referred to the bogus message.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)