From: Bruno Moreira-Guedes <codeagain@codeagain.dev>
To: Alison Schofield <alison.schofield@intel.com>
Cc: outreachy linux kernel <outreachy@lists.linux.dev>
Subject: Re: Information for the Kernelnewbies Outreachy Docs
Date: Fri, 01 Apr 2022 18:38:47 -0300 [thread overview]
Message-ID: <3dfdcbd06a0fe14254a7874b4894261da85073e0.camel@codeagain.dev> (raw)
In-Reply-To: <20220329175444.GA1170522@alison-desk>
On Tue, 2022-03-29 at 10:54 -0700, Alison Schofield wrote:
> On Tue, Mar 29, 2022 at 01:24:17PM -0300,
> brunodout.dev@gmail.com wrote:
NOTE: I posted my first e-mail with my gmail account, but the above
address and the one I'm using right now are the same person.
> >
> > I am sharing some info that could be updated in the KernelNewbies
> > Outreachy tutorial. Some instructions for Arch(/Arch based) users
> > and possibly other minimalist VM setups
>
> These sound very useful. Can you update the wiki yourself:
>
> From the https://kernelnewbies.org/Outreachyfirstpatch :
>
> 'To edit the wiki, create an account, and then send an email to
> the outreachy@lists.linux.dev with the subject "[KERNEL NEWBIES
> ACCESS]
> username", where username is your kernel newbies username.'
Just a follow up, I already requested a couple of days ago, and I have
updated the OutreachyfirstpatchSetup page[1] now including the
enumerated items from the previous e-mail and some new details.
>
> Thanks!
> Alison
>
> >
> > REQUIREMENTS
> >
> > 3. Possibly python3
> > I was following the tutorial for the staging kernel tree,
> > and ran `make` to build the kernel (I usually run `make
> > bzImage` followed by `make modules`, like usual in 2005
> > LOL), and got an error that python3 wasn't found. I installed
> > python but then switched back to my old procedure and it worked.
> > I'm not sure if the default target isn't doing something else,
> > since re docs[1] also don't mention python3 as a requirement.
I added this requirement and detailed the reason it might be needed:
several self-test and kunit tools in the /tools tree require python.
It likely explains why I just got the missing python error when I
built with `make` (default target) and not when running `make bzImage
&& make modules`.
I also added perl, which wasn't missing in my list but in minimalist
setups it might. Also added information regarding perl modules that
might be necessary for other tools, that could be installed easily
with `cpan`.
> >
> > ARCH PACKAGE NAMES
> >
> > some packages will be differently named. I have listed them just
> > in case anyone feels stuck:
> >
> > 1. gitk => already contained in: git
> > 2. git-email => already contained in: git
I detailed the above differences in packaging scheme in the wiki, but
I didn't update the information below:
> > 3. esmtp => libesmtp
Turns out this information was wrong, libesmtp and esmtp are not the
same package with different names as I thought, it's actually not
provided in ArchLinux official packages (to my knowledge). I think
users might find a build package in the AUR repo, though. However, the
`mail` utility, from the 's-nail' package, can also be used to achieve
the same goals. I'll go back there and write about that at some point.
> >
> > REFERENCES
> > [1] https://docs.kernel.org/process/changes.html
> >
Regarding kernel docs missing some points, mentioned in the original
post, could I update kernel docs on that too? I've found the online
docs to be based on the docs present in Documentation. Also, would it
count towards my 10 patches requirements? (I plan on doing anyway, but
the answer would help me to prioritize)
>
REFERENCES
[1] https://kernelnewbies.org/OutreachyfirstpatchSetup
--
Sincerely,
Bruno | Pronouns: they/them/theirs
IRC: CodeAgain
next prev parent reply other threads:[~2022-04-01 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 16:24 Information for the Kernelnewbies Outreachy Docs brunodout.dev
2022-03-29 17:54 ` Alison Schofield
2022-04-01 21:38 ` Bruno Moreira-Guedes [this message]
2022-04-01 23:52 ` Alison Schofield
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=3dfdcbd06a0fe14254a7874b4894261da85073e0.camel@codeagain.dev \
--to=codeagain@codeagain.dev \
--cc=alison.schofield@intel.com \
--cc=outreachy@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.