NSA: Please Turn off the Lights When You Leave. Nothing to See Here.

Linux Advocate Dietrich Schmitz shows how the general public can take action to truly protect their privacy using GnuPG with Evolution email. Read the details.

Mailvelope for Chrome: PGP Encrypted Email Made Easy

Linux Advocate Dietrich Schmitz officially endorses what he deems is a truly secure, easy to use PGP email encryption program. Read the details.

Step off Microsoft's License Treadmill to FOSS Linux

Linux Advocate Dietrich Schmitz reminds CIOs that XP Desktops destined for MS end of life support can be reprovisioned with FOSS Linux to run like brand new. Read how.

Bitcoin is NOT Money -- it's a Commodity

Linux Advocate shares news that the U.S. Treasury will treat Bitcoin as a Commodity 'Investment'. Read the details.

Google Drive Gets a Failing Grade on Privacy Protection

Linux Advocate Dietrich Schmitz puts out a public service privacy warning. Google Drive gets a failing grade on protecting your privacy.

Email: A Fundamentally Broken System

Email needs an overhaul. Privacy must be integrated.

Opinion

Cookie Cutter Distros Don't Cut It

Opinion

The 'Linux Inside' Stigma - It's real and it's a problem.

U.S. Patent and Trademark Office Turn a Deaf Ear

Linux Advocate Dietrich Schmitz reminds readers of a long ago failed petition by Mathematician Prof. Donald Knuth for stopping issuance of Software Patents.

Showing posts with label UNIX. Show all posts
Showing posts with label UNIX. Show all posts

Tuesday, April 30, 2013

Slackware: Is Systemd Inevitable?

by Dietrich Schmitz

I recently wrote a story Systemd: The New Pulse Audio as regards the work undertaken by Red Hat and one employee +Lennart Poettering to improve Linux with a middleware daemon called systemd.

Much press has been given to the story surrounding systemd putting the work into question. Still, the work progresses and continues to move forward and many Linux Distros have chosen to adopt it as others opt to take a 'wait and see' approach.

So, far, the oldest Linux Distro Slackware has avoided the issue and the most recent version, Slackware 14.0 released last fall by its Founder +Patrick Volkerding, is doing just fine without it.

I came across an interview done by LinuxQuestions.org with Patrick and share here a passage in his interview which deals directly with the issue of systemd.  Patrick writes:

"...Concerning systemd, I do like the idea of a faster boot time (obviously), but I also like controlling the startup of the system with shell scripts that are readable, and I'm guessing that's what most Slackware users prefer too. I don't spend all day rebooting my machine, and having looked at systemd config files it seems to me a very foreign way of controlling a system to me, and attempting to control services, sockets, devices, mounts, etc., all within one daemon flies in the face of the UNIX concept of doing one thing and doing it well. To the typical end user, if this results in a faster boot then mission accomplished. With udev being phased out in favor of systemd performing those tasks we'll have to make the decision at some point between whether we want to try to maintain udev ourselves, have systemd replace just udev's functions, or if we want the whole kit and caboodle...."
Given the foregoing and given that historically Gnome was removed from Slackware, it would seem that Patrick is being careful not to tip his hand one way or another as to whether he will 'yield to pressure' and become systemd-compliant.

I speculate (Patrick's development is kept private so nobody get's access to his decision making until he says so), that Patrick's plan's for the next revision may well include software design changes that successfully keep systemd out of his implementation.

If that is the case, it would be virtuous if other Community Developers fell in lock-step and provided him assistance in such a worthy effort.

Personally, I can understand the contention surrounding systemd's invasiveness and how it violates the UNIX concept of "doing one thing and doing it well".

Specifically, having the initialization process loosely coupled to a series of run level cascading shell scripts has served Linux well for many years and maybe the concern that work being done on systemd is too ambitious insofar as bringing too many processes under control of one daemon service, systemd is warranted.  Add that the logging of activities taken by systemd are no longer human readable, but journalized in a binary format and you have a recipe for programmer revolt.

