[21:25] Would anyone be able to explain to me the difference between oem-config and ubiquity? on the system I am using ubiquity is /usr/bin/ubiquity and oem-config is -> /usr/lib/ubiquity/bin/ubiquity [21:44] I am trying to run ubiquity/oem-setup (as I said I have no idea what the difference is) using debconf_ui in text mode on first boot of the device I am working on. How do I take over the console so that system messages are not displayed while the setup is running? [21:50] Norm_42: I may get scolded, but I suggest spending the 5 min to read and 20 min to watch it run: https://debconf-video-team.pages.debian.net/ansible/usb_install/usb_quick_start.html [21:50] just that one page [21:51] assuming you have a usb stick and x86 box handy that can be wiped [21:54] I have a usb stick but the availability of x86 boxes I can wipe is 0 [21:54] (working from home has its disadvantages) [21:58] What would be the result of following these steps and how would it going to help me with my current problem? [22:00] it demos an automated install from OS to application config [22:01] I have copied it and swapped out the app parts to setup something completely different [22:02] I'm not really doing an install. I am doing an OEM OOBE setup of an already installed box... Like the windows sysprep where you leave the device in a state where the end user has to agree to the EULA and create the user account and setup things like locale and networking [22:03] I have this mostly working (actually nVidia did the work) I am just trying to adapt what they did for my needs. [22:04] The problem is that the nvidia setup uses the gtk gui setup if a monitor is plugged in and a debconf_ui if there is no monitor and you setup via serial over USB [22:05] welp, if you make a usb stick, you will have it all working, and then you can adapt it. which might be less work. [22:05] the gui setup does not allow networking to be setup but the text mode debconf seems to work perfectly [22:05] I need to ship these boxes (nvidia Jetson Nanos) completely configured except for the last step [22:06] do you know ansible? [22:06] My only problem right now is that kernel messages display while the setup is running which is not a good user experience. [22:09] So there has to be a way of supressing the messages. I already have quiet on the boot args but systemd keeps wanting to tell me that there is a long running setup operation while the setup is running [22:12] heh - we made a point of making sure all that spew was visible [22:21] Really the most annoying one is [* ] (1 of 2) "A start job is running for End-user configuration after inital OEM installatoin (Debconf UI) (