Le Fri, 7 Mar 2008 12:06:08 -0500,
Jeff Dike <jdike@...> a écrit :
> On Thu, Mar 06, 2008 at 09:42:13PM -0500, lanas wrote:
> > OK, a bit of context. I'm starting the UML inside a small LFS
> > system running in text mode under VmWare. I just tried running the
> > same UML on Fedora and voilà, a xterm appears, ahem, "magically",
> > when run under a X server.
> > So I guess the stock LFS inittab I use produces these graphical
> > xterms and thus, must run under X. I'll have to then see how the
> > others UML are doing it to have a console prompt instead of an
> > xterm.
> What the UML console driver is trying to do is run an xterm on the
> *host*, where you have no $DISPLAY. If you want your consoles in
> xterms, then give it a DISPLAY. If not, then see the consoles
> section of
> The only thing the UML inittab does is control how many consoles are
> activated. It does nothing to control how they are attached to the
Well, I've tried with:
linux-LFS ubda=rootfs-LFS-1 con0=fd:0
But the xterm is still popping up.
The LFS system has no $DISPLAY variable defined when it boots straight
from the machine, and has none when run as UML (even though the xterm
Comparing with a fs and UML kernel obtained from the internet
(FedoraCore6-AMD64-root_fs), the Fedora fs is launched without any
other parameter than ubd0:
But manages to have the UML console inside the terminal where the UML
was launched. No xterm. I've built the linux-LFS UML kernel with 'make
defconfig ARCH=um' while the other kernel is one of the available
kernels from the internet. So perhaps other kernel parameters have to be
configured to permit text console interfaces.
The other difference I've seen is that inittab in the KFA uses agetty
and in Fedora mingetty.
0:2345:respawn:/sbin/agetty tty1 38400
It's nice to start from scratch like this because then I will learn
about all the details that are taken for granted when running available
UML kernels and filesystems.