Busybox 1.21.0 f2fs-patch

I have applied the 'f2fs' patch to Busybox 1.21.0 source, and compiled statically in the Aboriginal Linux root filesystem. Both for i486 and armv6.

The patched source is in my sources repo:
http://bkhome.org/sources/alphabetical/b/

The two static 'busybox' binaries are in Woof.

Woof commit:
http://bkhome.org/fossil/woof2.cgi/info/2b4f30bc23


Posted on 17 Feb 2013, 24:40


Comments:

Posted on 18 Feb 2013, 5:49 by 01micko
bb and kmod
Any idea if this fixes busybox depmod for kmod depmod?


Posted on 18 Feb 2013, 8:07 by BarryK
Re bb and kmod
I had a bit of a hunt around in BB git commmits, couldn't see anything about kmod fixes.



Posted on 19 Feb 2013, 8:50 by BarryK
Re kmod
Just a thought about kmod.

Ubuntu Precise Pangolin is still using module-init-tools.
I think that the move to kmod is being made in the upcoming 13.04, Raring Ringtail.

But, that doesn't mean we have to change, does it?

For continued compatibility with Busybox, we can stay with module-init-tools, until BB catches up.



Posted on 19 Feb 2013, 9:12 by 01micko
re re kmod
I'll consider compiling module-init-tools for the next slacko beta.

The problem though is with upgrading, say from 5.3.3 to 5.4 (slacko). I put an advisory on the slack14 website I maintain and it is reported as working. I know upgrading isn't the best way to use puppy, but it is supported and the reason I went with kmod is for future upgrading reasons.

Note that debian wheezy (and raspbian) are on kmod too.


Posted on 19 Feb 2013, 14:06 by pemasu
module-init-tools instead
I swapped kmod and udev to the Barry`s udev-167 and module-init-tools pets in Dpup Wheezy. Been using them now with several builds. Kernel module drivers seems to load ok. And no need for /run directory.
I havent tried to compile them in Dpup Wheezy since they have worked adequately....and I havent ever compiled udev, also Barry has stripped his version a lot.