From: Grant Grundler <grundler@parisc-linux.org>
To: dub@latnet.lv
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: can't compile 2.4.24: pdc_cons.o problem!
Date: Sat, 21 Feb 2004 17:52:41 -0700 [thread overview]
Message-ID: <20040222005241.GA30849@colo.lackof.org> (raw)
In-Reply-To: <1077183184.403482d04a190@clients.latnet.lv>
On Thu, Feb 19, 2004 at 11:33:04AM +0200, dub@latnet.lv wrote:
> BTW, it's not possible to navigate to
> http://cvs.parisc-linux.org/download/ from http://cvs.parisc-linux.org/
I think that's ok. It's just convient to build the kernels
on the same machine that's hosting CVS. It's not obvious to
me a link from cvs.p-l.o is needed since we have a link from
the www.p-l.org navigation bar.
www.p-l.o has a "Prebuilt binaries" in the navigation bar.
And from there, a link to the cvs.p-l.o/download/autobuild-kernels/.
I'll add links for linux-2.4 and linux-2.6 kernel downloads.
> How to find out status of pasisc-linux.org kernels? (stable vs testing)
Normally, follow the conversations on parisc-linux mailing list.
I don't know how useful bugs.debian.org is for kernel packages.
"stable" hppa kernel is horridly stale (kernel-image-2.4.18*).
Because of security bugs, folks should be using at least 2.4.24.
(2.4.25 is the lastest available, not).
2.6 kernels seem to be working well for me (except for SMP).
But it looks like the most recent debian upload was 2.4.21 based.
I see that http://cvs.parisc-linux.org/downloads/autobuild-kernels/32/
has a Packages.gz. But I don't know how the sources.list entry needs
to look for apt-get to find it.
hth,
grant
next prev parent reply other threads:[~2004-02-22 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 9:33 [parisc-linux] Re: can't compile 2.4.24: pdc_cons.o problem! dub
2004-02-22 0:52 ` Grant Grundler [this message]
2004-02-22 1:20 ` Matthew Wilcox
2004-02-22 6:51 ` Grant Grundler
2004-02-23 3:24 ` Grant Grundler
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=20040222005241.GA30849@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=dub@latnet.lv \
--cc=parisc-linux@lists.parisc-linux.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