It was most recently the genesis of a decision by Fuduntu to close its doors as the volume of programming required to merge needed systemd changes was simply too large an undertaking for its meager staff to handle.

Will Slackware be the next Distro to fall in line and become systemd-compliant?  Stay tuned for developments.

-- Dietrich



Enhanced by Zemanta

Monday, April 15, 2013

'Bitrot' Not a GNU/Linux Issue

by Dr. Roy Schestowitz

In computing, everything should ideally scale linearly or logarithmically if/where possible, except perhaps for innovation in hardware which can be nearly exponential in some terms due to multidimensionality and various other factors. Linux takes good advantage of hardware and, owing to reuse of code, programs are rarely bloated. With Windows, contrariwise, common practice/advice is to assume bloat is normal and reinstallation a routine task which mitigates bloat. Those are two separate issues; one deals with scalability and the other with the steps needed to remediate. In GNU/Linux, where malware is rare, optimising a system is often possible without radical measures like clean-installing.


It is not uncommon to see distributions of BSD or GNU/Linux running for years without a reboot or a reinstallation. These systems, which first found widespread use in (gradually more mission-critical) servers, required a high degree of tolerance, robustness, stability, and minimal downtime or rebuilding time. Windows, which had primarily emerged through the desktop, took over a decade to get the basics of networking and user privileges almost right -- an issue that still makes it attractive to rogue programs.

The three Rs, restart (application), reboot , and reinstall, have made infamous a class of box booters who are sometimes synonymous with Microsoft-certified administrators. Whereas UNIX and Linux professionals tend to deal with complicated issues of automation and troubleshooting, many of their Window-centric counterparts spend their days wrestling with issues associated with performance (setting aside restrictive licensing that impedes expansion) and malware, which are two related but separable issues. Over the years I have narrowed down the low efficiency of maintaining Windows clusters (requiring more administrators per cluster) to what some call bitrot, or the notion that digital data -- or an executable program - inevitably needs to erode over time, requiring one to revert it back to a pristine condition.

A solid GNU/Linux distribution is unlikely to slow down or break down on its own. On my main workstation (since 2008), for example, I never had to reinstall an operating system unless I switched between distributions (Mandriva was losing its corporate backing at the time). I could use the system for months at a time without any reboot. I could install over a thousand packages without it resulting in slowdown or performance degradation of any kind. It is harder to achieve the same thing with Windows, based on people to whom I speak. The three Rs are essential there.

More and more enterprises pursue GNU/Linux and people who know how to maintain it. For continuity of service and for minimal intervention it takes a system that will not 'rot' over time or be made deprecated because the company which has exclusive rights to the source code decides so.

-- Dr. Roy Schestowitz


Enhanced by Zemanta

Sunday, April 14, 2013

Dedoimedo with: A Beard and a Pipe



by Guest Writer Dedoimedo

Twenty years plus since being created, Linux remains a terrifying word in the global lexicon. Probably not as bad as it was for farmers watching cars take over the countryside in the early decades of the 20th century, but close. It's an operating system all right, but one that does not warm the cockles of your heart. It's the bastion of nerdy and geeky and difficult, and you are better off leaving it alone, to its bearded users. Which makes me think, why is the beard a status of sagacity in our society? Throw in a smoking pipe, and you have a PhD in trustworthiness. That's how it works. And yet, even though Linux is an obvious choice among the people of science, academy and industry, the popular desire to emulate the prototype intellectual status is in low demand. For most folks, the hardship of becoming a Linux user outweighs the benefits. (Image credit: Wikipedia.org)

Because of this phenomenon, if you happen to burrow your face into the job-seeking networks, you will see the string Linux featuring tall and mighty. There's quite a bit of demand for Linux system administrators and engineers, global recession and all notwithstanding. True, you will find a wealth of other occupations, professions and skill being hawked to the lowest bidder, but Linux is sort of a star.

A Day in Life


