Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/695158d7-1b68-800b-a02f-4817bf1f6d25
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: You’re good 😄 And yes — you can always retry. === You’re good 😄 And yes — you can always retry. Nothing you’re doing here can brick the hardware. Let’s answer the two concrete questions cleanly, then I’ll give you a pre-install boot checklist so you can be confident. ==== ### ==== That would overwrite the system root and break the install. ===== Leave the mountpoint EMPTY. ===== That is intentional. Why: * dom0 should not auto-mount untrusted data * You will attach/mount this partition later inside a VM (sys-usb / sys-files / personal qube) * Qubes security model expects external/unencrypted storage to be VM-mounted, not dom0-mounted ===== | | | ===== | --- | --- | | | | | | | | | | | | | This is 100% correct. ==== You can’t fully simulate boot, but you can check all conditions required for boot. ==== ===== #### ===== * Filesystem: EFI System Partition * Mountpoint: /boot/efi * Size: 300–600 MiB * Not encrypted ✔ If yes → UEFI firmware can load bootloader ====== - Filesystem: ext4 ====== * Mountpoint: /boot * Size: ~1 GiB * Not encrypted ✔ If yes → kernel + initramfs can load ====== - ESP and /boot are outside LVM ====== * LVM partition starts after them ✔ If yes → no “EFI cannot be luks” error ====== - / is assigned only to qubes-dom0 root ====== * No other partition uses / ✔ If yes → root filesystem is unambiguous ====== Top-left must say: ====== : ❌ If you still see a red warning → do not continue ==== From the installer terminal (Ctrl+Alt+F2): ==== <syntaxhighlight lang="bash">lsblk -f </syntaxhighlight> You should see something like: <syntaxhighlight>nvme0n1p1 vfat EFI /boot/efi nvme0n1p2 ext4 boot /boot nvme0n1p3 crypto_LUKS └─lvm ext4 qubes_dom0 / nvme0n1p4 ext4 media </syntaxhighlight> If ESP + /boot are mounted and not encrypted → ✔ boots. ==== You’re absolutely right: ==== * UEFI installs are deterministic * Worst case = reinstall * No firmware damage possible * You already backed up everything (👏) This mindset is healthy. ==== 15 000–20 000 tabs: ==== * Browsers are not designed for this (even Vivaldi) * Qubes + workspaces + multiple qubes is actually a very good mental model * You’ll probably end up with: - research qube - school qube - job qube - archive qube - “parking” qube for tab hoarding We can optimize that later (RAM, swap, browser profiles, tmpfs). ==== - How to check it will boot? → ESP + /boot unencrypted, correct mountpoints, no installer errors ==== * Mountpoint for unencrypted media? → Leave it empty If you want, paste the final partition list exactly as shown (just text), and I’ll say either: ✅ “Install now” or ❌ “Fix this one thing first” You’re at the finish line.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)