Webfish Linux is aimed at servers, routers, and customised workstations for experienced Linux users. It attempts to get away from the bloat factor of many common distributions, and does not include large amounts of binary packages or a package manager. It is based on a small base set that provides kernel, gcc, Perl, sed, awk, bash, ethernet tools, etc. (basically, all that is required to run a base system and compile software but not any software itself).
it's just a BAD idea.
I hope i'm not paraphrasing other people's
much, as a lot of valid points that I agree with
have been made but this is purely and simply a
As has already been mentioned the current system
allows greatest flexibility and configurations
that are actually well suited to the application
they partner with. If you want a
environment the try Windoze (or maybe MacOS?) and
you'll be happy for ever.
Three of the best things about the UNIX/Linux
1) There is more than one way to do it - AKA the
perl motto. We don't want standarisation - why do
you think a lot of us chose linux in the first
place - because we can do what WE not someone
else wants. Which brings me to point 2:
2) UNIX/Linux allows us not just to customise
WHAT we do but how we do it. By unifiying
configuration and having configurations modified
by a software layer we are potentialy removing
our freedom and control over our systems and the
way they behave.
3) Linux always has been about learning. If you
don't know how to configure something LEARN. The
information is out there, it may be hard at first
but the end result will be a better, more stable
system that fits your needs exactly. We have been
forced by Microsoft and others for years to
accept the way they want things done as "The
Standard". Instead, we should be encouraging
freedom of information, freedom of configuration,
freedom of choice. This is one of the only true
preventive measures to avoid monopolisation of
our software and systems - insist on being able
to do it HOW YOU WANT TO. It's your right.
I also agree with the theories on Leakage, which
effectively make this project almost redundant.
If any of you have tried to use Linuxconf et.al.
you will soon realise they are of little
practical use and make it difficult to recover
your configuration by hand should the program
screw up. In fact, if you edit a file by hand
in-between admin sessions, you can get into no
end of trouble. In fact, it can generate a lot of
hassle and wasted time just because of the fact
that the user, especially the inexperienced one,
will blindly believe that their configuration
interface is handling everything for them when in
many cases it may well not be doing this
Also, this can pose a major security risk.
Despite secuirty measures in place, it is REALLY
unwise to offer effectively root level access via
a web page, an open network port or any type of
front end. I would say this does not fit with
good practice and is not conducive to knowing
what your box is doing all the time - which is
actually a legal requirement in a lot of
countries as you are responsible for your
Another point that is worth noting is this:
Storing all of your configuration in one place is
bad. If you kill your configuration interface or
your config database, you kill your machine, at
least partially. One of the great things about
unix systems is that software is seperate. Apache
can die without taking out your mailserver.
Joining appplications together in any way is a
bad idea as it causes a single point of failure.
You only have to take a look at the Windows
Registry system and how easily registry and
profile information can get corrupted to prove
Anyway, these are my opinions, for what they are
Webfish Linux Project