From: khandelw@cs.fsu.edu
To: karim@opersys.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.4.16
Date: Sat, 3 Apr 2004 16:00:49 -0500 [thread overview]
Message-ID: <1081026049.f64d5288b5aaa@system.cs.fsu.edu> (raw)
In-Reply-To: <406F21CB.8070908@opersys.com>
The Patches/ directory of LTT is empty. Do I need to download the patches from
somewhere else? The installation of LTT suggests that we need to patch the
kernel.
Thanks in advance.
Amit
Quoting Karim Yaghmour <karim@opersys.com>:
>
> khandelw@cs.fsu.edu wrote:
> > I had few issues related to compiling 2.6.3 on redhat 9.0. I have got
> that up
> > and running except for the (networking)eth0 support. I see Ltt 0.9.6pre2
> and
> > not pre3 on the site am I missing sm thing??
>
> Right, I just didn't have time to put up the tradition HTML pointers on
> the project's site. You'll 0.9.6pre3 here:
> http://www.opersys.com/ftp/pub/LTT/
>
> Karim
> --
> Author, Speaker, Developer, Consultant
> Pushing Embedded and Real-Time Linux Systems Beyond the Limits
> http://www.opersys.com || karim@opersys.com || 1-866-677-4546
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
>
next prev parent reply other threads:[~2004-04-03 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 20:03 kernel 2.4.16 khandelw
2004-04-01 20:21 ` Karim Yaghmour
2004-04-01 20:31 ` Karim Yaghmour
2004-04-03 17:13 ` khandelw
2004-04-03 20:42 ` Karim Yaghmour
2004-04-03 21:00 ` khandelw [this message]
2004-04-03 21:10 ` Karim Yaghmour
2004-04-03 23:07 ` Amit
2004-04-03 23:23 ` Karim Yaghmour
2004-04-03 23:42 ` Amit
2004-04-03 23:59 ` Karim Yaghmour
2004-04-04 14:42 ` Amit
2004-04-05 20:04 ` Karim Yaghmour
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=1081026049.f64d5288b5aaa@system.cs.fsu.edu \
--to=khandelw@cs.fsu.edu \
--cc=karim@opersys.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