BusyBox

NeddySeagoon · Posted: Fri Mar 24, 2017 9:34 pm Post subject:

Tony0945,

USE=static isn't set anywhere by default. It leads to update nightmares and bloated binaries, as all required libraries are built into the binaries.
Its a terrible idea to set it globally.

In its place, (like the initrd) and for a rescue shell, USE=static is useful. I have

Tony0945 · Posted: Fri Mar 24, 2017 10:12 pm Post subject:

NeddySeagoon,

I understand what the flag does and the danger of setting it globally. i just don't understand why portage is putting the flag on busybox because I don't have it in make.conf and I don't have it in package.use (probably should) and it isn't marked with a + in IUSE.

BTW, I don't use an intrd and have firmware in the kernel.

NeddySeagoon · Posted: Fri Mar 24, 2017 10:35 pm Post subject:

Tony0945,

My setup is a hybrid. The kernel can boot alone, if it wasn't for the fact that root is on LVM inside a raid5.
The initrd contains mdadm, lvm and busybox, all build statically, oh, and an init script.
There are no kernel modules. Its like a piece of firmware, once it works, it never changes.

Like grub, there is no need to update it, since its not a potential attack surface unless the attacker has physical access.
Then I have a lot more to worry about than my PC.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

fcl · Tux's lil' helper Joined: 31 Dec 2016 Posts: 77

Tony0945, it's enabled by the linux profile

Tony0945 · Posted: Sat Mar 25, 2017 12:03 am Post subject:

Ah! I see. I forgot the profile sets flags too.

khayyam · Posted: Sat Mar 25, 2017 8:32 am Post subject: