9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "M. Osman Talayman" <talayman@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Questions about the P9 kernel code
Date: Sun, 18 Sep 2022 20:20:17 +0200	[thread overview]
Message-ID: <CAJ4zFbLAXqbM6n8Mns6PHBVr=5Kmq8H9Ymk5GqORPj9tboTqbQ@mail.gmail.com> (raw)
In-Reply-To: <b627944e-4882-64c8-9c75-c804bf5eb582@posixcafe.org>

Thanks Moody,

I have read documentation from the P9 Legacy website, the cat-v
website as well as man pages etc. I am by no means an expert, but I
think I understand the conceps of the system. I figured, that I would
begin reading throught he kernel code and figure out C as I went
along. The questions I have right now is not so much relating to C per
se, but more about the implementation.

However, you are right. It all starts with the language, the compiler
and the libraries that come along with it. I will start with the K&R
book, which I have.

Thanks again

Den søn. 18. sep. 2022 kl. 20.03 skrev Jacob Moody <moody@mail.posixcafe.org>:
> On 9/18/22 10:21, M. Osman Talayman wrote:
> > Hello,
> >
> > I have begun reading the code for P9 and am wondering if this is the
> > list to use for questions concerning the code I don't understand
> > (which is probably going to be most of it)?
> >
> > I work as a systems developer (D365FO). I have never coded in C and
> > never read kernel code before, so my questions will be simplistic for
> > many of you. (hopefully you will have the patiens to answer my
> > question)
> >
> Have you used the system? Read through the documentation? If you
> just sat down and started by reading the code first and trying to
> make sense of it with no C background, of course most of it is not
> going to make sense.
> Learn C first. Doing that while using 9front as a development
> environment sounds quite pleasant. But you need to start somewhere
> and learn things before just asking someone to walk you through
> how the C works out. Go read K&R, write the practice problems on
> 9front if you want, take a walk through our C libraries, read their
> implementations, try using them. In the process you'll pick up
> concepts about the system. In general just become acquainted with
> our tools and broad concepts, before trying to figure out how
> the sausage is made.
> Just ask the questions as you have them, don't ask for permission
> to ask questions.
> Good luck,
> moody

  reply	other threads:[~2022-09-18 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18 16:21 M. Osman Talayman
2022-09-18 17:59 ` Jacob Moody
2022-09-18 18:20   ` M. Osman Talayman [this message]
2022-09-18 18:50     ` Jacob Moody
2022-09-19  7:25     ` sirjofri
2022-09-19  9:14       ` M. Osman Talayman
2022-09-19  9:51         ` hiro
2022-09-19 14:41         ` Jacob Moody

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ4zFbLAXqbM6n8Mns6PHBVr=5Kmq8H9Ymk5GqORPj9tboTqbQ@mail.gmail.com' \
    --to=talayman@gmail.com \
    --cc=9front@9front.org \


* 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).