Now, let's expand on a day in life of Average Joe. He seeks employment, and he wishes to become a borg in that honey-tasting entity called the hi-tech industry, where productivity is measured in the number of presentations one makes and in the size of one's CC mailing list. Joe has a lot of opportunities before him: He may become a data center technician, a first level help desk operator going through a new headset every few months, or a system administrator fixing broken mail clients while racing the SLA graphs to the finish line. Or he may become a project manager. Some might choose electrical engineering or physics or math, in case they struggle with code, or even become fully fledged developers.

Encompassing it all, there's one thing that everyone should sort of consider, and that's the ecosystem. Does it have Linux in it? Or better yet, does Joe bring Linux along?

I am absolutely certain that most people do not think about Linux when they apply for a job, but it is probably the first thing they should be doing. For purely selfish reasons. Money.

The maverick, slightly outcast, unpopular status of Linux is what makes it, perversely, the popular and most 'in' commodity in the industry right now. It's sort of a metric by which people measure the quality of the ecosystem. When you say Linux, it's like the beard and the smoking pipe. There's a certain aura about it that makes a lesser man skip a beat. Nothing major, but the rumor and fear make for a very glamorous reputation.

Linux is the rogue of the operating system gang.

Ask anyone what operating system they use, they will most likely answer Windows. When you hear someone say Linux, you automatically assume they are much more skilled that your average user. You can try this exercise yourself. Call your ISP support and tell them you use Linux. You will be forwarded to would-be expert support, and no one will argue with your claims. I have been using this trick for years, which is why I have the personal emails of my ISP specialist staff, since no one dares dispute the Linux weirdo.

Linux as a Strategy: AKA The Minority Report


It gets better. Knowing Linux brings in a whole lot of assumptions along. The fact you know Linux means you know Windows, too! Doesn't have to be, but everyone will think that. They know you are above average in your troubleshooting skills. They know you have your unique ways of working out problems and searching for software, and that gives you an instant advantage. Linx saves time when it comes to job interviews. It's like when you drive a Lamborghini, you don't need to invest that much time impressing the other gender. Which is why you should know Linux. Even if you never get to use it.

Linux is the strategic minority luxury weapon of the industry, and it will remain so for many more years, as long as Microsoft remains the dominant player in the home market, and as long as its rivals maintain the operating system ambiguity as their marketing pitch. Because both OSX and Android have their roots in UNIX and Linux, respectively, but woe the user who voices that out loud. Oh, did you spot that joke?  Have their roots?  Hee hee.

This is where you come in. When you plan your future employment, you need to consider the market saturation. You need to try to wedge yourself into the premium tier, because that's where decent pay and prestige are. Of course, you can go about it the conventional way, slaving your way through annual assessment reviews, or you could leapfrog a few years by becoming well versed in the secrets of Linux.

A Medal of Binary Honor


If you apply for a job wearing a Linux badge on your shirt, you will have cleared away quite a few obstacles without having had to even prove yourself. Sure, this sleight of hand will work up to a certain level. For example, if you end up being unlucky of having me as your interviewer, you'd better be able to demonstrate your skills, but for most employers, Linux still remains a synonym for professional respect. Not at home no, but in the office, yes. The beard and the pipe trick.

If you are coming to work in a company that is using Linux, you know you have just been handed an unexpected bonus. Again, it's never black and white. Companies will use the best, i.e. cheapest tools they can find to get the job done. The fact someone uses Linux might just be a side effect of brute computational power or support cost they can afford. However, regardless of how Linux came to be in this or that company, the beautiful and inevitable side effect is that there is going to be a different mindset there. People will be more inclined to listen to new, radical ideas, to discuss non-mainstream software, to implement automation and command-line solutions, to try to conform to global practices and standards. Linux begets diversity. And you want that wherever you go to work. The alternative is a boring, monotone place that kills innovation. As preposterous as it sounds, Linux is a great indicator of the vitality and colorfulness of a workplace, when it comes to its human factor. Philosophically, you may ask, is it the human nature that affects software, or vice versa? It does not matter, because you reap benefits anyway.

