No c++ compiler, FORTRAN, objc, etc.
The gcc command is just a frontend for lots of other possible features.
But they're big. So I stick with what's crucial, namely plain GNU C. As of
this writing I haven't tested it, but a cLIeNUX Core should be able to
compile a kernel. (199901) does compile 2.2 kernels.
No groff.
The formatted manpages were formatted on a host system, not Core
itself. groff goes around in all kinds of vicious dependancy circles, and
that's where I was able to cut it.
(19990322)
I've now re-done most of the manpages from groff with man2html, modified
for cLIeNUX.
SUID and su
Not one SUID bit. That's innapropriate for a shell server or something,
but we default for client-use of the box. So cLIeNUX assumes you're root
most of the time anyway. In fact, if I ran a shell server it would have no
SUID bits. Think about it.
packages
I haven't decided what a cLIeNUX package management scheme, if any, will
be. And hopefully an exploding cLIeNUX membership will do most of that.
Meanwhile if you DL a Linux sourcecode archive of any kind and can't
install it I'd like to know. unrpm and undeb and cpio and tar and gzip
should get most of em. My current thinking (19990107) on cLIeNUX
"packages" is that they should be source, but known to install trivially
on cLIeNUX Core. The idea there is that Core would be the same to the
source packages on any platform. I do some non-GPL stuff to give cLIeNUX
cohesiveness, in hopes that that coherence gives cLIeNUX some
economic viability, but I am utterly convinced of the idea that source is
essential.
Rick Hohensee