I will need to learn the basics before anything else, and it will also take me some while to do so. Am happy, therefore, to see how this offer will work, and look forward to it. Am grateful for everyone’s advice and to know that if I do encounter issues as I begin to explore qubes, there will be people willing to guide me along.
1 Like
terminal commands. in a Linux Terminal.
For Sudo you could type in at dollar sign $ man sudo
or $ man man
Or search the internet for the most 20 common linux commands. usually uses a few of the options.
Most of the things that I have used Terminal commands for, have been copy from a source and Paste into Terminal. Do keep in mind that paste into Terminal is usually not CTRL v , but uses the option in the drop down menu to accomplish the paste. More options that you might have to enter are like, this install would take up so much drive space. Enter Y for yes or N for no. So read the output.
The most common issue I have with this, is someone has written a how to for something, and I do not know which Qube to put the Terminal command into, or should it be in dom0, for things like setting up unmans key into dom0 to begin to download his qubes.
If I was taking a course in Chemistry. When I did a Chemistry lab. I had a lab book that step by step listed what I should do for the experiment.
Hmm. How to create a lab book for Qubes?
While listening to the suggestions of a Human Rights attorney. He told me that for some time he used Qubes, using one Template as one would use a normal Computer. Qubes not so much highly secure, less private, as some malware could be perpetuated. but only to familiarize a newcomer to - I guess ignoring a lot of the other options Qubes is displaying. I already do not like that option. but to go on.
My thought is, if one had enough RAM. There is already a more normalized version of Fedora 42. First column left side, drop down to gear, “Template Manager.” I would prefer it came with the ability to install FlatPaks without the user doing so. A more normal Desktop. Which would be a new Template to build. Even if I built the Template, I would not give it to anyone else. and it could be more secure if we used it through a Disposable.
Well, most newcomers are not going to buy a computer with enough RAM to justify the efforts of a good technical person to create the more full OS, and its disposable, to act as training wheels.
unman created a simplified version of Qubes, I thiink it was somewhere on github, which was just a few Qubes.
There is a more full version of a Fedora 42 Template.
far left top column,
drop down to gear.
Template Manager.
If the option to use 'Software" was activated, in a how to by Solene.
If someone also installed the ability to use Flatpaks.
Then create the disposable Qube for that, to be downloaded through the “Template Manager”
Pretty much what a beginner would need, and keep Security through use of Containers.
But we have enabled beginners to easily install software that is more like malware. Sigh.
And most newcomers are not going to buy a computer with enough RAM to get this work very well.
Might it even be better to buy a laptop with Qubes pre-installed and learn from there? Or is it important for the beginner to also learn how to download Qubes as part of the overall process?
Important to know how to download and verify software, without specific relation to Qubes.
I can think about few considerations to buy laptop with pre-installed Qubes: 1) Wish to make indirect donation to project
2) Extreme supply chain security risks to mitigrate.
3) Wish to get coreboot+heads device.
For first impression, better to install Qubes on any available laptop you can find out there.
2 Likes
It might be helpful to make yourself familiar with the key concepts behind the system to get a clear understanding of templates, disposables, and so on. This could make it easier for you to dive into the documentation and get a better feeling for what these technical items are used for and how you can use them profitably.
To help newcomers to get more easily into the documentation and then perhaps into the system, I have created a short paper about these key concepts. The paper is written especially for non-technical people, who may use it as a first step. It’s currently in review in order to be included as a chapter in the introductory part of the documentation.
If you are interested, here is a preliminary version:
Security Architecture.pdf.gz (1020.6 KB)
Additionally, if you are living outside the US, the current discussion of digital sovereignty may be of interest to you. Here’s also a second paper on how Qubes can help to move in this direction:
Blueprint for Digital Sovereignty.pdf.gz (697.3 KB)
From there, I would suggest moving just along the path that @unman has described above, and you will soon feel at home in Qubes. It’s easier than you might think - I managed it years ago without having any previous experience with Unix or Linux - so it’s quite possible! 
I’m having hard time myself learning it, but I can express that for many people including me it’s way better to learn things visually and with someone explaining them to me. But there are no Qubes courses, only the very basic ones, sadly