From owner-freebsd-current Wed Oct 21 12:31:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28675 for freebsd-current-outgoing; Wed, 21 Oct 1998 12:31:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28669 for ; Wed, 21 Oct 1998 12:30:58 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id OAA22342; Wed, 21 Oct 1998 14:30:33 -0500 (CDT) Received: from klinzhai-1.isdn.mke.execpc.com(169.207.65.129) by peak.mountin.net via smap (V1.3) id sma022338; Wed Oct 21 14:30:06 1998 Message-Id: <3.0.3.32.19981021142537.00fe1ff4@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 21 Oct 1998 14:25:37 -0500 To: "Kenneth D. Merry" From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199810211646.KAA10038@panzer.plutotech.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:46 AM 10/21/98 -0600, Kenneth D. Merry wrote: >Actually, it isn't required. It's highly recommended, but optional. Some >folks might want to disable it for security reasons. There or not everything works. Don't understand the security part. However the man page does make reference, but: ls /dev/pa* crw------- 1 root operator 31, 0 Oct 17 22:58 /dev/pass0 crw------- 1 root operator 31, 1 Oct 17 22:58 /dev/pass1 crw------- 1 root operator 31, 2 Oct 17 22:58 /dev/pass2 crw------- 1 root operator 31, 3 Oct 17 22:58 /dev/pass3 How can userland? >I put warning messages in the transport layer so that when people go >looking for a passthrough device, but don't have it in their kernel, they >get hit on the head. I got tired of people asking me why camcontrol, >cdrecord, or whatever didn't work. (don't worry, if you've asked me about >that, you're in very good company...) Have yet to try a CDR on FBSD, but plan to (Philips 2600). FBSD doesn't seem to read Joilet from a M$ burn. A legend works for now, but I'd like to burn "base" systems to CD for checking against. >If you're looking for documentation on the passthrough driver, RTFM. ("man >pass") Don't believe I have a need to tinker with CAM, being transparent for the most part, AFAIC. Was thinking more along the lines of whitepaper. RTFM'ing man pages isn't fun, since references scatter one to the 4 winds. Guess I don't know the practical benefits or if/should there be any additional tweaks (mind you I only glaced through the pages and followed a few references). There is plenty of options if you need to debug. 8-) Somewhat related to what I started here is DPT card support. I've seen plenty of references to the 3334 cards, but from the "CD" HARDWARE.TXT:dpt n/a n/a n/a n/a DPT RAID SCSI controllers. RELNOTES.TXT:DPT SCSI/RAID controllers (most variants). Wondering about 2044/2144 support? Plan to use the 3334 for a few servers in the near future, but for home use a 2044 ($200) is sufficient. "Most variants" means "no test drive method for me, thank you." Rather know before buying or else it would be good for NT (bleh!). This should be more clear, after all there are not that many models. Checked in the sources and there is no reference for any model number, not suprising. cheers! Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message