Re: [uml-devel] Respawning too fast - 2.6.13-bs2

2005-10-07 Thread Etay Meiri
> INIT: Id "0" respawning too fast: disabled for 5 minutes> INIT: no more processes left in this runlevel >> I did play with it earlier (updated a few rpms and configured nfs) but> I'm not sure which of my steps caused this.> Any idea how to debug it?Problems like this come usually from:b) messing

Re: [uml-devel] 2.6.13-bs3 amd64 compilation broken?

2005-10-07 Thread Blaisorblade
On Friday 07 October 2005 15:45, Alan Menegotto wrote: > Antoine Martin wrote: > >I tried twice to be sure, but compile fails near the end: > > > > CC arch/um/sys-x86_64/stub_segv.o > >arch/um/sys-x86_64/stub_segv.c: In function `stub_segv_handler': > >arch/um/sys-x86_64/stub_segv.c:41: warnin

[uml-devel] 2.6.13-bs3 amd64 compilation broken?

2005-10-07 Thread Alan Menegotto
Antoine Martin wrote: I tried twice to be sure, but compile fails near the end: CC arch/um/sys-x86_64/stub_segv.o arch/um/sys-x86_64/stub_segv.c: In function `stub_segv_handler': arch/um/sys-x86_64/stub_segv.c:41: warning: implicit declaration of function `container_of' arch/um/sys-x86_64/

Re: [uml-devel] Respawning too fast - 2.6.13-bs2

2005-10-07 Thread Blaisorblade
On Friday 07 October 2005 15:43, Etay Meiri wrote: > Hi, > > I'm suddenly unable to boot my 2.6.13-bs2 based uml system. > Getting the following errors at the end: > > Starting anacron: [ OK ] > Starting atd: [ OK ] > Starting system message bus: [ OK ] > Starting HAL daemon: [ OK ] > INIT: Id "0"

Re: [uml-devel] echo 0 > /proc/sysemu == failed to wait at end of syscall

2005-10-07 Thread Blaisorblade
On Thursday 06 October 2005 21:58, Christopher S. Aker wrote: > Blaisorblade wrote: > > On Thursday 06 October 2005 08:08, Christopher S. Aker wrote: > > >2.6.13.3-um > > Which host, and which guest mode (SKAS0 vs. SKAS3)? > 2.6.7 with the skas patch right before the strace bug was fixed (like, >

[uml-devel] 2.6.13-bs3 amd64 compilation broken?

2005-10-07 Thread Antoine Martin
I tried twice to be sure, but compile fails near the end: CC arch/um/sys-x86_64/stub_segv.o arch/um/sys-x86_64/stub_segv.c: In function `stub_segv_handler': arch/um/sys-x86_64/stub_segv.c:41: warning: implicit declaration of function `container_of' arch/um/sys-x86_64/stub_segv.c:41: error: p

[uml-devel] Respawning too fast - 2.6.13-bs2

2005-10-07 Thread Etay Meiri
Hi, I'm suddenly unable to boot my 2.6.13-bs2 based uml system. Getting the following errors at the end: Starting anacron: [  OK  ] Starting atd: [  OK  ] Starting system message bus: [  OK  ] Starting HAL daemon: [  OK  ] INIT: Id "0" respawning too fast: disabled for 5 minutes INIT: no more pro

[uml-devel] Prove to others you have made it big with our reproduction chronometers.

2005-10-07 Thread scott pray
More than 1500 eye catching chronometers, all from major manufacturers. Each and every one of our wristwatches make perfect Christmas presents and come with included presentation boxes. Why own an average watch when you can pay for a real reproduction? Our store's eye catching reproductions are

Re: [uml-devel] RPM problem in UML rootfs of FC4

2005-10-07 Thread Etay Meiri
On 10/7/05, itamar <[EMAIL PROTECTED]> wrote: first try this   rm -rf /var/lib/rpm/__* rpm --rebuilddb EtayM: this one wasn't enough. if don´t fix the problem try this         echo "%__dbi_cdb  create cdb private mpool mp_mmapsize=16Mb" > /etc/rpm/macros EtayM: this one worked. rpm -qa  

Re: [uml-devel] RPM problem in UML rootfs of FC4

2005-10-07 Thread itamar
first try this   rm -rf /var/lib/rpm/__* rpm --rebuilddb   if don´t fix the problem try this         echo "%__dbi_cdb  create cdb private mpool mp_mmapsize=16Mb" > /etc/rpm/macros   rpm -qa   upgrade your FC4 using yum and remove the line "%__dbi_cdb  create cdb private mpool mp_mmapsize=16Mb

[uml-devel] RPM problem in UML rootfs of FC4

2005-10-07 Thread Etay Meiri
Hi, Was anyone successful in getting rpm running in the FC4 root fs from: http://uml.harlowhill.com/index.php/UML_Fedora_Core_4    ? I followed all the instructions, UML is working fine but all rpm invocations cause the following error: [EMAIL PROTECTED] ~]# rpm -qa rpmdb: unable to initialize mu