[11:14] <admin123> I noticed that the installer configures X automatic, how can I reinvoke it?
[11:15] <cjwatson> sudo dpkg-reconfigure xserver-xorg
[11:15] <cjwatson> if you want it not to ask lots of questions, sudo dpkg-reconfigure -phigh xserver-xorg
[11:30] <admin123> cjwatson, the progressbar worked fine, thanks in advance
[11:31] <admin123> cjwatson, how did the installer configure it?
[11:31] <admin123> I read something about debxconf ? some file in x11-common?
[11:32] <admin123> dexconf...
[11:32] <cjwatson> it just installs the xserver-xorg package (among many others) which configures it all by itself in its maintainer scripts
[11:32] <cjwatson> dexconf is involved somewhere in the middle of all that
[11:32] <cjwatson> progress bar> great!
[01:35] <admin123> We have amd systemes which have SIS chipets and intel systems which have Via chipsets. I was wondering how well X autoconfiguration is implented. for example: dpkg-reconfigure -f noninteractive -pcritical xserver-xorg dosn't modify my configuration, when I put a via cipset driver on a nv driver it still remains standing on the nv driver instead of chaning it.
[02:42] <mark> would it be easy to make the installer always automatically save the debug logs (http)?
[02:42] <mark> that would be very convenient in a number of cases
[02:44] <cjwatson> I'd rather not do that by default; I'd get complaints from people on insecure networks
[02:44] <cjwatson> might be possible to implement a boot option to do it though
[02:44] <cjwatson> file a bug on, er, I guess save-logs?
[02:45] <cjwatson> actually, the source package is installation-report
[02:46] <mark> of course not by default
[02:46] <mark> but it's no problem for us
[02:46] <mark> there's nothing secret in our logs
[02:48] <mark> so it's not easily possible through preseeding or early_command script?
[02:49] <cjwatson> you might be able to do it by calling /var/lib/dpkg/info/save-logs.postinst, or possibly pieces of it
[02:49] <cjwatson> and preseeding save-logs/menu
[02:49] <mark> alright, I will look into it
[02:49] <cjwatson> (web)
[02:49] <mark> yes
[02:49] <cjwatson> one tricky bit
[02:50] <cjwatson> you probably have to do it after network configuration, otherwise the httpd won't bind to the right network interface?
[02:50] <mark> yes
[02:50] <mark> but early_command is run after network config anyway
[02:50] <mark> in our case
[02:50] <mark> the preseed files are on the network
[02:50] <mark> actualy early_command reruns network config, but I can easily start this after that bit
[02:50] <cjwatson> true, if you're using preseed/url
[02:50] <mark> thanks!
[02:51] <cjwatson> I think for making it a standard bit of d-i it should probably be done at the end of netcfg
[02:51] <cjwatson> anyway, back to the weekend :)
[02:51] <mark> enjoy
[03:10] <mark> it's working :)