From: Mahavir Jain <mahavir.coep@gmail.com>
To: Carsten Peter Rasmussen <mail@cprasmussen.dk>
Cc: "linux-c-programming@vger.kernel.org"
<linux-c-programming@vger.kernel.org>
Subject: Re: Where to start C-programming open source?
Date: Wed, 15 Mar 2017 17:53:25 +0530 [thread overview]
Message-ID: <CAA4mPKCUF_G5ChTAn2ytndBLxiv0R5TC9DcGoXxgMCNtf1b0vw@mail.gmail.com> (raw)
In-Reply-To: <0d56ba3f-3880-2793-28b5-70ac13920d29@cprasmussen.dk>
On Fri, Mar 10, 2017 at 3:00 PM, Carsten Peter Rasmussen
<mail@cprasmussen.dk> wrote:
>
> Den 10-03-2017 kl. 01:23 skrev Trevor Woerner:
>>
>> On Fri, Mar 3, 2017 at 11:05 AM, Carsten Peter Rasmussen
>> <mail@cprasmussen.dk> wrote:
>>>
>>> Any comments and advice on getting started in OS with C is greatly
>>> appreciated.
>>
[Resending in plain text mode]
I was looking for similar resources earlier, mostly for learning
purpose, I could gather following information,
For minimal and baremetal OS development on x86,
http://www.osdever.net/bkerndev/Docs/gettingstarted.htm
For little advanced OS development which includes paging and
multitasking support (but in crude way),
https://web.archive.org/web/20160311205056/http://www.jamesmolloy.co.uk/index.html
Above has some known issues (beware and good to chase),
http://wiki.osdev.org/James_Molloy's_Known_Bugs
Xv6 (as already suggested) is rather more comprehensive with very good
documentation,
https://pdos.csail.mit.edu/6.828/2016/xv6.html
>>
>> http://eudyptula-challenge.org/
>
> Looks interesting, is it still working? I just send a plain-text email, but
> no reply.
>
This is also good starting point, but requires good patience, I
dropped from 6th stage as responses were extremely slow.
I could get to below with above references (basic but functional),
https://github.com/mahavirj/tinyos
Best luck!
Thanks,
Mahavir
prev parent reply other threads:[~2017-03-15 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:05 Where to start C-programming open source? Carsten Peter Rasmussen
2017-03-03 19:48 ` Jon Mayo
2017-03-04 9:42 ` Carsten Peter Rasmussen
2017-03-09 0:39 ` Celelibi
2017-03-10 0:23 ` Trevor Woerner
2017-03-10 9:30 ` Carsten Peter Rasmussen
2017-03-10 9:59 ` Trevor Woerner
2017-03-10 15:31 ` Dmitrii Galantsev
2017-03-11 1:30 ` Trevor Woerner
2017-03-15 12:23 ` Mahavir Jain [this message]
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=CAA4mPKCUF_G5ChTAn2ytndBLxiv0R5TC9DcGoXxgMCNtf1b0vw@mail.gmail.com \
--to=mahavir.coep@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=mail@cprasmussen.dk \
/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).