/srv/irclogs.ubuntu.com/2014/02/01/#ubuntu-installer.txt

* infinity kisses ti-omap4 goodbye from the archive.11:21
stgraberyay!11:22
^charlieis there a method for popping a custom prompt during ubuntu installation, but before first boot?  i want to collect a string and store it to a file for use during post-install firstboot.20:03
^charliei am currently using an unattended setup seed for 12.04LTS, plan to use it for 14.04LTS as well20:04
^charlieanyone here fielding questions?21:06
antarusthis channel is pretty quiet, even during the week ;)21:08
antarusinfinity, cjwatson, and xnox are about the only regulars21:09
* antarus is only in here to pester colin with annoying questions21:09
xnoxantarus: i am about, but coding. What's up?21:10
^charliei'd like to collect a string from the user either from d-i or ubiquity during installation, and store it to a file on the system for consumption during first boot when i take over with more scripts21:11
^charliefrom what i see online, a custom udeb might be able to ask questions but i'm not finding enough info about it to understand.21:11
^charlieonline general searches about "install prompt user" et al get me a lot of hits regarding apt-get and the like21:12
antarusyou can definitely use a udeb to add a step to the install process, that prompts the user if the answer is not preseeded21:12
antarusI can't say I could point you at some steps to do it though21:13
antarusit involves debconf, debconf templates, building udeb, and the right control fields to add your step to the right place in the install21:13
^charliedang, that was my next q :_21:13
antarusand at least for me, its mostly 'find another package that does this, copy liberally'21:13
antaruss/package/udeb/21:13
antarus;)21:13
antarusfwiw, this is for d-i21:14
^charlieok i'll take a look around, thanks.21:14
antarusubiquity is probably way easier21:14
antarusor asking them in oem-config21:14
antarusalso way easier21:14
^charliei haven't seen oem-config yet.21:14
^charlielet me look around for that.21:14
xnox^charlie: all of d-i is just shell scripts that invoke debconf to ask user questions, so all / any installer screens are examples of what you want.21:14
antarusoem-config is (IIRC) the UI that the user gets after the install21:14
antarusto let them pick their TZ,  language, and so forth21:14
^charliedoes that oem-install occur before the reboot21:15
antarusno21:15
antaruswell, possibly21:15
antarusit doesn't in our setup ;p21:15
^charliehow do i get ubiquity to askquestions?  is it the same udeb type stuff?21:16
antarusyou have to write some...python..or glade..or something21:17
antarusI don't have the code in front of me, and my code was written in 2008, so I'd hope there is something better now ;p21:17
^charliepython is just fine.  is there some example script i can look at?21:17
antarusI'd just go grab the ubiquity source21:17
^charlieok21:17
antarusor oem-config?21:17
antarusthere are screens that Ubuntu is using21:18
xnox^charlie: pure oem-config in d-i has (typically) three parts - ask questions during install / execute some things, allow reboot into final system and do as you like (optional), pop-up instance/end-user config when shipped.21:18
antarusalso maybe search the wiki21:18
^charlieyeah i'll check oem-config too.  it all depends if it's executing before the first boot.21:18
xnoxantarus: ubiquity wraps d-i with python modules, so one can do debconf based questions, or just pure python questions/answers + exec things in the target/first boot.21:18
antarusfor our process, we have basically given up on having things ready 'pre first boot'21:18
^charlieagree21:18
xnoxantarus: e.g. see ubuntuone plugin that asks non-d-i questions and does things to /target21:19
^charliethe vast majority of what i do occurs after first boot21:19
antaruswe try to get the machine as close as we can, and then reboot into a 'provisioning environment'21:19
antarus(which is essentially ubiquity)21:19
antarusand then we prep the machine21:19
^charliei am just trying to collect some credentials and have them ready for some git/svn activities during first boot21:19
^charliefirst boot being what happens after ubiquity is all done and ejects the disc21:20
^charliecurrently those credentials are in a script in the install media.... and i dislike the idea of having to do that.21:20
^charliei'd rather make the user cough them up.21:21
antarusyeah putting creds in the install media is not so nice21:21
antaruswe've been trying put stuff in the TPM21:21
antarusor wrapped with the TPM21:22
antarusbut shockingly, the TPM does not function very well21:22
^charlieheh21:22
^charliei'm not fond of tpm from the user side either.21:22
antaruswe end up fighting a lot with vendors who either ship a TPM that just doesn't work, or doesn't work in linux, or...21:22
antarusand canonical doesn't care about the TPM (not that I blame them...since no one uses it ;p)21:23
antarusso even when we try to buy canonical certified hardware21:23
antarusit still may not work ;p21:23
antarushardware is 'fun'21:23
antarusvirtual machines for everyone!21:23
^charlieTPM won't be so useful for me, i'm providing a dev/qa environment to teammates who use VMs and dumpy unwanted hardware21:23
antarusyeah21:24
antarusI'm more talking about credentials in general21:24
^charlieah okay21:24
^charlieso i'll take a look at oem-config and also the ubiquity sources and see what i can come up with.21:25
^charlieif anyone knows of a decent udeb tutorial that would be awesome.  or source of an existing udeb that asks for a string and stores it.21:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!