Hi all,
A bit more debugging information. Gdb shows that ./linux segfaults
at the same location in os_early_checks () at arch/um/os-Linux/start_up.c:264
no matter CONFIG_HOST_2G_2G is defined or not. Any clue how to fix?
See my earlier email below for my kernel settings. Thanks for your help.
Hi all,
Puzzled and need some help.
I downloaded the stock linux-2.6.14.3.tar.bz2, and
tried to make ARCH=um on RedHat's Enterprise Linux 4 update 2. And the output segfaults immediately.
My procedures are as follows:
1) cd linux-2.6.14.3
2) make menuconfig ARCH=um
2a) enable CONFIG_HOST_2
On Mon, Dec 12, 2005 at 09:25:04PM +0100, Blaisorblade wrote:
> On Monday 12 December 2005 08:20, Matthew Palmer wrote:
> > I'm running into problems booting UMLs at present, with a regular (though
> > not 100% consistent) hang at the point where the root filesystem is
> > mounted.
>
> > line_ioct
On Monday 12 December 2005 14:20, Blaisorblade wrote:
> First, you can say con1=fd:0,fd:1 instead to redirect tty1 to stdin/out,
> however you just need to add an entry in inittab for tty0 along with tty1
> and list tty0 in /etc/*securetty* (path varies) to allow root to login from
> tty0. Don't us
Sorry, I sent the wrong bridging interface. Here is the output from my
"public" bridge:
~# brctl show
bridge name bridge id STP enabled interfaces
br2 8000.00e0815a0ebc no apache-prod
eth0
Are you setup to forward IP packets on the host? Something like:
~$ cat /proc/sys/net/ipv4/conf/all/forwarding
1
~$
This assumes that you're using your host as a gateway. Alternatively, is
br0 connected to a physical device? For example:
~# brctl show
bridge name bridge id STP
Hello,
I'm usually pretty good at finding answers on my own, but I've only been
able to find information in regard to private UML networks and NAT etc.
I have some UMLs that are unable to access the network beyond the host.
Here is the scenario:
(Sorry about the "999", I'm using routable IPs)
H
On Monday 12 December 2005 08:20, Matthew Palmer wrote:
> I'm running into problems booting UMLs at present, with a regular (though
> not 100% consistent) hang at the point where the root filesystem is
> mounted.
> line_ioctl: tty0: ioctl KDSIGACCEPT called
(Ignore that, it's a harmless warning).
On Sunday 11 December 2005 22:08, Julius Schwartzenberg wrote:
> Hi,
> Thanks again for your messages!
>
> Blaisorblade wrote:
> >>I do not have X11 on my server. I also tried it with the DISPLAY
> >>environent pointing to my workstation's X11 server, but I got another
> >>error then.
> >
> > Test
