From: stuebinm <stuebinm@disroot.org>
To: nly@disroot.org
Cc: guix-devel@gnu.org
Subject: Re: New Operating System and Kernel development
Date: Wed, 7 Jul 2021 18:18:32 +0200 [thread overview]
Message-ID: <96c43083-af3c-e566-e376-ffcb1bc2cebd@disroot.org> (raw)
In-Reply-To: <mailman.23124.1625670084.20688.guix-devel@gnu.org>
Hi amar,
this is unrelated to GNU or Guix, but if you want to avoid C/C++ it may
be worth taking a look at https://www.redox-os.org, which is written in
Rust — of course there's also the GNU Hurd (and I'm sure many other
projects), but this is the only one I'm aware of that has "avoid using
C/C++" as one of its stated goals (apart from some more specific things
like MirageOS, which uses OCaml a lot).
~stuebinm
On 07.07.21 17:01, guix-devel-request@gnu.org wrote:
> Message: 5
> Date: Wed, 07 Jul 2021 11:51:45 +0000
> From: "Amar M. Singh" <nly@disroot.org>
> To: guix-devel@gnu.org
> Subject: New Operating System and Kernel development
> Message-ID: <aebc4dc14470c9e8939dc021696f0c3c@disroot.org>
> Content-Type: text/plain; charset="utf-8"
>
> Hello all,
>
> Is there any research into new Operating Systems and kernel
> development? I'd like to announce 'heh' that I'm starting on just
> such a project :)
>
> I have a few ideas about what i want to build but that's getting far
> ahead of myself, I think I should build it to run on Qemu or Xen
> hypervisor. The most dreaded thing i want to avoid is C or C++. The
> source code shall go on to https://codeberg.org/nly. And always
> appreciate feedback, in the end I hope to make something that is
> usable and used rather than purely for amusement purposes :)
>
> Thank you for reading so far,
> ~amar
next parent reply other threads:[~2021-07-07 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.23124.1625670084.20688.guix-devel@gnu.org>
2021-07-07 16:18 ` stuebinm [this message]
2021-07-07 11:51 New Operating System and Kernel development Amar M. Singh
2021-07-07 15:30 ` Pjotr Prins
2021-07-07 18:33 ` Gurjeet Singh
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96c43083-af3c-e566-e376-ffcb1bc2cebd@disroot.org \
--to=stuebinm@disroot.org \
--cc=guix-devel@gnu.org \
--cc=nly@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).