Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1380 - Provide method of "replacing" busybox to obtain non-distro functionality #6337

Closed
openwrt-bot opened this issue Feb 21, 2018 · 2 comments
Labels

Comments

@openwrt-bot
Copy link

jeffsf:

The busybox package is compiled in the pre-built images without functionality needed by some users, for example "ip tunnel".

While a user can compile a local version of the busybox package, there is no straightforward way of installing it on a running system. Apparently opkg required busybox to complete installation of a replacement package so that it cannot be "removed" and then the new version installed.

Without manual manipulation of the package, it appears that a complete re-flash is required. This is "dangerous" as booting into failsafe without a functional busybox may not allow recovery.

At least as I understood the filesystem, it should be possible to recognize that it is busybox being installed and perform something like the following:

  • Identify all symlinks installed in the flashed image to busybox
  • Identify all symlinks about to be installed by the "new" busybox from the package
  • Create a list of "removed" links by comparing the above results
  • Install busybox to the overlay
  • Update the overlay to "delete" the list of "removed" links

Assuming that the "new" busybox doesn't lack the functionality required for opkg, there shouldn't be a point in time where there is a "broken" busybox in the process.

Additionally, the flash will continue to have an operational "stock"busybox available for failsafe mode.

To be "super safe" it may be appropriate to install the busybox binary in a different location on the overlay, then mv/"relink" it into place.

@openwrt-bot
Copy link
Author

jeffsf:

See also FS#1381 which requests enabling the ip_tunnel and ip_neighhbor configuration for busybox

@openwrt-bot
Copy link
Author

jow-:

Installing full version of packages ("e.g. ip-tiny or ip-full) is usually preferred over reinstalling busybox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant