Giorgio Lando schrieb:
Moreover:
* (perhaps) merge with CRUX-PPC
A little distribution should not try to work on multiple architectures, because this implies a massive dissipation of efforts: CRUX is designed to work on i686 machine and should not try to be something else
Sorry, that's total nonsense! root@ecam:~$ crux CRUX version 2.3 root@ecam:~$ cat /proc/cpuinfo processor : 0 cpu : e500 revision : 2.0 (pvr 8020 0020) bogomips : 823.29 chipset : 8540 Vendor : Freescale Semiconductor Machine : mpc8540ads clock : 825MHz PVR : 0x80200020 SVR : 0x80300020 PLL setting : 0x5 Memory : 256 MB The CRUX philosophy (stay simple and functional) is the key to be portable to other architectures. One example is crux-ppc and the other one my creation called CRUX-embedded for some embedded PowerPC (see above) which I would call the most current native toolchain available for that platform. The funny thing is that from the current 102 ports in x86' core only 10 need special care to build for this (quite strange) embedded PowerPC. (I "forked" crux-embedded from crux-x86 and not from crux-ppc!) So, the official (x86-)CRUX is already over 90% architecture transparent! I don't really care if it's merged with crux-x86 or crux-ppc... It's no big deal to handle the 10 packages (the toolchain plus some crap) when there are some updates. (once every other month)
I do not need localizations, because their only point, besides wasting disk space, is to obfuscate the original language in which a software is thought and written.
Here, you get my ACK! Regards, -- Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm-technology.com Phone: +49-89-741518-50 Fax: +49-89-741518-19