Probably having "owner" _and_ "user" as options is a bad idea.
On Sun, 3 Mar 2002, Janus Christensen wrote: > On Sun, 2002-03-03 at 12:05, Brad Hards wrote: > > Thanks for taking the time to respond, Brad. > > > > > Whilst the device works when mounted as root and I can read from it with > > > a normal user, I can only write to it if I su to root, which is rather > > > annoying. > > But is at least secure. > > True, but at home, on my workstation, and behind the firewall I am > willing to sacrifice a security for convenience; at least in this case. > > ,-) > > > You should read relevant docs before posting. In this case, man mount tells > > you the answer. Here is a verbatim extract from the man page on a RH7.2 > > install: > > Oops. I left out a bit of information here; sorry about that, my mistake > - I will do penance by using Microsoft Windows for a whole day > tomorrow. ,-) > > I did try to modify the fstab entry thus: > > /dev/sda1 /mnt/diskonkey auto user,noauto,owner 0 0 > > but I stille get the same message when I try to mount it as non-root. > > Writing (and thus thinking) about the problem got me to experiment a bit > and I ended up with a fstab entry that actually works: > > /dev/sda /mnt/diskonkey auto user,noauto,owner 0 0 > > With this entry I can mount the DiskOnKey device as any user with > > mount /mnt/diskonkey > > which is what I am after. So I guess I am a happy camper, having figured > out a fstab entry that works the way I want to. .-) > > Initially my worry was that the entry would get overwritten when I > re-plug the device or reboot the machine, but this does not seem to be > the case. > > > > > Is it because the DiskOnKey device is a SCSI device? > > Nope. > > I didn't think so either. > > > I am also experiencing problems of a different nature: whenever I have > been using the USB device, the system hangs for a while when I reboot or > shutdown the system right after the "Turning off quotas" message. If the > DiskOnKey device was unplugged prior to the reboot/shutdown, a SCSI > error message is written on the screen after some time, after which the > system reboots or shuts down. If the device is left in the USB port, > error messages from usb-uhci.c are written on the screen (the system > seems to hang for less time if I unplug the device when it hangs; then > the error messages appear a short time-span after unplugging the > device). Unfortunately none of these messages are written to the log and > the messages are not displayed for long enough for me to write them > down. > > This problem is not of critical nature, since no data is lost or > corrupted (either on the DiskOnKey device or on the Linux box) and the > system seems to recover, but it is none the less an annoyance. > > I realise that for members of this list to be any help with this issue I > need to supply the error messages. How can I make the USB code write the > messages to a file instead of just to STDERR (I suppose)? > > Regards, > -- *Please check you have my SLAC address in your addressbook for me* /------------------------------------+-------------------------\ |Stephen J. Gowdy | SLAC, MailStop 34, | |http://www.slac.stanford.edu/~gowdy/ | 2575 Sand Hill Road, | | | Menlo Park CA 94025, USA | |EMail: [EMAIL PROTECTED] | Tel: +1 650 926 3144 | \------------------------------------+-------------------------/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
