Bug#50048: libg++2.8.2-dev: empty package on sparc

1999-11-13 Thread Matthias Klose
There is a bug against ftp.debian.org to remove egcs (and
libg++2.8.2-dev) from potato. The current libg++, which works with
gcc-2.95 ist libg++2.8.1.3. Are there problems, that gcc-2.95 does not 
correctly work on sparc?

Is this really a grave bug for sparc?

Madarasz Gergely writes:
  Package: libg++2.8.2-dev
  Version: 2.91.66-2
  Severity: grave
  
  [EMAIL PROTECTED]:/var/cache/apt/archives$ dpkg -c
  libg++2.8.2-dev_2.91.66-2_sparc.deb
  drwxr-xr-x root/root 0 1999-06-03 16:34:56 ./
  drwxr-xr-x root/root 0 1999-06-03 16:32:35 usr/
  drwxr-xr-x root/root 0 1999-06-03 16:32:29 usr/doc/
  drwxr-xr-x root/root 0 1999-06-03 16:33:10 usr/doc/libg++2.8.2/
  -rw-r--r-- root/root  9475 1998-08-31 12:56:33 
  usr/doc/libg++2.8.2/NEWS.gz
  lrwxrwxrwx root/root 0 1999-06-03 16:32:29 usr/doc/libg++2.8.2-dev 
  - libg++2.8.2
  
  
  -- System Information
  Debian Release: potato
  Kernel Version: Linux debella 2.2.13 #17 SMP Tue Nov 9 18:17:19 CET 1999 
  sparc unknown
  
  Versions of the packages libg++2.8.2-dev depends on:
  ii  libg++2.8.2 2.91.66-3  The GNU C++ extension library - old 
  runtime 


Re: Bug#50048: libg++2.8.2-dev: empty package on sparc

1999-11-13 Thread Ben Collins
On Sat, Nov 13, 1999 at 11:02:32AM +0100, Matthias Klose wrote:
 There is a bug against ftp.debian.org to remove egcs (and
 libg++2.8.2-dev) from potato. The current libg++, which works with
 gcc-2.95 ist libg++2.8.1.3. Are there problems, that gcc-2.95 does not 
 correctly work on sparc?
 
 Is this really a grave bug for sparc?

Gcc 2.95 works perfectly on sparc afaik. I'll check into the empty package
though.

Ben

 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
` [EMAIL PROTECTED]  -  [EMAIL PROTECTED]  -  [EMAIL PROTECTED]'
 `---=--===-=-=-=-===-==---=--=---'


Spacr linux: bug in autofs and nis

1999-11-13 Thread Dinh-Tuan . Pham
   Hi,
   I just upgrade a sparc linux system to the lastest potato
version. Now autofs no longer works. In fact the installation fail
with this mesage:

Setting up autofs (3.1.3-2) ...
/etc/init.d/autofs: line 198: syntax error near unexpected token `|'
dpkg: error processing autofs (--configure):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 autofs

   On the other hand, nis no longer hangs at installation (it is
ypbind which hangs actually) but it still dosen't works. ypcat
passwd yields this message:

No such map passwd.byname. Reason: Can't bind to server which serves
this domain

I have also try to ypwhich and get

ypwhich: Can't communicate with ypbind

I also try to put explicitly the name of ny nis server in the file
/etc/yp.conf, but to no avail

I have waited for almost one year now to see if nis ever
works. Actually I have planned to convert some of Solaris machine to
Linux, but this has been put off. I just have a small machine (SUN
IPC) to spare just to see if Linux ever works right.

-- 
PHAM Dinh Tuan | e-mail: [EMAIL PROTECTED]
Laboratoire de Modelisation et Calcul  | Tel: +33 4 76 51 44 23
BP 53, 38041 Grenoble cedex 9 (France) | Fax: +33 4 76 63 12 63
---


Re: Spacr linux: bug in autofs and nis

1999-11-13 Thread Ben Collins
On Sat, Nov 13, 1999 at 07:34:02PM +0100, [EMAIL PROTECTED] wrote:
   I have waited for almost one year now to see if nis ever
 works. Actually I have planned to convert some of Solaris machine to
 Linux, but this has been put off. I just have a small machine (SUN
 IPC) to spare just to see if Linux ever works right.

I don't know about autofs since I don't use it. But I admin a set of 3
sparc linux servers which are using NIS/NFS. The NIS master is running on
a Sparc LX, running Debian/Slink, kernel 2.2.9 (it is also a client). The
two clients are UltraSparc's running Debian/Potato, kernel 2.2.13.

Looks to me from the error that you are having a configuration problem. Is
this NIS master you are pointing to a Solaris one? If so what version of
Solaris, and what type of system.

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
` [EMAIL PROTECTED]  -  [EMAIL PROTECTED]  -  [EMAIL PROTECTED]'
 `---=--===-=-=-=-===-==---=--=---'


Re: Sparc linux: bug in autofs and nis

1999-11-13 Thread Paul Vojta
 Date: Sat, 13 Nov 1999 19:34:02 +0100 (CET)
 To: debian-sparc@lists.debian.org
 Subject: Spacr linux: bug in autofs and nis
 From: [EMAIL PROTECTED]

Hi,
I just upgrade a sparc linux system to the lastest potato
 version. Now autofs no longer works. In fact the installation fail
 with this mesage:

 Setting up autofs (3.1.3-2) ...
 /etc/init.d/autofs: line 198: syntax error near unexpected token `|'
 dpkg: error processing autofs (--configure):
  subprocess post-installation script returned error exit status 2
 Errors were encountered while processing:
  autofs

