From: Matthew Wilcox <willy@debian.org>
To: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Users staying up to date.
Date: Wed, 15 Aug 2001 01:00:34 +0100 [thread overview]
Message-ID: <20010815010034.K22144@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20010814154037.I25258@megatonmonkey.net>; from carlos@baldric.uwo.ca on Tue, Aug 14, 2001 at 03:40:37PM -0400
On Tue, Aug 14, 2001 at 03:40:37PM -0400, Carlos O'Donell Jr. wrote:
> Obviously the latest kernel/glibc/gcc... will reside in the
> CVS. It's a matter of slurping/building and testing on one
> of our boxen.
Actually, the debian glibc package has more uptodate bits than our CVS tree.
> The packages are a slightly different matter. Is the 0.9.2
> iso the latest collection of packages? Is anyone in debain-hppa
> compiling/testing packages?
we're compiling packages constantly. we have a lack of testing though,
which is what we rely on people like you for :-)
> Instead we have used the baseplus tar from sid to install the nodes.
> The only extra packages we required were NIS(yp*) and MPICH(1.2.1).
We seem to have those compiled already in debian...
> I recently found though, that when compiling more complicated
> MPI programs, cc and ld start dropping SIG11's like there was
> no tommorow (more on this after I do some testing).
OK, I'd be interested to see more detail once we're sure you're on
an uptodate system.
> We were doing:
> 1- Unpack sid baseplus root tarball
> 2- x-compiled and installed NIS(yp*) and MPICH
> 3- Use this as my new root tarball for the rest of the cluster
>
> Should I be doing:
>
> 1- Unpack sid baseplus and export via nfs
> 2- Download latest debs and export via nfs
> 3- Boot "clone" box with nfs root
> 4- Point apt to the debs on the nfs share
> 5- Update packages like mad
> 6- Use "clone" as my new root tarball for the rest of the cluster
You should be doing:
Run debian installer to completion on one machine
apt-get dist-upgrade
apt-get install nis mpich
tar up / and copy it to all other machines
If the latest debian installer (never mind what's on the CDs) doesn't
work, then please report the problems.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-08-15 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 19:40 [parisc-linux] Users staying up to date Carlos O'Donell Jr.
2001-08-14 19:46 ` Bdale Garbee
2001-08-14 23:27 ` Matt Taggart
2001-08-15 0:00 ` Matthew Wilcox [this message]
2001-08-15 1:50 ` Carlos O'Donell Jr.
2001-08-15 3:16 ` Matthew Wilcox
2001-08-15 3:37 ` [parisc-linux] Users staying up to late. ;) Carlos O'Donell Jr.
2001-08-17 19:53 ` [parisc-linux] Users staying up to date Carlos O'Donell Jr.
2001-08-27 23:07 ` Richard Hirst
2001-08-28 4:22 ` Carlos O'Donell Jr.
2001-08-28 14:34 ` Richard Hirst
2001-08-28 15:14 ` Matt Taggart
2001-08-28 15:40 ` Carlos O'Donell Jr.
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=20010815010034.K22144@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=carlos@baldric.uwo.ca \
--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