Date: Tue, 06 Feb 2001 15:43:33 +0900 From: non@ever.sanda.gr.jp To: current@FreeBSD.ORG Cc: ticso@cicely5.cicely.de, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT Message-ID: <20010206154333F.non@ever.sanda.gr.jp> In-Reply-To: <20010205170041.A86739@panzer.kdm.org> References: <200102040157370.13362-100000@blues.jpj.net> <20010206001527.B548@cicely5.cicely.de> <20010205170041.A86739@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Kenneth D. Merry" <ken@kdm.org> Date: Mon, 5 Feb 2001 17:00:41 -0700 > I think we already have the most important functionality from the od(4) > driver in the da and cd drivers. If there are any features that are > in the od(4) driver that should be in the da(4) or cd(4) drivers, but > aren't, please speak up. Though I have not tried `da' lately, if you don't insert a medium in the drive at the time of CAM rescan bus, `da' tries to get the geometry by XPT_CALC_GEOMETRY then panics with divided by zero in most SCSI drivers. With `od' it says just the medium is 0MB and does not cause panic. Probably `od' knows the medium is not in the drive (watching UNIT READY or something?). Is it safe to change the size (geometry) of media with `da', eg. at first no medium (0MB), then 128MB, 230MB, 640MB (sector size is 2048bytes) and so on ? // Noriaki Mitsunaga // 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?20010206154333F.non>