Re: Won't startup after 2.1 upgrade


Subject: Re: Won't startup after 2.1 upgrade
From: Marc Stergionis (stermarc@home.com)
Date: Tue Nov 13 2001 - 15:05:32 MST


Sometime around 3:27 PM -0500 on 11/12/01, Bo Brinkman pounded out this ditty:
>Hi again Marc. I sometimes do something that breaks X: If you have
>another machine so you can ssh (or telnet) into your 8100, and then
>do "/sbin/telinit 3" which will tell the system to go to runlevel 3,
>the text-only runlevel. I believe the boot-time default runlevel is
>stored in inittab, and looks like this:
>
>id:5:initdefault:
>
>If you change the 5 to a 3, you should now be put into text mode
>when you reboot.
>
>Another option, if you can't log in remotely, is to use the "single"
>boot option to boot linux, and then make the change to your inittab
>and reboot. I'm not sure what boot loader you use, but for NuBus
>machines I use the MkLinux booter. In the MkLinux booter, you need
>to edit your lilo.conf and add a mach_options= "single" line.
>
>Also, I don't know if I told you before: tuxppc.org (the
>imaclinux.net, powermaclinux.net, etc people) have added a nubus
>section (nubus.tuxppc.org) and a NuBus forum. I am the maintainer,
>and I'm trying to figure out what content we need, so let me know if
>you have suggestions.

I tried the "single" boot option to mach_options. That didn't seem
to change anything. I also tried just mach_options= single (where
single had no quotes). Again, no change.

 From My OSX machine, I tried telnet -- and got this:

setenv TERM
;telnet -l root 192.168.1.13;exit;
[localhost:~] marcster% setenv TERM
[localhost:~] marcster% ;telnet -l root 192.168.1.13;exit;
Trying 192.168.1.13...
telnet: Unable to connect to remote host: Operation timed out
logout
[Process completed]

Then I tried ssh1:

setenv TERM
;ssh -l root 192.168.1.13;exit;
[localhost:~] marcster% setenv TERM
[localhost:~] marcster% ;ssh -l root 192.168.1.13;exit;

and SSH2:

setenv TERM
;ssh -2 -l root 192.168.1.13;exit;
[localhost:~] marcster% setenv TERM
[localhost:~] marcster% ;ssh -2 -l root 192.168.1.13;exit;
Secure connection to 192.168.1.13 refused.
logout
[Process completed]

I'm just putting in the "IP" on my network that my OSX Cube sees, ie.
afp://192.168.1.16 (without the "afp://") This is all while the clone
is upstairs looping between the text login and attempts to start X.
That *is* the "server" I'm trying to telnet to isn't it?

Maybe I'll try "single" again in the MkLinux booter with quotes....

-ms

-- 
Many have Montana envy ... the lucky get to live here!
Marc Stergionis
Community Relations & website author
Benefis Healthcare -- http://www.benefis.org
"Opinions expressed are not necessarily those of my employer"



This archive was generated by hypermail 2a24 : Tue Nov 13 2001 - 15:16:40 MST