MX Linux Forum

AK-47 wrote: ↑Sat May 08, 2021 7:08 pm @dolphin_oracle @anticapitalista @fehlix @richb how big are your disks?

0.5TB
1TB
4TB

for LiveUSB: both together : mostly using persist_root and rarely p_static_root, which is in frugal talk: frugal_root or f_static_root
for installed: always together

Please open a new thread for new issues and questions and perhaps make the subject title reflect the issues and post within the correct antiX subforum. (B/c this thread is both miss-placed and the thread titel would have nearly no meaning within MX for default file managers, which all come with an &...

Bin seit Oktober 2020 konstant mit mx unterwegs und so weit zufrieden. Ein Umstand nervt mich allerdings sehr, dass ich mich bei jeden Browser, der nicht Firefox heißt, noch mal extra anmelden muss. Nutze in erster Linie brave, hatte das Problem aber auch bei Opera und Vivaldi. Ist die Extra-Anmeld...

waldmattis wrote: ↑Sat May 08, 2021 6:37 am The MX-ahs installation does not appear in the boot menu.

Have you re-generated the grub configuration as mentioned.
If not do open a terminal within the booted encrypted installation
and run Or open MX Boot Option, to regnerated the grub menu.

Thank you! :happy: I should note that on my system, when I decrypted and mounted my drive with MX-KDE on it from within MX-19.4 AHS /boot appeared to be empty even in a root Thunar or terminal, so I actually had to boot from a live USB, select Boot Rescue Menus from its boot menu, select Find EFI B...

Yes, edit and adjust the custom.cfg to your liking.

I think SpaceFM is pretty good and a lot like Thunar. And probably a lot lighter than adding Thunar to antiX. Indeed SpaceFM is very good. It comes with a "Designmode", where e.g. adding a "Open Terminal here" or "Open Midnight Commander here" right click menu entry ta...

A revised instruction: Create menu entries for installed LUKS encrypted MX Linux installations On Luks-encrypted installations GRUB cannot be detected from another GRUB-installation on another partition. In this case we have two Luks-encrypted installation first installation on drive /dev/sda the 2n...

Perhaps, adjust the thread title to something like this, to reflect the issue is related to encrypted installs: Dual booting two Luks-encrypted UEFI MX installations on different drives. B/c for unencrypted installs os-prober, which is run by update-grub, would have no issue to find and generate cor...