Peace in IT

Dalai LamaThe creation of a more peaceful and happier society has to begin from the level of the individual, and from there it can expand to one’s family, to one’s neighborhood, to one’s community and so on.

He gets the idea of sharing and local action having global effect. GNU/Linux is a shared project of the world. M$’s prohibition of sharing is one of several reasons that other OS causes rancor and misery around the world. BSODs, re-re-reboots, malware, high costs and sluggish performance all stem from M$’s attempts to prohibit sharing. Enjoy your favourite distribution of GNU/Linux, share it with family and friends and all of society. Make 2012 a peaceful and happy year.

About Robert Pogson

I am a retired teacher in Canada. I taught in the subject areas where I have worked for almost forty years: maths, physics, chemistry and computers. I love hunting, fishing, picking berries and mushrooms, too.
This entry was posted in technology. Bookmark the permalink.

8 Responses to Peace in IT

  1. oiaohm says:

    Ivan In 10 years I have not seen a single Linux Kernel panic happen that I did not cause or was not by bad ram.

    Kernel panic because I build a kernel without filesystem drivers kind was doomed to fail.

    The machine I am using is Windows incompatible due to poor quality drivers under windows that exist for its hardware.

    Maybe the machine you have has one of the intel video cards that are known crap under Linux. Or maybe you have one of the motherboards where the audio control is truly defective.

    Kernel Panic/BSOD/RSOD is not a major problem really. How to handle that is better documented on the Linux side than the Windows.

    Issue is under Linux the documentation for handling Kernel Panic is written under a very strange name. Kernel Oops debuging.

    http://penberg.blogspot.com.au/2010/07/linux-kernel-oops-debugging.html

    The tools for Linux exist to deal with kernel panic. Ivan is basically I can tell you have not touched Linux for many years.

    https://kgdb.wiki.kernel.org/ was introduced to the Linux kernel in 2008. With a debugging kernel you can see in more detail exactly where as failed.

    The annoying part is the documentation for it is not back on line at kernel.org so you have to hunt it down from other locations. “LinuxCon 2010 State of Kernel Debugging Presentation” is on youtube. I would recommend going and watching it. Before stating again you don’t have tools to address kernel panic problems. Mostly that you are too lazy to know about them.

    True prior to 2008 without custom patching. After 2008 you are a telling fibs.

    Networking has got simpler to reconfigure since network-manager takes care of it.

    Xorg mostly these days don’t require a configuration file at all unless you are running old hardware that does not have monitor ids or hardware that has defects you are having to work around.

    Yes basically Xorg goal is to be configuration less. Or the min amount in the configuration files.

    Audio still can be an annoying beast from hell. But even there the issues reduced. The end of the jackaudio pulseaudio cat fight in 2010 was really nice.

    If you use a 50 000 drives disk on windows Audio goes south as well. Reason many devices in Audio have the same id but with ports hooked up differently. MS documentation really don’t help you much when the wrong driver loads. At least Linux is the right driver with the wrong configuration option.

    Audio is a misery under Windows and Linux. Audio is the most common thing under windows broken by a Window update sent out driver update. Same issue the Audio hardware lacks unique id’s so wrong drivers or wrong configure drivers get loaded.

    Lets just blame linux for poor audio. Lets forget that Windows suffers from it as well. Cause us to have to download drivers of the maker to fix the issue.

    Most people miss the directory /etc/modprobe.d

    Yes got a problem create a new unique named file that goes in there with option and working options. Or if it wrong driver loading you can blacklist a driver from ever being loaded.

    Difference is you are in control. Windows I have a machine that was working perfectly until it run windows update and windows now auto blacklisted video controller without removing it. System kinda did not boot into a usable form. I had that with Windows 7.

    Windows kicks up more issues you cannot work around. Linux you are in full control of the driver blacklisting.

  2. Xorg is auto-configured these days. It’s been a year or so since I tweaked an xorg.conf. That was when Squeeze was in testing.

    Ethernet is pretty well auto-configured with DHCP these days. Wifi is a gui, too. Nothing but a password field to fill in.

    I have seen a few “kernel panics” but only on experimental systems like a kernel I compiled from scratch without a driver I needed. The stock Debian GNU/Linux is very reliable in the stable branch.

    So, Ivan, you are going on about nothing.

  3. Ivan says:

    “In all my years of using GNU/Linux once configured it stays configured.”

    Sure, Bob, Debian never needs networking to be reconfigured, it never needs Xorg reconfigured, and it never needs audio reconfigured.

    Until it does, at which point you are stuck with the frustration of dealing with an undocumented nightmare of amateurish responses on mailing lists or the asinine responses of elitist schmucks on PHP forums, neither of which solve the problem at hand, usually.

    I won’t mention the pain and suffering that comes when you inevitably see the blocky white text ‘kernel panic…’ without having a reliable way to discover and fix what is wrong, something Microsoft provides tools and documentation for. All of which makes IT life far more peaceful and harmonious.

    So, unless you have discovered a new Zen path to peace and harmony through masochism, I just don’t see it.

  4. Dr Loser wrote, “Under no definitions of the term does Microsoft prohibit sharing.”

    Check the EULA, the ones I have read state that you can only run the software on one machine, ie. you cannot legally share. Also the damned thing puts a legal limit on the number of machines you can connect on your LAN. M$ has a lot of nerve, but they get away with it in some places.

  5. Ivan wrote, “How does the frustration of having to reconfigure your computer every six to eighteen months to get audio, video, and networking working acceptably promote peace in any real fashion, Bob?”

    Assumptions, Ivan:

    1. One has to reconfigure stuff periodically in GNU/Linux, and
    2. reconfiguration is frustrating.

    In all my years of using GNU/Linux once configured it stays configured. For instance, in Debian GNU/Linux, the default behaviour of an upgraded package is to keep the old configuration unless the installer wants to start fresh for some reason.

    “10.7.3 Behavior

    Configuration file handling must conform to the following behavior:

    local changes must be preserved during a package upgrade, and

    configuration files must be preserved when the package is removed, and only deleted when the package is purged.”

    see http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3

    That’s one of the reasons I love Debian GNU/Linux. They take the frustration out of IT. Believe it. The stable branch of Debian GNU/Linux is really stable.

  6. Dr Loser says:

    Peace, man.

  7. Ivan says:

    How does the frustration of having to reconfigure your computer every six to eighteen months to get audio, video, and networking working acceptably promote peace in any real fashion, Bob?

  8. Dr Loser says:

    Take your meds and lie down.

    Under certain definitions of the term, Microsoft might be a monopoly.

    Under no definitions of the term does Microsoft prohibit sharing.

    Much like Google, in fact, they share what they think is worth sharing and keep the rest behind a walled garden.

    I’m rather shocked that you didn’t bring Mother Theresa into the conversation here.

Leave a Reply