On Tue, 2006-05-09 at 18:34, Albert White wrote:
> Martin Man wrote:
> >
> > I can guess what -devel does, but I can't see what 'r' and 'u' are,
> > thanx for explaining that m = man and h = header ;-) Are we still in 8.3
> > world? Probably, with half of the filename being eaten by SUNW ;-)
>
> User packages, for example SUNWcsu, install files under /usr.
> Root packages, like the corresponding SUNWcsr, install elsewhere. /var/
> /etc /sbin /lib etc.
>
> Diskless client is one thing that relies on having the packages split this
> way. I think zones also takes advantage of this.
I'm starting to wonder whether packages was the right way to do this.
In fact, I'm long past starting, and am mostly convinced that using the
package system as a configuration mechanism for diskless clients, or
zones - or to implement corporate policy as to which particular files
in an application may be installed - is stretching the system way
outside
its comfort zone.
> oh and the longest filename in s10 seems to be
> SUNWgnome-img-editor-devel-share at 33 chars :)
Well, 32 + the trailing NULL/newline.
I had a feeling somewhere that 32 was the actual limit, but on checking
the real limit seems to be 64. (See /usr/include/pkgstrct.h.) Back
in Solaris 7 the limits were very much smaller!
I sniff a possible bug here, but haven't enough machines to
check fully. Try:
pkginfo -l SUNWgnome-img-editor-devel-share
Now, on my sparc boxes (both S10 and nevada) this works correctly;
on my test x86 machine (running patched S10U1 - so as far as I
know it's got the same patches as the S10 sparc boxes I tested)
completely misses the files and only says:
FILES: 1 installed pathnames
unfortunately I haven't got a proper nevada x86 machine (although
I did try with pkg binaries and libraries I built from source and
those didn't work either).
One other comment regarding long package names: the way the tools
parse the contents file requires them to parse the lines into an
internal data structure. See the pkgstruct header file, above.
This involves allocating a fairly large amount of memory just in
case you have an entry with a 64 charcater package name and a 64
character class name. As a result, you end up needing to use RAM
equal to 3 times the size of the contents file, or something like
that. My machine needs about 80M - not a problem on a big system,
but could create quite a lot of pressure on a machine with little
in the way of free memory.
--
-Peter Tribble
L.I.S., University of Hertfordshire - http://www.herts.ac.uk/
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
