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-next>] [day] [month] [year] [list]
Message-ID: <45AE507E.3040601@imap.cc>
Date:	Wed, 17 Jan 2007 17:36:14 +0100
From:	Tilman Schmidt <tilman@...p.cc>
To:	Linux Kernel mailing List <linux-kernel@...r.kernel.org>
Subject: where to maintain userspace daemon for line discipline

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?

Thanks
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