Hi, FYI, here's the patch for adding back pre-2.6.26 kernel support and fix some char devices creation as block ones.
Best Regards, Vladislav Grishenko -----Original Message----- From: busybox [mailto:[email protected]] On Behalf Of Rob Landley Sent: Friday, March 31, 2017 4:10 AM To: Peter Korsgaard <[email protected]>; Ralf Friedl <[email protected]> Cc: [email protected] Subject: Re: mdev change no longer supporting v2.6.2x kernels by using /sys/dev On 03/30/2017 02:34 PM, Peter Korsgaard wrote: >>>>>> "Ralf" == Ralf Friedl <[email protected]> writes: > > Hi, > >>> /sys/dev support got added in 2.6.27-rc1 (July 2008), E.G. ~9 years ago: > > > Busybox is often used in embedded devices, where kernels (and other > > software) are not changed that often. Firmware may contain kernel > > modules without full source, so a change to a newer kernel is not an > > option. As an example, I have a router with kernel 2.6.13. I can't > > update the kernel, but I can replace the busybox with a newer > version > (and much more applets) than the original. > > True, but generally you will run into a number of issues when you > combine SW components of significant different "age". E.G. lots of > modern user space requires new kernel features, either explicitly or > simply because nobody has tested it on such old systems. My old rule of thumb back in the day was trying to support 7 year old build and deployment environments: http://lists.busybox.net/pipermail/busybox/2006-September/058440.html This is 2 years beyond that. Just FYI, Rob _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
0001-busybox-mdev-recover-pre-2.6.26-kernel-support.patch
Description: Binary data
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
