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

busybox: bump package to v1.28.1 #2504

Merged
merged 1 commit into from
Feb 27, 2018
Merged

busybox: bump package to v1.28.1 #2504

merged 1 commit into from
Feb 27, 2018

Conversation

spycat88
Copy link
Contributor

As the title says...

Patches updated to reflect the bump.

In regards to the config changes, I have left these as the default answers during build time.

@MilhouseVH
Copy link
Contributor

Do we need CONFIG_RUN_INIT=y in host and target?

//config:config RUN_INIT
//config:       bool "run-init"
//config:       default y
//config:       select PLATFORM_LINUX
//config:       help
//config:       The run-init utility is used from initramfs to select a new
//config:       root device. Under initramfs, you have to use this instead of
//config:       pivot_root.
//config:
//config:       Booting with initramfs extracts a gzipped cpio archive into rootfs
//config:       (which is a variant of ramfs/tmpfs). Because rootfs can't be moved
//config:       or unmounted, pivot_root will not work from initramfs. Instead,
//config:       run-init deletes everything out of rootfs (including itself),
//config:       does a mount --move that overmounts rootfs with the new root, and
//config:       then execs the specified init program.
//config:
//config:       util-linux has a similar tool, switch-root.
//config:       run-init differs by also having a "-d CAPS_TO_DROP" option.

We use switch_root in init.

@MilhouseVH
Copy link
Contributor

This PR adds CONFIG_FEATURE_CROND_SPECIAL_TIMES=y which should be added as a new sed here whenever CRON is not configured (arguably not required, but for the sake of completeness...).

Also, I'm not sure we need the following for host:

CONFIG_HEXEDIT=y
CONFIG_NUKE=y
CONFIG_RESUME=y
CONFIG_SETFATTR=y

In order:
HEXEDIT: Ability to hexedit a file
NUKE: nuke utility, equivalent to rm -fr
RESUME: resume from "suspend-to-disk" image
SETFATTR: set/delete extended attributes on files

None of these seem particularly useful for the host config (so we just waste time building them).

@spycat88
Copy link
Contributor Author

Updated

@MilhouseVH
Copy link
Contributor

Thanks.

Copy link
Contributor

@MilhouseVH MilhouseVH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, so far no issues...

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

Successfully merging this pull request may close these issues.

None yet

3 participants