From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1a40eb020fc3455dd328b4bd4a8bcf40@quanstro.net> From: erik quanstrom Date: Sun, 8 Feb 2009 10:04:07 -0500 To: 9fans@9fans.net In-Reply-To: <4e6ca2050902072214h54e4cb15k2f356324f3375c5f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] External HDD over USB Topicbox-Message-UUID: 99c5981c-ead4-11e9-9d60-3106f5b1d025 > 2009/2/6 erik quanstrom : > > are you running usb/disk as the host owner (eve)? > > > > oh, *eve* -- yes, I've tried as eve also, with the same > results. hostowner, after /dev/hostowner, and eve, after the kernel variable name, refer to the same thing. eve is "" until set by factotum -S (cpuserver) or factotum -u (terminal). factotum writes the hostowner to /dev/hostower and as a special case the setting process' owner is reset as well. with the default install, a cpu server's hostowner is bootes. > any debugging I ought to try? auth/debug is always a good start. no arguments, no man page. just run it. once that fails, i'd use acid(1) truss to pinpoint the system call that results in permission denied. if it is /dev/usb*, i would use scuzz(8) to double-check that it isn't a bug or misleading message in devusb. giving scuzz the "probe" command should list all the available sd devices. if it does not, then it's likely a real permissions problem. it's pretty likely that i haven't foreseen what's really going wrong on your system. so you're probablly going to need to do a bit of experimentation. good luck. - erik