All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S.Zick <mszick@pflash.com>
To: Andrew Shugg <andrew@neep.com.au>
Cc: parisc-linux@parisc-linux.org, debian-hppa@lists.debian.org
Subject: [parisc-linux] Re: Version 0.9 of PA-RISC Linux Released
Date: Tue, 5 Jun 2001 07:24:31 -0500	[thread overview]
Message-ID: <01060507541700.00472@wolf01.my.home> (raw)
In-Reply-To: 20010605172316.A12216@neep.com.au

Matthew -

Great idea - both sites should CLEARLY cross-link their information pages=
=2E

My own suggestions:
1) - leave the /devel directory on the CD image until at least
version 12.0.0 of pa-risc.linux.

I am using the kernel snap-shot of 06/03/2001 - in the hopes
that it is close to what was used to build the kernels in V0.9 -
but that is only a guess on my part

2) - don't drop a built kernel into an image of even a pre-release
CD until it compiles error (and warning) free.

Some of the problems I have found and fixed were clearly
mentioned by the compiler.

3) - Note to others trying fix "Old Box" support -

Please use a command line such as:
date >0603_something_cmnd.txt ; \
date >0603_something_errs.txt ; \
make vmlinux (or whatever) >>0603_something_cmnd.txt 2>>0603_something_er=
rs.txt

Then tar-zip the linux/.config, ...cmnd.txt, and the ...errs.txt -
attach to e-mail directed to Mike <mszick@pfash.com>

The more paths through this code taken by the compiler, the faster=20
I should be able to find (and maybe fix) the "Old Box" support.

4) - Note to folks posting the daily kernel snapshots -
4.a) - Please make the "daily snapshots" contain only changed
files from the prior "daily snapshot".
4.b) - Please make a "complete" kernel snapshot only once
a week.
4.c) - Please include the three files mentioned above in
each and every snapshot.

Being able to diff those three files is a big aid in making
progress on these problems.

Mike

On Tue, 05 Jun 2001, Andrew Shugg wrote:
> Matthew Wilcox said:
> > Well, 720 is explicitly mentioned as not yet being supported.
>=20
> I'm not sure who is looking after the debian-hppa web page at
> /ports/hppa/ (glad to see it is being kept up to date though!) but
> perhaps whomever it is could point to the parisc-linux.org hardware
> compatibility page.
>=20
>   http://parisc-linux.org/release-0.9/systems.html
>   http://parisc-linux.org/hardware/supported.html
>=20
> Or perhaps its information could be paraphrased on the debian-hppa page
> for first-time visitors?  eg "for the curious amongst you, the followin=
g
> systems work: xxx, these maybe work yyy, and these definitely don't zzz=
"
>=20
> Andrew.
>=20
> --
> Andrew Shugg <andrew@neep.com.au>                   http://www.neep.com=
=2Eau/
>=20
> "Just remember, Mr Fawlty, there's always someone worse off than yourse=
lf."
> "Is there?  Well I'd like to meet him.  I could do with a good laugh."
>=20
>=20
> -- =20
> To UNSUBSCRIBE, email to debian-hppa-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debi=
an.org

       reply	other threads:[~2001-06-05 12:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010605172316.A12216@neep.com.au>
2001-06-05 12:24 ` Michael S.Zick [this message]
2001-06-05 19:10   ` [parisc-linux] Re: Version 0.9 of PA-RISC Linux Released Matthew Wilcox
2001-06-05 19:16     ` Michael S.Zick
2001-06-05 19:29       ` Matthew Wilcox
2001-06-05 20:22         ` Michael S.Zick
2001-06-05 21:07           ` Matthew Wilcox
2001-06-05 21:16             ` Alan Cox
2001-06-05 21:13           ` Andrew Shugg
2001-06-05 21:18             ` Michael S.Zick
2001-06-05 21:36               ` Andrew Shugg
2001-06-01 14:59 MEYER,ALAN C. (HP-FtCollins,ex1)
  -- strict thread matches above, loose matches on Subject: below --
2001-06-01  9:37 Jayadeep Purushothaman
2001-06-01  3:02 [parisc-linux] " Matt Taggart
2001-06-04  3:38 ` [parisc-linux] " Michael S.Zick

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=01060507541700.00472@wolf01.my.home \
    --to=mszick@pflash.com \
    --cc=andrew@neep.com.au \
    --cc=debian-hppa@lists.debian.org \
    --cc=parisc-linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.