Re: Suggestion: Static libs policy, a draft

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bill Nottingham wrote:
In other words, for all statically linked executables in Core (recovering, init/boot time etc.), all the libraries which take place in the correspond static linkage must be present.

Obviously. This is sort of prerequisite for self-hosting.

Well, not so fast. There is no reason for booting to require static linking. It might even be that the static linking meanwhile increases the ramdisk size (2.7M for both binaries). In any case, we're not booting from floppy disks anymore so this is not an issue. The static linking should be removed where it is currently used for booting.

As for recovery: you're a fool if you trust the binaries on the system which has to be covered. This is what the rescue mode of the boot CD is for.

--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux