x27;t seem to work quite right.
> i suspect my issue is that multipath wants a bunch of info from udev
> which i don't have since it's busybox.
... I think what you need instead is dmsetup, maintained within LVM2, to
create the /dev/mapper nodes for multipathd.
[1]: https:/
be able to verify that or to fix it.
Yes, I believe the copy of libarchive in BusyBox is affected.
The file that defines the vulnerable function is only built if
CONFIG_LZOP is enabled, so disabling that (if enabled) is a temporary
way to avoid the overflow issue.
--
Patrick "P. J." Mc
; + docs/busybox.pod
> .kernelrelease Module.symvers tags TAGS cscope* \
> busybox_old
You need to escape the newline characters in the added lines with "\".
With that fix, the patch looks fine to me for what that's worth.
stem.
Anyone running BusyBox uname on a non-BusyBox system can easily patch
coreutils/uname.c to change the output of `uname -o`.
I suggest that "BusyBox/Linux" be the "default" otherwise. Perhaps this
could be added as an option to Kconfig to obviate a patch.
--
Patrick "
NU/Linux"
and BusyBox uname won't be able to call it "BusyBox/Linux", because it
actually won't be either. That doesn't contradict me at all.
--
Patrick "P. J." McDermott
http://www.pehjota.net/
Lead Developer, ProteanOS
http://www.proteanos.com/
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
- strcpy(uname_info.os, "GNU/Linux");
+ strcpy(uname_info.os, "BusyBox/Linux");
--
Patrick "P. J." McDermott
http://www.pehjota.net/
Lead Developer, ProteanOS
http://www.proteanos.com/
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
