look closer.
The "coreutils" is not the GNU coreutils but rather an assembly of suckless.org "sbase" and OpenBSD utilities.
I guess they have used the name "coreutils" for Arch compatibility reasons.
https://github.com/StarchLinux/starc...utils/PKGBUILD
Last edited by staalmannen; 01-25-2013 at 09:28 AM.
I looked through the packages in my starch chroot and the majority of the unix utilities originate from sbase.
For the util-linux utilities: It is natural that some of those will have to be included since the distro is dealing with a Linux kernel (and thus Linux file systems).
The significant remainders of GNU would be GCC, gmake, gfindutils
Strangely enough bash is still included but mksh should (become?) the default system shell.
i see everybody including Michael missed the point so il' put it bold
ITS A PROJECT FOR A STATIC VERSION OF ARCH LINUX !!
its not about BSD or linux or what libc it uses, its just a project for making a statically linked userspace
musl is chosen cuz glibc dosent fully support static linking
bsd tools are chosen cuz GNU are made with glibc in mind
etc etc
y'all should at least check their web site before ranting nonsense
And you think Red Hat, Suse, Oracle don't do this? Go home.
Much more than on BSD. In contrary there were 25+ year old bug in bsd.So why did KDE recently have a 10 years old bug fixed? More people looking at it, eh?
FAILed QA.
Oh, it does need the same protection genius, but it's meaningless OS, so nobody cares to make it secure.It just does not need them like your Linsux does.
Because they're too smart to use Unix or Unix like OS while there's Linux. However, they're not smart enough, because many of them is using Windows.Because Americans are too stupid to handle Unix?
Described in another thread already.How?
Starch Linux piqued my interest, so I took the time to actually install it in a chroot. It is minimally functional and it needs a great deal of work. However, what Starch Linux's developer(s) have accomplished so far is a fairly good start for a distribution that is doing something genuinely different. This is especially true when you consider how limited the man power behind Starch Linux is.
chroot is insecure by design. You can get a perl script that demonstrates this:
http://pentestmonkey.net/blog/chroot-breakout-perl
Various *BSD port trees usually lag behind KDE upstream, so any bugs that the *BSD maintainers fix likely are no longer relevant. :/
The same can be said for RHEL and other Linux distributions that tend to lag behind upstream.
Last edited by ryao; 01-25-2013 at 11:59 AM.
Wrong, RHEL and other Linux distros contribute fixes that often also effect the current development version of KDE as they do not lag very much behind.
BSD ports tree lacks so far behind that the bug fixes made to them were already done in Linux. And even more, they do not contribute back to KDE, they keep the fixes to themselves.
Thus they are holding KDE (and for that matter, all open-source projects) back. But luckily, GNOME has taken the smart decision to ignore BSD and focus on linux instead. This gave them the choice of implementing linux-specific features which give superior performance and characteristics like udev and systemd.
it's interesting cos the majority of BSD desktop users are gnome users so they be forced to switch to linux which is good.
I also strongly think that all other open-source projects should forget about BSD and should implement feature which require the linux kernel so that would make it hard or impossible to port them to BSD. So BSD with have no apps and thus can die quicker. If they don't like it, I'll give them a noose.
It should serve them right for holding back linux and at the same time spreading anti-Linux FUD.![]()
Last edited by BSD SUCKS DICKS; 01-25-2013 at 03:54 PM.