So I tried/changed a few things and it’s almost working? I think
mount currently gives me this:
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/mtdblock6 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
/dev/mmcblk0p1 on /mnt/sd type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
(I changed SD to lowercase)
So the SD card is mounting in /mnt/sd
but /etc/config/samba is currently:
config samba
option workgroup ‘WORKGROUP’
option homes ‘1’
option name ‘GL-MT300A’
option description ‘GL-MT300A-5a3’
option interface ‘loopback lan wan’
config sambashare
option name ‘data’
option path ‘/data’
option read_only ‘no’
option guest_ok ‘yes’
I added
config sambashare
option name ‘sd’
option path ‘/mnt/sd’
option read_only ‘no’
option guest_ok ‘yes’
to /etc/config/samba. and
[sd]
path = /mnt/sd
read only = no
guest ok = yes
to /etc/samba/sm.conf and /var/etc/smb.conf. I don’t know if those are necessary, but even after a restart I can still access the sd card on other devices.
…Until I plug in an USB. Then all my entries disappear and I stop seeing the sd card on my other devices. I assume the steps above are supposed to be done automatically for it to work; when I remove the sd card, the ‘data’ samabashare disappears so I’m guessing it does it work, but only for ‘data’ instead.
So as a work around, I created a folder, /data, and just made a symbolic link between /data and /mnt/sd and called it a day. I works even after a reboot, and even after plugging in a USB.
I do want to find out what the correct procedure was supposed to be, but after hours of troubleshooting I think I’m okay with calling this ‘good enough’