Now come the crucial questions:


  • How does one become skilled in Linux?, 
  • Where do you learn it?, and,
  • How do you overcome the fear of this geeky system that tolerates no noobiness? 


If you are reading this article, you are most likely on the far, far end of the spectrum, so the message is quite irrelevant for you, but if you have friends facing tough job-seeking dilemmas, you might want to encourage them to read this.

Let's Get Linuxy


Learning Linux is often an informal process. People start dabbling in this or that distribution, get hooked and begin their distro-hopping journey. After a while, they settle on the most comfortable distro that meets their needs, and that's it. But you can do more, so much more.

Take your distribution, to an extreme. Choose any which subcomponent, and try to master it, completely. The definition might sound abstract, but Linux was created with self-learning as its chief ingredient. Hence those man and info pages. Now, I do not suggest you send panicking newbies down that lane, but for aspiring enthusiasts, this is your portal to knowledge. You will find yourself in a sea of definitions and tools, each taking you their own way.

Still, some formality can go a long way. Even if your job description never takes you down the path of pure system administration, qualifying for a diploma or a certification of some sort can prove that you're capable of working through a process, if needed, give your wild Linux beasts its corral and nosebag. For example, you might want to consider the distribution-independent LPI certifications. Novell, RedHat and Ubuntu also offer their own qualification programs. I can vouch for these myself, as a customer. While they really mean absolutely nothing in my actual daily work, they do add to that beard-and-pipe image ever so slightly. They were also useful in my job seeking phase, as they allow companies to more easily filter the applicants. When one says, I know Linux, it's really hard to quantify this. However, when you go by an industry standard or a well-accepted criterion, you save time and confusion and potential misinterpretation.

But a nice, glossy paper is meaningless without actual knowledge. It's nice to have a framework to help you define your Linux glory roadmap, but you still need actual hands-on experience. This is where Linux really shines. It is possible, conceivable to have a semi-professional Linux environment in one's home. It's virtually impossible, for a variety of reasons, to get the same quality of results using Microsoft Windows or other operating systems. Take a couple of laptops, a few desktops, a dozen virtual machines, and you can create an extremely elaborate Linux test setup, all for free. This is your proving ground, and here you learn skills. Some GUI at first, then more and more scripting and automation. As your knowledge builds, so does your understanding of how things need to be done. When it comes being practical, Linxu has this other advantage: it is intuitively efficient. You will learn how to do things the right way, all on your own, because the architecture of the system will force you.

Conclusion


After several months or years, you will find yourself immersed in a beautiful, fruitful world called Linux, and you will have gained yourself a wealth of knowledge that has nothing to do with Linux itself. You will have learned about hardware, networking, firewalls, services, and other useful ideas, all because trying Linux made you study them. Now, when you seek employment, even as a Microsoft specialist, you will have a solid, confident wall of knowledge to back your claims, and maybe you will get that next pay rise that sooner. Just as some would tell you any man ought to go through a military service because it builds character, I say, you ought to dip your hand in Linux, because it will build your career. Even if you never use it at work.

Be selfish, think of yourself, think of money.  Use Linux.

-- Dedoimedo

__________________________________________

Igor Ljubuncic aka Dedoimedo is the guy behind dedoimedo.com. He makes a living out of his very hobby - Linux, and holds a bunch of certifications that make a nice pile in the bottom drawer.

Hello, Dedoimedo here, a man who makes a living fiddling with Linux. Approximately nine years ago, I had my first chance encounter with Linux, and since, we've been together, quite happy. Like most chance things, Linux comes into people's lives in random, strange ways, and trying to define them with a mathematical formula probably misses the point. Which is why we are here, to talk about Linux, and how it makes sense to have it in your life. No fanboyism, no religion, just pure and simple logic.
Enhanced by Zemanta

Wednesday, March 20, 2013

The Linux Filesystem Need Not Be Mysterious

by Dietrich Schmitz

