From: Jesse Pollard <jesse@cats-chateau.net>
To: Rick Hohensee <humbubba@smarty.smart.net>, linux-kernel@vger.kernel.org
Subject: Re: inserting a Forth-like language into the Linux kernel
Date: Sun, 6 May 2001 18:24:45 -0500 [thread overview]
Message-ID: <01050618263300.10132@tabby> (raw)
In-Reply-To: <200105060357.XAA29873@smarty.smart.net>
In-Reply-To: <200105060357.XAA29873@smarty.smart.net>
On Sat, 05 May 2001, Rick Hohensee wrote:
>kspamd/H3sm is now making continuous writes to tty1 from an
>in-kernel thread. It was locking on a write to /dev/console by
>init, so I made /dev/console a plain file. This is after
>hollowing out sys_syslog to be a null routine, and various
>other minor destruction.
>
>I am now typing at you on tty4 or so while the kernel itself
>sends an endless stream of d's to tty1. It will scroll-lock
>and un-scroll-lock, which is how I can tell it's not just a
>static screen of d's.
>
>I don't know about H1 S&M, but the ability to open a tty
>normally directly into kernelspace may prove popular, particularly
>with a Forth on that tty in that kernelspace. Persons with actual
>kernel clue may want to look at allowing /dev/console users and
>an in-kernel tty user to play nice. For my purposes I'll do without
>a real /dev/console and syslogging for now.
>
>Now I get to find out how many worlds of trouble I didn't foresee
>in _reading_ a tty from the kernel :o)
>
>If someone knows of another example of interpreter-like behavior
>directly in a unix in-kernel thread I'd like to know about it.
Only in reference to allowing for virus infection of the kernel.
It isn't a good idea.
--
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: jesse@cats-chateau.net
Any opinions expressed are solely my own.
next prev parent reply other threads:[~2001-05-06 23:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 3:57 inserting a Forth-like language into the Linux kernel Rick Hohensee
2001-05-06 23:24 ` Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 6:12 Rick Hohensee
2001-05-06 16:32 Dunlap, Randy
2001-05-06 20:33 ` Rick Hohensee
[not found] <200105060652.f466qwH316756@saturn.cs.uml.edu>
2001-05-06 12:21 ` Rick Hohensee
2001-05-05 6:27 Rick Hohensee
2001-05-02 2:29 Rick Hohensee
2001-05-02 3:26 ` Alexander Viro
2001-05-02 15:44 ` Rick Hohensee
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=01050618263300.10132@tabby \
--to=jesse@cats-chateau.net \
--cc=humbubba@smarty.smart.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.