All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumitra Sharma <sumitraartsy@gmail.com>
To: outreachy@lists.linux.dev
Subject: Introductory message
Date: Wed, 8 Mar 2023 03:41:22 -0800	[thread overview]
Message-ID: <20230308114122.GA312977@ubuntu> (raw)

Hi I am Sumitra Sharma, an outreachy applicant. This is my first time
applying to outreachy and linux-kernel. I am currently working on
setting up the enviornment. I observed that building the kernel i.e.
running "make -j2" command itself is taking a lot of time. I would
appreciate some suggestions on it.
Also I recieved an error stating "make[2]: *** No rule to make target
'debian/canonical-certs.pem', needed by 'certs/x509_certificate_list'.
Stop." to which I edited the .config file as below
#
# Certificates for signature checking
#
CONFIG_MODULE_SIG_KEY="certs/signing_key.pem"
CONFIG_MODULE_SIG_KEY_TYPE_RSA=y
# CONFIG_MODULE_SIG_KEY_TYPE_ECDSA is not set
CONFIG_SYSTEM_TRUSTED_KEYRING=y
CONFIG_SYSTEM_TRUSTED_KEYS=""
CONFIG_SYSTEM_EXTRA_CERTIFICATE=y
CONFIG_SYSTEM_EXTRA_CERTIFICATE_SIZE=4096
CONFIG_SECONDARY_TRUSTED_KEYRING=y
CONFIG_SYSTEM_BLACKLIST_KEYRING=y
CONFIG_SYSTEM_BLACKLIST_HASH_LIST=""
CONFIG_SYSTEM_REVOCATION_LIST=y
CONFIG_SYSTEM_REVOCATION_KEYS=""
# CONFIG_SYSTEM_BLACKLIST_AUTH_UPDATE is not set
# end of Certificates for signature checking

             reply	other threads:[~2023-03-08 11:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 11:41 Sumitra Sharma [this message]
2023-03-08 11:49 ` Introductory message Julia Lawall
2023-03-08 17:13   ` Ira Weiny
2023-03-08 18:40     ` Fabio M. De Francesco
2023-03-09 16:20       ` Dave Jiang
2023-03-08 15:44 ` Alison Schofield
  -- strict thread matches above, loose matches on Subject: below --
2023-03-09  8:26 Introductory Message Olofu Ojoachubione
2023-03-09  9:32 ` Nikolai Kondrashov
2023-03-07  9:47 agabaderrick18
2023-03-07 16:04 ` 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=20230308114122.GA312977@ubuntu \
    --to=sumitraartsy@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.