Introductory Message

Introductory Message

[agabaderrick18]

Hi there am  Derrick an Outreachy applicant,I'm happy to be here.Been
reading through the archives and learning alot and right now am working
on my first patch welcome any correction and direction as a way
forward.
   I. Thanks

Re: Introductory Message

[Alison Schofield]

On Tue, Mar 07, 2023 at 12:47:45PM +0300, agabaderrick18@gmail.com wrote:
> Hi there am  Derrick an Outreachy applicant,I'm happy to be here.Been
> reading through the archives and learning alot and right now am working
> on my first patch welcome any correction and direction as a way
> forward.
>    I. Thanks
> 
>
Hi Derrick,

Welcome to the Linux Kernel Community!

Alison

Introductory message

[Sumitra Sharma]

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

Re: Introductory message

[Julia Lawall]

On Wed, 8 Mar 2023, Sumitra Sharma wrote:

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

I think it would take a lot of time...

You may be able to optimize your configuration to what modules are
actually used on your machine, rather than everything that your distro
wants to offer.  Maybe make localconfig.

> 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"

I just have "" as the string.

julia

> 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
>
>

Re: Introductory message

[Alison Schofield]

On Wed, Mar 08, 2023 at 03:41:22AM -0800, Sumitra Sharma wrote:
> Hi I am Sumitra Sharma, an outreachy applicant. This is my first time

Hi Sumitra,

It's good that you posted this message for all to see and learn from.

It would be even better if posted as a new message and subject line.

There is another setup related question that is buried beneath an
intro. It's better to do a new message with appropriate subject line.

Thanks,
Alison

> 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
> 

Re: Introductory message

[Ira Weiny]

Julia Lawall wrote:
> 
> 
> On Wed, 8 Mar 2023, Sumitra Sharma wrote:
> 
> > 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.
> 
> I think it would take a lot of time...

Also:

-j is an option which chooses how many threads to build in parallel.

If you have enough cores on your machine you could increase '2' to
something larger.

Ira

> 
> You may be able to optimize your configuration to what modules are
> actually used on your machine, rather than everything that your distro
> wants to offer.  Maybe make localconfig.
> 
> > 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"
> 
> I just have "" as the string.
> 
> julia
> 
> > 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
> >
> >
> 

Re: Introductory message

[Fabio M. De Francesco]

On mercoledì 8 marzo 2023 18:13:33 CET Ira Weiny wrote:
> Julia Lawall wrote:
> > On Wed, 8 Mar 2023, Sumitra Sharma wrote:
> > > 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 environment. 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.
> > 
> > I think it would take a lot of time...
> 
> Also:
> 
> -j is an option which chooses how many threads to build in parallel.
> 
> If you have enough cores on your machine you could increase '2' to
> something larger.
> 

Sumitra,

That "something larger" can be calculated with a rule of thumb and then 
adapted to your necessities...

Look at /proc/cpuinfo if you don't know how many cores you have in your 
system...

# cat /proc/cpuinfo | grep processor
processor: 0
processor: 1
processor: 2
processor: 3
processor: 4
processor: 5
processor: 6
processor: 7
processor: 8
processor: 9
processor: 10
processor: 11

The output shows that I'm using a 12 core SMT system (https://
en.wikipedia.org/wiki/Simultaneous_multithreading).

So "-j12" is my usual choice for building a kernel in the host, minus the 
number of SMT cores reserved for running VMs.

Thanks,

Fabio
 

Introductory Message

[Olofu Ojoachubione]

Hello, I'm Chubi and I'm an outreachy applicant.
I am happy and willing to contribute to this project.

Re: Introductory Message

[Nikolai Kondrashov]

On 3/9/23 10:26, Olofu Ojoachubione wrote:
> Hello, I'm Chubi and I'm an outreachy applicant.
> I am happy and willing to contribute to this project.

Hi Chubi, and welcome to the project!

I just sent you an invite to our Slack. Please proceed to the #outreachy 
channel there with any questions you might have.

We still have one "good first issue" unassigned, which you could pick:

https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+no%3Aassignee+repo%3Akernelci%2Fkcidb-io+repo%3Akernelci%2Fkcidb+label%3A%22good+first+issue%22

and I could create some more. Once you're done with one or more of these, you 
could move onto "good second issues", which would be harder:

https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+no%3Aassignee+repo%3Akernelci%2Fkcidb-io+repo%3Akernelci%2Fkcidb+label%3A%22good+second+issue%22+

Have fun, and don't hesitate to ask questions!
Nick

Re: Introductory message

[Dave Jiang]

On 3/8/23 11:40 AM, Fabio M. De Francesco wrote:
> On mercoledì 8 marzo 2023 18:13:33 CET Ira Weiny wrote:
>> Julia Lawall wrote:
>>> On Wed, 8 Mar 2023, Sumitra Sharma wrote:
>>>> 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 environment. 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.
>>>
>>> I think it would take a lot of time...
>>
>> Also:
>>
>> -j is an option which chooses how many threads to build in parallel.
>>
>> If you have enough cores on your machine you could increase '2' to
>> something larger.
>>
> 
> Sumitra,
> 
> That "something larger" can be calculated with a rule of thumb and then
> adapted to your necessities...
> 
> Look at /proc/cpuinfo if you don't know how many cores you have in your
> system...
> 
> # cat /proc/cpuinfo | grep processor
> processor: 0
> processor: 1
> processor: 2
> processor: 3
> processor: 4
> processor: 5
> processor: 6
> processor: 7
> processor: 8
> processor: 9
> processor: 10
> processor: 11
> 
> The output shows that I'm using a 12 core SMT system (https://
> en.wikipedia.org/wiki/Simultaneous_multithreading).
> 
> So "-j12" is my usual choice for building a kernel in the host, minus the
> number of SMT cores reserved for running VMs.

or just run 'make -j`nproc`'. Notice it's not single quote "'" but "`" 
around nproc to execute the command. The return value of nproc is fed to 
make. That what it just picks the max threads on whatever system you are 
on.

> 
> Thanks,
> 
> Fabio
>   
> 
> 
> 
>