Hi ?????,
????? ???????????? wrote: > Can you list the file names of scripts which are in the miniroot? I don't have such a list at hand. I was just curios if there is an estimation available about how much space is to be saved by this effort. If you would like to generate that list for purposes of your task, there could be several ways how to approach this. [1] Inspecting some existing boot archive. You could take a look at existing boot archive in some image (LiveCD, AI). E.g. in build 128 (mentioning this, as location of boot archives changes in this particular build), you could make the boot archive content accessible following way for Sparc AI ISO: # mkdir /tmp/iso /tmp/ba # mount -F hsfs <path_to_ai_iso_image> /tmp/iso # mount -o ro /tmp/iso/platform/sun4u/boot_archive /tmp/ba And for x86 (starting build 128, 32 and 64 AI archives are separated): # mkdir /tmp/iso /tmp/ba_32 /tmp/ba_64 # mount -F hsfs <path_to_ai_iso_image> /tmp/iso # gzcat /tmp/iso/platform/i86pc/boot_archive > /tmp/boot_archive_32 # gzcat /tmp/iso/platform/i86pc/amd64/boot_archive > /tmp/boot_archive_64 # mount -o nologging /tmp/boot_archive_32 /tmp/ba_32 # mount -o nologging /tmp/boot_archive_64 /tmp/ba_64 [2] Using Distro Constructor (DC) --------------------------------- DC manifests describe the content of particular image and the steps to create it. They contain (among other things) * list of packages to be pulled into the image - section <packages> * subset of files and directories which constitute boot archive - section <boot_archive_contents> You could let DC populate boot archive filesystem (pause at step ba-arch) and inspect the boot archive area after that, e.g. # /usr/bin/distro_const build -p ba-arch <dc_manifest> Then structure of boot archive can be inspected in 'build_data/boot_archive' subdirectory of DC build area (specified in DC manifest in section <build_area> Cheers, Jan > > 2009/11/24 Jan Damborsky <Jan.Damborsky at sun.com>: >> Hi ?????, >> >> ????? ???????????? wrote: >>> I don't have a rough estimate, I have real values: >> I can see how process of compiling the scripts affect particular >> files, but I was more interested in how this would affect size of >> the whole microroot - if you might have rough idea how much space >> would be approximately freed in total. >> >> Jan >> >> > > >
