From: Alison Schofield <alison.schofield@intel.com>
To: brunodout.dev@gmail.com
Cc: outreachy linux kernel <outreachy@lists.linux.dev>
Subject: Re: Information for the Kernelnewbies Outreachy Docs
Date: Tue, 29 Mar 2022 10:54:44 -0700 [thread overview]
Message-ID: <20220329175444.GA1170522@alison-desk> (raw)
In-Reply-To: <3485392358307ad16335e30e6bd41c78cc977840.camel@gmail.com>
On Tue, Mar 29, 2022 at 01:24:17PM -0300, brunodout.dev@gmail.com wrote:
> Hello,
>
> As Roopa suggested me on IRC yesterda, 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 (I run a minimal arch
> install on a small filesystem for each kernel tree, and all
> space necessary to build the kernel I use virtiofs).
>
> I will try to enumerate them:
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.'
Someone on list, with edit privileges can grant you edit privilege
and then you can do it yourself.
Thanks!
Alison
>
> REQUIREMENTS
>
> 1. cpio
> A non-minimalist install will likely have cpio on it, but
> case it doesn't you'll likely get a tricky error when the
> build system runs kernel/gen_kheaders.sh. (sorry, I didn't
> save the output, but the error code is 127)
> Perhaps the script also needs a better error message
>
> Cpio requirement is also missing in the kernel compiling
> docs[1].
>
> 2. ncurses5
> This one isn't missing but it's outdated. It says arch users
> must build it, but actually the arch available package
> 'ncurses' (version 6) worked for me so far (at least for
> targets like menuconfig, which I believe to be the reason of
> this requirement, right?)
>
> 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.
>
> ARCH PACKAGE NAMES
>
> Arch packages are not as much granular as other
> distributions, so 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
> 3. esmtp => libesmtp
>
> REFERENCES
> [1] https://docs.kernel.org/process/changes.html
>
>
> I hope it becomes helpful for other applicants and to
> improve the docs.
>
> Sincerely,
> Bruno | Pronouns: they/them/theirs
> IRC: CodeAgain
>
next prev parent reply other threads:[~2022-03-29 17:52 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 [this message]
2022-04-01 21:38 ` Bruno Moreira-Guedes
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=20220329175444.GA1170522@alison-desk \
--to=alison.schofield@intel.com \
--cc=brunodout.dev@gmail.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.