Alpha arch development list
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Frank Scheiner <frank.scheiner@web.de>,
	debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org,
	mcree@orcon.net.nz
Subject: Re: [alpha] Debian 9.0 NETINST fails
Date: Wed, 21 Nov 2018 14:53:30 -0600	[thread overview]
Message-ID: <20181121205330.GA19204@gherkin.frus.com> (raw)
In-Reply-To: <847ee7b7-29fa-c1ec-fd1d-610ddad190d9@physik.fu-berlin.de>

On Wed, Nov 07, 2018 at 04:12:27PM +0100, John Paul Adrian Glaubitz wrote:
> I can unfortunately not build updated installer images for Alpha since I
> don't have an Alpha porterbox available where I can build the debian-installer
> package for Alpha.
> 
> I do have two AlphaStation 233 sitting in the basement at the university now,
> but I don't have any time and space to set them up to be used as porterboxes.
> 
> The only porterbox currently currently available to me is Michael Cree's "electro"
> but the repositories of the chroots there don't include the debian-installer
> component packages, so building d-i fails - at least last time I tried.

I've carved out a bit of time to deal with getting my PWS back on-line.
The above is the most recent post in the thread, as far as I can tell...

Michael -- is it a relatively easy thing to do to make the d-i component
packages available on "electro"?

Another option: is the SMP version of the 4.9.0-3 kernel available to
substitute into the existing netinst image?  Unless I'm missing something,
rebuilding the ISO with that substitution appears to be a simple task
(assuming the existing initrd image for the generic kernel can be used).
I *did* see further postings indicating that, while the SMP kernel *did*
boot where the generic one wouldn't, there were other issues encountered
subsequent to booting.

I have not yet tried a prior netinst image, so there's a window of
opportunity here are far as me being a willing/motivated tester of the
installer if a working one can be cobbled together.  After all, I'm
currently sitting at the "worst case scenario" state and would lose
nothing but a bit of time by trying a new installer :-).  For that
matter, if "the community" thinks a better thing to do would be to try
out the Gentoo installer, I think I could get to the desired end state
via that route as well.

Opinions welcome.

--Bob


  reply	other threads:[~2018-11-21 20:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 18:41 [alpha] Debian 9.0 NETINST fails Bob Tracy
2018-11-02 18:56 ` Bob Tracy
2018-11-06 12:36   ` Frank Scheiner
2018-11-07 15:08     ` Bob Tracy
2018-11-07 15:12     ` John Paul Adrian Glaubitz
2018-11-21 20:53       ` Bob Tracy [this message]
2018-11-22  5:34         ` Michael Cree
2018-11-22  7:58           ` Helge Deller
2018-11-22  8:34             ` John Paul Adrian Glaubitz
2018-11-23 19:41               ` Bob Tracy
2018-11-23 19:57                 ` John Paul Adrian Glaubitz
2018-11-23 20:07                 ` Michael Cree
2018-11-24 21:57                   ` Bob Tracy

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=20181121205330.GA19204@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=debian-alpha@lists.debian.org \
    --cc=frank.scheiner@web.de \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mcree@orcon.net.nz \
    /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