From: random832@fastmail.com (Random832)
Subject: [TUHS] Help with a Unix-ish project?
Date: Fri, 15 Jul 2016 21:32:42 -0400 [thread overview]
Message-ID: <1468632762.1363402.667765737.350D807F@webmail.messagingengine.com> (raw)
In-Reply-To: <20160715225617.GB30146@minnie.tuhs.org>
On Fri, Jul 15, 2016, at 18:56, Warren Toomey wrote:
> Unfortunately, while the kernel is nice, they don't provide much of
> a run-time environment, so it feels too much of a toy to use. I had the
> idea of porting a small set of libraries and commands over to get it to
> the point where it feels a bit like 7th Edition.
>
> I've made a start by using the Minix 2.0 libraries and commands, see
> https://github.com/DoctorWkt/xv6-minix2 and the NOTES file. I now realise
> that bringing up a libc plus associated commands will involve a fair bit
> of
> work.
https://github.com/DoctorWkt/xv6-minix2/commit/f6159743fd9d7dd13a1a4c2285a16629176931da
Wouldn't it be easier to simply change the xv6 stat structure itself,
and possibly the filesystem structure as well?
next prev parent reply other threads:[~2016-07-16 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 22:56 Warren Toomey
2016-07-16 1:32 ` Random832 [this message]
2016-07-16 1:44 ` Warren Toomey
2016-07-16 1:56 ` Ronald Natalie
2016-08-14 3:37 ` Random832
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=1468632762.1363402.667765737.350D807F@webmail.messagingengine.com \
--to=random832@fastmail.com \
/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;
as well as URLs for NNTP newsgroup(s).