Hi Jean Finally was able to get back to this. I'm trying to walk through the process by using the stop and resume options to distro_const but its not working as I understand the docs. I ran distro_const -p im-pop test.xml
looked at the check points hpcuser at hpcdevel:/# distro_const build -l /test.xml /usr/share/distro_const/DC-manifest.defval.xml validates /tmp/test_temp_1718.xml validates Step Resumable Description -------------- --------- ------------- im-pop X Populate the image with packages im-mod X Image area modifications slim-im-mod Slim CD Image area Modifications br-init Boot root initialization slim-br-config Slim CD boot root configuration br-config Boot root configuration br-arch Boot root archiving slim-post-mod Slim CD post bootroot image area modification grub-setup Grub menu setup post-mod Post bootroot image area modification iso ISO image creation usb USB image creation then tried to restart resuming at im-pop. hpcuser at hpcdevel:/# distro_const build -r im-mod -p slim-im-mod /test.xml /usr/share/distro_const/DC-manifest.defval.xml validates /tmp/test_temp_1728.xml validates You must specify an earlier step to resume at. Valid steps to resume from are: im-pop Populate the image with packages im-mod Image area modifications shouldn't this work? Bruce Jean McCormack wrote: > Bruce Rothermal wrote: >> It is not mandatory to boot. But I would like this user account to be >> there when the install is complete. What would be the correct way to >> accomplish this. The end goal is to have a system installed with >> specific packages/tools and environment setup. The user would then >> login as a preconfigured user to learn a set of HPC tools which are >> already set up installed and ready to follow the instruction material. >> >> Any pointers, examples would be appreciated. > > Bruce, > > I'm now wondering if the presence of hpcuser in the bootroot could be > causing your problems. It turns out that this file is not in the > bootroot for the image I created that booted fine. > Since you don't need it there to boot, you should remove it from the > base_include list. That is specifically for the boot root. > If you want it in your installed system, make sure it gets into the > pkg_image area. If this file is in one of your new packages, you need > to do nothing. If not, create a finalizer script > that will copy it from where ever you have it, to the pkg_image area. > > You can use checkpointing to check that it's in the pkg_image area > after you've installed the packages via ips. To do so, pause at > im-mod, look at the pkg_image area and then resume from im-mod. > > Does that make sense? > > Jean McCormack >> >> >> Bruce >> >> On Jan 21, 2009, at 1:11 PM, Karen Tung wrote: >> >>> Hi Bruce, >>> >>> You mentioned that you added the following line to the >>> bootroot_contents section of the manifest: >>> >>> <base_include type="dir">export/home/hpcuser</base_include> >>> >>> Is the content of export/home/hpcuser a must-have when the system is >>> booting up? >>> The items listed in the bootroot_contents section are all the >>> must-haves in order for the system to boot up. >>> If those are not a must have, you can try to remove that line and >>> rebuild and see whether >>> the image works better. >>> >>> When you drop into maintenance mode, do you see any error message? >>> "ls" doesn't work for you probably >>> because the path is not set. "ls" is included in the bootroot. You >>> can try to specify the full path: >>> /usr/bin/ls >>> >>> --Karen >>> >>> >>> Jean McCormack wrote: >>>> Bruce, >>>> >>>> Copying caiman-discuss so everyone can be included in this discussion. >>>> It's not clear what is going on here. I know you said the build had >>>> no errors, but can you send the detailed log anyway? >>>> You also might try breaking up the builds to do the just the >>>> studio tools. See if it breaks. >>>> It might give us a clue as to where the problem is. >>>> >>>> Jean >>>> >>>> -------- Original Message -------- >>>> Subject: Need help with using Distribution Constructor >>>> Date: Wed, 21 Jan 2009 08:48:24 -0700 >>>> From: Bruce Rothermal <Bruce.Rothermal at Sun.COM> >>>> To: Jean.McCormack at Sun.COM, Jack.Schwartz at sun.com, >>>> Karen.Tung at Sun.COM >>>> >>>> >>>> >>>> Hi All >>>> >>>> I'm trying to figure out how to use the DC for creating an install >>>> image of a specific configured system. I keep having problems >>>> during the boot up. Everything else runs creating the iso and usb >>>> images with no errors. >>>> >>>> I ran the simple example provided on the OpenSolaris web site and >>>> everything ran fine, booted, etc. >>>> >>>> We want to take the basic system and include in the distro the >>>> studio and clustertools packages. We also would like to include >>>> certain directories which would contain our configuration scripts >>>> etc that we would like to have run at startup. >>>> >>>> For now I created a manifest file which includes: >>>> <pkg name="sunstudioexpress"/> >>>> <pkg name="clustertools_8.1"/> >>>> >>>> I've also include the line >>>> <base_include type="dir">export/home/hpcuser</base_include> >>>> >>>> (I've attached the entire manifest file) >>>> I then run >>>> /usr/bin/distro_const build ./slim_cd.xml >>>> >>>> Like I said it runs all the way through with no errors. I try both >>>> burning the resulting iso and use usb_copy for a flash drive. >>>> >>>> When I boot using these I get past the physical checks, get to >>>> grub menu and select the first default boot option. After a short >>>> while I get enter maintenance user and password or Ctrl D. It will >>>> not allow Ctrl D. I can log in as root but the system is not >>>> really their. For example doing a ls at this point provides no >>>> listing. >>>> >>>> Can you help me by first letting me know if distribution >>>> constructor is the right tool to be using (for Solaris we use a >>>> flash image of the installed system). If this is the right tool >>>> what am I doing wrong in setting up the manifest file. Are there >>>> intermediate steps that need to be done instead of running all the >>>> way through the entire process. >>>> >>>> Thanks for your help >>>> >>>> Bruce >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> _______________________________________________ >>>> caiman-discuss mailing list >>>> caiman-discuss at opensolaris.org >>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>> >> >
