How I learned to love Liteqube (and why you should, too, even if you have enough RAM)

General Discussion
61

Up to you.

62

I will just echo what other people have already said in this thread and say it’s a great idea, I love it, but it needs official backing from the Qubes team whos signing keys we all already trust, therefore the chain of trust can be extended without having to put the burden on users to audit and understand the code they are running in dom0 to install liteqube. Most people just don’t have time for that.

At that stage, it might as well get upstreamed into QubesOS proper, perhaps as a 2nd version to install as a “lite” version (perhaps similar to Lubuntu?)

@arkenoi maybe you could try get some funding for the project to turn it into something proper?

1 Like
63

Well, I documented almost everything. The accusation “it runs a lot in dom0” is a myth (at least for now when we do not even have widgets), there is a bunch of harmless notification services on dom0 end mostly, and that’s it. Will publish on github soon.

The install script is very simple, too.
Will try to get some EU grant, let’s see how it goes.

2 Likes
64

Well, pushed the update to GitHub - arkenoi/liteqube: Liteqube - put Qubes OS on a diet

will prepare the release tomorrow, meanwhile feel free to look, test and tell me what you think

3 Likes
65

What is actually the point of Liteqube? Like if I would just switch to minimal templates and remove stuff I don’t need from them? What difference it would make?

1 Like
66

Protected boot, readonly root, secrets not spread across qubes, easy installation so you do not need to experiment. Come on, it’s all in README. I keep answering the same questions again and again: “why not just minimal templates”, “we do not trust complex scripts in dom0”.

2 Likes
67

This is a good answer. You need to set up a tl;dr somewhere based on this

1 Like
68

I am willing to try this thing out when you will release 1.0 version. And I think more people will be willing to try this out when you will release it as an iso, not post installation script

I personally even know on what hardware (for my case) to this is on

1 Like
69

I did! It is in README. Will try to emphasize it somehow :slight_smile:

2 Likes
70

1.0 will mostly focus on moving installation process to some at least semi-declarative with correct rollbacks. Functionality change would be minimal (widgets maybe)

2 Likes
71

The Readme is a good read … and… it has “Mb” instead of “Gb” in a few places, referring to RAM.

2 Likes
72

Ha! Those are typos from Alex Barinov era and I did not notice them til now :)) will fix.

Most important, I documented whole RPC thing.

2 Likes
73

Bug report:
On a fresh install of R4.3.0, while trying to install liteqube-0.97, while running ./install.sh in 1.Base, I get:

./install.sh: line 108: [: missing ]'`

Line 108 reads:

if [ x"${VM_CORE_CREATED}" = x"true" && -e "/dev/mapper/${VM_GROUP}--${VM_LVM}--root" ] ; then

… so it’s unclear what happened. Checked the previous “test constructs” and they all seem to have properly matched brackets (‘[’ and ‘]’).

1 Like
74

Ah, mystery solved: you cannot have “&&” inside the […] test.
You have to either:

  • use “-a” (and) instead of “&&”, or
  • separate the two tests : [ test1 ] && [ test2 ] .
2 Likes
75

So… same thing happens on line 110. This fixes the install.sh script :

$ diff install_bad.sh install.sh
108c108
< if [ x"${VM_CORE_CREATED}" = x"true" && -e "/dev/mapper/${VM_GROUP}--${VM_LVM}--root" ] ; then
---
> if [ x"${VM_CORE_CREATED}" = x"true" ] && [ -e "/dev/mapper/${VM_GROUP}--${VM_LVM}--root" ] ; then
110c110
<     if [ x"${ROOT_DISK_MB}" != x"" && x"${ROOT_DISK_MB}" != x"0" ] ; then
---
>     if [ x"${ROOT_DISK_MB}" != x"" ] && [ x"${ROOT_DISK_MB}" != x"0" ] ; then

Later EDIT:
Ok, I gave up on 0.97.
“Step 2.Networking” install.sh also throws errors, first of which caused by the script referencing a file “liteqube-0.97/2.Network/default.first/dom0/etc/qubes-rpc/policy/liteqube.SignalTor” which does not exist. Actually, the whole “policy” directory doesn’t exist in that path.

2 Likes
76

Probably my install wasn’t clean enough. More motivation to do better rollbacks. Will make an update soon. Sorry for inconvenience, it was last minute commit before travel.

2 Likes
77

please try the repo clone. 1-3 should definitely work now. the rest i will clean up in the next couple of days.

i did not pay proper attention to all this because i am moving it to ansible in parallel, my bad.

2 Likes