Alexander wrote: > Is "entire" package necessary in AI manifest? When I missed it, pkg said > "pkg: no packages matching the following patterns you specified are > installed on the system. Try specifying -r to query remotely: > > entire > Automated Installation failed". > But if I include it in package list, doesn't it mean that pkg will install a > lot of packages, on which entire depends? >
I would not expect a failure without entire, and that's something that ought to be checked out, but there's no reason to fear that its inclusion will install additional software. entire is what's known as an "incorporation", which is more or less a virtual package that just ties together the packages in the repo so that they are updated together to the same version (note that in its manifest each of the dependencies has a "type=incorporate" property). The packages that will cause additional inclusions are the large group packages such as "slim_install", "babel_install", or "redistributable" that we use to build the CD images and the complete repository contents. Dave > However, OS without entire boots to the following state: > Rebooting with command: boot > > Boot device: /pci at 1f,700000/scsi at 2/disk at 0,0:a File and args: > SunOS Release 5.11 Version snv_111b 64-bit > Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > WARNING: add_spec: No major number for fp > mpt: cannot load driver > Cannot load drivers for /pci at 1f,700000/scsi at 2/disk at 0,0:a > Can't load the root filesystem > Type 'go' to resume > > Now I've added SUNWpd to my initial manifest, trying to proceed...
