The FreeBSD operating system is the unknown giant among free operating systems. Starting out from the 386BSD project, it is an extremely fast UNIX-like operating system mostly for the Intel chip and its clones. In many ways, FreeBSD has always been the operating system that GNU/Linux-based operating systems should have been. It runs on out-of-date Intel machines and 64-bit AMD chips, and it serves terabytes of files a day on some of the largest file servers on earth. Elsewhere, here is a guide to PC-BSD.
To read all comments associated with this story, please click here.
Member since:2005-07-14
So libraries in PBIs are statically linked with their respective binaries? Maybe it makes more sense the opposite way: So binaries in PBIs are statically linked with their respective binaires, but the result is the same.
If my memory serves me well, statically linked libs would not be shared in memory. So if I ran e.g. gnome-terminal and Evolution, I would end up with all GNOME libraries twice in my RAM? Ouch 
Yeah, why would someone run a GNOME program on a KDE system. I just picked GNOME as a prime example of something, which would not be in the base install, hence distributed through PBIs and has a lot of libraries involved.
If you read my first post, the long one, I went thinking on how the link would behave, if you had dynamically linked libraries in PBIs. I hoped for an answer on that.
Member since:
2005-06-29
Dynamic linking, when creating PBI's there are 2 options...
1) specify a Library Folder (Statically linked lib's in side the application folder... self-contained)
2) using standard libraries (dynamically linked from /lib, /usr/lib, /usr/share/lib, etc... semi-self contained)
so dynamic linking is possible, but then you end up with the questions... which libraries do i leave? what libraries is it safe to remove?