As intimidating as the Linux filesystem may appear at first, there is some sensibility to all of those folders you see.  Fear not. (Image Credit Right: Codepuppet.com)

What's good is that you need not focus on any area other than your $HOME folder.

Essentially, every user (Linux is a true multi-user operating system) has his/her very own 'Home' directory structure.  Here is a terminal list of mine:


dietrich@AOD260 ~ $ ls
Desktop    Downloads        Music     Public     Videos
Documents  linux-advocates  Pictures  Templates
dietrich@AOD260 ~ $ pwd
/home/dietrich
dietrich@AOD260 ~ $ 

Note, the pink 'ls' is to list and 'pwd' is to print the working directory, in this case "/home/dietrich".

It's all very sensible and as you become more comfortable with Linux, you may get more familiar with how the filesystem works in more detail.  But for now, trust, that Linux inherits most of what you see from the venerable Unix operating system.  Unix was designed to be secure, safe, and reliable and has a proven track record in the computer industry of doing major heavy lifting production work.

So, whether you come from Windows or Apple or are just a computer newbie, welcome, and know that you have made a good choice with Linux.  In fact, most often you will seldom need to go out to a terminal as I just did.  I was just being a 'show-off'.

Every Linux Distro will come with its own Filesystem navigation application, like Explorer is to Windows.  In my case, I am using Fuduntu which comes with Gnome Nautilus Elementary.  Here's what opening the home folder looks like:

Gnome Nautilus Elementary on Fuduntu viewing my home folder


It's pretty easy to find your way around in Linux--contrary to popular belief--today it's easier to use than Windows and more flexible.



I'm not going to go into further detail regarding the Linux filesystem today, but will let you watch the above video from NixieDoesLinux.  It's a great way to get introduced to the subject.  Ease into it.  Find your way around, slowly and don't worry.  With time you will be winging your way around the system without giving it a thought.  

You will be fine.  -- Dietrich

Enhanced by Zemanta

Tuesday, February 12, 2013

How I got to use Linux and why you should too

Tux, the Linux penguin
Tux (Photo credit: Wikipedia)

By Guest Writer Aioanei Rares


The history part

While I know that this topic was used and abused lately, I'm going to take my chances in the humble hope that I'll manage to bring something new and fresh to the table. If I'm to fail, I apologize just as humbly, and hope I won't be wasting your time completely. The first computer I ever laid my hands on, if it can be called a computer, was a HC90, back in 1991, which was a ZX80/Sinclair clone at the local computer club. You know, BASIC interpreter, the works. When I finally managed to convince my folks to get me one of those, said computers disappeared off the market. So fast forward a few years later: I was using DOS 6.22 on a 286, then it was Windows 95, 98, Me, 2000...and so on. Since I already liked the idea of programming a computer since the HC90 days, if BASIC can be called programming, I started digging around to see how I can program on my Windows machine. My connection back then was via an external modem, with a limited data plan, so I had to download
documentation from Internet Cafes or whatever source I could.

Sunday, February 10, 2013

The GNU/Linux "Desktop"

Wildebeast or Gnu
Wildebeast or Gnu (Photo credit: jomilo75)
By: Robert Pogson

Personal computers and the software that runs them has evolved greatly over the years. In the process, motherboards (the guts of the computer) have become smaller and more functional as the number of transistors in a chip has risen from thousand to hundreds of millions and clock speeds have increased thousands of times. In the process, software has changed from simple monitors controlled by serial links to complex operating systems with hundreds of processes running and GUIs (Graphical User-Interfaces). For many years the GUI has followed the "desktop" paradigm, a virtual space where "documents" and images and multi-media "files" lay about or were placed in "folders" and a user pointed and clicked to start processes, usually starting a new application or a new process (usually seen by the user in a window). There are many personal computers these days leaving the "desktop" paradigm for a new style or out of necessity, being on tiny screens like smartphones. There just isn't enough space on the tiny screen for much of anything to point and click and fingers are fumbly pointing devices anyway.