jklyekai wrote: > In the third paper in Dec 11 2008 > I have another questions. > 1.do you still using the default DC direcotry and it configure files? > 2.there is only a fs-root script ,can't find live-fs-root. > 3.I use the slim_cd.xml template and only changes the packages that you > list in the first paper. OK. It executes to im-mod step correctly. > But then distro-const build -r im-mod small_cd.xml. I see many error > information and then build failed. > > cp: cannot access > /rpool/dc/build_data/pkg_image/etc/xdg/autostart/updatemanagernotifier.desktop > rm: > /rpool/dc/build_data/pkg_image/etc/xdg/autostart/updatemanagernotifier.desktop: > No such file or directory > cp: cannot access > /rpool/dc/build_data/pkg_image/usr/share/dbus-1/services/gnome-power-manager.service > rm: > /rpool/dc/build_data/pkg_image/usr/share/dbus-1/services/gnome-power-manager.service: > No such file or directory > cp: cannot access > /rpool/dc/build_data/pkg_image/usr/share/gnome/autostart/gnome-power-manager.desktop > rm: > /rpool/dc/build_data/pkg_image/usr/share/gnome/autostart/gnome-power-manager.desktop: > No such file or directory > cp: cannot access > /rpool/dc/build_data/pkg_image/usr/share/gnome/autostart/gnome-keyring-daemon-wrapper.desktop > ................ > Configuring Gnome in package image area > ................ > /usr/bin/sh: line 1: /lib/svc/method/pixbuf-loaders-installer: not found > en_US.UTF-8: unknown locale > Creating font cache > > I think slim_cd.xml is a basic input file and don't need to reduce some other > parts . Can you give me some suggestion about your small_cd.xml. > > > When customizing your image, you will have to pay attention to 3 major sections in the manifest to make sure that they are consistent. The <packages> section is where you specify what packages to include. This is the section you modified. The second section that you need to pay attention to is the <bootroot> section. This is the list of files and directories that will go into the boot archive. This list is copied from an area that's populated with the packages specified in the <packages> section. So, if you remove some packages which resulted in files/directories listed in <bootroot> section to not exist anymore, you should remove the item from the bootroot section. Be very cautious when you modify this section as it affects whether the image boots up. If you are not sure, I suggest leaving the <bootroot> section alone. The 3rd section you need to modify is the <finalizer> section. This is the set of scripts that modifies the image. It is heavily dependent on the content of the <packages> section. You see all the GNOME error above, because some of the scripts in the <finalizer> section assumes GNOME is in the <packages> list.
My suggestion is that after you have your reduced list of packages, go through each script specified in the <finalizer> section, and make sure the content of those scripts still make sense for what you want to do. --Karen
