From: Jerome Brock <jpbrock@pacbell.net>
To: "Linux-Kernel Mailing List (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Getting user input from the kernel?
Date: Sun, 11 Feb 2001 16:31:17 -0800 [thread overview]
Message-ID: <000a01c0948b$1d8fc420$0201a8c0@chinook> (raw)
Sorry if this is a stupid question.
Is it possible to get user input from within the kernel?
I am trying to develop simple text-based user interface for a user to
perform some security critical actions, i.e. logging in. Basically, I am
trying to implement a security manager that will be invoked via the magic
key sequence. For all you security gurus this is a trusted path.
Once the user has invoked my kernel code, I believe I can use printk to
provide output to the user. However, there is no equivalent scank. How can
I get user input from the kernel?
Can this be done, or should I use the magic key sequence to launch a user
mode process that will implement the security manager I have in mind? Also
does it make a difference whether I use kernel 2.2 or 2.4?
Thanks
Jerome
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-02-12 0:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000a01c0948b$1d8fc420$0201a8c0@chinook' \
--to=jpbrock@pacbell.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®