Skip to content

Commit

Permalink
force truser to use uid:gid of 1000:1000 so that we always have a fixed
Browse files Browse the repository at this point in the history
uid:gid mapping (required for usbmount.conf).
  • Loading branch information
jens-maus committed Nov 19, 2019
1 parent 6e1d287 commit 2954d94
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion buildroot-external/board/intel_nuc/users_table.txt
Original file line number Diff line number Diff line change
@@ -1 +1 @@
truser -1 truser -1 * /home/truser /bin/sh video,audio,input,tty thinRoot main user
truser 1000 truser 1000 * /home/truser /bin/sh video,audio,input,tty thinRoot main user
4 changes: 2 additions & 2 deletions buildroot-external/rootfs-overlay/etc/usbmount/usbmount.conf
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ FILESYSTEMS="vfat ntfs fuseblk ext2 ext3 ext4 hfsplus exfat f2fs"
#############################################################################
# Mount options: Options passed to the mount command with the -o flag.
# See the warning above regarding removing "sync" from the options.
MOUNTOPTIONS="noexec,nodev,noatime,nodiratime"
MOUNTOPTIONS="noexec,nodev,noatime,nodiratime,sync"

# Filesystem type specific mount options: This variable contains a space
# separated list of strings, each which the form "-fstype=TYPE,OPTIONS".
Expand All @@ -46,7 +46,7 @@ MOUNTOPTIONS="noexec,nodev,noatime,nodiratime"
# For example, "-fstype=vfat,gid=floppy,dmask=0007,fmask=0117" would add
# the options "gid=floppy,dmask=0007,fmask=0117" when a vfat filesystem
# is mounted.
FS_MOUNTOPTIONS="-fstype=vfat,utf8,uid=1001,gid=1004,umask=022 -fstype=ntfs-3g,nls=utf8,uid=1001,gid=1004,umask=022 -fstype=fuseblk,nls=utf8,uid=1001,gid=1004,umask=022"
FS_MOUNTOPTIONS="-fstype=vfat,utf8,uid=1000,gid=1000,umask=022 -fstype=ntfs-3g,nls=utf8,uid=1000,gid=1000,umask=022 -fstype=fuseblk,nls=utf8,uid=1000,gid=1000,umask=022"

# If set to "yes", more information will be logged via the syslog
# facility.
Expand Down

0 comments on commit 2954d94

Please sign in to comment.