Casper.Dik at sun.com wrote:
>
>> What we're actually thinking about here is a daemon that emulates the
>> /var/sadm/install/contents file; the first time the file would be read
>> after a pkg{add,rm} a new global contents file would be constructed
>>from all the per-package contents files. After that, the cached
>> global version would be used until another pkg cmd was used.
>>
>> The mechanism to do this doesn't exist yet, but it's under active
>> discussion. The simplest idea is the ability to have a daemon
>> respond to open/stat commands on the file; it would return a
>> fd to the kernel which could be used for either operation....
>
>
> Would the daemon always run or does this require a new kernel mechanism
> to autostart daemons?
Why wouldn't SMF/contracts handle that ?
> How do you propose the daemon handles:
>
> rename("t.contents", "contents"):
>
> (In case someone runs old packaging tools)
Why would running old pkg commands on a newer release be supported ?
--
Darren J Moffat
