| Author |
Message |
jpeddicord
Joined: 19 Jan 2008
Posts: 9
|
| Posted: Tue Feb 19, 2008 9:13 pm Post subject: Lish borked? |
|
|
| It worked on UML, but I never tried it on Xen since I moved. It *works* in terms of rebooting and the like, but you can't screen into a terminal to sign in. You get the console log and everything, but the logon never shows. Is this just me, or is this just a funky bug in Xen? :P |
|
| Back to top |
|
caker
Joined: 15 Apr 2003
Posts: 2371
Location: Galloway, NJ
|
| Posted: Tue Feb 19, 2008 9:20 pm Post subject: |
|
|
It's most likely that you don't have a getty listening on tty1. UML wanted tty0, so one of the "filesystem helpers" we set up for Xen is supposed to make the required change to /etc/inttab for you automatically.
Are you running /sbin/init or the upstart thing in recent Ubuntu?
For an init setup, simply edit /etc/inittab and make sure a getty is listening on tty1. The other getty lines can be commented out. "init q" to apply the changes.
-Chris |
|
| Back to top |
|
jpeddicord
Joined: 19 Jan 2008
Posts: 9
|
| Posted: Wed Feb 20, 2008 10:25 am Post subject: |
|
|
| I'm running Upstart, which would probably be why. Working on starting getty on tty1. Thanks! |
|
| Back to top |
|
jpeddicord
Joined: 19 Jan 2008
Posts: 9
|
| Posted: Wed Feb 20, 2008 4:38 pm Post subject: |
|
|
For those wondering, I created a new Upstart job by copying the tty0 job:
Code: # tty1 - getty
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
stop on shutdown
respawn
exec /sbin/getty 38400 tty1
Save that as /etc/event.d/tty1 and then activate it to avoid restarting:
Code: sudo start tty1 |
|
| Back to top |
|
| |
