All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Michael Halcrow <lkml@halcrow.us>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] BSD Secure Levels LSM (1/3)
Date: Tue, 10 Aug 2004 13:17:04 -0400	[thread overview]
Message-ID: <1092158224.3290.9.camel@mindpipe> (raw)
In-Reply-To: <20040810151420.GA4993@halcrow.us>

On Tue, 2004-08-10 at 11:14, Michael Halcrow wrote:

> This particular patch adds a set of hooks that are necessary to catch
> attempts to decrement the system time.

Argh, IMHO this was the most annoying thing about adminning BSD/OS, if
the clock got ahead somehow you needed to down the thing to fix it.

Of course I am sure there are plenty of good reasons for this
functionality, I just would not want that one.

Lee


  reply	other threads:[~2004-08-10 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 15:14 [PATCH] BSD Secure Levels LSM (1/3) Michael Halcrow
2004-08-10 17:17 ` Lee Revell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-30 14:35 Michael Halcrow
2004-08-30 16:08 ` Chris Wright
2004-08-30 15:15   ` Michael Halcrow
2004-08-30 16:10 ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1092158224.3290.9.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@halcrow.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.