On 03/06/2017 07:44 AM, sm8ax1 wrote:
Using Btrfs instead of LVM is completely valid in many cases. The
question is whether the performance advantage of traditional LVM would
justify supporting it in addition to image files.
BTW, Qubes R4 will have a new storage architecture with plugin
capability, and IIRC it will default to using a Xen block driver +
thin-provisioned LVM plugin.
I wanted to setup MAC address spoofing on my wireless interface too, so
I modified /etc/NetworkManager/NetworkManager.conf in sys-net, but when
I restarted it my changes were gone. I read that I have to make changes
in the TemplateVM itself (fedora-23) for them to be persistent, but the
problem is that I don't necessarily need all VMs to have this change.
I'm still not sure of the correct way to make changes to a single VM
that inherits from a TemplateVM.
On MAC anonymization:
https://www.qubes-os.org/doc/anonymizing-your-mac-address/
That's more or less what I read on other sites. I think we should
consider putting a Big Fat Warning on that page saying that your changes
will be lost on restart if the VM belongs to a template, or you could
easily leak your real MAC address by accident.
This behavior is explained in Qubes introductory material...
template-based VMs forget anything that isn't in /rw (such as home/).
That's why its routine for Qubes docs to instruct adding settings to the
template. In this case, the doc also has the user restarting the netVM
before checking the MAC address.
Also, a given template does boot differently depending on the VM type
(netVM, proxyVM, appVM) that's using it. So Network Manager settings
don't really affect appVMs since they aren't intended to run NM.
This is an interesting point I wasn't aware of. Are there more details
on the specific differences between types of VMs? I guess I could have
just made the changes to the fedora-23 TemplateVM then.
IIRC it revolves around qvm-service. This doc has some details:
https://www.qubes-os.org/doc/dom0-tools/qvm-service/
On TemplateVM persistence:
https://www.qubes-os.org/doc/templates/#important-notes
On making directories persistent without making the changes in a
TemplateVM:
https://www.qubes-os.org/doc/bind-dirs/
Thanks. It sounds like bind-dirs.sh is just what I need!
There are several alternatives for configuration. The VPN doc describes
using /rw/config (without bind-dirs) to configure and script things for
a specific VM. You could also create a standalone netVM so that config
changes become very straightforward. It depends on the specific case.
Chris
Thanks. I went with bind-dirs.sh so far, but I'll look into the
/rw/config method as well. I thought about creating a standalone VM at
first, but having to update it separately is a disadvantage there. Like
you said, it depends on the case.
Here is a related example using rc.local. Instead of starting a process
directly, it adds a new systemd service and starts it...
https://github.com/tasket/Qubes-vpn-support
--
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/7fcb0a80-f715-426f-9fdd-94deafcad8b0%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.
