All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aaron St. Pierre" <asp@ungod.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] B132L: Success and thanks!
Date: Thu, 6 Feb 2003 08:14:51 -0500	[thread overview]
Message-ID: <20030206131451.GB5012@hadron> (raw)
In-Reply-To: <20030206130003.GB22480@lug-owl.de>

I have a J2240 and was able to dist-upgrade to sid without a problem. I
am still battling with being able to boot a custom built kernel, but I
haven't noticed any problems when running the stock kernel and unstable
distribution. 

It has been suggested to keep a version of gcc-3.0 around (gcc-3.2 gets
installed w/ sid ) and perhaps use that to build your kernels. 
I am not sure is this is a requirement any longer. 

aaron 

In another life Jan-Benedict Glaw wrote:

> Hi!
> 
> These days, I got a B132L, downloaded some ISO image from a near debian
> mirror and booted the box (after reading the palo boot howto:-)
> 
> Well, installing a HPPA box seems to be nothing harder than installing
> any other alpha/mips(el)/... . So: Thanks for all the nice work!
> 
> Another question remains for me: is it currently "safe" to dist-upgrade
> woody -> sid? Or are there some servere breakages? I do use sid on quite
> a number of boxes (with no problems), but there might be hppa specific
> pitfalls...
> 
> MfG, JBG
> 
> -- 
>    Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
>    "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur
>     fuer einen Freien Staat voll Freier B?rger" | im Internet!
>    Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/



-- 
Aaron St. Pierre			tel: 978.828.6177
asp@ungod.com

 If it's worth doing, it's worth doing for money.

  reply	other threads:[~2003-02-06 13:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 13:00 [parisc-linux] B132L: Success and thanks! Jan-Benedict Glaw
2003-02-06 13:14 ` Aaron St. Pierre [this message]
2003-02-06 15:37   ` John David Anglin
2003-02-06 15:49     ` Matthew Wilcox
2003-02-06 16:12       ` Joel Soete
2003-02-06 15:59     ` Aaron St. Pierre

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=20030206131451.GB5012@hadron \
    --to=asp@ungod.com \
    --cc=jbglaw@lug-owl.de \
    --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 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.