All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: sparclinux@vger.kernel.org
Subject: Re: Can't boot linux on sun blade 2000
Date: Thu, 08 Apr 2004 02:26:57 +0000	[thread overview]
Message-ID: <20040408022657.GG1947@phunnypharm.org> (raw)
In-Reply-To: <200404071043.30060.snake@penza-gsm.ru>

On Wed, Apr 07, 2004 at 01:23:46PM -0700, Joshua Kwan wrote:
> On Wed, Apr 07, 2004 at 03:17:59PM -0400, Ben Collins wrote:
> > > You should really be using the Sarge tftboot images.
> > > http://people.debian.org/~jbailey/d-i/sparc/daily/sparc64/netboot/boot.img
> > 
> > No, he shouldn't those images aren't tested very well. My woody images
> > are.
> 
> You seem to have missed the numerous successful (or mostly so) installation
> reports on both sparc and sparc64 and my hijack (to Debian Install System
> Team) of your mostly broken silo-installer package and serial console fixes,
> all of which contributed to successes with the new Debian installer.
> 
> In short, thanks for undermining our past few months' work.

Thanks for belittling my years of work on the sparc port. I appreciate
that.

> > > Pass devfs=mount on the command line and it should Just Work.
> > > Note that this crude hack isn't required in the latest images.
> > 
> > That shouldn't matter with the image he is using.
> 
> I thought that the images were d-i/sarge based. This was a dominant
> problem until fairly recently (where the hack was to pass devfs=mount on
> the command line.)
> 
> I basically know nothing about boot-floppies on !i386, so I'd not have
> spoken up if I had known.

Great, piping in when you aren't sure of what's going on.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/

  parent reply	other threads:[~2004-04-08  2:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07  6:43 Can't boot linux on sun blade 2000 Alexey Nezhdanov
2004-04-07  6:53 ` Joshua Kwan
2004-04-07 19:17 ` Ben Collins
2004-04-07 19:17 ` Ben Collins
2004-04-07 20:23 ` Joshua Kwan
2004-04-07 21:03 ` Vincent Cojot
2004-04-08  2:26 ` Ben Collins [this message]
2004-04-08  4:07 ` Joshua Kwan
2004-04-08 11:56 ` Vincent Cojot
2004-04-08 12:14 ` Ben Collins
2004-04-08 12:29 ` Alexey Nezhdanov
2004-04-08 18:42 ` David S. Miller
2004-04-08 19:52 ` Vincent Cojot
2004-04-09  4:10 ` Alexey Nezhdanov
2004-04-09  5:03 ` Alexey Nezhdanov
2004-04-09  6:22 ` David S. Miller
2004-04-09  6:37 ` Alexey Nezhdanov
2004-04-09 12:04 ` Ben Collins
2004-04-13  5:09 ` Alexey Nezhdanov
2004-04-13  5:21 ` David S. Miller
2004-04-13  6:04 ` Alexey Nezhdanov
2004-04-14 11:29 ` Ben Collins

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=20040408022657.GG1947@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=sparclinux@vger.kernel.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.