From: Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Kernel versions
Date: Thu, 2 Apr 2009 09:16:51 +0200 [thread overview]
Message-ID: <2d05c4580904020016o44801253p441ff9739aae74da@mail.gmail.com> (raw)
Hello,
I have noticed that when compiling various kernel versions with same
.config file
(this is .config file from generic 2.6.27-7 kernel that works)
on same machine the results are unpredictable :) Sometimes machine just
shuts down during the compilation, and in most cases it won't boot. I am always
downloading kernel sources from official site and I think these are
stable versions.
For example, 2.6.27.7 , 2.6.27.21 etc.
I am compiling kernel and modules with:
make
make modules
make modules_install
make install
and then run in /boot folder
mkinitrd initrd.img-2.6.27.21 2.6.27.21
and modify /boot/grub/menu.lst
So, is there some convention or practice, to know which versions are
stable or do
different distribution have something to do with it ?
thanks,
Dragoslav Zaric
[Professional programmer, MSc in Astrophysics]
next reply other threads:[~2009-04-02 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 7:16 Dragoslav Zaric [this message]
2009-04-02 8:19 Tomasz Chmielewski
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=2d05c4580904020016o44801253p441ff9739aae74da@mail.gmail.com \
--to=dragoslav.zaric.kd@gmail.com \
--cc=gorcunov@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®