Hi, I'm a qubes newbie, but I am learning a lot about security, firewalls, and networking in general through my exploration with the os. I have created an rsyncd server as a standalone, debian app-vm and appropriately configured the firewall in sys-net, sys-firewall and my-rsyncd. I am able to connect and use rsync to store files on the server from a machine other than the qubes machine. Yay. However, I did notice that I had to connect the storage (it's an internal sata drive) as a block device after I booted the server in order to have the data disk available for mounting. I looked around for help and didn't see anything that seemed to really fit with my problem (just want to tell qubes to attach the block device to the app-vm at startup). I searched google and found a really popular message with some pretty arcane instructions about allowing the app-vm to run scripts on qubes dom0 and that just sounds wrong on so many levels that I thought I would ask it here in the hopes of finding some simple instructions, advice, and or rationale.
Is is possible to make a second hard disk available to an app-vm's fstab so that it can be mounted when the vm starts up? If it's a security no-brainer why this is an ill conceived idea, I would appreciate hearing about that as well, but really, I just want my rsyncd app-vm to have access to that honking big drive when it starts up without my having to manually mount stuff every time I restart. Thanks for being patient with the newbs, Will -- 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/975f48bc-b219-4b30-bf02-5a6e813efc06%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
