From: Jeffrey Young <jyoung82@carolina.rr.com> Date: Sat, 19 May 2001 22:02:04 -0400 Message-ID: <m19egt8duh0lflulv93h4g9s605ai4rrgp@4ax.com> Subject: Re: [suse-sparc] Netra problem with login
>Get network access, by means of a cross cable or so.
I set up "eth0" on the sparc with ip 192.168.0.1 and connected it to my intel
Linux pc via a cross connect cable. I then tried to telnet into the sparc.
Telnet responds "machine unreachable"....Any ideas?
>Otherwise boot from the CD and mount the file system.
>Check that /dev/null is a DEVICE and not a regular file.
Could you describe how I could do this? Since I can't get a "login", how can I
check /dev/null? How can I mount the file system given the circumstances?
Thanks,
Jeff
>If it is a regular file, remove it and recreate the device as described in
>the man page.
>This worked for me (had the same symptoms, plus some curses about a
>read-only fs)
>
>Hope this helps,
>
>Peter.
>
>----- Original Message -----
>From: "Jeffrey Young" <jyoung82@carolina.rr.com>
>To: <suse-sparc@suse.com>
>Sent: Saturday, May 19, 2001 4:33 PM
>Subject: Re: [suse-sparc] Netra problem with login
>
>
>> I rebooted again (apart from YAST's automatic reboot after the install)
>but the
>> same thing occurs...Also, I have no network access to the machine at this
>> time....
>>
>> Jeff
>>
>>
>> >On Sat, May 19, Jeffrey Young wrote:
>> >
>> >> Almost there on the Netra t1 105.....
>> >>
>> >> I've got Linux on the machine and YAST has rebooted......However, when
>the
>> >> system enters runlevel 3 and the 'login:' prompt is about to appear, I
>get the
>> >> following message:
>> >>
>> >> INIT: Id "1" respawning too fast: disabled for 5 minutes
>> >> INIT: Id "2" respawning too fast: disabled for 5 minutes
>> >> INIT: Id "3" respawning too fast: disabled for 5 minutes
>> >> INIT: Id "4" respawning too fast: disabled for 5 minutes
>> >> INIT: Id "5" respawning too fast: disabled for 5 minutes
>> >> INIT: Id "6" respawning too fast: disabled for 5 minutes
>> >>
>> >> This repeats every 5 minutes. I know this problem is caused by my
>/etc/inittab
>> >> file but I can't get into the system to edit the file. The is a
>headless box
>> >> accessed through the serial port so I assume from the posts I've been
>reading
>> >> that the Rescue Disk is not an option.....
>> >
>> >Do you have network access to the box ? (telnet, ssh, rlogin, ... )
>> >If you have installed over serial console with YaST2 or YaST, you
>> >only need to reboot. There is a bug that sometimes the init process
>> >does not see that /etc/inittab is changed and that it should spawn
>> >an getty on the serial line.
>> >
>> > Thorsten
>>
>>
>>
This archive was generated by hypermail 2.1.0 : Wed Jun 06 2001 - 11:09:14 PDT