Re: MX-23 Rpi Respin -- Beta testing

Message

Thu Dec 28, 2023 12:04 pm

@fehlix on the resize of the OS thing, the imgtool we are using creates a file "/etc/resize-root-fs" that may be of use for use with the UUID. not sure if it applies or not. it creates an init.d script, and is called from rc.local on a first boot. this is setup script is also the source of the first reboot. the init.d script is created during the first pass, on reboot at init 3 the file system is resized, and then the init.d script is disabled.

all this happens before oobe starts at init 5.

which implies this could be done without the reboot if the init.d script existed on the first boot. and maybe an opportunity to mess with the UUID.

the rpi's fstab uses the PARTUUID so they don't particularly care about the filesystem UUID.

the disk is still mounted at that point, so probably not a good spot.

#222 Post by **Jerry3904** » Thu Dec 28, 2023 1:19 pm

I thought I would share this comment on the intro video we have up; for me it captures much of the pleasure I get from working with the whole MX Team:

Thank you for all the work of making an Xfce build for the Pi in MX-23 and for this video tour. I especially appreciate the informal conversational approach; it's like having a friend over who brought MX-23 on a micro-SD card to share. (I especially like not editing out any small glitches like, "I'm not going to start... [tool starts] Oh. I guess I am." Really adds to the "just chillin' out and MX-ing with friends" atmosphere.) Thanks again!

#223 Post by **fehlix** » Thu Dec 28, 2023 1:51 pm

dolphin_oracle wrote: ↑Thu Dec 28, 2023 12:04 pm @fehlix on the resize of the OS thing, the imgtool we are using creates a file "/etc/resize-root-fs" that may be of use for use with the UUID. not sure if it applies or not. it creates an init.d script, and is called from rc.local on a first boot. this is setup script is also the source of the first reboot. the init.d script is created during the first pass, on reboot at init 3 the file system is resized, and then the init.d script is disabled.

all this happens before oobe starts at init 5.

which implies this could be done without the reboot if the init.d script existed on the first boot. and maybe an opportunity to mess with the UUID.

the rpi's fstab uses the PARTUUID so they don't particularly care about the filesystem UUID.

the disk is still mounted at that point, so probably not a good spot.

Yeah, I looked into the resize part thing. They seem to enlarge with parted even so rootfs is mounted.
And they seem to use intentianally PARTUUID, b/c on dos drive is PARTUUID is generated based "Disk Identifier" + part-number, and they try to change "Disk identifier" and adjusting fstab accordingly,
But is I see it, they fail to set either Disk Identifier, at at least PARTUUID seems to be unchanged, and always identical to the one on the image. need a look closer, maybe we can do it differently, for both UUID's ...

#224 Post by **chrispop99** » Thu Dec 28, 2023 3:04 pm

In the Wiki>rpi-tips, the Miscellaneous section mentions that if using auto-login, Chrome will ask for a password the first time after every session start, but it only does that now once after a new install. Can that Wiki entry be corrected to reflect the change?

Chris

#225 Post by **Jerry3904** » Thu Dec 28, 2023 3:37 pm

Of course--I have been changing it almost every day! I thought I had tested that this morning, so will take another look.

Thanks for looking at it.

#226 Post by **Jerry3904** » Thu Dec 28, 2023 3:41 pm

OK, I did check it. I now have autologin selected (via raspi-config), and CHROMIUM asks me for the password every new boot.

I installed with no autologin, then changed, so I wonder if there's a conflict there?

EDIT: in ~/.local/share/keyrings I see two items: login.keyring and user.keystore. I'm going to delete the folder, log out/in and try again.

EDIT2: did that, even rebooted a couple of times with no change. May have to use MX User, it's possible that raspi-config can't carry out the necessary change (?).

EDIT3: MX User already had me registered for autologin. So I logged out/in and this time Chromium did not ask.

#227 Post by **chrispop99** » Thu Dec 28, 2023 3:59 pm

I set auto login during the install process, and only get the keyring request once. It doesn't happen after subsequent reboots.

Chris

#228 Post by **Jerry3904** » Thu Dec 28, 2023 4:02 pm

Well it doesn't work if autologin is set up after installation, apparently. I just ran a reboot and was asked once again for a pwd. I'll just wait for @fehlix and @dolphin_oracle to take a look.

#229 Post by **dolphin_oracle** » Thu Dec 28, 2023 4:11 pm

its supposed to ask for the keyring login if autologin is enabled. I can't say what hilariousness the rpi folks have done to chromium that might change expected behavior, and I'm not particularly worried about it.

my system asks everytime if I'm using autologin.

#230 Post by **Jerry3904** » Thu Dec 28, 2023 4:48 pm

So I should leave the Tips as it is, I guess, at least for now. @chrispop99 Were you testing that on the Pi 5 or the Pi 4?

About to do a new installation ...