From owner-freebsd-questions Sun Feb 6 23:26:18 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail1.noc0.hsacorp.net (mail1.noc0.hsacorp.net [208.247.171.140]) by builder.freebsd.org (Postfix) with ESMTP id 0A7013DAB for ; Sun, 6 Feb 2000 23:25:46 -0800 (PST) Received: from [24.216.177.226] (HELO kwan) by mail1.noc0.hsacorp.net (CommuniGate Pro SMTP 3.2b8) with ESMTP id 6822290; Mon, 07 Feb 2000 02:26:24 -0500 Message-Id: <4.3.0.33.0.20000207022300.00aa8950@pseudonet.org> X-Sender: jconner@mail.enterit.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.33 (Beta) Date: Mon, 07 Feb 2000 02:26:38 -0500 To: "Kenneth D. Merry" From: Jim Conner Subject: Re: CDrecord issues Cc: Stephen , freebsd-questions@FreeBSD.ORG In-Reply-To: <20000206224738.A18941@panzer.kdm.org> References: <4.2.0.58.20000202154804.00a40e40@mail.enterit.com> <20000202092022.A17219@visi.com> <4.2.0.58.20000202100505.00a30b70@mail.enterit.com> <4.2.0.58.20000202100505.00a30b70@mail.enterit.com> <4.2.0.58.20000202105928.00a30b88@mail.enterit.com> <4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 22:47 06-02-00 -0700, Kenneth D. Merry wrote: >.2.0.58.20000202154804.00a40e40@mail.enterit.com> ><20000204141307.B63538@panzer.kdm.org> ><4.3.0.33.0.20000206232730.00add100@pseudonet.org> >Mime-Version: 1.0 >Content-Type: text/plain; charset=us-ascii >X-Mailer: Mutt 1.0i >In-Reply-To: <4.3.0.33.0.20000206232730.00add100@pseudonet.org>; from >jconner@enterit.com on Sun, Feb 06, 2000 at 11:31:25PM -0500 >Sender: owner-freebsd-questions@FreeBSD.ORG >X-Loop: FreeBSD.ORG >Precedence: bulk >X-RCPT-TO: >X-UIDL: 242361134 >Status: U > >On Sun, Feb 06, 2000 at 23:31:25 -0500, Jim Conner wrote: > > At 14:13 04-02-00 -0700, Kenneth D. Merry wrote: > > >[ It is generally better to send SCSI questions to the freebsd-scsi list ] > > > > This didn't start out as SCSI issues so I didn't even think about it. I > > apologize for the posts if they are not related to the topic of the > mailing > > list. Should I send this over there now instead or may I continue here? > >That's just for future reference. It's fine to continue it here, so the >folks on the list can (hopefully!) see the answer. > > > >On Wed, Feb 02, 2000 at 15:59:00 -0500, Jim C wrote: > > > > (hist 503)# ls -al /dev/pas* > > > > crw------- 1 root operator 31, 0 Dec 23 11:43 /dev/pass0 > > > > crw------- 1 root operator 31, 1 Dec 23 11:43 /dev/pass1 > > > > crw------- 1 root operator 31, 2 Dec 23 11:43 /dev/pass2 > > > > crw------- 1 root operator 31, 3 Dec 23 11:43 /dev/pass3 > > > > > >Are you running as root or not? If you're not running as root, you won't > > >be able to access the pass devices. Also, what are the permissions on > > >/dev/xpt0? You need permissions on that device to be able to use cdrecord > > >-scanbus. > > > > I am running as root (always have). Here is the listing of /dev/xpt* > > > > (hist 501)# id > > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), > > 5(operator), 20(staff), 31(guest) > > > > (hist 502)# ls -al xp* > > crw------- 1 root operator 104, 0 Dec 23 11:43 xpt0 > > crw------- 1 root operator 104, 1 Dec 23 11:43 xpt1 > >Are you running with a securelevel greater than 1? You can't access the >passthrough device with a securelevel greater than 1, since it allows >nasty things to happen. (e.g. you can format disks, write to random >sectors, etc.) > >I should have noticed that camcontrol and cdrecord were returning >"operation not permitted" instead of "permission denied". (The pass(4) >driver returns EPERM when the securelevel is > 1.) Yeah!! In fact I am running with a securelevel of 3. I will test this tomorrow when I am at console. I will let you know what happens. As a side note, the messages I was getting (above) were occurring while I was running the kernel in securelevel 1. Tomorrow, I will attempt running it in level -1 (for grins and giggles). >[ ... ] > > > > > (some optional info) > > > > > > > > (hist 505)# camcontrol devlist -v > > > > scbus-1 on xpt0 bus 0: > > > > < > at scbus-1 target -1 lun -1 (xpt0) > > > > scbus0 on ncr0 bus 0: > > > > at scbus0 target 0 lun 0 (pass0,da0) > > > > < > at scbus0 target -1 lun -1 () > > > > scbus1 on ahc0 bus 0: > > > > at scbus1 target 2 lun 0 (pass1,da1) > > > > at scbus1 target 6 lun 0 (pass2,cd0) > > > > < > at scbus1 target -1 lun -1 () > > > > > > > > Hmm...now I was tinkering with camcrontrol and I got this: > > > > > > > > (hist 507)# camcontrol periphlist -v > > > > camcontrol: cam_real_open_device: couldn't open passthrough device > > > /dev/pass0 > > > > cam_real_open_device: Operation not permitted > > > > > > > > Why on earth would I get this? I recompiled the kernel with the > following > > > > options before I started to perform any camcontrol commands: > > > > > >It looks like you might not be running as root, but your pass devices are > > >accessible only for root. Maybe your transport layer device (/dev/xpt0), > > >which is needed > > > > > >Ken > > >-- > > >Kenneth Merry > > >ken@kdm.org > > > > Let me know if I should send this over to SCSI. I am not even a member of > > that list yet. Should I be to send this (is it moderated?) > >It's not moderated, but if you have any interest in SCSI stuff at all, I'd >suggest subscribing to it. > >Ken Well, I wouldn't say that I have a huge interest in SCSI right now...an occasional question now and then but thats about it :) But since its unmoderated, I may send this to that list too...I wanna see how far we can get... Thanks Jim >-- >Kenneth Merry >ken@kdm.org > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Today's errors, in contrast: Windows - "Invalid page fault in module kernel32.dll at 0032:A16F2935" UNIX - "segmentation fault - core dumped" Humanous Beingsus - "OOPS, I've fallen and I can't get up" ------------------------------- Jim Conner NOTJames jconner@enterit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message