Comment 12 for bug 1013843

I just grabbed the Quantal Desktop daily image of 19-Jun-2012 and extracted the squashfs.

There I found that resolvconf's database contains an "original.resolvconf" record with "nameserver 10.122.37.1" in it. Explanation: When resolvconf is installed it puts a copy of the original resolv.conf file in /etc/resolv.conf.d/original and another copy in /run/resolvconf/interface/original.resolvconf so that no nameserver information is lost. The latter file (correctly) disappears at the next reboot. I wonder if that file belongs in the live image.

=================BEGIN LOG ================
 # ls -l ./etc/resolv.conf
./etc/resolv.conf -> ../run/resolvconf/resolv.conf
# cd run/resolvconf
# ls -l
total 12
drwxr-xr-x 2 root root 4096 Jun 19 09:39 interface
-r--r--r-- 1 root root 0 Jun 19 09:39 resolv.conf
# ls -l interface
total 12
-r--r--r-- 1 root root 417 Jan 23 20:56 original.resolvconf

# cat interface/original.resolvconf
#
# m
# mmmm m m mmmm mmmm mmm mm#mm
# #" "# # # #" "# #" "# #" # #
# # # # # # # # # #"""" #
# ##m#" "mm"# ##m#" ##m#" "#mm" "mm
# # # #
# " " "
# This file is managed by puppet. Do not make local changes.

domain buildd
nameserver 10.122.37.1
============== END LOG ==============

Can someone please explain exactly how nameserver and other networking information is passed from one program to another when booting a live image, installing Ubuntu on a machine, (apparently) chrooting to the installed system to run late_command, and rebooting?

A good overview of how live CDs are built would also be helpful to me.