From: Catalin BOIE <util@deuroconsult.ro>
To: SVR Anand <anand@eis.iisc.ernet.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel development in kernel
Date: Thu, 27 Nov 2003 12:54:10 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.58.0311271252550.1341@hosting.rdsbv.ro> (raw)
In-Reply-To: <200311271045.QAA10220@eis.iisc.ernet.in>
> Hi,
Hi.
> I am thinking of developing kernel development environment which provides
> a pseudo shell, and runtime environment that resides in the kernel itself.
> The goal of this exercise is to create an environment that simplifies the
> kernel programming effort by creating a virtual user area that sits above
> kernel but within the kernel protected region. The runtime environment should
> provide all that is necesary to build and debug kernel image as if it is a
> C program.
>
> My wish is that kernel development should eventually become somewhat like
> a C development, if not completely, partially, so that the idea takes the
> lead over spending lots of time in getting a code work in kernel.
>
> Sure, too much of hand waving without any substance went in my mail. If you
> can let me know the worthwhileness of the effort itself I will be motivated
> to slog.
>
> Thanks for your time.
I think you describe uml (http://user-mode-linux.sourceforge.net/).
>
> Anand
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
---
Catalin(ux) BOIE
catab@deuroconsult.ro
next prev parent reply other threads:[~2003-11-27 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 10:45 SVR Anand
2003-11-27 10:54 ` Catalin BOIE [this message]
2003-11-27 11:54 ` Paul Jackson
2003-11-27 12:22 ` SVR Anand
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=Pine.LNX.4.58.0311271252550.1341@hosting.rdsbv.ro \
--to=util@deuroconsult.ro \
--cc=anand@eis.iisc.ernet.in \
--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®