<br><br><div class="gmail_quote">On Sun, May 17, 2009 at 12:17 PM, Michael Mol <span dir="ltr"><<a href="mailto:mikemol@gmail.com">mikemol@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Sun, May 17, 2009 at 12:00 PM, Bob Kline <<a href="mailto:bob.kline@gmail.com">bob.kline@gmail.com</a>> wrote:<br>
> On Sat, May 16, 2009 at 10:44 PM, Michael Mol <<a href="mailto:mikemol@gmail.com">mikemol@gmail.com</a>> wrote:<br>
>> On Sat, May 16, 2009 at 10:43 AM, Bob Kline <<a href="mailto:bob.kline@gmail.com">bob.kline@gmail.com</a>> wrote:<br>
</div><div class="im">>> > 755 root root<br>
>> ><br>
>> > I changed the owner to myself, and<br>
>> > nothing changes.<br>
>> ><br>
>> > But then, I can look at any other directory<br>
>> > in root with similar permissions. Just not the<br>
>> > external drive.<br>
>><br>
>> When you mount something, the mount permissions override that of the<br>
>> mount point. Try setting the user and permissions for the mount as<br>
>> part your parameters to the mount command.<br>
><br>
> Would that be any different than just setting<br>
> them afterwards?<br>
><br>
> Anyway, I tried the mount as:<br>
><br>
> mount -t ext3 -o owner,group /dev/sdb7 /disk2<br>
><br>
> I see the same behavior as before: I can view<br>
> items within /disk2, but not the contents of /disk2.<br>
><br>
> And of course the contents of any directory on<br>
> the primary drive.<br>
><br>
<br>
</div>In a perfect and intuitive world with perfect and intuitive software?<br>
No. At this point, I'm trying to exhaust all possible options,<br>
keeping in mind the different systems involved and where there might<br>
be failures in their interaction.<br>
<br>
Try setting the owner and group of the mount by uid and gid<br>
respectively, rather than by name.<br>
<br>
If that doesn't work, try adding the mount to fstab with the options<br>
"user,noauto,exec". Then, as the user you want to have access to the<br>
data, try "mount /disk2", and see if Firefox can see the directory<br>
contents.<br>
<br>
If *that* doesn't work, then it's probably not a permissions issue at<br>
all; Something in Firefox might be disallowing enumeration of mount<br>
point roots as a security feature. You'd have to dig through<br>
about:config to find it, if it's configurable.<br>
<br>
Another observation: Since this is an external disk, it might be<br>
worthwhile for you to use the persistent-naming schemes that seem to<br>
be part of udev now; Take a look under /dev/disk, and see if any of<br>
those symlinks device nodes will continue to refer to the disk you<br>
want to access under circumstances which change the device-devicenode<br>
mapping. (Such as, for example, if you were to add a SATA disk; the<br>
external USB or firewire disks would get moved to sdc or sdd, and the<br>
SATA disk would be sdb.)<br>
<font color="#888888"><br> </font></blockquote><div>Re "all possible options," I'll play around <br>with this some over time. I suppose Firefox<br>could be doing this on purpose, and it might<br>be stated so in some documentation. As far<br>
as I can see, the fact that konqueror works<br>and Firefox doesn't suggests as much. <br><br>I'll be back if anything changes.<br><br>BTW, anyone else see this same phenomena?<br><br> -- Bob<br><br><br><br></div>
</div><br>