From mboxrd@z Thu Jan 1 00:00:00 1970 From: insane79@yandex.ru (Dennis Semakin) Date: Fri, 23 Dec 2016 12:01:37 +0300 Subject: Is kernel Bugzilla a good way to start? In-Reply-To: <9013.1482427538@turing-police.cc.vt.edu> References: <68331482423678@web4j.yandex.ru> <9013.1482427538@turing-police.cc.vt.edu> Message-ID: <2069841482483697@web1o.yandex.ru> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org Thanks for such detailed information. Now I have a subject what I should think about. And yes, I'll chose my own way :) 22.12.2016, 20:26, "valdis.kletnieks at vt.edu" : > On Thu, 22 Dec 2016 19:21:18 +0300, Dennis Semakin said: >> ?I just thought that may be it will be quicker to start to develop for kernel. > > The quickest way to start will depend on why you're thinking of doing > kernel development at all. > > Did your boss just tell you that you have 13 weeks to ship a Linux driver > for your company's new USB widget? > > Do you have a device that Linux doesn't support? > Do you have a device that Linux *claims* to support, but it doesn't work quite right? > Do you have a device that used to work, but broke recently? > > (And yes, the approaches for the 3 are different) > > Do you have a deep desire to do something specific? "Wow, filesystems are > really cool"? "I want to push my laptop to the limits"? Something else? > > Do you just want to give back to the community? If so, skip developing and > just build and run a new linux-next kernel once a week. Lots easier to get > started, and we have plenty of developers - but lots fewer people actually > testing the 600,000 lines of new code every release. And how do I know there's > less testers than developers? Because if we had as many testers, I wouldn't > personally trip over an average of 3 to 5 bugs in linux-next per release cycle. > > Did you think it would be a babe magnet? Or looking for something to put > on your resume? > > All these have different paths.... > > (And here's the quick hint on how to get started with linux-next: > > $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > (the clone created a subdirectory, so cd to it for the following) > $ 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 > ... # later on > $ git remote update > ... > > Once a week, do a 'git remote update' and build/install/run the new kernel. > If anything explodes, send an email to linux-kernel at vger.kernel.org > > And yes, it really *is* that easy.