salixosuser wrote:I forgot to mention Igelle, a new architecture trend to use self-contained modules of apps.
Similar to TinyCore on modularity, but fixing the flaw Linux, which followed MS Windows to no longer keep apps in one place but sprinkle their pieces all over the place...
That's wrong.

Linux distributions always complied closely to this standard:
http://www.pathname.com/fhs/
So it's no surprise your system looks like this:
Code: Select all
# egrep -hs '^[^/]*/[^/]*/$' /var/log/packages/* | sort -u | tail -n10
var/lib/
var/lock/
var/log/
var/man/
var/named/
var/run/
var/slapt-get/
var/spool/
var/state/
var/tmp/
From a single pretty small Salix package:
Code: Select all
grep '/$' /var/log/packages/wakeonlan-0.41-x86_64-1ab
./
install/
usr/
usr/bin/
usr/doc/
usr/doc/wakeonlan-0.41/
usr/lib64/
usr/lib64/perl5/
usr/lib64/perl5/5.10.0/
usr/lib64/perl5/5.10.0/x86_64-linux-thread-multi/
usr/lib64/perl5/vendor_perl/
usr/lib64/perl5/vendor_perl/5.10.0/
usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/
usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/auto/
usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/auto/wakeonlan/
usr/man/
usr/man/man1/
usr/src/
usr/src/wakeonlan-0.41/
And what is it like on Windows:
Code: Select all
C:\Program Files\blub\*
D:\blubprogs\blab\fart\sth\*
Though the Windows system, mostly keeps stuff in one place, I wouldn't call it better. Ever installed a cli application on windows. You need to extend your PATH variable for every single application you add. Apart it makes everything really hard to find as there are no rules where to put what and thus where to search for it. You've got a hard time guessing where an application is installed and it's even harder to understand how the different parts are splitted there (apart from the fact that especially games store a lot in big encrypted binary archives) and almost impossible to find out where else an application might have installed something. Still some applications try to work around that problem by logging the installation, but that's imho a halfhearted, poor solution.
So conclusively, also the different parts are spread over many different parts, it's easier to find those as there are pretty precise rules where to put what. Often there are also on Linux multiple places for the same thing, but almost always there's a good reason for that (system-wide, per-user, ....). On top of that there's a package system, which keeps track of all installed files. This excludes files generated at runtime though. But most of the time they're stored at a view obvious places.
Apart, my unbelievably hyper-intelligent brain is suggesting to me that we might be diverging a bit too far from the original (intended) topic.
