On Tue, Feb 09, 1999 at 07:39:53AM -0900, Hogland, Thomas E. wrote:
> Interesting problem - I've upgraded to slink as part of kernel 2.2.1 on two
> different PC's, and I think I goofed on one. When the new X stuff went in
> and asked if I should use my current config files, the PC at work was told
On Tue, Feb 09, 1999 at 07:39:53AM -0900, Hogland, Thomas E. wrote:
> Interesting problem - I've upgraded to slink as part of kernel 2.2.1 on
> two different PC's, and I think I goofed on one. When the new X stuff went
> in and asked if I should use my current config files, the PC at work was
> to
"Hogland, Thomas E." wrote:
>
> Interesting - if I can ever figure out how to get into the system I'll do
> that :-) There's no way to shut down and reboot clean - xdm won't do
> anything till you log in ...
>
>
I was having the same problem. I was able to do a "++F1" to
get to the console. Try
Sergey V Kovalyov <[EMAIL PROTECTED]> writes:
| How about just pressing Ctrl-Alt-F1 and login through the text console ?
| AFAIK, you problem is a known bug - missing ;; in the /etc/X11/Xsession.
| Hopefully it will get fixed soon.
|
| Sergey.
|
| On Tue, 9 Feb 1999, Hogland, Thomas E. wrote:
|
How about just pressing Ctrl-Alt-F1 and login through the text console ?
AFAIK, you problem is a known bug - missing ;; in the /etc/X11/Xsession.
Hopefully it will get fixed soon.
Sergey.
On Tue, 9 Feb 1999, Hogland, Thomas E. wrote:
> Interesting problem - I've upgraded to slink as part of kern
wo
on a mistake I made ...
> --
> From: Mitch Blevins[SMTP:[EMAIL PROTECTED]
> Reply To: Mitch Blevins
> Sent: Tuesday, February 09, 1999 8:45 AM
> To: Hogland, Thomas E.
> Cc: debian-user@lists.debian.org
> Subject: Re: Slink, xbase-comm
Hogland, Thomas E. wrote:
> Interesting - if I can ever figure out how to get into the system I'll do
> that :-) There's no way to shut down and reboot clean - xdm won't do
> anything till you log in ...
Can't you just -- to another console?
-Mitch
Hmmm... I'll have to try the ^R and see if it works first. That'd just be
too convenient...
> > Interesting - if I can ever figure out how to get into the system I'll
> > do that :-) There's no way to shut down and reboot clean - xdm won't
> > do anything till you log in ...
>
> You could boot
Hogland, Thomas E. wrote:
>
> Interesting - if I can ever figure out how to get into the system I'll
> do that :-) There's no way to shut down and reboot clean - xdm won't
> do anything till you log in ...
You could boot into single user mode to modify your settings.
When lilo comes up, type "l
Thanks - this is the other piece of the puzzle...
> At the Lilo: prompt, type:
> linux single
>
> or whatever your linux image is named if it's not linux. that'll put
> you in
> single-user mode and won' start xdm. then do:
> chmod a-x /usr/X11R6/bin/xdm
> so that xdm won't start at all. re
At the Lilo: prompt, type:
linux single
or whatever your linux image is named if it's not linux. that'll put
you in
single-user mode and won' start xdm. then do:
chmod a-x /usr/X11R6/bin/xdm
so that xdm won't start at all. reboot and you'll be in normal mode
without
xdm running so that you ca
Interesting - if I can ever figure out how to get into the system I'll do
that :-) There's no way to shut down and reboot clean - xdm won't do
anything till you log in ...
Now I'm wondering if maybe my work PC's boot disk will work... I wish I had
known about this bug (or the "no - don't fool with
Interesting problem - I've upgraded to slink as part of kernel 2.2.1 on two
different PC's, and I think I goofed on one. When the new X stuff went in
and asked if I should use my current config files, the PC at work was told
No - leave mine alone; the PC at home was told Yes - overwrite with new
on
13 matches
Mail list logo
