LKML Archive on
help / color / mirror / Atom feed
From: Andrew Morton <>
To: Tilman Schmidt <>
Subject: Re: where to maintain userspace daemon for line discipline
Date: Mon, 22 Jan 2007 11:56:44 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> On Wed, 17 Jan 2007 17:36:14 +0100 Tilman Schmidt <> wrote:
> The recent discussion on LKML convinced me that a line discipline
> is the correct way to layer a driver over a serial interface.
> This means, however, that I'll need a (trivial) userspace daemon
> which will hold the serial interface open after pushing the line
> discipline onto it.
> Which raises the question: Where can I drop the source for that
> daemon so that it is
> a) maintained together with the line discipline in case a kernel
> developer feels the need to change something and
> b) picked up by distributions so that they don't end up shipping
> the line discipline without the necessary daemon?
> Is there an appropriate place in or near the kernel tree for
> stuff like that?

Nope.  The requirement arises regularly.

util-linux would seem to be a suitable place, but apparently there
are, umm, isues surrounding that.

  reply	other threads:[~2007-01-22 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 16:36 Tilman Schmidt
2007-01-22 19:56 ` Andrew Morton [this message]
2007-02-07 22:05   ` H. Peter Anvin
2008-01-15 23:03     ` Tilman Schmidt
2008-01-15 23:17       ` Randy Dunlap
2008-01-16 11:54     ` Tilman Schmidt

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:

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

  git send-email \ \ \ \ \
    --subject='Re: where to maintain userspace daemon for line discipline' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).