On Saturday, December 9, 2017 at 8:47:19 AM UTC-7, Unman wrote: > Yes, you can run the mount from rc.local. > Obviously you'll need to ensure that the device is attached first, so > if you're using the qrexec service I suggested, make sure that's called > first and completes before you attempt the mount.
Unfortunately, running the mount from rc.local doesn't seem to work (nothing gets mounted and I don't know why). I'm using a persistent attach for an AppVM. After adding "sudo mount /dev/xvdi /mnt/removable" to /rw/config/rc.local, I shut down the AppVM, and then start Terminal. After the AppVM starts up, I see that the mount didn't happen. Any tips on diagnosing this? I didn't see the word "mount" in journalctl. Not sure where else to look or what to look for. > Just for completeness, I'll point out that you can use bind-dirs to make > any file persistent within a qube - have a look at > www.qubes-os.org/doc/bind-dirs/ > I'm not sure how this would work with /etc/fstab - I cant check the > service order at the moment - but it's something you might not be aware > of. At worst you'd need an extra 'mount -a' call after bind-dirs. This is an interesting idea. I didn't know you could persist custom things. I guess the worry here is if /etc/fstab is an autogenerated file. Personally, I'd like to keep things simple and get the rc.local mount working, but I'll keep bind-dirs in mind for other things. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/529422b7-3dd7-4f6e-9d9e-df4f2721c4ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
