Quote:
Originally Posted by vharishankar
You have a roundabout way of saying things which takes time for me to understand. I am unsure about whether you are insulting or complimenting me, but OK, thanks for the clarification and you thoughts about my website.
|
Try to understand the reasons behind instead of judge
what I say in a TRUE|FALSE way. Do you think that my
interest of posting here is complimenting or insulting
people?
My roundabout way of saying things aims to avoid to be
trolled or accused of trolling each time I say
something that could hurt the "fans" TRUE|FALSE
approach. Perhaps doing that I got the opposite
effect :-).
By the way, I know that my english is horrible. But
perhaps the mistake I did referencing to the links in
the Alien Bob's post added confusion.
I will give you an example that I wish will clarify my
"cryptic" posts. I've read just one more Alien Bob
article (in my life. And no, I am not experimenting
nothing symilar to an obsesson with his articles)
besides the games one. The first one was this*:
http://alien.slackbook.org/blog/inte...the-gnome-out/
I made comments there like Walter (my real name). Read my
comments and think again about how giving WYSIWYG
facilities to Windows like users could not be
compatible with a KISS intended system. Do you see the
relation with systemd issue? We are talking about
rc init scripts.
You use Debian. Well, the Network Manager run like a
daemon and is included in init.d. To be able to get a
connection with simple tools like iwconfig (in case NM
can't, which was the case with some Ralink chipsets)
you must first kill the network manager process. Try
now to restart the networking process on Debian:
/etc/init.d/networking restart
and see what happens. Then search in Google or Debian
forums the solution for the issue. You will see why
Lennart is fixing the fix.
Now I will point something that will hurt the feelings
of a lot of new Linux desktop users. The history tell
us that till now (let's see what happens with
Android), in the same way Windows won "naturally" its
place in desktop market, Unix do it in server side.
It could be said that in "general" terms the
modifications you do to a OS to facilitate things to
desktop users are in the better case useless to the
server side. In the worst case they add bugs,
security holes, incompatibilities, besides to gratuity
complicate thinks to the server admin. I reach to the
point to be asked by a VPS provider to update my
kernel (Slackware virtual machine on CentOS) to update
glibc (what he guessed was the cause of the issue),
based in what a Debian user (one of his clients) had
done to fix the issue because apt-get (I ignore if
this is true) resolved the glib package like a kernel
package dependency. The funny thing was that I had no
need to have a kernel installed in Slackware, the
kernel used was a patched CentOS one :-). That's the
dark side of automagically resolving dependencies in
package managers. See? Now I am pointing something
negative about debian dependencies, am I insulting you
now?
Furthermore. In general terms the more you facilitate
the computer use to humans the more you complicate
things to the system. And in the same sense I told
that Unix won "naturally" a good place on the server
side market I consider what Apple did "counter natural"
to the Unix bases. I could give you examples but I
don't want to write a book here :-).
At some point you (and Linux in general) must stablish
priorities and choose to what extent to serve God or
daemons.
Walter
(*) Eric didn't feel insulted in that opportunity.