From owner-freebsd-hackers Sat Jul 19 03:40:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19383 for hackers-outgoing; Sat, 19 Jul 1997 03:40:54 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19348 for ; Sat, 19 Jul 1997 03:40:49 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id MAA04732; Sat, 19 Jul 1997 12:42:30 +0200 (CEST) From: Mikael Karpberg Message-Id: <199707191042.MAA04732@ocean.campus.luth.se> Subject: Re: Iomega Zip In-Reply-To: <199707190441.OAA12625@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jul 19, 97 02:11:36 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 19 Jul 1997 12:42:29 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Michael Smith: > Howard Lew stands accused of saying: > > > > The probe doesn't look right, but it works: > > The probe is _exactly_ right. > > > sd0 at scbus0 target 5 lun 0 > > sd0: Direct-Access > > sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > sd0 could not mode sense (4). Using ficticious geometry > > The drive has refused a MODE SENSE command, so it's not possible to > establish its geometry. Geometry is only (really) relevant for > processing the MBR. Instead, the driver will fake some sensible > falues. > > > sd0: NOT READY asc:3a,0 Medium not present > > sd0: could not get size > > 0MB (0 512 byte sectors) > > The driver has attempted to interrogate the drive to obtain its total > size in sectors. The drive reports an error because you haven't > inserted a disk. This is common for removables, particularly those > that support more than one media size. > > > sd0: with 0 cyls, 64 heads, and an average 32 sectors/track > > And this is the resultant fake geometry, given a size of 0 sectors. It's > good enough. Is this in non-verbose boot mode? It really seem to be completely unneeded information, which should be hidden behind the verbose flag. Don't you guys think so? It's bound to be interpreted as an error message. Furthermore, shouldn't the messages maybe explain themselfs a bit better and tell the poor, innocent user that it's not really an error, kinda like autoconf printouts during probing: "Couldn't find stricmp, but that's ok..." :-) *pokes maintainer to fix it* :-) /Mikael