linux-kernel - Re: where to maintain userspace daemon for line discipline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070122115644.b538908f.akpm@osdl.org>
Date:	Mon, 22 Jan 2007 11:56:44 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: where to maintain userspace daemon for line discipline

> On Wed, 17 Jan 2007 17:36:14 +0100 Tilman Schmidt <tilman@...p.cc> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/