hardware technician wrote: > I would like to make a custom cd using distroconstructor. However, it has to > be cd and it cannot be dvd. I would like to be able to get it to smallest > size possible. > > 1. I noticed these are the only packages installed by default, from the > manifest file: > <packages> > <pkg name="SUNWcsd"/> > <pkg name="slim_cd"/> > > <pkg name="SUNWcs"/> > <pkg name="slim_install"/> > <pkg name="SUNWslim-utils"/> > <pkg name="entire"/> > > </packages> > > I would like to get more information on the packages, and I found this to get > more information on packages: > http://pkg.opensolaris.org/release/en/index.shtml > > I also tried this to get information for all of the packages: > # pkg info -r pkg:/SUNWslim-utils at 0.5.11-0.101 > > Name: SUNWslim-utils > > Summary: SUNW-slim-utilities > > Category: Applications/System Utilities > > State: Not installed > > Authority: opensolaris.org > > Version: 0.5.11 > > Build Release: 5.11 > > Branch: 0.101 > > Packaging Date: Wed Nov 19 22:59:17 2008 > > Size: 179.73 kB > > FMRI: pkg:/SUNWslim-utils at 0.5.11,5.11-0.101:20081119T225917Z > > > But this didn?t always provide information about all of the packages, or it > didn?t provide much information. Is there a better resource about about the > packages, what they do, what files or applications they install? Would I be > able to break the pkg clusters into smaller parts? Because I would like to > install only certain languages, or accessibility options. Is there a way to > remove specific applications after they?ve already been installed, if the > packages are installed as clusters? For example, totem, > pkg:/SUNWgnome-media-player at 0.5.11-0.101. Is SUNWgnome-media-player a > part of the package clusters? Which ones? > You can use "pkg contents -m <package_name>" to see the manifest of a package or a cluster. Note that you might or might not be able to exclude a package because another package might depend on it. > In the manifest I saw: > <post_install_remove_packages> > <pkg name="slim_install"/> > </post_install_remove_packages> > in the slim_cd.xml file, but is that packages the distro-constructor is going > to remove from the final .iso (which is what I would want), or are these > packages included in the iso, but are going to be removed from the system > after it? installed on the machine (which wouldn?t affect the size of the > image)? > This is for excluding packages from the ISO. This is useful if you just want to exclude a few packages from the list of packages defined in the <packages> section. > 2. I was interested in customizing the final install grub menu. I saw: > <!-- Grub menu modifications. Will use menu.lst if not specified--> > > <grub_menu_modifications> > > <entry> > <title_suffix>with magnifier</title_suffix> > > <line> > kernel$ /platform/i86pc/kernel/$ISADIR/unix -B assistive_tech=magnifier > </line> > <line>module /boot/x86.microroot</line> > </entry> > > <entry> > <title_suffix>with screen reader</title_suffix> > > <line> > kernel$ /platform/i86pc/kernel/$ISADIR/unix -B assistive_tech=reader > </line> > <line>module /boot/x86.microroot</line> > </entry> > </grub_menu_modifications> > In the manifest files, but will this modify grub for the boot cd, or the > final install? I am interested in modifying the grub for the final install. > This is modification for the Slim CD, not the final install. The grub menu for the final install is currently done by the ICT module. > 3. I also created a device using lofiadm -a, and using: > pfexec mount -F hsfs -o rw /dev/lofi/1 /mnt > to mount my image created by distroconstruct. > > I received an error, stating that it was ignoring rw option. However, in > lofiadm man pages, under device, it states: > When a file is added, it is opened for reading or writing by root. > I am logged in as root, and I have no write access to files. Is there > something I?m doing wrong? Are there files I could modify to customize the > bookmarks in firefox, and customize the grub menu? Or should I leave the > image alone after the image has been created by distroconstruct? Would I > have to create a script? > This is expected behavior as designed. You can't mount a hsfs ISO with rw. It will be mounted ro. See the arch case that implemented this feature.
http://opensolaris.org/os/community/arc/caselog/2008/290/onepager/ > 4. I would like to be able to have the image automatically installed, > using predefined user, timezone, etc. without having to boot into the > desktop. Would that be possible? > > Then, later, I could use this as my automated install image, like provided on > genunix.org: > http://genunix.org/distributions/indiana/osol-0811-ai.iso > > They got that image size down to like 300. Is that image pulling from the > IPS repository, or is that the complete install? Are there any how to?s on > how that image was created? I would love to get my image that small. I > tried to boot to the ai image, but it wouldn?t install. I received error > ?couldn?t determine source of automated install image.? I would love to get > the manifest file for that image as well. > The AI iso is created by the Distro Constructor as well. The AI image is in the prototype state. The AI image is created using the following manifest: /usr/share/distro_const/auto_install/ai_x86_image.xml Here's some documentation about the AI project: http://opensolaris.org/os/project/caiman/auto_install/Documentation/ --Karen > Using Installadm, would I be able to use a windows XP or linux image that > I?ve already created to install xp/linux on remote machines from the install > server? >
