On Saturday 25 June 2005 13:32, Tim Warnock wrote:
> I realised two things were wrong:
> My image is 256000 bytes decompressed, even though theres only 180mb of
> data on the drive. So I have to specify: ramdisk_blocksize=1024 (at bb's
> recommendation) and ramdisk_size=256000 bytesize of the deco
On Monday 27 June 2005 11:11, Bernhard Schauer wrote:
> > Revert the fork-not-clone patch:
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0506.1/0665.html
>
> Tried to revert the patch, but it did not succeed from 2.6.12 (Woozy
> Numbat).
That patch is not in 2.6.12, it was in the -mm tree
#1 bonehead mistake when running UML:
mount -o loop somefile somedir
su
mount -o loop somefile somedir
umount somedir
linux ubd0=... etc...
If I got a pound for every time I did that...
Of course, I'm not saying that's what's happening
here, but you never know.
-Simon.
--- Attila BODY <[EMA
Hi all,
trying to boot a root image created with debootstrap the boot process
goes fine until virtual console startup
Relevant part of inittab is:
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:
> Trying again 2.6.12.rc4 ...
O.k.
2.6.12-rc4-mm2 with deleted include/asm-um/elf.h and hand edited
arch/um/include/user.h (commented out kfree, in_aton and strlcpy) the
resulting ./linux works as expected ;-)!
Now I'm more relaxed (searching for that nearly a week!) ...
best regards
Bernha
> Revert the fork-not-clone patch:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0506.1/0665.html
>
Tried to revert the patch, but it did not succeed from 2.6.12 (Woozy
Numbat). Maybe I should revert an other patch before (An other solution
would be to put the changes in by hand)?
F
