What’s the error and command you are trying? (Full command, not just the “template” unman provided)
Don’t know why I am having such a hard time…
Here is what I am doing…
qvm-run -p ‘cat /home/username/Downloads/Templates/Arch linux/’ > <template_Arch_4.0>
I hit enter then get this
bash: syntax error near unexpected token ‘<’
You’re missing the VM it should copy from, <disposablevm> in unmans “template”.
I downloaded the templates from his link. I have them in oblivious the downloads folder. They are pretty big in size
My bad, in unmans “template” command the VM you copy from is called <disposablevm>
Oh and also you should not have <> around the last thing
I also believe this can only copy one file at a time
Here is the Qubes doc: Copying from (and to) dom0 | Qubes OS
Sorta like this:
qvm-run -p nameOfVMWhereYouHaveTheTemplateDownloadedToGoesHere ‘cat /home/username/Downloads/Templates/Arch linux/’ > template_Arch_4.0
Great, went good
Next input line…should I use
sudo dnf install template_Arch_4.0
Or
sudo dnf install qubes-template <template_Arch_4.0>
<> is used to denote something that should be changed so the first one.
Except if you used qvm-run -p nameOfVMWhereYouHaveTheTemplateDownloadedToGoesHere ‘cat /home/username/Downloads/Templates/Arch linux/’ > <template_Arch_4.0> in which case the file will be (I think) <template_Arch_4.0> so you should use the latter. So the answer is whatever the file name is.
No good
sudo dnf install template_Arch_4.0
sudo dnf install qubes-template_Arxh_4.0
It appears that it wants to download but why I have them downloaded already
Maybe if you renamed it (can be done using mv) to include .rpm? Or maybe try ./<filename>
I downloaded them at work cause I have limited internet connection at home…
So I do this
sudo install qubes-template_Arch_4.0
I get this
install: missing destination file operand after 'qubes-template_Arch_4.0
There should be a space between qubes-template and the filename.
I think this:
sudo dnf install qubes-template template_Arch_4.0
Nope just more problems. I’ll just delete them. I cannot download from home ISP only gives us 10gb a month.
Thank you for your time
So I figured out my problem I think.
I need to add my other internal SSD’s where I have these templates saved…
I run this command in “dom0”
qvm-rum -p fedora-30-dvm 'cat ’ > template_Arch_4.0
Fedora-30-dvm starts and I get 2 errors…
- cat: run/media/username/New: No such file or directory
-cat: Volume/Templates/Arch/: No such file or directory.
So much believe that is my problem… and why I can’t even install my custome build debian software that’s stored on these SSD’s…
Qubes doesn’t see the sD’s even though I can mount them and see all my files.
But wait a minute my wallpaper is saved on one of the internal SSD’s and it is on the desktop.
I can mount/unmount these SDD’s.access and see all file, copy,paste between both of them. Actually copy and paste from them to desktop, screenshot desktop and save to them.
But yet can’t install,run to or from them…WTF!!! Am I missing something???
There are 2 stages here.
If you have downloaded a package on a machine called dload and they are
at /home/user/Downloads/qubes-template-parrot.rpm
In dom0:
qvm-run -p dload 'cat /home/user/Downloads/qubes-template-parrot.rpm' > qubes-template-parrot.rpm
When that transfer has completed, make sure you are in the directory
where you transferred the file, and run:
sudo dnf install qubes-template-parrot.rpm
Change dload to the name of the qube you used.
Change the path /home/user/Downloads/qubes-template-parrot.rpm to the
actual path to the file you downloaded.
You cant download on a disposableVM and then shutdown the disposableVM
because the download will disappear. Either keep the disposableVM
running or use an AppVM for the purpose.
1 Like
Thank you so much (unman) for breaking it down. All is well now and installed!!!
I will say though I found myself doing some STUPID windows CMD stuff unconsciously and had to take a step back and think.
Yes there is a “learning curve” moving from Windows to Qubes but in time I’ll get it as this OS will now be the “Main driver” from r lots of reasons… Of course I’ll still have to suffer with windows for the time being and I am not really a big fan of them now with all the supposedly safety features they are adding with this new “chip” they want to do and all the “back doors” they have…
Again thank you very much (unman)
@unman I installed your focal template in R4.1. When I run any program (say Firefox from the Q menu, for example) the content of the window is entirely black. Closing the window causes a dialog to open (as expected when exiting Firefox). The dialogue is entirely black as well, but responds to clicks (I can close Firefox gracefully by guessing where the OK button would be).
I’m guessing the templates for R4.0 may not be the same as for R4.1, am I correct?
In what ways do their differ? Could the black screens be a symptom of that?
Obviously you shouldn’t use Templates built for 4.0 in 4.1, (or vice
versa). The installed Qubes packages are different.
Debian has a nice warning about this sort of thing:
When using mixed source of archives, you must ensure compatibility of
packages by yourself since Debian does not guarantee it. If package
incompatibility exists, you may break system. You must be able to judge
these technical requirements.
Build the Qubes packages for 4.1, and then build a 4.1 template.
1 Like
Question unman,
Would you recommend updating the templates that you built? If updating them would it cause some issues within Qubes?
I have made a “full backup” so if all hell comes descending upon me I can always go back,LOL!!!
Thank you for all that you and the others have done…
Absolutely no reason not to update, and you should. I try to keep the
packages for Ubuntu updated, so you could grab those from
https://qubes.3isec.org
The Parrot template is based on Debian testing, but some Qubes packages
are held to try to avoid the usual “I updated my bullseye template and
things stopped working”.
I’d always keep a backup on hand just in case. Users seem to
forget that Debian testing is just that - testing - and it’s
possible/likely that things will break.
Sweet thanks.