From owner-freebsd-hackers Fri Sep 25 08:02:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13140 for freebsd-hackers-outgoing; Fri, 25 Sep 1998 08:02:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13131 for ; Fri, 25 Sep 1998 08:02:31 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id IAA05118; Fri, 25 Sep 1998 08:01:50 -0700 (PDT) (envelope-from dhw) Date: Fri, 25 Sep 1998 08:01:50 -0700 (PDT) From: David Wolfskill Message-Id: <199809251501.IAA05118@pau-amma.whistle.com> To: djw@cyberstation.net, hackers@FreeBSD.ORG Subject: Re: ccd & dump In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Fri, 25 Sep 1998 01:06:55 -0500 (CDT) >From: Dan Walters >Does anyone have any tips on how to dump a ccd device? I just get >something to the tune of "/dev/ccd0c: Permission denied." This is with >2.2 stable. As long as the effective {user,group} ID associated with the process has permission to read the raw dev (/dev/rccd0c), it should work just fine. For example, I'm using amanda, set up to run as user "operator" (which I've manually added to group "operator"), and here's a machine that amanda backs up that uses ccd: crab[3]% ls -l /dev/*ccd0c brw-r----- 1 root wheel 21, 2 Jan 15 1997 /dev/ccd0c crw-r----- 1 root operator 74, 2 Apr 29 1997 /dev/rccd0c david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message