The maintainer of autofs seems to be asleep at the switch.  I submitted
a bug report, with patch, 39 days ago, but have seen no response from him.
See Debian bug #46638.

--Paul Vojta, [EMAIL PROTECTED]


Update: serial console on Sparc IPX

1999-11-13 Thread ferret

It turns out that the 'mac printer' cable does the crossover already. I
connected a second null-modem adapter inline with my cable and did get
serial output from the IPX.

I'm posting the entire output below. Unfortunately at this point it
doesn't seem to respond to input from the serial port (I'm running minicom
on the Lintel end of things)

What keycode do I need to send to the IPX to get the openprom to break for
me, being L1-S obviously can't be sent over?

Am I reading the selftest messages correctly and thinking it wants parity
memory and it's erroring because it has non-parity?

-- Ferret no baka


Power-Up State Test 
Context Register Bit Test 
Context Register Addressing Test 
Segment Map RAM MATS Pattern Test, Context  
Segment Map RAM MATS Pattern Test, Context 0001 
Segment Map RAM MATS Pattern Test, Context 0002 
Segment Map RAM MATS Pattern Test, Context 0003 
Segment Map RAM MATS Pattern Test, Context 0004 
Segment Map RAM MATS Pattern Test, Context 0005 
Segment Map RAM MATS Pattern Test, Context 0006 
Segment Map RAM MATS Pattern Test, Context 0007 
Page Map RAM MATS Pattern Test 
Limit 0 Register Test 
Counter Interrupt Level 10 Test 
Limit 1 Register Test 
Counter Interrupt Level 14 Test 
WARNING: Unable to determine keyboard type
Synchronous Error Reg Test 
Synchronous Error Virtual Address Reg Test 
Asynchronous Error Reg Test 
Asynchronous Error Virtual Address Reg Test 
Asynchronous Error Data Reg1 Test 
Asynchronous Error Data Reg2 Test 
System Enable Register Bit Test 
Cache Data RAM MATS Pattern Test 
Cache Tag RAM MATS Pattern Test 
PTE Access Bit Test 
PTE Modify Bit Test 
PTE Write-Protect Bit Test 
PTE Write-Invalid Bit Test 
PTE Read-Invalid Bit Test 
PTE Type 2 Space Bit Test 
PTE Type 3 Space Bit Test 
Synchronous Timeout Test 
Asynchronous Timeout Test 
 16 MegaBytes Found in Address Range 0x to 0x00ff 
DRAM Word MATS Pattern Test (0x00fe - 0x0100) 
Parity/Memory Control Registers Bit Test 
33-bit SIMM Parity Test 
FAILURE: No Trap Taken, Exp Trap Type = 0009
Setting Segment Map
Setting RAM Parity Mode
Mode set to 33-bit
Sizing Memory
Mapping ROM
Mapping RAM
Probing /[EMAIL PROTECTED],f800 at 0,0  dma esp sd st le 
Probing /[EMAIL PROTECTED],f800 at 1,0  Nothing there
Probing /[EMAIL PROTECTED],f800 at 2,0  Nothing there
Probing /[EMAIL PROTECTED],f800 at 3,0  cgsix 
Probing /[EMAIL PROTECTED],f800 at 0,0  dma esp sd st le 
Probing /[EMAIL PROTECTED],f800 at 1,0  Nothing there
Probing /[EMAIL PROTECTED],f800 at 2,0  Nothing there
Probing /[EMAIL PROTECTED],f800 at 3,0  cgsix 

SPARCstation IPX, No Keyboard
ROM Rev. 2.6, 16 MB memory installed, Serial #2165154.
Ethernet address 8:0:20:c:dc:80, Host ID: 572109a2.



Power-On SelfTest FAILED ... Replace CPU Board

Testing   16 megs of memory   16  15  14  13  12  11  
10   9   8   7   6   5   4   3   2   1  
 0  
SBus slot 0 le esp dma 
SBus slot 1 
SBus slot 2 
SBus slot 3 cgsix 

Initializing  16 megs of memory at addr 0  15  14  13  
12  11  10   9   8   7   6   5   4   3  
 2   1   0  

Type b (boot), c (continue), or n (new command mode)