On Tue, 26 Oct 2004 19:45:15 +0200, martin f krafft <[EMAIL PROTECTED]> said: 

> also sprach Frank Küster <[EMAIL PROTECTED]> [2004.10.26.1916 +0200]:
>> > Lastly, the policy promises that /usr can be read-only and
>> > guarantees software to be fully functional.
>> 
>> Now, where is the possible policy bug?

> Section 9.1.1 of the policy. The software writes to /usr, which is
> to be treated as read-only at any time other than package
> management. Thus, effectively, dpkg is the only tool allowed to
> manipulate files in /usr, though other tools are used from time to
> time (e.g. ln(1)), but only during installation or removal of the
> owner package.

        Again, what's the policy bug?

        manoj
-- 
Zeus gave Leda the bird.
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


Reply via email to