rahul wrote: > > | So can we assert that future squid versions will very likely continue > | to be config and interface compatible? In other words we can continue > | updating the versions through patches and there won't be any of the > | issues faced by apache & php? That's nice, simplifies everything.. > > Yes, AFAIK
That's great.. > | Some other components deliver a stub manpage in the system location, > | which points to the component-specific manpages available in the > | above location. (For example /usr/share/man/man1/php.1 for php). > > I had opted to follow the apache model since apache was the closest to > squid. more over the bin/sbin directories (which are documented by man) are > under squid too. Apache does have a stub manpage (/usr/share/man/man1m/apache.1m) but apache2 does not. So looks like there isn't a rule about including these, though some components do. I'm ok with either approach, though I do kind of like getting something if I type "man squid" on a new system as it helps discovery so it eases the user experience a bit. > | > 7.2. Imported Interfaces > > I am in the process of adding that in the wiki (link at the end.) The imported list in http://wikis.sun.com/display/WebStack/SquidARC has shrunk a lot, did you just take them off as you research each one before adding them back? > | > Solaris Trusted Extensions library (libtsol) Ah, ok, this is in SUNWcsl -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
