From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Theodore Ts'o" <tytso@mit.edu>, bulk88 <bulk88@hotmail.com>,
Antti Heikkinen <antti.heikkinen.4@gmail.com>,
linux-kernel@vger.kernel.org, advocacy@perl.org,
beginners@perl.org
Subject: Re: Propose for LINUX kernel and PERL
Date: Mon, 6 Jan 2014 01:01:36 +0000 [thread overview]
Message-ID: <20140106010136.GH10323@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20140105234307.GA16071@thunk.org>
On Sun, Jan 05, 2014 at 06:43:07PM -0500, Theodore Ts'o wrote:
> > Since Perl is Turing complete you can run the Linux kernel inside
> > Perl. Although Perl doesn't run in kernel mode ATM, I don't see why
> > I can't be ported to be a LKM, maybe with RPC to glibc. You could
> > also have Perl running as user mode driver or some kind daemon with
> > calls from a kernel driver to the user space daemon Perl. You can
> > use Perl version 5 or 6.
>
> My favorite suggestion, going back several decades to the early 90's,
> was those who suggested porting BSD 4.3 to Emacs LISP, so that you
> could run your entire system under GNU Emacs. :-)
ISAGN: drivers/staging/vi[1]. As a TTY line discipline. Surely once that
thing is in, somebody will come up with Perl interpreter in vi macros.
And once _that_ is done, the rest will be easy...
[1] or drivers/staging/sam, for extra credits - as far as macros go,
it'd be more convenient implementation platform...
next prev parent reply other threads:[~2014-01-06 1:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 5:46 Propose for LINUX kernel and PERL Antti Heikkinen
2014-01-05 8:12 ` bulk88
2014-01-05 23:43 ` Theodore Ts'o
2014-01-06 1:01 ` Al Viro [this message]
2014-01-05 8:50 ` Richard Foley
2014-01-05 17:48 ` Austin S Hemmelgarn
2014-01-06 1:45 ` Jovi Zhangwei
2014-01-05 22:32 ` Steven Rostedt
2014-01-06 1:49 ` Jovi Zhangwei
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=20140106010136.GH10323@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=advocacy@perl.org \
--cc=antti.heikkinen.4@gmail.com \
--cc=beginners@perl.org \
--cc=bulk88@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.