Hi!
I have recently made a restricted-capability system, using
medusa DS9. It has some properties of a TCSEC B3 level system,
and IT WORKS!
There were some little problem though, one is Bug#60303:
The start-stop script of postgresql assumed DAC_SEARCH capability.
Oliver has added the needed chan
>>"Ian" == Ian Jackson <[EMAIL PROTECTED]> writes:
>> Secondly, looking at what policy covers, there is no
>> such thing as an expert.
Ian> You're assuming that I'm suggesting that a single individual (or small
Ian> group) be responsible for the whole of policy. But, I don't think
Ian> that
reopen 61116
thanks
On Mon, 27 Mar 2000, Santiago Vila wrote:
> On Sun, 26 Mar 2000, Adam Heath wrote:
>
> > package: base-files
> > severity: important
> >
> > During my upgrade tonite, /etc/motd was flagged as a changed conf file, so I
> > hit 'D' to see the diff. I was a little disturbed wh
> That may violate the principle of least surprise.
ok
> What I do not have a handle on yet is which is the more common case, and
> thus which should be the default behavior.
default should be: restart=always start and this will not broke any
existing configurations. So it would be nice to add
Hi,
Wichert suggested a meeting on IRC, for discussion about
-policy. The discussion is open to all comers (irc.debian.org), but
may be moderated and read only, on a channel to be decided.
Since Wednesday appears to be the earliest time that may work,
how about this:
Wednesda
Hi,
This is my take on the subject. An user should not need to
know about /usr/share/doc; mentioning it, espescially with the
wording that implies that one needs look into both dirs to be sure,
is exactly the kind of user interface lossage we were trying to
avoid.
/usr/doc sym
6 matches
Mail list logo
