Date: Fri, 04 Dec 1998 06:26:41 +0000 From: curtis <ufkartfm@pacific.net> To: Jim King <jim.king@mail.sstar.com> Cc: "freebsd-alpha@FreeBSD.ORG" <freebsd-alpha@FreeBSD.ORG> Subject: Re: Multia - now booting from hard disk - flag problem Message-ID: <366780A1.E7D98D0@pacific.net> References: <199812040639.AAA11885@oasis.zycor.lgc.com>
index | next in thread | previous in thread | raw e-mail
Good Morning Jim,
Thank you! (blush - chuckle) It never occurred to me, to try telneting
to the Multia (Wavy tells me this is due to chromosome amnesia from the
'60s - snicker) and needless to say, it worked.
$ telnet 192.168.1.19
Trying 192.168.1.19...
Connected to 192.168.1.19.
Escape character is '^]'.
FreeBSD/alpha (multia.alienbabies.org) (ttyp1)
login: ufkartfm
Password:
Last login: Fri Dec 4 13:35:12 from 192.168.1.5
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 3.0-19981128-SNAP (alienbabies) #1: Fri Dec 4 05:29:02 GMT 1998
$ su
multia#
On the P2 minicom (where I boot the Multia from and under the date where
I thought it was hung) I am getting (smile) abbreviated messages (like a
normal root window) in the form of a capital letter D when I 'su' under
telnet; example follows (I have four 'su' telnet sessions running):
Local package initialization:.
starting local daemons:.
Fri Dec 4 13:32:40 GMT 1998 <---- where I thought it was hanging
DDDD <---- appear when I su from telnet
so it looks like some information is making back to the boot window.
Very Best2u, curtis
Jim King wrote:
>
> At 10:26 PM 12/3/98 +0000, curtis wrote:
> >I finally have it booting from the hard disk (smile) and
> >disklabel -B -b /usr/mdec/boot1 /dev/da0c works for me.
> >
> >The new problem only occurs when I do: >>>boot dka0 -flags a or
> >>>>boot dka0 and enter ^D at the prompt which results in a 'hang'
> >at the date.
> >
> [deleted]
> >Local package initialization:.
> >starting local daemons:.
> >Fri Dec 4 05:38:08 GMT 1998
> >[this is where it hangs]
>
> My AlphaStation 200 does this also, but it's not actually hung. The serial
> console is unresponsive, but I can telnet to it from another box and
> everything works fine. I don't have a boot.conf - I was wondering if there
> needs to be some command in there, or maybe something /etc/ttys.
> Unfortunately I haven't had time to chase this down...
>
> Jim
--
curtis - ufkartfm@pacific.net - site administrator for Nobody
I want Nobody to control my life! How about you?
http://www.netvideo.com/nobody
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?366780A1.E7D98D0>