On Fri, 2017-07-07 at 08:14 -0400, Nico Kadel-Garcia wrote: > On Thu, Jul 6, 2017 at 2:57 PM, Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: > > > We want to make the default installation do the right thing, as far > > as > > possible, on any system, without any explicit configuration or > > admin steps. > > In this case it's possible: if a virtualization "channel" is > > configured, > > we should assume that the user wants the service. This means that > > the > > "guest additions" rpms should be a) installed by default, b) > > enabled > > when installed, c) work ootb when running in the right > > virtualization > > and silently do nothing otherwise. > > Essentially, I want to take the same image and boot it in > > virtualbox, > > kvm, on bare metal, and in a container, and have things just work. > > Good luck with that. Since the Virtualbox guest additions are *not* > RPM enabled from their installation CD images, RPM is likely to > interfere with working, more recent installations of VBox drivers > from > the "Guiest Additions" iso image, unless great caution is employed > and > unless someone can convince them to be completely consistent in > installation tools, or to gracefully allow older and newer verson on > the same host. yes, we need install VirtualBox-guest-additions , which means VirtualBox will be one Fedora Package and BTW I hope that Fedora use RPMFusion package or based on that, I have many work there. And there [1] we got vboxservice.service which have ConditionVirtualization=|oracle [1] https://pkgs.rpmfusion.org/cgit/free/VirtualBox.git/tree/vboxservice.service https://pkgs.rpmfusion.org/cgit/free/VirtualBox.git/tree/ > > > how do you come to the conclusion that a dsiablked service is > > > suddenly enabled just because of that additional > > > ConditionVirtualization in the systemd-unit? > > > > Like I wrote above, we want it installed and enabled by default. > > > > End users on windows can be expected to be even less experienced > > than > > average, so it's important to make things as automatic and seamless > > as possible. > > > > Zbyszek > > _______________________________________________ > > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Sérgio M. B. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
