Skip to contentSkip to conversation

root access and u-boot-test-hooks scripts

DISCUSSION Tom Rini 2 participants 3 messages Apr 29, 2022

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

Hey all,

I'm looking for some feedback and ideas. Today, in our u-boot-test-hooks repository we have 2 cases that use sudo, imx_usb and L4T-based flashing. Other places that may require root access, such as mounting a filesystem instead assume an /etc/fstab entry exists and has "user" as one of the attributes.

Locally, I've extended using "sudo" instead for further access, and so far have updated the rpi3_mount script to be like the flashair one and support all of the platforms (by naming u-boot.bin correctly for the platform) and I've got an easily re-usable ti-omap writer as well (ti-k3 is harder since you need to build two distinct U-Boots).

Would people rather see more sudo use, or more /etc/fstab setup required? I'm happy to adjust what I've done to not use sudo and post that.

Signature · 1 line
Tom
#1 lore raw

Hi Tom

Quoted 5 lines · Tom Rini

Hey all,

I'm looking for some feedback and ideas. Today, in our u-boot-test-hooks repository we have 2 cases that use sudo, imx_usb and

I'm not a super expert but is it sufficient to use udev and insert the right on a group for a particular vendor and product id?

Quoted 3 lines

L4T-based flashing. Other places that may require root access, such as mounting a filesystem instead assume an /etc/fstab entry exists and has "user" as one of the attributes.

If you have a docker container --previlege should not be possible to mount but stay in a different name space?

Michael

Quoted 13 lines

Locally, I've extended using "sudo" instead for further access, and so far have updated the rpi3_mount script to be like the flashair one and support all of the platforms (by naming u-boot.bin correctly for the platform) and I've got an easily re-usable ti-omap writer as well (ti-k3 is harder since you need to build two distinct U-Boots).

Would people rather see more sudo use, or more /etc/fstab setup required? I'm happy to adjust what I've done to not use sudo and post that.

--
Tom

Signature · 11 lines
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
[email protected]
__________________________________

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
[email protected]
www.amarulasolutions.com
author
#2 lore raw
Quoted 11 lines · Michael Nazzareno Trimarchi

Hi Tom

Quoted 5 lines · Tom Rini

Hey all,

I'm looking for some feedback and ideas. Today, in our u-boot-test-hooks repository we have 2 cases that use sudo, imx_usb and

I'm not a super expert but is it sufficient to use udev and insert the right on a group for a particular vendor and product id?

You can do some mount-based rules there as well, but that gets trickier still to document / make portable.

Quoted 6 lines
Quoted 3 lines

L4T-based flashing. Other places that may require root access, such as mounting a filesystem instead assume an /etc/fstab entry exists and has "user" as one of the attributes.

If you have a docker container --previlege should not be possible to mount but stay in a different name space?

I honestly don't know how well all of the tooling would work containerized, especially since we're talking about dynamically appearing/disappearing devices (ie we run sd-mux-ctrl to tell the sd-mux board via USB to present the SD card to us as a mass storage device, mount it via UUID, copy things, unmount, tell the sd-mux board to present it to the device under test now instead).

Signature · 1 line
Tom