From: Dan Temple <dant@mips.com>
To: linux-mips@oss.sgi.com
Cc: Ilya Volynets <ilya@theilya.com>
Subject: 2.4 on MIPS FTP site
Date: Thu, 16 Aug 2001 08:45:24 +0200 [thread overview]
Message-ID: <3B7B6C04.A40B009C@mips.com> (raw)
Ilya Volynets writes:
> Do NOT go there. Do NOT look for development tools.
> Port 2.4.x
> I wonder when MIPS will remove that 2.2.12 kit from their site.....
>
as the one responsible for a (small) part of the MIPS website, I am wondering if you are seeing the same as I am! If I go to the Linux page:
http://www.mips.com/devTools/devArea/Linux.html
..it mentions both 2.2.12 and 2.4 kernels, and the link to the FTP site leads to
ftp://ftp.mips.com/pub/linux/mips/
..where you will find both the 2.2 and 2.4 kernels under the kernel/ directory, complete with notes on how we recommend a userland upgrade. It is of course up to the user to choose what they want to do, but from your mail it sounds like you are seeing no 2.4 material on the site at all.
Ilya - If you are seeing somewhere else on the site where the 2.2.12 kernel is hailed as the latest and greatest, please let me know and it will be severely dealt with.
Dan Temple
MIPS Denmark
reply other threads:[~2001-08-16 6:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B7B6C04.A40B009C@mips.com \
--to=dant@mips.com \
--cc=ilya@theilya.com \
--cc=linux-mips@oss.sgi.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