[11:18] <xnox> mpt, good morning! =)
[11:18] <mpt> XNOX
[11:19] <xnox> mpt, have you seen plans to enforce kernel module signature verification, and subsequent option to disable doing that in the ubiquity installer? =)
[11:20] <mpt> xnox, no, I have not seen it and don’t know what it is
[11:21] <xnox> mpt, i shall take some screenshots for you to cringe at =)
[11:54] <mpt> ok :-)
[12:19] <xnox> mpt, https://goo.gl/photos/tBPoEqMtZwxEXn3K9 is approximate screenshot
[12:20] <xnox> the password fields follow similar to the others and flick through matching/non-matching/strong on the side.
[12:20] <xnox> the learn-more button opens a modal dialog with paragraphs of gibberish.
[12:20] <xnox> gibberish is here: https://code.launchpad.net/~mathieu-tl/ubiquity/disable-verification/+merge/278668 scroll down to debian/ubiquity.templates file with loads of new gibberish.
[12:20] <xnox> i'll try to get proper screenshots shortly.
[12:26] <mpt> crikey
[13:04] <stevenm_> anyone here familiar with ubiquity's file...  ubiquity/plugins/ubi-prepare.py  ?
[13:05] <stevenm_> specifically the very bottom (ok_handler_... i'm trying to determine what extractly is done differently about a ubuntu 14.04 install when choosing the non-free option
[13:05] <xnox> yes we are, what about it?
[13:05] <stevenm_> that bit just seems to set the variable the installer uses - i'd like to see what it actually does
[13:06] <xnox> it sets debian-installer / debconf values that are used by other d-i components during installation.
[13:06] <stevenm_> where I can see that?
[13:07] <xnox> stevenm_, do grep for 'nonfree' to see things it affects.
[13:07] <xnox> scripts/plugininstall.py
[13:07] <stevenm_> yeah I have already, it isn't clear
[13:07] <xnox> scripts/simple-plugins
[13:08] <stevenm_> ok i'll look around there - thanks
[13:09] <xnox> stevenm_, it runs ubuntu-drivers to install proprietary things (e.g. nvidia graphics drivers)
[13:10] <xnox> and i think it used to install ubuntu-restricted-extras package, but let me check that.
[13:10] <stevenm_> essentially if someone hasn't chosen that option... i'm wondering what things someone could enter in to a terminal directly after installing - that would do the same thing
[13:10] <xnox> sorry ubuntu-restricted-addons
[13:10] <xnox> carefully hidden in restricted_package_name variable as kubuntu has a different addons package.
[13:10] <stevenm_> yeah that package i know about -but i think it does other things too
[13:11] <xnox> open unity, search for additional drivers - install optional drivers
[13:11] <xnox> open software centre - search for "ubuntu-restricted-addons" install it
[13:11] <stevenm_> not terminal though
[13:11] <xnox> open source source - enable restricted/universe/multiverse, if disabled.
[13:11] <stevenm_> and jockey has gone hasn't it?
[13:12] <xnox> that's it.
[13:12] <xnox> not source source - but "software sources"
[13:12] <stevenm_> i'm still going to go about seeing it for myself
[13:12] <stevenm_> but thanks
[13:12] <xnox> one can do same from terminal.
[13:12] <xnox> no jockeys is long dead, $ ubuntu-drivers is the brave new world.
[13:12] <xnox> $ ubuntu-drivers list
[13:13] <stevenm_> so your saying if someone installed regular ubuntu 14.04 without the tickbox.... a quick 'apt-get install ubuntu-restricted-addons ubuntu-drivers' would do everything?
[13:13] <xnox> for me it offers to only install intel-microcode, and that's it.
[13:13] <stevenm_> oh after first enabling multiverse/universe/restricted
[13:13] <xnox> and well, modify software sources to include componetsn, install addons package with like apt-get.
[13:13] <xnox> no
[13:14] <xnox> yes, enable componets.
[13:14] <xnox> ubuntu-drivers is always installed, one would need to run it and choose to install things it offers to install, if one deems that to be a good fit.
[13:14] <stevenm_> looks like the main operation is in the 'run' function
[13:14] <xnox> e.g. $ sudo ubuntu-drivers autoinstall
[13:14] <xnox> and yeah, that's about it.
[13:16] <stevenm_> does uniquity do all 3?  universe, multiverse & resritced? or just 1 or 2 of them?
[13:17] <stevenm_> it sounds like this would do everything...
[13:17] <stevenm_> add-apt-repository universe; add-apt-repository restricted; add-apt-repository multiverse; apt-get install ubuntu-restricted-addons; ubuntu-drivers autoinstall
[13:17] <stevenm_> (as root)
[13:17] <xnox> we enable main and universe by default, and we enable all 4 for "3rd party blah blah" checkbox.
[13:17] <stevenm_> ah ok so...
[13:17] <stevenm_> add-apt-repository restricted; add-apt-repository multiverse; apt-get install ubuntu-restricted-addons; ubuntu-drivers autoinstall
[13:17] <xnox> yes, thats all.
[13:18]  * xnox guesses we have restricted by default, but one OEM preseed to have e.g. main only
[13:18] <xnox> stevenm_, for automation that would do it, yes.
[13:18] <stevenm_> i'd still feel happier seeing it in the code :P thanks though
[13:18] <xnox> add-apt-repository should be smart about re-enabling already enabled restricted/universe, so wouldn't hurt to run that too.
[13:19] <xnox> stevenm_, hehe. well it's all doing funny things via debconf database, to pass things from ubiquity, to debian-installer (which ubiquity runs in portions, wrapped in file descriptors)
[13:20] <xnox> open a bug/request to get it traced if you really want to. it's "obvious" to ubiquity/d-i developers.... not so much for just any ordinary programmer.
[18:47] <cyphermox> xnox: I updated the branch to account for d-i component merges I've been doing
[18:47] <cyphermox> still need to test build it now again to make sure there aren't other missing files like this, but I'm confident it should work