Kernelnewbies Digest, Vol 77, Issue 7
HI,
I have signed up for the eudyptula challenge to start off.
How exactly do i start to contribute to linux community, i.e fix bug, etc
Thanks
Quoted 187 lines · kernelnewbies-request at kernelnewbies.org
Send Kernelnewbies mailing list submissions to
kernelnewbies at kernelnewbies.orgTo subscribe or unsubscribe via the World Wide Web, visit
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
or, via email, send a message with subject or body 'help' to
kernelnewbies-request at kernelnewbies.orgYou can reach the person managing the list at
kernelnewbies-owner at kernelnewbies.orgWhen replying, please edit your Subject line so it is more specific than "Re: Contents of Kernelnewbies digest..."
Today's Topics:
1. Re: Welcome to the "Kernelnewbies" mailing list
(juan pedro meri?o)
2. Re: Welcome to the "Kernelnewbies" mailing list (Lino Sanfilippo)
3. Btrfs Questions for Personal Data Archive (nick)----------------------------------------------------------------------
Message: 1
Date: Mon, 10 Apr 2017 19:10:46 -0500
From: juan pedro meri?o <[email protected]>
Subject: Re: Welcome to the "Kernelnewbies" mailing list
To: kernelnewbies at kernelnewbies.org
Message-ID:
<CAC8C0kTRaN9jnk72K26YB8ZRBcnBbirGXE6NYL-stfv1vYc5Gg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"Hi!
I have been looking at versions 1,2,3 and 4 of the linux kernel. I would like to know what are the programs for the kernel development environment. To test them and add new features.
Thank you very much!
Quoted 31 lines · On Mon, Apr 10, 2017 at 7:05 PM, <[email protected]>…
Welcome to the Kernelnewbies at kernelnewbies.org mailing list! Welcome to the kernelnewbies mailing list. Please see
http://lists.kernelnewbies.org/ to change membership info and preferences.To post to this list, send your email to:
kernelnewbies at kernelnewbies.org
General information about the mailing list is at:
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at:
https://lists.kernelnewbies.org/mailman/options/kernelnewbies/juapdiaz%
40gmail.comYou can also make such adjustments via email by sending a message to:
Kernelnewbies-request at kernelnewbies.org
with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions.
You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is:
Quoted 8 lines
juanpepe
Normally, Mailman will remind you of your kernelnewbies.org mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170410/d61d3900/attachment-0001.html------------------------------
Message: 2
Date: Tue, 11 Apr 2017 02:50:06 +0200
From: Lino Sanfilippo <[email protected]>
Subject: Re: Welcome to the "Kernelnewbies" mailing list
To: juan pedro meri?o <[email protected]>,
kernelnewbies at kernelnewbies.org
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252Hi,
Quoted 7 lines · juan pedro meri?o
Hi!
I have been looking at versions 1,2,3 and 4 of the linux kernel. I would like to know what are the programs for the kernel development environment. To test them and add new features.
Thank you very much!
Please take a look at this site:
https://www.kernel.org/doc/html/latest/dev-tools/index.html
I suggest that you also take a look at the eudyptula challenge:
http://eudyptula-challenge.org/Quoted 5 lines
Quoted 5 lines
You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is:
juanpepe
Did you notice that you have just made your password public to the whole world?
Regards,
Lino------------------------------
Message: 3
Date: Mon, 10 Apr 2017 23:28:31 -0400
From: nick <[email protected]>
Subject: Btrfs Questions for Personal Data Archive
To: kernelnewbies <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8Greetings All,
I am assuming this is coming from me it's just going to get no reply. However if someone who works on btrfs is willing to reply to this I have a few questions. Firstly I have a lot of personal storage for archiving various things probably around ~37TB filled currently in external drives and estimate the archive to grow to around ~300 to 400 TB. All of these numbers are unformatted for people's information. I have been using btrfs but need to ask a few questions for how to create a central archive best:1.Does the compression algorithms used as according to my knowledge they don't do it well enough to enable it for non text files? What are the performance disadvantages from a IO perspective(I can Google this but I want numbers from someone who works in a data center)? This is primary due to the central archive needing to be used for many different systems at a time. I assume around 3-4 on average maybe more including during a rebuild. Some of it is also hit bit rate encodes I have done for bluray which are around 10-22mbps per second and may need to be watched during a raid rebuild. GPU processing will be client side so don't worry about that.
2. Same as above but for software raid versus hardware raid in btrfs.I am stressing rebuild time here on a raid 5/6. Probably going to use raid 60 as that gives me a mirror plus two drives failure for redundancy.
3. I have found very little information on this but does the metadata being on a SSD actually help with performance? Very little information exist off the wiki for this. I literally goggled for a few hours and found very little even in terms of papers.
Further more the archive is going to be on external hard drives for a while, as hard drives are not big enough. If people want more information or have advice on how to scale this out that would be very helpful. Generally I am looking for information related to btrfs.
If anyone replies huge thanks,
NickP.S. If anyone tells me to send my questions to the btrfs list I did some stupid things and was banned from vger so I am just sending it here for now.------------------------------
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbiesEnd of Kernelnewbies Digest, Vol 77, Issue 7
********************************************
Signature · 1 line
Spending hours typing this email ...just for YOU -The Incredible- and no one else!
Hi Tran Ly Vu,
Quoted 1 line
How exactly do i start to contribute to linux community, i.e fix bug, etc
Below are my suggestions:
(1) Select a module which you are interested;
(2) Dive into the source code; subscribe the related mailing list and concentrate on the news& updates of this module;
(3) After you are familiar with this module, you can take part in it: add feature, fix bug, etc.
Best Regards
Nan Xiao
Quoted 232 lines · Tran Ly Vu
HI,
I have signed up for the eudyptula challenge to start off.
How exactly do i start to contribute to linux community, i.e fix bug, etc
Thanks
Quoted 25 lines · kernelnewbies-request at kernelnewbies.org
Send Kernelnewbies mailing list submissions to
kernelnewbies at kernelnewbies.orgTo subscribe or unsubscribe via the World Wide Web, visit
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
or, via email, send a message with subject or body 'help' to
kernelnewbies-request at kernelnewbies.orgYou can reach the person managing the list at
kernelnewbies-owner at kernelnewbies.orgWhen replying, please edit your Subject line so it is more specific than "Re: Contents of Kernelnewbies digest..."
Today's Topics:
1. Re: Welcome to the "Kernelnewbies" mailing list
(juan pedro meri?o)
2. Re: Welcome to the "Kernelnewbies" mailing list (Lino Sanfilippo)
3. Btrfs Questions for Personal Data Archive (nick)----------------------------------------------------------------------
Quoted 7 lines
Message: 1
Date: Mon, 10 Apr 2017 19:10:46 -0500
From: juan pedro meri?o <[email protected]>
Subject: Re: Welcome to the "Kernelnewbies" mailing list
To: kernelnewbies at kernelnewbies.org Message-ID:<CAC8C0kTRaN9jnk72K26YB8ZRBcnBbirGXE6NYL-stfv1vYc5Gg@mail.gmail.com>
Quoted 6 lines
Content-Type: text/plain; charset="utf-8"
Hi!
I have been looking at versions 1,2,3 and 4 of the linux kernel. I would like to know what are the programs for the kernel development
environment.
Quoted 5 lines
To test them and add new features.
Thank you very much!
On Mon, Apr 10, 2017 at 7:05 PM, <kernelnewbies-request@
kernelnewbies.org>
Quoted 13 lines
Quoted 11 lines · wrote:
Welcome to the Kernelnewbies at kernelnewbies.org mailing list! Welcome to the kernelnewbies mailing list. Please see
http://lists.kernelnewbies.org/ to change membership info and preferences.To post to this list, send your email to:
kernelnewbies at kernelnewbies.org
General information about the mailing list is at:
Quoted 7 lines
Quoted 7 lines
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at:
kernelnewbies/juapdiaz%
Quoted 21 lines
Quoted 13 lines
40gmail.com
You can also make such adjustments via email by sending a message to:
Kernelnewbies-request at kernelnewbies.org
with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions.
You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is:
Quoted 8 lines
juanpepe
Normally, Mailman will remind you of your kernelnewbies.org mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you.
Quoted 3 lines
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170410/d61d3900/attachment-0001.html
Quoted 12 lines
------------------------------
Message: 2
Date: Tue, 11 Apr 2017 02:50:06 +0200
From: Lino Sanfilippo <[email protected]>
Subject: Re: Welcome to the "Kernelnewbies" mailing list
To: juan pedro meri?o <[email protected]>,
kernelnewbies at kernelnewbies.org
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252Quoted 7 lines
Hi,
Quoted 4 lines · juan pedro meri?o
Hi!
I have been looking at versions 1,2,3 and 4 of the linux kernel. I would like to know what are the programs for the kernel development
environment.
Quoted 11 lines
Quoted 3 lines
To test them and add new features.
Thank you very much!
Please take a look at this site:
https://www.kernel.org/doc/html/latest/dev-tools/index.html
I suggest that you also take a look at the eudyptula challenge:
http://eudyptula-challenge.org/Quoted 6 lines
Quoted 5 lines
Quoted 5 lines
You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is:
juanpepe
Did you notice that you have just made your password public to the whole
world?
Quoted 17 lines
Regards,
Lino------------------------------
Message: 3
Date: Mon, 10 Apr 2017 23:28:31 -0400
From: nick <[email protected]>
Subject: Btrfs Questions for Personal Data Archive
To: kernelnewbies <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8Quoted 2 lines
Greetings All,
I am assuming this is coming from me it's just going to get no reply.However if someone
Quoted 1 line
who works on btrfs is willing to reply to this I have a few questions.
Firstly I have a
Quoted 1 line
lot of personal storage for archiving various things probably around
~37TB filled currently
Quoted 1 line
in external drives and estimate the archive to grow to around ~300 to
400 TB. All of
Quoted 1 line
these numbers are unformatted for people's information. I have been
using btrfs but
Quoted 3 lines
need to ask a few questions for how to create a central archive best:
1.Does the compression algorithms used as according to my knowledge they
don't do
Quoted 1 line
it well enough to enable it for non text files? What are the performance
disadvantages
Quoted 1 line
from a IO perspective(I can Google this but I want numbers from someone
who works
Quoted 1 line
in a data center)? This is primary due to the central archive needing to
be used
Quoted 1 line
for many different systems at a time. I assume around 3-4 on average
maybe more
Quoted 1 line
including during a rebuild. Some of it is also hit bit rate encodes I
have done
Quoted 1 line
for bluray which are around 10-22mbps per second and may need to be
watched during
Quoted 1 line
a raid rebuild. GPU processing will be client side so don't worry about
that.
Quoted 2 lines
2. Same as above but for software raid versus hardware raid in btrfs.I
am stressing
Quoted 1 line
rebuild time here on a raid 5/6. Probably going to use raid 60 as that
gives me
Quoted 3 lines
a mirror plus two drives failure for redundancy.
3. I have found very little information on this but does the metadata
being on a SSD
Quoted 1 line
actually help with performance? Very little information exist off the
wiki for this.
Quoted 1 line
I literally goggled for a few hours and found very little even in terms
of papers.
Quoted 2 lines
Further more the archive is going to be on external hard drives for a
while, as hard
Quoted 1 line
drives are not big enough. If people want more information or have
advice on how
Quoted 1 line
to scale this out that would be very helpful. Generally I am looking for
information
Quoted 5 lines
related to btrfs.
If anyone replies huge thanks,
NickP.S. If anyone tells me to send my questions to the btrfs list I didsome stupid things and
Quoted 6 lines
was banned from vger so I am just sending it here for now.
------------------------------
Quoted 8 lines
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbiesEnd of Kernelnewbies Digest, Vol 77, Issue 7
********************************************--
Spending hours typing this email ...just for YOU -The Incredible- and no one else!
Quoted 5 lines
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170412/12d71921/attachment.html
Hello all,
I would suggest to peruse https://kernelnewbies.org/.
BR,
Sebastien.
Quoted 298 lines · Nan Xiao
Hi Tran Ly Vu,
Quoted 1 line
How exactly do i start to contribute to linux community, i.e fix
bug, etc
Below are my suggestions:
(1) Select a module which you are interested;
(2) Dive into the source code; subscribe the related mailing list and concentrate on the news& updates of this module;
(3) After you are familiar with this module, you can take part in it:
add feature, fix bug, etc.Best Regards
Nan XiaoQuoted 28 lines · Tran Ly Vu
HI,
I have signed up for the eudyptula challenge to start off.
How exactly do i start to contribute to linux community, i.e fix bug, etc
Thanks
Quoted 5 lines · kernelnewbies-request at kernelnewbies.org
Send Kernelnewbies mailing list submissions to kernelnewbies at kernelnewbies.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies [1]
Quoted 7 lines
or, via email, send a message with subject or body 'help' to kernelnewbies-request at kernelnewbies.org
You can reach the person managing the list at kernelnewbies-owner at kernelnewbies.org
When replying, please edit your Subject line so it is more
specific
Quoted 3 lines
than "Re: Contents of Kernelnewbies digest..."
Quoted 11 lines
Quoted 5 lines
Today's Topics:
1. Re: Welcome to the "Kernelnewbies" mailing list (juan pedro meri?o)
2. Re: Welcome to the "Kernelnewbies" mailing list (LinoSanfilippo)
Quoted 4 lines
3. Btrfs Questions for Personal Data Archive (nick)
----------------------------------------------------------------------
Quoted 36 lines
Quoted 8 lines
Message: 1
Date: Mon, 10 Apr 2017 19:10:46 -0500
From: juan pedro meri?o <[email protected]>
Subject: Re: Welcome to the "Kernelnewbies" mailing list
To: kernelnewbies at kernelnewbies.org Message-ID:<CAC8C0kTRaN9jnk72K26YB8ZRBcnBbirGXE6NYL-stfv1vYc5Gg@mail.gmail.com>
Quoted 5 lines
Content-Type: text/plain; charset="utf-8"
Hi!
I have been looking at versions 1,2,3 and 4 of the linux kernel.
I would
Quoted 1 line
like to know what are the programs for the kernel development
environment.
Quoted 5 lines
To test them and add new features.
Thank you very much!
On Mon, Apr 10, 2017 at 7:05 PM,
Quoted 3 lines
Quoted 1 line · wrote:
Welcome to the Kernelnewbies at kernelnewbies.org mailing list!
Welcome
Quoted 2 lines
Quoted 2 lines
to the kernelnewbies mailing list. Please see
http://lists.kernelnewbies.org/ [2] to change membership infoand
Quoted 6 lines
Quoted 6 lines
preferences.
To post to this list, send your email to:
kernelnewbies at kernelnewbies.org
Quoted 12 lines
Quoted 3 lines
Quoted 3 lines
General information about the mailing list is at:
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies [1]
Quoted 2 lines
Quoted 2 lines
If you ever want to unsubscribe or change your options (eg,
switch to
Quoted 4 lines
Quoted 4 lines
or from digest mode, change your password, etc.), visit your subscription page at:
https://lists.kernelnewbies.org/mailman/options/kernelnewbies/juapdiaz%
Quoted 18 lines
[3]
Quoted 4 lines
Quoted 4 lines
40gmail.com [4]
You can also make such adjustments via email by sending a
message to:
Quoted 7 lines
Quoted 7 lines
Kernelnewbies-request at kernelnewbies.org
with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions.
You must know your password to change your options (including
changing
Quoted 4 lines
Quoted 4 lines
the password, itself) or to unsubscribe. It is:
juanpepe
Quoted 13 lines
Quoted 1 line
Quoted 1 line
Normally, Mailman will remind you of your kernelnewbies.org [5]
mailing
Quoted 1 line
Quoted 1 line
list passwords once every month, although you can disable this
if you
Quoted 2 lines
Quoted 2 lines
prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a
button on
Quoted 5 lines
Quoted 2 lines
your options page that will email your current password to you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:Quoted 130 lines
[6]
Quoted 12 lines
------------------------------
Message: 2
Date: Tue, 11 Apr 2017 02:50:06 +0200
From: Lino Sanfilippo <[email protected]>
Subject: Re: Welcome to the "Kernelnewbies" mailing list
To: juan pedro meri?o <[email protected]>, kernelnewbies at kernelnewbies.org
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252Quoted 6 lines
Hi,
Quoted 3 lines · juan pedro meri?o
Hi!
I have been looking at versions 1,2,3 and 4 of the linux kernel.
I would
Quoted 1 line
Quoted 1 line
like to know what are the programs for the kernel development
environment.
Quoted 12 lines
Quoted 3 lines
To test them and add new features.
Thank you very much!
Please take a look at this site:
https://www.kernel.org/doc/html/latest/dev-tools/index.html [7]
I suggest that you also take a look at the eudyptula challenge:
http://eudyptula-challenge.org/ [8]Quoted 1 line
Quoted 1 line
You must know your password to change your options (including
changing
Quoted 5 lines
Quoted 4 lines
Quoted 4 lines
the password, itself) or to unsubscribe. It is:
juanpepe
Did you notice that you have just made your password public to
the whole world?
Quoted 17 lines
Regards,
Lino------------------------------
Message: 3
Date: Mon, 10 Apr 2017 23:28:31 -0400
From: nick <[email protected]>
Subject: Btrfs Questions for Personal Data Archive
To: kernelnewbies <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8Quoted 2 lines
Greetings All,
I am assuming this is coming from me it's just going to get noreply. However if someone
Quoted 1 line
who works on btrfs is willing to reply to this I have a few
questions. Firstly I have a
Quoted 1 line
lot of personal storage for archiving various things probably
around ~37TB filled currently
Quoted 1 line
in external drives and estimate the archive to grow to around
~300 to 400 TB. All of
Quoted 1 line
these numbers are unformatted for people's information. I have
been using btrfs but
Quoted 1 line
need to ask a few questions for how to create a central archive
best:
Quoted 2 lines
1.Does the compression algorithms used as according to my
knowledge they don't do
Quoted 1 line
it well enough to enable it for non text files? What are the
performance disadvantages
Quoted 1 line
from a IO perspective(I can Google this but I want numbers from
someone who works
Quoted 1 line
in a data center)? This is primary due to the central archive
needing to be used
Quoted 1 line
for many different systems at a time. I assume around 3-4 on
average maybe more
Quoted 1 line
including during a rebuild. Some of it is also hit bit rate
encodes I have done
Quoted 1 line
for bluray which are around 10-22mbps per second and may need to
be watched during
Quoted 1 line
a raid rebuild. GPU processing will be client side so don't worry
about that.
Quoted 2 lines
2. Same as above but for software raid versus hardware raid in
btrfs.I am stressing
Quoted 1 line
rebuild time here on a raid 5/6. Probably going to use raid 60 as
that gives me
Quoted 3 lines
a mirror plus two drives failure for redundancy.
3. I have found very little information on this but does the
metadata being on a SSD
Quoted 1 line
actually help with performance? Very little information exist off
the wiki for this.
Quoted 1 line
I literally goggled for a few hours and found very little even in
terms of papers.
Quoted 2 lines
Further more the archive is going to be on external hard drives
for a while, as hard
Quoted 1 line
drives are not big enough. If people want more information or
have advice on how
Quoted 1 line
to scale this out that would be very helpful. Generally I am
looking for information
Quoted 5 lines
related to btrfs.
If anyone replies huge thanks,
NickP.S. If anyone tells me to send my questions to the btrfs list Idid some stupid things and
Quoted 10 lines
was banned from vger so I am just sending it here for now.
------------------------------
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies[1]
Quoted 4 lines
End of Kernelnewbies Digest, Vol 77, Issue 7
********************************************Quoted 8 lines
--
Spending hours typing this email ...just for YOU -The Incredible- and no one else!_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies [1]Links:
------
[1] https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
[2] http://lists.kernelnewbies.org/
[3]
https://lists.kernelnewbies.org/mailman/options/kernelnewbies/juapdiaz%
[4] http://40gmail.com
[5] http://kernelnewbies.org
[6]
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170410/d61d3900/attachment-0001.html
[7] https://www.kernel.org/doc/html/latest/dev-tools/index.html
[8] http://eudyptula-challenge.org/_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
How to contribute (was Re: Kernelnewbies Digest, Vol 77, Issue 7
In reply to Tran Ly VuQuoted 1 line · Tran Ly Vu
How exactly do i start to contribute to linux community, i.e fix bug, etc
Step 0: Figure out *why* you want to contribute to the Linux kernel.
Did your boss just tell you that you have 6 weeks to write a driver for your company's new widget?
Do you have a device that doesn't have Linux support?
Is your kernel crashing/misbehaving?
Do you have an intense interest in filesystems, or memory management, or networking, or process scheduling, or other aspect of kernels?
Do you just want to give back to the community?
Did you think it was a good way to attract members of the appropriate gender?
What you do next will depend on *why* you're here, and what your current technical skills are.
Note that asking others for what you should do is as bad an idea as asking people whether you should write a murder mystery or a romance novel, and for exactly the same reason. If you're doing it because somebody else suggested it but you don't care for it, the results will be bad.
Though if you just want to give back to the community, the easiest thing to do, and the most useful, is to build and boot linux-next kernels and see if anything breaks on your system. We have *lots* of people slinging code, and not so many testing. And testing is easier than coding. :)
Here's the cheat sheet for linux-next:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git $ git fetch linux-next $ git fetch --tags linux-next
(now get a .config file - grabbing your distro's config is a good place to start. 'make locallmodconfig' if you want a faster build by not building device driver modules for devices you don't have.
Then do a 'make' and install/boot your kernel. Google for detailed instructions for how to build/install your own kernel on your distro
... # later on - do this once every 1-3 weeks or as time permits
$ git remote update $ make oldconfig $ make (install as above) Boot it, and report any problems.
Do *not* do a 'git pull' to get the most recent linux-next, it won't do what you think.
Yes, it really *is* that simple.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170412/550e6fea/attachment.bin
How to contribute (was Re: Kernelnewbies Digest, Vol 77, Issue 7
Quoted 63 lines · valdis.kletnieks at vt.edu
Quoted 1 line · Tran Ly Vu
How exactly do i start to contribute to linux community, i.e fix bug, etc
Step 0: Figure out *why* you want to contribute to the Linux kernel.
Did your boss just tell you that you have 6 weeks to write a driver for your company's new widget?
Do you have a device that doesn't have Linux support?
Is your kernel crashing/misbehaving?
Do you have an intense interest in filesystems, or memory management, or networking, or process scheduling, or other aspect of kernels?
Do you just want to give back to the community?
Did you think it was a good way to attract members of the appropriate gender?
What you do next will depend on *why* you're here, and what your current technical skills are.
Note that asking others for what you should do is as bad an idea as asking people whether you should write a murder mystery or a romance novel, and for exactly the same reason. If you're doing it because somebody else suggested it but you don't care for it, the results will be bad.
Though if you just want to give back to the community, the easiest thing to do, and the most useful, is to build and boot linux-next kernels and see if anything breaks on your system. We have *lots* of people slinging code, and not so many testing. And testing is easier than coding. :)
Here's the cheat sheet for linux-next:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git $ git fetch linux-next $ git fetch --tags linux-next(now get a .config file - grabbing your distro's config is a good place to start. 'make locallmodconfig' if you want a faster build by not building device driver modules for devices you don't have.
Then do a 'make' and install/boot your kernel. Google for detailed instructions for how to build/install your own kernel on your distro... # later on - do this once every 1-3 weeks or as time permits
$ git remote update $ make oldconfig $ make (install as above) Boot it, and report any problems.Do *not* do a 'git pull' to get the most recent linux-next, it won't do what you think.
Yes, it really *is* that simple.
Quoted 4 lines
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hey, that's quite interesting.
(And Hi, I'm really new here)
So, the best "branch" of developement to test if it doesn't break our system is the linux-next branch, or the mainline kernel (currently tagged by Linus as 4.11-RC6) ?
I'm currently trying to understand how kernel developement is actually organized, here's what I've understood
Developers pull the code fror the next kernel release (mainline? linux-next?) and make changes. They gett the diff of theses changes (patches), and send them by mail to the relevent maintainers and mailing lists.
Maintainers approves (or discuss) the changes, and acked/sign them off.
Quoted 1 line
From there, where are the patches going? To Linux Next? or th Linus's
mainline tree?
- In the mean time, Linux get patches from trusted mainaines into he's own tree while working on what will become the next kernel version. After a while, he decide to not accept "new features" patches for that version, only bugfixes. That's when he's doing "release candidates" of the kernel. After multiple of these, when eveything is "ready", the new kernel is released. For example, the next one will be 4.11.
- Once that is done, Linux start's working on getting the patches from 4.12 in the same way, while the maintainer for the "stable" kernel, port back the important fixes to the current kernel. That's hw we get kernels like the 4.10.9 that I'm currently running (Just got out of my distro's testing process. ArchLinux holds binary packages in a "testing" repository before putting them in "core" Arch. That's off-topic).
So, how "linux-next" works ? Is that a "testing ground" for new kernel patches? When/how does the changes the maintainers accepted are merged into the mainline kernel? ^^"
Oh, and, I almost forgot : If I try to use a linux-next kenrel, and things breaks, who do I tell? ^^"
Sorry if that's a lot of questions, but I'm fairly curious right now
Thanks in advance,
Arthur Brainville
How to contribute (was Re: Kernelnewbies Digest, Vol 77, Issue 7
Quoted 3 lines · Arthur Brainville (Ybalrid)
So, the best "branch" of developement to test if it doesn't break our system is the linux-next branch, or the mainline kernel (currently tagged by Linus as 4.11-RC6) ?
Depends how brave you are. Linus is currently at -rc6, and linux-next *should* be what will become 4.12. (Should be, as in "4.11 is at -rc5, so people *should* already have sent maintainers patches for the next release").
Quoted 2 lines
I'm currently trying to understand how kernel developement is actually organized, here's what I've understood
You're a bit off...
Quoted 3 lines
So, how "linux-next" works ? Is that a "testing ground" for new kernel patches? When/how does the changes the maintainers accepted are merged into the mainline kernel? ^^"
And explaining how you're off answers this question as well... :)
Here's how it works..
Developers create patches. See Documentation/process/submitting-patches.rst for the details on that.
They then e-mail those to maintainers. See MAINTAINERS for the canonical list.
Maintainers then review the patches, and if there's an issue, e-mail back to the submitter with an explanation of the issue. If the patch is OK, the maintainer puts it into his git tree (usually with 'git am').
There may be several levels of sub-maintainer. For instance, somebody may maintain a driver for one specific USB sound card. They feed those patches to the USB sound maintainer, who then feeds it to the USB subsystem maintainer. That gets done by the higher-up maintainer doing a 'git pull' of the appropriate tree.
In addition, most of the trees *also* get pulled every day and built into 'linux-next', to find merge conflicts and provide a test kernel.
So at this point, we have top-level maintainers with trees full of patches.
At some point, Linus tags the final V4.11. This opens the "merge window". For 2 weeks, Linus does 'git pull' from all the maintainers and merges it to his tree, and then tags V4.12-rc1, which closes the merge window. During the merge window, most maintainers will not accept new patches, because there's a chance that a patch could come in and be immediately merged upstream without
having appeared in several linux-next dailys - so no testing. Once the
window is closed, maintainers start collecting patches for the v4.13 cycle, and only sending Linus bugfixes and minor stuff between 4.12-rc1 and final 4.12
Lather, rinse, repeat. release, merge cycle, -rc1, collect patches for next release, -rc8 (or so) and another release....
Quoted 2 lines
Oh, and, I almost forgot : If I try to use a linux-next kenrel, and things breaks, who do I tell? ^^"
Depends how granular you can identify the issue. If you do a 'git bisect'
of a problem, you can narrow it down to a specific patch, you mail the patch
author, the maintainer, any subsystem-specific list, and the linux-kernel list.
If you just know "USB is hosed", you send it to the USB list and linux-kernel,
and if you have *no* idea, toss it to linux-kernel.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170412/46ea96a6/attachment.bin
How to contribute (was Re: Kernelnewbies Digest, Vol 77, Issue 7
Quoted 67 lines · valdis.kletnieks at vt.edu
Quoted 3 lines · Arthur Brainville (Ybalrid)
So, the best "branch" of developement to test if it doesn't break our system is the linux-next branch, or the mainline kernel (currently tagged by Linus as 4.11-RC6) ?
Depends how brave you are. Linus is currently at -rc6, and linux-next *should* be what will become 4.12. (Should be, as in "4.11 is at -rc5, so people *should* already have sent maintainers patches for the next release").
Quoted 2 lines
I'm currently trying to understand how kernel developement is actually organized, here's what I've understood
You're a bit off...
Quoted 3 lines
So, how "linux-next" works ? Is that a "testing ground" for new kernel patches? When/how does the changes the maintainers accepted are merged into the mainline kernel? ^^"
And explaining how you're off answers this question as well... :)
Here's how it works..
Developers create patches. See
Documentation/process/submitting-patches.rstfor the details on that.They then e-mail those to maintainers. See
MAINTAINERSfor the canonical list.Maintainers then review the patches, and if there's an issue, e-mail back to the submitter with an explanation of the issue. If the patch is OK, the maintainer puts it into his git tree (usually with 'git am').
There may be several levels of sub-maintainer. For instance, somebody may maintain a driver for one specific USB sound card. They feed those patches to the USB sound maintainer, who then feeds it to the USB subsystem maintainer. That gets done by the higher-up maintainer doing a 'git pull' of the appropriate tree.
In addition, most of the trees *also* get pulled every day and built into 'linux-next', to find merge conflicts and provide a test kernel.
So at this point, we have top-level maintainers with trees full of patches.
At some point, Linus tags the final V4.11. This opens the "merge window". For 2 weeks, Linus does 'git pull' from all the maintainers and merges it to his tree, and then tags V4.12-rc1, which closes the merge window. During the merge window, most maintainers will not accept new patches, because there's a chance that a patch could come in and be immediately merged upstream without
having appeared in several linux-next dailys - so no testing. Once the
window is closed, maintainers start collecting patches for the v4.13 cycle, and only sending Linus bugfixes and minor stuff between 4.12-rc1 and final 4.12Lather, rinse, repeat. release, merge cycle, -rc1, collect patches for next release, -rc8 (or so) and another release....
Quoted 2 lines
Oh, and, I almost forgot : If I try to use a linux-next kenrel, and things breaks, who do I tell? ^^"
Depends how granular you can identify the issue. If you do a 'git bisect' of a problem, you can narrow it down to a specific patch, you mail the patch author, the maintainer, any subsystem-specific list, and the linux-kernel list. If you just know "USB is hosed", you send it to the USB list and linux-kernel, and if you have *no* idea, toss it to linux-kernel.
Quoted 4 lines
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Thanks for the explaination!
Indeed I was quite a bit off, now I know the process better ;-)
Regards,
Arthur Brainville
How to contribute (was Re: Kernelnewbies Digest, Vol 77, Issue 7
In reply to valdis.kletnieks at vt.eduQuoted 48 lines · valdis.kletnieks at vt.edu
Quoted 1 line · Tran Ly Vu
How exactly do i start to contribute to linux community, i.e fix bug, etc
Step 0: Figure out *why* you want to contribute to the Linux kernel.
Did your boss just tell you that you have 6 weeks to write a driver for your company's new widget?
Do you have a device that doesn't have Linux support?
Is your kernel crashing/misbehaving?
Do you have an intense interest in filesystems, or memory management, or networking, or process scheduling, or other aspect of kernels?
Do you just want to give back to the community?
Did you think it was a good way to attract members of the appropriate gender?
What you do next will depend on *why* you're here, and what your current technical skills are.
Note that asking others for what you should do is as bad an idea as asking people whether you should write a murder mystery or a romance novel, and for exactly the same reason. If you're doing it because somebody else suggested it but you don't care for it, the results will be bad.
Though if you just want to give back to the community, the easiest thing to do, and the most useful, is to build and boot linux-next kernels and see if anything breaks on your system. We have *lots* of people slinging code, and not so many testing. And testing is easier than coding. :)
Here's the cheat sheet for linux-next:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git $ git fetch linux-next $ git fetch --tags linux-next(now get a .config file - grabbing your distro's config is a good place to start. 'make locallmodconfig' if you want a faster build by not building device driver modules for devices you don't have.
Then do a 'make' and install/boot your kernel. Google for detailed instructions for how to build/install your own kernel on your distro... # later on - do this once every 1-3 weeks or as time permits
Quoted 8 lines
$ git remote update $ make oldconfig $ make (install as above) Boot it, and report any problems.Do *not* do a 'git pull' to get the most recent linux-next, it won't do what you think.
As far as I understand unless a git pull or fetch + merge/rebase is run, nothing would change locally. make oldconfig would result in the same config. Then what are we testing for here?
Thanks
Aishwarya
Quoted 11 lines
Yes, it really *is* that simple.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
How to contribute (was Re: Kernelnewbies Digest, Vol 77, Issue 7
Quoted 55 lines · Aishwarya Pant
Quoted 54 lines · valdis.kletnieks at vt.edu
Quoted 1 line · Tran Ly Vu
How exactly do i start to contribute to linux community, i.e fix bug, etc
Step 0: Figure out *why* you want to contribute to the Linux kernel.
Did your boss just tell you that you have 6 weeks to write a driver for your company's new widget?
Do you have a device that doesn't have Linux support?
Is your kernel crashing/misbehaving?
Do you have an intense interest in filesystems, or memory management, or networking, or process scheduling, or other aspect of kernels?
Do you just want to give back to the community?
Did you think it was a good way to attract members of the appropriate gender?
What you do next will depend on *why* you're here, and what your current technical skills are.
Note that asking others for what you should do is as bad an idea as asking people whether you should write a murder mystery or a romance novel, and for exactly the same reason. If you're doing it because somebody else suggested it but you don't care for it, the results will be bad.
Though if you just want to give back to the community, the easiest thing to do, and the most useful, is to build and boot linux-next kernels and see if anything breaks on your system. We have *lots* of people slinging code, and not so many testing. And testing is easier than coding. :)
Here's the cheat sheet for linux-next:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git $ git fetch linux-next $ git fetch --tags linux-next(now get a .config file - grabbing your distro's config is a good place to start. 'make locallmodconfig' if you want a faster build by not building device driver modules for devices you don't have.
Then do a 'make' and install/boot your kernel. Google for detailed instructions for how to build/install your own kernel on your distro... # later on - do this once every 1-3 weeks or as time permits
$ git remote update $ make oldconfig $ make (install as above) Boot it, and report any problems.
Quoted 6 lines
Quoted 2 lines
Do *not* do a 'git pull' to get the most recent linux-next, it won't do what you think.
As far as I understand unless a git pull or fetch + merge/rebase is run, nothing would change locally. make oldconfig would result in the same config. Then what are we testing for here?
git remote update
git tag --list "next-*"
git checkout -b branch_name next-201704xy
Quoted 21 lines
Thanks
AishwaryaQuoted 11 lines
Yes, it really *is* that simple.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies