Cristian Rodríguez wrote:
It can link statically.. but dynamic linking is required for certain functionality, this is a design decision, it is the same in all distributions.
1) What functionality? What functionality is needed BEFORE the network is turned on, or Before the the disks are mounted? 2) Realize not all users need said functionality. No NSS/NIS/LDAP here... I do try to use winbind... but not always, because samba-windows don't always play nice. 3) The functionality you want to provide could be provided in run-time loadable binaries -- so they only memory usage would be for those services the user actually is using!
Or not having a systemd that supports booting --
Systemd is not a bootloader, however it does interface with UEFI bootloader "gummiboot".
---- That's nice for those wanting to convert to UEFI boot, however, for the majority of users *now*, you required a hack in order to boot.
system services? (and shoving the rest into hiding in a ramdisk that people are expected/required to use)....
Yes, an initrd is required, this is also on purpose, a design decision to make maintenance and development of the distribution easier, developer time and resources are limited.
You required it because of the switch to systemd -- This is so typical of suse -- switching to new techs and having to drop support for old techs that people use -- because the new tech's don't support or don't work with the old. GRUB/XFS was the same way. XFS was default choice for FS for a short while, then grub came with it's buggy live-disk modifies that took XFS out of action -- no longer recommended as a boot FS, etc...
Can anyone name the benefits of putting the files that used to be in /bin in /usr/bin and replacing them with symlinks? Same for /sbin and /lib64 that couldn't have been solved by putting the originals in the root dirs and symlinks in /usr?
http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge
---- Yeah... Been there, got the : ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: ' http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge Zero Sized Reply ---- The argument was baseless -- nothing could be said that couldn't be turned around, switching the places of /usr and /, EXCEPT, moving to /usr would be certain to cause compatibility problems, where as moving everything to /bin or /sbin, would be far less likely to cause problem (space maybe?, but if /usr wasn't already on your rootfs, you were screwed.
Still haven't seen a good reason for requiring dynamic linking of the libc routines getXXX when the network is down and services aren't running.
So you did not really read anything on the link I sent to you, or most likely you dont want to listen.
Did you read my response? I can't replace a DSO without 100 apps complaining that they need some 'SPECIAL' version of the DSO.... I can't upgrade to a newer fixed version that I want to install, I'm on your HOOK -- I'm not allowed to upgrade my libs, I have to wait for a suse patch. Worse, I'm not even allowed to upgrade from suse packages from different versions!... (or so some, including you have told me). You break the 1st reason for having dynamic libs unless they come from you. None of the other stuff he wrote is important if you are in single user. Saving memory? It's running in 'S' or '1'. Security problems? I'm not connected to a network (yet). That page is very Dated..... over 2 years old (2.5 years). If it was that great of a 'meme', why hasn't anyone else spoken up in support showing further support?... a lone wolf posting in 2010.... people don't know how to apply critical thinking skills. Just like [g]vim that supports perl/python & ruby scripting can be build without any of those libraries linked in -- and you can have any of those libs, that you don't use not even present on your system -- but [g]vim still *WORKS* -- THAT's the part you don't seem to understand. Even when your dynamic features aren't working, the product can still work well enough to engage in repair/restore work. But there's nothing in glibc that couldn't be offered via loadable plugins like pam, samba, bash or dovecot (or many other products use) -- even the kernel has run-time config based on what you need. Why not glibc? Now will you read this one? The only reason I speak strongly about these things is I KNOW they can be better. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org