NetBSD Problem Report #13507

Received: (qmail 23053 invoked from network); 18 Jul 2001 21:46:46 -0000
Message-Id: <20010718215004.5A1801110F@www.netbsd.org>
Date: Wed, 18 Jul 2001 14:50:04 -0700 (PDT)
From: maxunder@choisyclub.org
Sender: nobody@netbsd.org
Reply-To: maxunder@choisyclub.org
To: gnats-bugs@gnats.netbsd.org
Subject: Unable to use ifconfig from the miniroot
X-Send-Pr-Version: www-1.0

>Number:         13507
>Category:       port-mvme68k
>Synopsis:       Unable to use ifconfig from the miniroot
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    port-mvme68k-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 18 21:47:01 +0000 2001
>Closed-Date:    Fri Sep 21 18:33:58 +0000 2001
>Last-Modified:  Fri Sep 21 18:33:58 +0000 2001
>Originator:     Kurkdjian
>Release:        1.5.1
>Organization:
ChoisyClub
>Environment:
>Description:
It seems that the binary of 'ifconfig' just core dump.
>How-To-Repeat:
boot from the installation miniroot, chose shell, type ifconfig on shell prompt.
>Fix:

>Release-Note:
>Audit-Trail:

From: Martin Husemann <martin@duskware.de>
To: maxunder@choisyclub.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-mvme68k/13507: Unable to use ifconfig from the miniroot
Date: Thu, 19 Jul 2001 00:00:29 +0200 (MEST)

 > boot from the installation miniroot, chose shell, type ifconfig on shell prompt.

 Interesting. We just found out "ifconfig" in sparc64 miniroots does not work
 either. Not sure if this is related, though.

 Martin

From: Steve Woodford <scw@netbsd.org>
To: <maxunder@choisyclub.org>
Cc: <gnats-bugs@netbsd.org>
Subject: Re: port-mvme68k/13507: Unable to use ifconfig from the miniroot
Date: Thu, 19 Jul 2001 23:08:20 +0100 (BST)

 Can you try the miniroot in:

 	ftp://ftp.netbsd.org/pub/NetBSD/misc/scw/mvme68k-miniroot

 and let me know if it works please?

 Cheers, Steve




From: David Brownlee <abs@formula1.com>
To: <maxunder@choisyclub.org>
Cc: <gnats-bugs@gnats.netbsd.org>, <sparc64@netbsd.org>
Subject: Re: port-mvme68k/13507: Unable to use ifconfig from the miniroot
Date: Fri, 20 Jul 2001 16:48:41 +0100 (BST)

 	The ifconfig in the sparc64 miniroot seems to have some issues
 	too (addresses always reported as 0.0.0.0) - maybe this is
 	related?

 -- 
 		David/absolute		abs@formula1.com

 On Wed, 18 Jul 2001 maxunder@choisyclub.org wrote:

 >
 > >Number:         13507
 > >Category:       port-mvme68k
 > >Synopsis:       Unable to use ifconfig from the miniroot
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       low
 > >Responsible:    port-mvme68k-maintainer
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Wed Jul 18 14:47:01 PDT 2001
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Kurkdjian
 > >Release:        1.5.1
 > >Organization:
 > ChoisyClub
 > >Environment:
 > >Description:
 > It seems that the binary of 'ifconfig' just core dump.
 > >How-To-Repeat:
 > boot from the installation miniroot, chose shell, type ifconfig on shell prompt.
 > >Fix:
 >
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 >


From: Steve Woodford <scw@netbsd.org>
To: David Brownlee <abs@formula1.com>
Cc: <gnats-bugs@netbsd.org>
Subject: Re: port-mvme68k/13507: Unable to use ifconfig from the miniroot
Date: Fri, 20 Jul 2001 19:32:42 +0100 (BST)

 On 20 Jul 2001, David Brownlee wrote:

 >  	The ifconfig in the sparc64 miniroot seems to have some issues
 >  	too (addresses always reported as 0.0.0.0) - maybe this is
 >  	related?

 I doubt the problems are related. mvme68k's miniroot simply got corrupted
 somehow before it was uploaded to ftp.netbsd.org.

 Cheers, Steve


State-Changed-From-To: open->closed 
State-Changed-By: scw 
State-Changed-When: Sat Jul 21 21:16:57 BST 2001 
State-Changed-Why:  
Corrupted miniroot on ftp.netbsd.org replaced by working one. 
State-Changed-From-To: closed->open 
State-Changed-By: jhawk 
State-Changed-When: Sat Jul 21 14:41:53 PDT 2001 
State-Changed-Why:  
The old miniroot on ftp.netbsd.org is back. It is not acceptable 
to change the release binaries after the release. We need to work 
out a better solution. 
State-Changed-From-To: open->analyzed 
State-Changed-By: jhawk 
State-Changed-When: Sat Jul 21 14:42:40 PDT 2001 
State-Changed-Why:  
We have thought about this problem (a little bit) 
State-Changed-From-To: analyzed->closed 
State-Changed-By: scw 
State-Changed-When: Fri Sep 21 19:32:56 BST 2001 
State-Changed-Why:  

This PR can be closed now that the faulty 1.5.1 mvme68k release has 
been superceded by 1.5.2. 

>Unformatted:

Home	PR Database Search