mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akula2 <akula2.shark@gmail.com>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Jumping into Kernel development: About -rc kernels...
Date: Wed, 10 Jan 2007 02:34:52 +0530	[thread overview]
Message-ID: <8355959a0701091304g3efc0051o71466d871d5494e7@mail.gmail.com> (raw)
In-Reply-To: <9a8748490701090749u3fc503f3vb05a7063bf40c120@mail.gmail.com>

On 1/9/07, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> Depends on what you want to do.  If you want a stable kernel to use in
> production you should probably pick the latest stable kernel

I am a Linux user/developer in all my IT career which began in 1997.
But always my goal to be a kernel developer and a contributor after
getting hardened. But my career didn't allow me to do this LKML work
except regular reading (frequent change of projects & skills in
Telecom/Embedded). Since last year am with Big B (don't want to name
my company here. Because many people on this list are from the same
company, might get offended because of my novice questions. Or, They
might see me as a silly guy!)

But my interest reached to impossible level to hold anymore. From now
on I want to be an active contributer among this great community :)

Sorry for this big rant. These kernels I test would be for my
Workstations/Embedded  boards (ARM & Power) at my home & my Labs
(example ThinkCentre A51). Not for any production Servers as of now.

> (currently that's 2.6.19.1).

I did start involving with LKML & posted a few too. But, I didn't get
any pointer from you guys.

http://lkml.org/lkml/2007/1/4/228
http://lkml.org/lkml/2007/1/5/74

Maybe I did something naive or stupid in the effort above or in the
posting here. Dunno!


> If you want to help fix bugs, develop features, test etc, then it is
> usually best to use the latest development snapshot available.  An
> easy way to always have the tip of the tree available is to use git -
> see this document for more info : http://linux.yyz.us/git-howto.html

Just now compiled 2.6.20-rc4 too.  So I have already started the
effort, here is we go:-

[sukhoi@Typhoon linux-2.6.20-rc4]$ ll /boot/
total 13004
-rw-r--r-- 1 root root   70195 Dec 16 04:22 config-2.6.18-1.2868.fc6
drwxr-xr-x 2 root root    4096 Jan 10 02:15 grub
-rw------- 1 root root 1519417 Dec 26 19:35 initrd-2.6.18-1.2868.fc6.img
-rw------- 1 root root 1391180 Jan  9 23:12 initrd-2.6.19.1-Topol-M.img
-rw------- 1 root root 1383782 Jan 10 02:15 initrd-2.6.20-rc4.img
-rw-r--r-- 1 root root   94600 Jul 13 10:44 memtest86+-1.65
-rw-r--r-- 1 root root   95025 Dec 16 04:23 symvers-2.6.18-1.2868.fc6.gz
lrwxrwxrwx 1 root root      21 Jan 10 02:14 System.map -> System.map-2.6.20-rc4
-rw-r--r-- 1 root root  887701 Dec 16 04:22 System.map-2.6.18-1.2868.fc6
-rw-r--r-- 1 root root  965328 Jan  9 23:11 System.map-2.6.19.1-Topol-M
-rw-r--r-- 1 root root  957961 Jan 10 02:14 System.map-2.6.20-rc4
lrwxrwxrwx 1 root root      18 Jan 10 02:14 vmlinuz -> vmlinuz-2.6.20-rc4
-rw-r--r-- 1 root root 1816959 Dec 16 04:22 vmlinuz-2.6.18-1.2868.fc6
-rw-r--r-- 1 root root 2036631 Jan  9 23:11 vmlinuz-2.6.19.1-Topol-M
-rw-r--r-- 1 root root 1993172 Jan 10 02:14 vmlinuz-2.6.20-rc4


> Jesper Juhl <jesper.juhl@gmail.com>

Thanks,
~Akula2

  reply	other threads:[~2007-01-09 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 15:33 Akula2
2007-01-09 15:49 ` Jesper Juhl
2007-01-09 21:04   ` Akula2 [this message]
2007-01-09 16:23 ` Horst H. von Brand
2007-01-09 18:08 ` Stefan Richter
     [not found] <20070110150051.63974.qmail@web15914.mail.cnb.yahoo.com>
2007-01-10 18:07 ` Stefan Richter
2007-01-10 20:05   ` Paolo Ornati

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=8355959a0701091304g3efc0051o71466d871d5494e7@mail.gmail.com \
    --to=akula2.shark@gmail.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®