Originally Posted by
MAFoElffen
If you look at the installation logs, is it even reading the preseed file? for instance if you did something else in a overtly purposeful off manner, does it follow the script? That just seems so odd... Because from I hear you saying, it should be working. I think may it might be "me" that is missing or not seeing what is going on... because what you are describing should be working.
I'd say that finding these lines in /var/log/installer/syslog would indicate that it's at least reading the preseed config:
Code:
Oct 12 18:26:55 ubuntu kernel: [ 0.000000] Command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/custom.seed auto=true priority=critical boot=casper automatic-ubiquity quiet splash noprompt noshell ---
Oct 12 18:26:55 ubuntu kernel: [ 0.067562] Kernel command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/custom.seed auto=true priority=critical boot=casper automatic-ubiquity quiet splash noprompt noshell ---
Oct 12 18:26:55 ubuntu kernel: [ 0.994447] file=/cdrom/preseed/custom.seed
Oct 12 18:28:04 ubuntu localechooser: info: debian-installer/locale preseeded to 'en_US' (seen: true)
Oct 12 18:28:38 ubuntu /install.py: keeping packages due to preseeding:
However I'd expected to find more lines than only those about preseeding when doing:
Code:
fgrep preseed /var/log/installer/*
But those are the only lines containing 'preseed'...
Bookmarks