From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
Cc: linux-hams@vger.kernel.org
Subject: mkiss, udev and kernel 2.6
Date: Tue, 02 Nov 2004 17:48:51 +0100 [thread overview]
Message-ID: <4187BA73.2080908@ccr.jussieu.fr> (raw)
In-Reply-To: <20040729113651.6517fe27@dell_ss3.pdx.osdl.net>
Hi,
Does someone have an experience with mkiss and udev in 2.6 kernel ?
I need to use mkiss-kissattach to drive a dual port TNC 1200/9600 KPC9612.
However I don't see how to set up a master-slave pseudo tty system with
udev.
Actually, I went through by instructing the kernel to load devfs at boot
(append="devfs=mount... " in lilo.conf.
But Is there any other solution with udev alone (without devfs) ?
73 de Bernard, f6bvp
next prev parent reply other threads:[~2004-11-02 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 18:36 [PATCH 2.6] convert netrom to module_param Stephen Hemminger
2004-07-29 23:02 ` David S. Miller
2004-11-02 16:48 ` Bernard Pidoux [this message]
2004-11-12 0:56 ` mkiss, udev and kernel 2.6 AA6QN
2004-11-12 4:59 ` Jeremy Utley
2005-03-13 23:25 ` Bernard Pidoux
2005-03-20 23:38 ` AX25 udev pseudo tty support Bernard Pidoux
2004-11-02 17:34 ` xfbb ports and kernel 2.6.8 Bernard Pidoux
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=4187BA73.2080908@ccr.jussieu.fr \
--to=pidoux@ccr.jussieu.fr \
--cc=linux-hams@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox