Requirements for Qubes Tools and seamless integration?
Drew White
I'm trying to find out what is required for building template in Qubes, but I still can't find any documentation on it that accurately tells me what I want to know.
I've asked this a long time ago when I was first thinking about building a template and want this information so that I will know if it's even going to be possible in the first place.
Is there anyone out there that can list for me what is required for Qubes integration on a Linux System? (Debian based and RedHat based)
I'm looking to find out the EXACT requirements, not what many think that I'm asking.
Some of the things, but not all of what I'm trying to find out the requirements of..
SystemD requirements, GUI requirements, Qubes Packages requirements, system package requirements, kernel requirements.
Pretty much all the packages that are REQUIRED as a minimum to get it all to work.
Sincerely,
Drew.
Drew White
> Is there anyone out there that can list for me what is required for Qubes integration on a Linux System? (Debian based and RedHat based)
Also the dependancies for NetVM and ProxyVM and AppVM differences.
That way I know what is required for each.
Thanks.
Andrew David Wong
Hash: SHA512
you've already read these documents, and since they're relevant to the topic,
I'll share the links here in case they happen to contain some information that
is relevant to you:
https://github.com/QubesOS/qubes-template-configs
https://www.qubes-os.org/doc/building-non-fedora-template/
https://www.qubes-os.org/doc/building-archlinux-template/
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXvhCwAAoJENtN07w5UDAwUfEQAKCG/ZqoicJO5Va/SB/+7NFz
7Bo09feV/lmD08C8L0ZMBPgXPVY6rQ+XqyzNeu9cKkLGBq/IfZqF91tZ2u3shGhP
QADo7ZmdUiFnuXX038ZrfccX53Tlevz7CaMRLGJ99rVEDNHSfYQwo5ld0EK7afio
o2Or6U8wXIhq1aYyB5vYSGuOjBA/FJy5MbOzlJze+g5SFuP3EC5nQugXPzzjyzyT
TO4EatWdFkJFPidpJtcwKf/roEGA8llDD0TBdX5yEpyNhvmwmzN4NVMkLAXec6e2
R7lJQlMqve83elhbr6QXyyebssgzkbZDM+Ys6Jhep0OCNpGQTL4GyaxyHaO+Jz7H
GdFpcFnMC8lyj3WbPSh/fGBRK5iUku5pCy43o2iq/N78EvJbAJ/9U+JscVQL58wI
p6YmyI7SB7S4u1vLeiFiQzLibHrcI+BXkAwZu6Wk6JWCQ3nPn7t9LkQxNXy7GbUz
weA+zw9biVJxYc8kI0EqQN+kIoN/u5ZiB5Q4yCEQAJi5TZKa/rA6bhTykKuxH5YT
QQDOQ/ZMpvorWjStIUsNdBqojYFiLshDco3WA/9/LQlbX03ABMEAuttp+tfZNhUn
znqjqYH1Sz6lURC3sxlcU3sPLb7be7cDxExX8YjZ5YFqzE0nN+DzG8bGe0Dpe5LI
Fiy4mnzIUs3Pp177lLzV
=65sE
-----END PGP SIGNATURE-----
Drew White
> These probably aren't what you're looking for, but since you didn't say that
> you've already read these documents, and since they're relevant to the topic,
> I'll share the links here in case they happen to contain some information that
> is relevant to you:
>
> https://github.com/QubesOS/qubes-template-configs
> https://www.qubes-os.org/doc/building-non-fedora-template/
> https://www.qubes-os.org/doc/building-archlinux-template/
Hi Andrew,
You are correct, they are relevant. Yes, I have already read them the last time I asked this question and someone linked me those.
I was hoping for a new resolution and an actual answer, not a link to something that does not have any information on what I'm asking.
What you linked me are instructions on how to, not what I am needing to know.
I don't want to download all that and more and do many things just to find out that in the last 1% of it all that it won't work because I have to install something first, or a different version.
The main reason I'm asking what the prerequisites are is to know EXACTLY what the MINIMAL requirement is to be able to get it running on Qubes.
I can't use a no-gui option on the VM that is a CLI and then access it via the console commands without it having the Qubes tools installed in it.
In my OP I did say
"I still can't find any documentation on it that accurately tells me what I want to know"
and
"Pretty much all the packages that are REQUIRED as a minimum to get it all to work."
This is what I'm after, not instructions.
I'm trying to build a template, and the instructions there are not detailed enough to tell me what I want and need to know, because I'm not an "end-user" I'm a developer and a technician by trade. I like things to be cleaner and more efficient than they currently are in some of the templates, including the "minimal" templates, which aren't exactly minimal, since they are missing things that are NEEDED and they have things that shouldn't be there as a "minimal". (In my opinion at least)
So by knowing WHAT is required, I will know what it is that I can turn into a Template with Qubes integration.
Foppe de Haan
From reading through the qubes-devel list a bit, I'm fairly sure that what you ask for simply does not exist in a central location, because the few devs there are have different priorities, and nobody else has stepped up to the plate yet. Having said that, you can probably get an impression of what is involved by reading the reports by the people who had a go at building the archlinux and debian templates there; which involved quite a bit of trial & error, as is obvious from the email chains. There are more exchanges to be found, but these two seem relevant:
https://groups.google.com/forum/#!searchin/qubes-devel/archlinux$20template|sort:relevance/qubes-devel/Jdqd_Cn1Gwg/FpgNBoVa6S0J
https://groups.google.com/forum/#!searchin/qubes-devel/archlinux$20template|sort:relevance/qubes-devel/CB30pD5J56U/TmpIrj8yhswJ
Your (only) other option is probably to have a look at the builder.conf etc. files for e.g. the archlinux template (or the debian template from qubes), and go from there.
Drew White
I've had a look at things, and those files and the instructions and all are so illogical it's not funny. Makes them very hard to follow. so I'd rather have it told to me by the people that decided to make instructions and files that are that illogical and hard to follow.
Not saying it's bad programming or anything, just saying that for me who is very logical, it's not that logical to follow.