From: Halil Demirezen <halil@debian-tr.org>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: about upgrading the kernel.
Date: Sun, 27 Apr 2003 20:52:23 +0300 [thread overview]
Message-ID: <20030427175223.GA1259@storm.armateknik.com.tr> (raw)
In-Reply-To: <5.1.0.14.1.20030427103023.01f12610@celine>
> As to "any easy way" ... what do you find difficult about doing a kernel
> compile? On my machines, it takes a lot of machine time, but only small bit
Compiling kernel a few times a day to see the effects of the new upgraded kernel is ok for me.
However, doing it 20 times a day is little difficult, isnt it?
never mind. I got the procedure each developer does in doing so.
Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2003-04-27 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 17:20 about upgrading the kernel Halil Demirezen
2003-04-27 17:35 ` Ray Olszewski
2003-04-27 17:52 ` Halil Demirezen [this message]
2003-04-28 16:30 ` Elias Athanasopoulos
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=20030427175223.GA1259@storm.armateknik.com.tr \
--to=halil@debian-tr.org \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/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