All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "J.R. Mauro" <jrm8005@gmail.com>
Cc: Christopher Brannon <cmbrannon@cox.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /dev/time for Linux, inspired by Plan 9
Date: Fri, 6 Mar 2009 21:54:04 -0800	[thread overview]
Message-ID: <20090307055404.GA549@kroah.com> (raw)
In-Reply-To: <3aaafc130903062143g4b7d6afel575781208319454e@mail.gmail.com>

On Sat, Mar 07, 2009 at 12:43:43AM -0500, J.R. Mauro wrote:
> On Fri, Mar 6, 2009 at 12:57 PM, Greg KH <greg@kroah.com> wrote:
> > On Tue, Mar 03, 2009 at 09:06:46PM -0600, Christopher Brannon wrote:
> >> Under Plan 9 from Bell Labs, one queries or sets the system clock by
> >> reading or writing text strings to a special file named /dev/time.
> >> I implemented such a facility for Linux.  A read of /dev/time produces
> >> four decimal numbers: epoch seconds, nanoseconds since start of epoch,
> >> jiffies since boot, and jiffies per second.  Writing a decimal number to
> >> /dev/time sets the system clock to the given number of epoch seconds.
> >> Anyone who is permitted to write to /dev/time may set the clock.
> >> Granting this privilege becomes as easy as modifying groups and file
> >> permissions.
> >>
> >> Signed-off-by: Christopher Brannon <cmbrannon@cox.net>
> >
> > I'm starting to see a few plan9 specific devices being proposed
> > recently, with one making it into the staging tree recently (the p9auth
> > interface).  Should we just start lumping them all together so to keep
> > them in one place?  drivers/plan9/ ?
> 
> That might be a good idea, assuming it doesn't start up a flamewar.

I don't think if we keep it all in one place, it would.

> The Glendix folks are working hard to get a lot of these device files
> and filesystems implemented and it would be nice to see them have a
> place to feel welcome.
> 
> Would it be very involved to get a little sandbox for these things?

drivers/plan9 looks like a nice place to me, any objections?

thanks,

greg k-h

  reply	other threads:[~2009-03-07  5:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  3:06 [PATCH] /dev/time for Linux, inspired by Plan 9 Christopher Brannon
2009-03-06 17:57 ` Greg KH
2009-03-07  5:43   ` J.R. Mauro
2009-03-07  5:54     ` Greg KH [this message]
2009-03-07 16:08       ` Chris Brannon
2009-03-08 16:03       ` J.R. Mauro
2009-03-06 22:56 ` john stultz
2009-03-07 16:23   ` Chris Brannon
2009-03-12 18:12     ` J.R. Mauro
2009-03-14 23:27       ` Chris Brannon
2009-03-10 11:22 ` Pavel Machek
2009-03-11  7:28 ` Américo Wang
  -- strict thread matches above, loose matches on Subject: below --
2009-03-11 15:10 Christopher Brannon
2009-03-11 21:49 ` Jochen Voß
2009-03-11 22:07 ` Bill Nottingham
2009-03-12  8:00   ` David Newall
2009-03-12 18:15     ` J.R. Mauro
2009-03-12  9:30 ` Giacomo A. Catenazzi
2009-03-14 16:13 ` Pavel Machek
2009-03-17 15:15   ` J.R. Mauro
2009-03-21 22:05     ` Pavel Machek

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=20090307055404.GA549@kroah.com \
    --to=greg@kroah.com \
    --cc=cmbrannon@cox.net \
    --cc=jrm8005@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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.