Core live-usb always root and demo?

[Member PDP-8]

Getting tripped up on something with AntiX CORE 21 on my uefi-only box – maybe you can spot my error:

Problem: Even though I’ve used live-usb maker to make a secondary writable stick, and answer the text-based menu for things like timezone, static persistence, swapfile, from=usb etc, when I reboot, it acts like I am still in the original live-usb mode with root and demo user running with the default passwords. Note that I supplied my own new passwords originally when asked by setup after indicating my persistence choices which created the new root and home files. These choices were made on the secondary writable stick, not the original which was just a dd of the iso from the repo.

I more or less followed the same procedure when I made a stick using the BASE iso. No problems there with it recognizing my new passwords, so I’m stumped at what step I’m missing with core.

The ONE thing that is different however, that might be a cause, is that on my box, I have to manually edit the menu option (2nd one which prompts you with text menu choices) by changing the kernel parameter to “nosplash” and using F10 to boot out of grub.

Also note that after using AntiX-cli-cc to make the live usb to the secondary stick, after reboot I only have ONE choice now to boot, not the usual plethora of other options to choose from. Is that normal?

I only have to edit that grub stanza with nosplash with core. I don’t need to do this with base.

But maybe that’s not the reason/bug? Or am I just missing something particular to core that I’m overlooking?

• This topic was modified 1 year, 3 months ago by PDP-8.

[Moderator christophe]

Helpful

Up

0

::

In my experience, if you are using persistence, and then you change your password, it will be changed only when using persistence. I believe if you then boot up without persistence, it will not remember the password. Is that your situation?

confirmed antiX frugaler, since 2019

[Anonymous]

Helpful

Up

0

::

am I just missing something particular to core that I’m overlooking?

Toward determining what’s missing, I’ll invite you to read
topic Lists of packages preinstalled in AntiX 21 editions

Toward possibly achieving a partial solution for your current situation, I’ll mention package “bootrepair-antix” ~~ preinstalled in Base Edition but absent from Core Edition.

ps: if you generate a difflist, hopefully you’ll be kind enough upload it as an attachment to a post in that topic —^

Anonymous wrote:

I neglected to generate a list of packages preinstalled in BASE edition which are absent in CORE edition.

Someone else can please followup.
Use the cut command to grab the first column of instpkgs-a21x64-base_sysv.txt
and pipe the output to the sort command and save to a new file e.g. BaseSorted.txt

Then use the cut command to grab the first column of instpkgs-a21x64-core_sysv.txt
and pipe the output to the sort command and save to a new file e.g. CoreSorted.txt

Then generate the diff list using the following command:
comm -2 -3 BaseSorted.txt CoreSorted.txt > inBASEnotinCORE.txt

[Anonymous]

Helpful

Up

0

::

Problem: Even though I’ve used live-usb maker to make a secondary writable stick, and answer the text-based menu for things like timezone, static persistence, swapfile, from=usb etc, when I reboot, it acts like I am still in the original live-usb mode with root and demo user running with the default passwords.

As a troublshooting step, I would not trust “reboot”. Instead I would first full shutdown // poweroff (and ensure the pre-existing liveUSB has been detached prior to restarting).

My further suggestions here will be somewhat limited, as I’ve near-zero experience with booting (U)EFI.
In advance, I would not discount the possibility that you’ve managed to flesh out some dormant edge-case bug within live-usb-maker or within one of the live scripts residing inside the antiX initrd.gz

[Member PDP-8]

Helpful

Up

0

::

Thanks for the hints guys! I’ll see if I can find the pebcak and follow up.

It’s just weird – after allowing the system to make the persistence files, which then prompts for new passwords all goes well.

Yet when I reboot, I only have ONE option to choose from in the framebuffer menu structure. (Totally beautiful btw – gorgeous to look at and use) and is back to the default passwords.

Weirdly enough, if I use the AntiX-cli-cc utility, and try to recreate persisitence files that way, those files are already there!

I’ll dig in and try to find what’s probably very obvious once I find it…

[Author]

Posts