Seeking busybox guidance
Posted: 07 Nov 2021, 11:18
I frequently compile and run the default config of the latest Busybox - but only at a user-level. Porteus' devel module makes that super easy to compile.
So no problem as a user (putting busybox and it's symbolic links in a directory in front of my path - the usual stuff.)
BUT, I'd like to take it further to see if I can start replacing things on a system-wide level without breaking things too much.
So I'm wondering what would you suggest as a system plan for a busybox test? Replacing the gnu file utils one by one and seeing what breaks, or perhaps making an entire module to load first?
I kind of have the itch to see if I can make a "busybox'ed" version of Porteus, but as you can see, I'm more likely to break it and end in tears. As a user-level thing, no sweat. But wholesale replacement? I'm scared....
So no problem as a user (putting busybox and it's symbolic links in a directory in front of my path - the usual stuff.)
BUT, I'd like to take it further to see if I can start replacing things on a system-wide level without breaking things too much.
So I'm wondering what would you suggest as a system plan for a busybox test? Replacing the gnu file utils one by one and seeing what breaks, or perhaps making an entire module to load first?
I kind of have the itch to see if I can make a "busybox'ed" version of Porteus, but as you can see, I'm more likely to break it and end in tears. As a user-level thing, no sweat. But wholesale replacement? I'm scared....