Re: [uml-user] Can't get <ctrl c> to work on /dev/console on home made root_fs

[Jeff D. <jd...@ka...>]

rw...@ea... said:
> I can make stty -a show the same on both by running this on the
> non-working one: stty kill '^x' -cread clocal ignpar -ixoff ixany
> ofdel echoprt
> <ctrl c> behavior didn't change though. 

Hmmm, beats the shit out of me then...

> > Use 'con=pts' instead, then.
> When I use con=pts from inside X or from console, the last thing the
> uml boot process shows is: Initializing stdio console driver 

Well, yeah, you told it to put all the consoles on pts devices, including
the main console.  What you have to do is log in somehow, look at the boot
log to figure out what host device the main console got attached to, and use
kermit or minicom or something to attach to it.

> The ls command below prints nothing when UML is booted with:
> eth0=tuntap,,,192.168.0.231 con0=tty:/dev/tty24 root=/dev/ubd0
> ls -l /proc/*/fd | grep tty24  	 

Hmmm, is there anything in the UML boot log about not being able to open
the device?  (And you did change the permissions so that you can open it,
right?)

> The  slack filesystem wants to be fsck'd, and fsck -y -v /dev/ubd/0
> and fsck -y -v -b 8193 /dev/ubd/0 return an error.

That sounds like something that needs fixing...

> ioctl(3, 0x4b33, 0x5ffff8e7)            = -1 EINVAL (Invalid argument)
> ioctl(3, 0x4b33, 0x5ffff8e7)            = -1 EINVAL (Invalid argument)

I wonder what ioctl that is...

				Jeff