On Apr 9, 2010, at 10:26 AM, Shawn Walker wrote: > On 04/ 9/10 11:14 AM, Adam Leventhal wrote: >>> What's the output of "pkg version" ? >> >> 38fe0f4bd5ca >> >> I this version of the pkg tools by following the flag day mail and >> downloading this: >> >> http://nana.sfbay/products/osol_dev/133/svr4_ips_packages_i386.zip > > Ah, ok. In 133, repository configuration was temporarily changed to require > the 'repository.origins' property to be set in your $REPO_DIR/cfg_cache file. > > So, in your case, it should be: > > [repository] > origins = http://localhost:12345 > > This requirement was removed in 134 (the requirement was well intentioned but > there are some use cases it didn't account for).
Where can I find an updated svr4 package? >> 1. How can I use my repo to create-image and bless the directory I'm >> installing into? > > Temporarily change your configuration as mentioned above. > > Please note that you shouldn't create an image using '/' on an SVR4-installed > or managed system -- you will get unexpected results. I can imagine :-) >> 2. I'm not sure of the prescribed method for installing everything in ON, >> but I tried install '*'. > > I don't think that's what you want. > > I honestly don't know if there's a "install cluster" just for ON yet, perhaps > someone else does. So do I have to enumerate all packages effectively by hand? >> 3. That quickly barfed saying >> >> pkg: No version of network/dhcp/dhcpmgr can be installed: >> pkg://on-nightly/network/dhcp/[email protected],5.11-0.136:20100409T022934Z: >> Suitable required dependency pkg:/runtime/java cannot be found >> >> Can someone suggest a way forward on that? > > The on-nightly repositories are meant to be used in combination with the > opensolaris.org publisher configured to use the http://ipkg.sfbay/dev > repository as an origin. > > In this particular case, I'm going to guess you configured the > opensolaris.org publisher to use the pkg.opensolaris.org/dev repository, > which currently doesn't have any builds beyond 134. > > I'll send you the steps off-list. I see. I don't want to use the opensolaris.org repository for this particular project. >> 4. How is the depot server on opensolaris.org invoked? > > Via SMF. See "man pkg.depotd" for more information about what SMF properties > are available. What I mean is: how is that particular instance configured, what properties are set, etc? >> 5. Is the distro constructor something that would be potentially useful here? > > It sort of depends. > > For automated installs, use AI. > > For creating your own custom image suitable for a LiveCD/DVD, etc. use > Distribution Constructor. > > If you just want to install a recent build on a system and you want a fairly > minimal set of packages, I'd suggest using the text install CD or USB images. Yes, I'm trying to build a complete boot image. I don't want any particular customization -- I just want to lay down the bits I'd get from the old combinations of bfu+postinstall. >> 6. How would I serve up both repo.extra and repo.redist? Would I need two >> servers? > > You currently would need one pkg.depotd process for each repository you want > to provide access to. Elegant :-) And can I somehow point the pkg(1) command at multiple repositories to get them to pull packages from both? Adam -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ install-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/install-discuss
