On Fri, 10 Feb 2006 13:41:57 -0600, Dave Kleikamp wrote:

>> One thing however is worth to be mentioned:
>> the options for 'mount' must place umask=x first, before you can use uid=y 
>> and gid=z.
>
>I don't understand this part.  The testing I did (which was against a
>different kernel) was with "uid=500,gid=100,umask=xxx".  What kind of
>error was reported when you didn't have umask first?

Dave,

please excuse, I am unable to reproduce the failing now. When it happened
I even got a 'jfs-entry' when checking the log with 'dmesg | tail'.
and jfs did not accept the uid= option - probably some old information in cache?
Now also uid=1000,gid=100,umask=013 works fine - I have no explanation.
Most probably an error of the human beeing sitting in front of the computer.

All is fine - congratulations and many thanks,
Ingo





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion

Reply via email to