On Wed, Aug 23, 2006 at 12:24:19AM -0700, Mathew Brown wrote:
> Sorry to bring this issue up again, but I was wondering if there was
> some wiki that could be updated to reflect things such at the TT
> issue? I'm sure that I'm not the only one that ran into this. If
> there is one, I woul
Hi,
Sorry to bring this issue up again, but I was wondering if there was
some wiki that could be updated to reflect things such at the TT
issue? I'm sure that I'm not the only one that ran into this. If
there is one, I wouldn't mind updating parts myself (with my limited
knowledge) :D
On Sun, Aug 20, 2006 at 12:08:50PM +0200, Blaisorblade wrote:
> Jeff, could you add to the "Tracing Thread mode" the (OBSOLETE) / (DEPRECATED
> mark so that users won't enable it?
Yeah, that's a good idea.
Jeff
-
On Sunday 20 August 2006 15:21, Mathew Brown wrote:
> Hi,
> If you mean by statically linked, CONFIG_STATIC_LINK=y
Yes.
> , I tried it
> with 2.6.17-9 and it worked fine. Here's a diff between the .config
> file that I used for static linking (without TT) and when I tried to
> use TT (.
Hi,
If you mean by statically linked, CONFIG_STATIC_LINK=y, I tried it
with 2.6.17-9 and it worked fine. Here's a diff between the .config
file that I used for static linking (without TT) and when I tried to
use TT (.configwithttthatsegfaults). If you'd like, I can send you
the actual .
On Sunday 20 August 2006 11:37, Mathew Brown wrote:
> Hi,
> I think I solved it. I also think that I found a bug. Here's what I
> did and why I think it's a bug:
>
> I thought the problem might be related to 2.6.17-9 so I downloaded
> 2.6.16 and compiled it. It's behavior was different b
Hi,
I think I solved it. I also think that I found a bug. Here's what I
did and why I think it's a bug:
I thought the problem might be related to 2.6.17-9 so I downloaded
2.6.16 and compiled it. It's behavior was different but it still
wouldn't boot. It would give me the following:
Thanks. I added stderr=1 to the kernel line and it gives me the
following:
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Kernel panic - not syncing: Segfault with no mm
<6>Stopping all CPUs...done
EIP: 00
On Sat, Aug 19, 2006 at 11:58:44AM -0700, Mathew Brown wrote:
> Checking that ptrace can change system call numbers...OK
> Checking syscall emulation patch for ptrace...OK
> Checking advanced syscall emulation patch for ptrace...OK
> Checking for tmpfs mount on /dev/shm...OK
> Checking PROT_EXEC mm
Thanks. I downloaded the latest stable kernel (2.6.17-9) and enabled
most options (I build in everything inside the kernel instead of
modules). However, when I tried running it, it would give me the
following and then exit:
Checking that ptrace can change system call numbers...OK
Checking syscal
On Friday 18 August 2006 21:34, Mathew Brown wrote:
> Hi,
> I'm currently using the 2.6.17-rc1 UML kernel provided at
> http://user-mode-linux.sourceforge.net/new/ However, when attempting
> to use iptables:
>
> iptables -L
>
> I get the following error: iptables v1.2.11: can't initialize i
Hi,
I'm currently using the 2.6.17-rc1 UML kernel provided at
http://user-mode-linux.sourceforge.net/new/ However, when attempting
to use iptables:
iptables -L
I get the following error: iptables v1.2.11: can't initialize iptables
table `filter': iptables who? (do you need to insmod?)
An
12 matches
Mail list logo
