On Sep 3,  5:09pm, Jason Thorpe wrote:
}  jspath@mail.bcpl.lib.md.us (I) wrote:
}  > It found the hard drive and cd fine; the jaz drive is there but
}  > not readable yet -- I'll dig some more on that.
} the jaz drive will/should work ... they don't support the MODE SENSE scsi 

$ df -k
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/wd0a       25624    13098    11244    54%    /
/dev/wd0e      242506   194458    35922    84%    /usr
/dev/sd1a     1013743      137   962918     0%    /j

I made up a disktab entry, newfs, mount and voila!  I think this is
wonderful!  This is probably a FAQ, but here's my disktab for the jaz
drive:

jaz1gb|Iomega Jaz 1GB: \
        :ty=winchester:dt=ESDI:se#512:nt#64:ns#32:nc#1021:rm#3600:\
        :pa#:oa#0:ba#4096:fa#512:ta=4.2BSD: 

} You may want to build a kernel with "options INSECURE" to allow the X 
} server to get at the framebuffer ... Or, you can load the XFree86 
} Aperture Driver as an LKM ...

Running the "generic-adp" kernel fixed that :-)

Now, how do I tell what options are compiled into a kernel (besides
`strings' of course)?
-- 
I don't speak (or work) for the Baltimore County Public Library.
They keep telling me, "Shhhhh!"