From owner-freebsd-scsi Sun Jul 26 17:40:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07031 for freebsd-scsi-outgoing; Sun, 26 Jul 1998 17:40:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07002 for ; Sun, 26 Jul 1998 17:40:28 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id UAA09322; Sun, 26 Jul 1998 20:38:56 -0400 (EDT) To: freebsd-scsi@FreeBSD.ORG Subject: non-root pass, symlinks to pass fail X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 26 Jul 1998 20:38:56 -0400 Message-ID: Lines: 31 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If I attempt to use cam_scsi_open() on one of the /dev/pass devices as a non-root user, it failes with errno 13 (access). Interestingly enough, though, ls -l /dev/pass* produces: 0 brw-rw-rw- 1 root operator 200, 0 Jul 14 16:50 /dev/pass0 0 brw-rw-rw- 1 root operator 200, 1 Jul 14 16:50 /dev/pass1 0 brw-rw-rw- 1 root operator 200, 2 Jul 14 16:50 /dev/pass2 0 brw-rw-rw- 1 root operator 200, 3 Jul 14 16:50 /dev/pass3 0 brw-rw-rw- 1 root operator 200, 4 Jul 14 16:50 /dev/pass4 As I chmod'd things to 666 when I first got the error. Why can't I open a pass device as a non-root user? On what might be a related note, I created a symlink (i.e. ln -s) to a pass device. cam_scsi_open() refuses to open that either. Why? And, in both cases, how do I fix? Thanks, +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message