supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
Cc: misc@list.smarden.org, supervision@list.skarnet.org,
	mkettler@evi-inc.com
Subject: Re: a problem with linux 2.6.11 and sa
Date: Thu, 10 Mar 2005 00:30:22 +0000	[thread overview]
Message-ID: <8765004a1t.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <m3is40z9dy.fsf@multivac.cwru.edu> (Paul Jarc's message of "Wed, 09 Mar 2005 18:28:35 -0500")

On Wed, 09 Mar 2005, Paul Jarc uttered the following:
> "George Georgalis" <george@galis.org> wrote:
>> It (Gerrit Pape's technique) very defiantly stopped working a few revs
>> back (2.6.7?). I'm seeing a similar failed read from /dev/rtc and
>> mplayer with 2.6.10, now too.
> 
> The /proc/kmsg problem happens because the kernel now checks for
> permission at read() instead of open().

Am I the only person who thinks `eee-ick, how utterly non-POSIX' at
that?

-- 
> ...Hires Root Beer...
What we need these days is a stable, fast, anti-aliased root beer
with dynamic shading. Not that you can let just anybody have root.
 --- John M. Ford

  reply	other threads:[~2005-03-10  0:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050303214023.GD1251@ixeon.local>
     [not found] ` <6.2.1.2.0.20050303165334.038f32a0@192.168.50.2>
     [not found]   ` <20050303224616.GA1428@ixeon.local>
     [not found]     ` <871xaqb6o0.fsf@amaterasu.srvr.nix>
2005-03-08 16:58       ` George Georgalis
2005-03-08 17:19         ` George Georgalis
2005-03-08 19:21           ` George Georgalis
2005-03-08 20:10             ` Andre Tomt
2005-03-09 13:06         ` Nix
     [not found]         ` <871xap9dfg.fsf@amaterasu.srvr.nix>
2005-03-09 15:29           ` George Georgalis
2005-03-09 23:28             ` Paul Jarc
2005-03-10  0:30               ` Nix [this message]
2005-03-16  3:18               ` George Georgalis
2005-03-16 22:37                 ` Paul Jarc
2005-03-17  2:03                   ` George Georgalis

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=8765004a1t.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=misc@list.smarden.org \
    --cc=mkettler@evi-inc.com \
    --cc=supervision@list.skarnet.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).