Re: Will bin-sbin-merge migrate existing systems?
John Mellor <[email protected]>
| Newsgroups | gmane.linux.redhat.fedora.testers |
|---|---|
| Message-ID | <[email protected]> |
On 2025-01-23 5:32 p.m., Samuel Sieb wrote: > On 1/23/25 2:17 PM, John Mellor wrote: >> >> On 2025-01-23 2:51 p.m., Adam Williamson wrote: >>> On Thu, 2025-01-23 at 06:00 +0000, George R Goffe via test wrote: >>>> . . . >>>> >>>> 2) Are we forgetting why we have the concept of statically linked >>>> binaries? >>> What does that have to do with where they are? >> >> If I may offer some insight: >> >> In the Unix philosophy, everything in /sbin is statically linked. >> Things in /bin may be statically linked, but more normally are >> dynamic. The root user PATH normally has /sbin and /usr/sbin before >> the others, while normal users have that reversed or even leave /sbin >> and /usr/sbin out altogether. This makes a difference when you are >> trying to recover a system in the middle of the night. With tools >> like vi, sed, grep, mount etc. being statically linked, there are >> less dependencies required to get basic recovery tools working, >> increasing the likelihood that you can get the system at least >> partially back up without having to reinstall and lose >> mission-critical data. > > sbin being for static binaries is ancient history. More recently it's > for system (superuser) binaries. I checked my sbin directory and the > only statically linked binary there is "ldconfig". > Yes, its been broken for a lot of releases now. The people who make these decisions are not admins with critical resources to keep flying. -- _______________________________________________ test mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue