Talk:Mdev/Automount USB
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using
~~~~
:
A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC) : A reply [[User:Sally|Sally]] 23:34, 12 November 2024 (UTC) :: Your reply ~~~~
busybox ash?
Why not just /bin/sh like uncle POSIX says? - Michał Górny 09:57, 12 July 2012 (UTC)
Answer: As mentioned in the "Constraints" section, the only guarantee on an mdev-based system is that it's running busybox, which mdev is part of. That in turn implies that the only guaranteed common shell is "busybox ash". On my system, /bin/sh is a symlink to /bin/bash. I could write scripts with bash-specific features, and it might work fine on my system. That script might not run on someone else's machine with /bin/sh being a symlink to another shell. If you want to customize the script for your machine, or use another shell or your own custom apps, feel free to do so. Remember that I'm trying to come up with scripts that are portable to as many mdev-based machines as possible, which means using "busybox ash" --Walter Dnes 02:55, 11 August 2012 (UTC)
username in sudoers
wouldn't it make sense to re-use the plugdev group here and replace USERID with %plugdev? also, I'm not sure if HOSTNAME makes sense here, if you want to mount/umount something from USB, you're usually on localhost - Christoph Mende 16:56, 30 July 2012 (UTC)
Answer: Like you said "usually". I don't want to restrict the flexibility of the system. Also, this would mean that all members of plugdev would get unmount permission on inserted USB devices. There may be situations where the admin might want one or more user to be able to read/write to an inserted device in /media, but not be able to unmount it. --Walter Dnes 02:55, 11 August 2012 (UTC)