Your message dated Mon, 11 Oct 2004 12:14:32 +0100
with message-id <[EMAIL PROTECTED]>
and subject line 
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Oct 2004 08:12:27 +0000
>From [EMAIL PROTECTED] Sun Oct 10 01:12:27 2004
Return-path: <[EMAIL PROTECTED]>
Received: from host217-35-105-99.in-addr.btopenworld.com (mail.redbricks.org.uk) 
[217.35.105.99] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CGYoc-0002PP-00; Sun, 10 Oct 2004 01:12:26 -0700
Received: from melognome (wormhole.redbricks.org.uk [192.168.1.4])
        by mail.redbricks.org.uk (8.12.8/8.11.1) with ESMTP id i9AABmXg005798
        for <[EMAIL PROTECTED]>; Sun, 10 Oct 2004 11:11:48 +0100
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Sun, 10 Oct 2004 09:11:06 +0100
MIME-Version: 1.0
Subject: sparc32 vmlinuz mis-labelled sparc64 in d-i pre-rc2 boot.img
Message-ID: <[EMAIL PROTECTED]>
Priority: normal
X-mailer: Pegasus Mail for Windows (4.21c)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.4 required=4.0 tests=BAYES_00,HAS_PACKAGE,
        NO_REAL_NAME autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: install
Version: pre-rc2

I am using debian-installer pre-rc2 on a Sun Ultra 1 Workstation Model 170 (A11) using 
a 
boot floppy image boot.img from here:
http://people.debian.org/~joshk/d-i/images/2004-09-29/sparc32/floppy/
and here:
http://people.debian.org/~joshk/d-i/images/2004-09-29/sparc32/floppy/2.6/

>From what I understand this should have automatically tried to load the 
>vmlinuz-sparc32 
image but instead it automatically fails trying vmlinuz-sparc64 (it says something 
like "cannot 
find vmlinuz-sparc64 (unknown ROMFS error)" and stops).

I can manually type 'boot=/vmlinuz-sparc32' and it succesfully finds it and tries to 
unpack it 
(tho, an unrelated problem, it fails to fully unpack it, presumably bcos I wrote the 
disk on i386 
when the Sparc wants the disk written on a Sun m/c).

I have the same problem with both 2.4 and 2.6 kernel boot floppy images

p


---------------------------------------
Received: (at 275784-done) by bugs.debian.org; 11 Oct 2004 11:15:53 +0000
>From [EMAIL PROTECTED] Mon Oct 11 04:15:53 2004
Return-path: <[EMAIL PROTECTED]>
Received: from host217-35-105-99.in-addr.btopenworld.com (mail.redbricks.org.uk) 
[217.35.105.99] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CGy9g-00026v-00; Mon, 11 Oct 2004 04:15:52 -0700
Received: from melognome (wormhole.redbricks.org.uk [192.168.1.4])
        by mail.redbricks.org.uk (8.12.8/8.11.1) with ESMTP id i9BDFGXg015794
        for <[EMAIL PROTECTED]>; Mon, 11 Oct 2004 14:15:17 +0100
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Mon, 11 Oct 2004 12:14:32 +0100
MIME-Version: 1.0
Subject: 
Message-ID: <[EMAIL PROTECTED]>
Priority: normal
X-mailer: Pegasus Mail for Windows (4.21c)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-1.4 required=4.0 tests=BAYES_00,NO_REAL_NAME 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

my fault. I misunderstood my machine's architecture


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to