Slashdot Mirror


Novell's Certified Linux Engineer

AEnertia writes "Novell have been quick in moving ahead with their recent aquisition of SuSE. I was browsing their site when I found this page describing their new certification (CLE) under their certifications programs. Looks like they are positioning their well respected certification program for their newest asset."

29 of 248 comments (clear)

  1. Good for them by t0ny · · Score: 2, Insightful
    Im glad to see Novell adding further to their product line-up, and hope it goes well for them. Ive always liked Netware, ever since my first exposure to it at 4.1

    BTW, its pretty lame dissing on MCSE's- the paper ones generally get exposed in the real world, and since there are lots of us out there who can fix most NT issues with our eyes closed, I can very much say a real MCSE is an asset to any company. Its not like there arent paper CCNAs, CNAs, etc.

    But its easy to make fun of someone else, especially when they can fix things you cant; most *nix people just wave their hands and complain about Microsoft instead of actually *fixing* the Windows servers. Its a poor craftsman who blames his tools.

    --

    Manipulate the moderator system! Mod someone as "overrated" today.

    1. Re:Good for them by muonman · · Score: 4, Insightful

      Its a poor craftsman who blames his tools.

      Its an even poorer craftsman who cant tell a good tool from a bad one.

      --
      Anything NOT worth doing is NOT worth doing well...
    2. Re:Good for them by brsmith4 · · Score: 4, Insightful

      I think most *nix people, like myself, are turned off to MS not simply because their servers are less stable or more bug prone, god knows that *nix admins have to run patches a lot too. I think my biggest gripe has to be the cumbersome nature of admining a box with a UI that was really designed for a user-friendly home machine. Compared to linux or solaris, where I can admin a hundred boxes by typing in one command (of course, after I set everything up to do that), its a bitch to admin multiple windows machines. On linux desktops, if i want to set up printers, i simply copy over the cups config files to the new machine. 1 second, done. Windows, you must go through a myriad of printer configuration screens, esp. if your printer is on an lpd server. I could ghost a windows image and burn it in to each machine, preserving settings, but that is as well, time consuming. I could copy out the registry settings and reimport them at install, but its still easier to scp/rcp files and be done with it. Now a good MCSE is a master at his/her craft and I admire his/her patience (hehe) and his/her ability to navigate and troubleshoot a poorly documented and closed source system. However, I do agree with the parent/parent/parent/.. that the MCSE test is quite lacking. Real-world scenarios in a lab and not on a A-B-C-D answer sheet would make the MCSE test more worthy of the money that you put into it.

    3. Re:Good for them by tzanger · · Score: 4, Insightful

      Its also quite easy for people to make fun of things they dont understand; I love how people always say MS stuff is simplistic, until they need to fix it. Then they just say its poorly designed. Maybe if they spent time trying to understand how the OS or application does things, instead of complaining about it, they could fix it.

      Actually that's not my problem with Windows. My problem is that it's too complex, too convoluted, and simply lacks the tools to properly diagnose and repair. Sure you can buy third party tools to make up for some of these deficiencies but I'd rather use Linux. The configuration for pretty much everything is plain text and documented freely instead of hidden behind a single-point-of-failure binary registry and anonymous GID identifiers. The system internals are all public and I can access any part of it I need without gagging NDAs and/or paying for the privilege and finally -- I am not tied to one megacorp with a penchant for monopolistic practises and stifling innovation. I have enough problems with running a business that I don't need to compound the issue by welcoming the vampire into my house.

      Basically my beef with Windows and my desire to use Linux stems from the simple fact that when something does go wrong, I can fix it far easier and without paying for the privilege. And in those cases when Microsoft is either unwilling or unable to fix something, I can always hire a programmer to fix it for me.

    4. Re:Good for them by tzanger · · Score: 2, Insightful

      This [windows system configuration] has never been an issue for me, since TechNet documents just about anything you need to know. Understanding how the registry works helps a lot, too, and Ive never found the registry to be a single point of failure (well, misconfiguration can be that on any platform).

      Any time I've tried to find out anything nontrivial on TechNet I've come up empty. A recent example was optimizing SMB to tell it that it was perfectly fine to fragment packets so that I could get better TCP/IP SMB throughput.

      Ive been working on Windows servers for almost ten years, and I have yet to even see an NDA.

      Good for you. Now try doing anything that has you digging around in kernelspace. Oh, or how about working with SMB? That's under NDA these days.

      Ah, the typical Slashdot line makes its appearence. This is like when a Republican cant think of anything to say, so they just shout "Well, Clinton got a blow-job!"

      I could care less about the typical slashdot line. Microsoft's been proven time and time again that they're using their monopoly to stifle competition (and innovation, by extension) -- I've got plenty of meat to my original post, this was just another datapoint. Clinton's blowjob doesn't have anything to do with his ability to lead a nation. His lying about it was the problem. Same thing with MS. Being the 800-lb gorilla isn't inherently bad. It's when you use your position to beat down competition that it becomes a problem.

      I say thank goodness for MS flipping everyone the bird and including components into the OS, so you could just buy the OS and have a network client, or a computer which can access the internet, all without having to purchase and install three seperate pieces of software.

      Oh yeah, thank you MS for embracing and extending so many technologies and locking everyone in to the MS way of doing things. That's made life so much better...

      You're absolutely right about creating a common platform but interop is also very important... and to get interop you need open protocols and UNEXTENDED protocols. MS is not keen on either. And now enter DRM and DMCA and you've got MS' wet dream: total vendor lock-in.

      If most companies had Linux systems, they would need to pay for the privilege of getting it fixed; more people know how to support MS than Linux, and they are most likely already employees.

      It all comes back to my orignal post -- oftentimes the only fucking way to solve a nontrivial problem with MS is to format, reinstall and restore from backup. Even if you can get the system back online, it's unstable because something is wonky and you just can't get to what... Or, if you've cast the right incantations and sacrificed to the right board members, you know exactly where the problem is but can't replace just that one subsystem. On Linux I have never ever had to do fix a software problem by restoring from backup, and oftentimes correcting the problem was far faster than a total reinstall. Any monkey can say they support Windows and their typical response is "reboot, hmm ok, reinstall" -- I don't know of any other operating system where that is SOP and acceptable. You can have tons of "windows support" if that's their response.

      I cant for the life of me figure out how this would apply to any real-world scenarios... Its basically like me saying its Ford's fault that my fan belt broke, and they should be responsible for fixing it. Heaven forbid you bring the car in to a mechanic...

      Win95 support has been terminated. You can't upgrade your Win95 system for whatever reason. You're fucked. If you have a RedHat 5 system you can still solve the problem and continue on. There's no forced-upgrade cycle. Of course you pay for the privilege, but you can still get done what you need. It's just like drive recovery... You were stupid/unlucky enough to not have a backup, you're gonna pay to get your data back. But you can still (wi

    5. Re:Good for them by PimpBot · · Score: 1, Insightful

      t0ny, I just want to know, I hear you.

      There's a belief out there that Unix (and its variants) is the end-all-be-all of Operating Systems - to understand Unix is to understand everything.* Well, its not.

      Windows NT systems, Unix systems, QNX, etc. all have their good sides and their bad sides. They are all equally complex, but each in their own unique way.

      Some people will scoff at my comment, but trust me - I've developed and help maintain Windows Servers, Solaris Servers, Linux Servers, AIX Servers, MacOS X setups (no MacOS X Servers yet :-( ), HP-UX Servers, FreeBSD Servers, NetBSD servers, and IBM Mainframes running z/OS. I have rants and raves about each of them - but none of them is any better or worse than the others.

      Why? Because they're all tools used in getting a job done.

      Console-based development is a dream on Unix-variants, but I would never depend upon them for any - the graphical environments are just too fragmented. I would probably go with Windows or MacOS X for that (most likely Windows due to higher use in the market).

      Right tool for the job, people. Just because you've never used (or don't like a certain tool) doesn't mean its the wrong solution to a particular problem.

      P.S. - The one thing I will give Unix is that its simple design helps facilitate understanding it. You can learn a lot from reading the source and working with the OS - its very much tied to its hardware.

    6. Re:Good for them by CAIMLAS · · Score: 2, Insightful

      Good god, you're not terribly aware of the other side of the fence, are you?

      The problem with fixing (and knowing) a Windows system is many times more complex than fixing a *nix system. It's not because the system itself is inherrently more complex, it's because it's more heavily obscured and much less documented.

      But that's besides the point. A windows system -is- more complex, and needlessly so. The people that designed the Windows registry don't even understand it completely, how are windows admins or anyone else?

      The problem *nix admins have with windows is because it's -not- as good as a *nix variant in terms of administration. Admin tasks take many, many times longer on a windows system than a *nix system because the fundamental tools and framework for providing those functions isn't there. Simply put, Windows wasn't designed for ease of administration in a professional environment, it wasn't designed for ease of access to system functions, and it wasn't designed to do anything but increase the coffers in Redmond.

      And don't think you can refute this saying something like, "But longhorn will..." - it's too little, 10 years too late (and it's still only rumored, at that).

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    7. Re:Good for them by _Sprocket_ · · Score: 2, Insightful


      As I said, its the misconception people have that Windows is 'easy', and anybody can do it.


      But as you point this out, you have to keep in mind just who is fostering this perception.

      First, it comes squarely from Microsoft. Windows has always been marketed as the easy solution. Even on the server. Heck - Microsoft even claims that Windows admins cost less. The implication here is that your admin doesn't have to be as experienced or skilled.

      Secondly, Windows proponents will often push "ease of use". Whenever the *nix vs. Windows jihad starts up in some conversation in these parts, there is always the Windows proponent talking about how much easier it is to set something up in Windows. Or they talk about the ease of a GUI configuration (what's amusing is seeing one talk about how advanced the Windows GUI config utilities are while another says that critics just don't understand the depth of Windows since all they know about is the GUI). I don't bring this up to summon the jihad or get in to a debate about configuration options. The point is that "ease of use" becomes the first and foremost point in a lot of these conversations.

      I agree that Windows is much more complex than many seem to believe. But this perception has nothing to do with the *nix camp.


      So they try, and fail; for the most part, its hard NOT to work in IT and have no exposure to Windows, but they think being an expert on one platform somehow makes them an expert on another, and so to mask their lack of knowledge, they just say Windows is stupid and not made 'correctly'. Never mind the fact that they dont really understand that most things access the registry in some way, or how to deal with the APIs, proper Windows troubleshooting, etc.


      When I was saddled with a Windows server again, I was finding myself asking my Windows friends lots of stupid questions. I had forgotten a LOT over the last few years. But even as I remembered, re-learned, and outright discovered new things about Windows... I still find myself despising the platform. I admit my bias. But that bias comes a dislike for the Microsoft / Windows way of doing things (or more accurately, an appreciation for the *nix way).

      Sure. Some Windows critics could probably learn from some time in front of a Windows server. But you're too quick to dismiss all this expressed dislike for Windows as ignorance of the platform.


      Im saying if you have to do something, do it right. Complaining doesnt fix problems, nor does sticking your head in the sand and acting like something is 'wrong' just because they dont want to understand it. As I said, theres nothing wrong with not wanting to learn it, but acting like it's worthless knowledge is insulting to those who actually know what they are doing.


      I guess I have to agree here. When my new job had me facing a rather horrid Windows system, I buckled down and did what I had to do to administer it. That's involved a lot more Windows knowledge than I've had interest in. And I definitely value the advice from my Windows-knowledgeable friends in dealing with this albatross.

      But I still think the Windows way is "wrong". And not from a lack of working with it.
  2. Fake "engineer" certs should not be legal by Rex+Code · · Score: 5, Insightful

    I went to a real engineering school to learn Computer Engineering (a 4 year EEE + CS program), and every time I see a company create a certification program that takes less than a month to become an "engineer", well... it makes me cringe. I know in other parts of the world that it's not legal to abuse terminology like that, and wish the US would adopt some similar standards. This dilutes the prestige associated with earning an actual engineering degree (really, there is some!).

    I know the difference between a real engineer and a fake one, but I'm not so sure the average guy on the street understands the distinction. I also suspect people in hiring positions give a lot more weight to a certification that pretends to be an engineering degree than they really should.

    1. Re:Fake "engineer" certs should not be legal by JayAEU · · Score: 2, Insightful

      This is indeed very true. The company I work at also has this tendency to look for such pseudo-engineers. Being an engineer myself (MSc. in manufacturing automation) I keep telling them to look for real qualification that lasts, not just short lived and narrow focused stuff that can be acquired in a few weeks' time.

      Becoming a real engineer takes time - a lot of time - digging down deep into the core of the matter, not just scratching the surface and pretending to know what's going on.

      Unfortunately, the original poster is absolutely right in assuming that the average Joe on the street (and it seems in some personnel departments as well) does not make the right distinction in this regard.

    2. Re:Fake "engineer" certs should not be legal by BeerMilkshake · · Score: 5, Insightful

      Of course, if IT became a Profession (like engineering, medicine, law, real-estate, accounting,...) then there would be a regulating body with real power to stop people from practicing when they do not have the necessary credentials.

      Such a body would also help educational institutions in preparing their curricula and would promote ethical practice.

      A Profession of IT would also elevate the standard of practice and protect our careers a little better than the current 'wild west' system.

    3. Re:Fake "engineer" certs should not be legal by JayAEU · · Score: 2, Insightful

      I think you're missing the point here. The term "engineer" as it is used nowadays implies that someone knows the scientific theory and is able to apply it in real world situations.

      Most certifications abuse the term "engineer" as far as the scientific theory is concerned. The attendants are fed with pseudo-information and half-truths, leading them to believe they are worth their salt in real-life situations.

      Suffice it to say that I have seen enough of those "engineers" fail when confronted even with the simplest of their original test scenarios.

    4. Re:Fake "engineer" certs should not be legal by Graelin · · Score: 4, Insightful

      I went to a real engineering school to learn Computer Engineering (a 4 year EEE + CS program), and every time I see a company create a certification program that takes less than a month to become an "engineer", well... it makes me cringe.

      That's funny, I get the same feeling when I hear people claim that their 4 year degree makes them an engineer. Last I checked you need to know the math and also be able to apply it. (It's that last part that university cannot teach.)

    5. Re:Fake "engineer" certs should not be legal by Daniel+Dvorkin · · Score: 4, Insightful

      The problem, IMO, is that people want the word "engineer" to mean all sorts of things it shouldn't. My job title is Software Engineer -- but it shouldn't be; it should be Programmer, or Developer, because IMO what I do isn't engineering at all. (What I really do, when you get right down to it, is applied math.) To me, the crucial distinction is, or ought to be, that an engineer makes actual physical objects, whether those objects are airplanes (AE), buildings (CE), cars (ME), or circuits (EE). The expansion of "engineering" into things that have no physical existence, such as software, goes hand-in-hand with other abuses of the language such as calling widgets on a Web page "technologies." I'll barely buy "network engineer," since a large part of setting up a network is determining its physical layout. But people who maintain networks others have set up aren't engineers; they're mechanics.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    6. Re:Fake "engineer" certs should not be legal by iggymanz · · Score: 2, Insightful

      yes, they should be called "technicians" and "operators".....I've held the title of "software engineer" and "systems engineer" before, but that's baloney. I've also held real engineering jobs & have degree in "engineering physics", and that's a whole different world altogether.

    7. Re:Fake "engineer" certs should not be legal by feronti · · Score: 2, Insightful
      (What I really do, when you get right down to it, is applied math.)
      Isn't engineering by definition applied math? Engineering isn't about building things. It's about designing things. For example, I know a couple of automotive engineers who got into that field because they loved to work on cars. They were quite disappointed to discover that most of what they did as engineers involved nothing with the physical cars themselves. They were merely applying known principles to design cars that others built.

      The main problem with software engineering is not that it's not engineering... it's that the principles of design are still very much in flux due to the youth of the discipline. I have the good fortune of attending a university where computer science is a part of the engineering school, and while we don't get nearly the level of respect as the other engineering disciplines (which is fair, my university's primary mission is actually to supply the automotive industry with mechanical and electrical engineers) we are still considered engineers by anyone outside of the school of engineering. We have to complete the same mathematics core as the engineers. The only real difference is that the artifacts we create are not physical.

      Defining engineering as merely physical objects implies that anyone who builds software does not do a thorough analysis of the design. This is the kind of attitude that makes people think that good programmers are a dime a dozen.

  3. Bleh by Anonymous Coward · · Score: 3, Insightful

    Oh great. Another reason for non-engineers to call themselves engineers.

  4. Re:Novell had a Linux track years ago by iggymanz · · Score: 4, Insightful

    Since the only *real* purpose of a cert is to give companies "good vibes" about you or get your foot in the door, who cares what the real training is? A person has good troubleshooting & admin skills, or they don't. Other than that, if your cert is printed on absorbent paper you could wipe your ass with it. I've worked with too many people who had more certs than Seymour Cray who were dumber & more useless than a bag of rocks. Anyway, if Novell/SuSE takes off, having this cert could open door for you, and it's then served its only purpose.

  5. How long does it last? by iamsure · · Score: 4, Insightful

    The Novell page doesnt seem to reference how long the cert is good for - even in the faq..

    Anyone know?

  6. This is not new by voideng · · Score: 3, Insightful

    Novell mentioned it was comming in '02 and announced it at Brain Share '03.

  7. Certifications are overrated by Robber+Baron · · Score: 3, Insightful

    The only reason to have a certification is to be able to prove to someone who doesn't have a clue about computers that you might know what you're doing, ie: it's something to flash the HR lepton who has concocted a bunch of hiring "qualifications" that they themselves don't understand. I've held an MCSE for nearly 5 years now and I still have yet to be asked to produce it. I'm just glad somebody else paid for it. A certification is no replacement for the problem solving skills that only experience can teach you, but try telling that to some HR drone. That's one of the reasons I decided to go the self-employed route. For some weird reason, it's a hell of a lot easier to bid a support contract for a company than it is to get hired by them, even though you may be doing the exact same thing for more money!

    --

    You're using her as bait, Master!

    1. Re:Certifications are overrated by gr8fulnded · · Score: 4, Insightful

      I suppose it depends where you work. I could care less about fancy titles myself, but like you said, it gives HR the warm and fuzzies. However, dollars give me the warm an fuzzies and for whatever reason, the gov't loves to pay for certs (I'm a gov't contractor).

      Yeah, I'm solaris 8 certed. Woopdeefuckingdoo. I was bored and the testing center was there. For $300 out of my pocket (reimbursed by my company), I can make an extra 5k a year. You do the math.

  8. This has nothing to do with SuSE by Anonymous Coward · · Score: 2, Insightful

    The CLE program was well underway long before SuSE was acquired, the certification is to test candidates knowledge of running Novell services for linux (which is now in beta testing, and we here are a beta site). As you probably know by Netware 7.0 Novell has the intention to offer all services on either the netware kernel or linux kernel. That is what this certification is about, not SuSE, please get the facts straight.

  9. Re:Give me a break by Anonymous Coward · · Score: 1, Insightful

    Sort of like a physician is "just" someone who passed some exams and pays dues to the AMA every year?

  10. I'm proud to be lazy! by WolfVenge · · Score: 4, Insightful
    The adjective lazy means, according to Merriam-Webster Online: disinclined to activity or exertion

    I suggest that any good technically competent person is lazy, and someone I'd rather hire. Put yourself in a supervisory role for a moment. Who would you rather hire:

    1. the person who enjoys running from fire to fire and is demonstrably active at all times
    2. The person who works diligently to prevent those fires from occurring in the first place.

    The second person, disliking the "fireman" syndrome so common in support departments, would have to be defined as lazy in that he/she is disinclined to work putting out fires. One can argue that the time spent in preventing the fires in the first place disqualifies the person from being called lazy. It's a shame that upper management tends to look at hard numbers, and it is much more difficult to provide a number for prevented problems, than it is to provide a number for solved problems. Upper management sees that person A solved 30 problems, person B ( the lazy one ) solved 10 problems in the same time period. However, management often does not quantify the extra work person B did to prevent those 20 problems, they just give person A great praise, and quietly replace person B for "underperforming".

    Suffice it to say, I'd rather hire the lazy ones.

  11. Re:The Price of Doing Certs by drinkypoo · · Score: 2, Insightful

    I'd want in my contract an exit method where if they canned me for any reason other than a breach of law that I wouldn't pay a dime. Of course that might make them disinclined to hire me, but the fact is that they can train you and then fire you if they so desire. It makes sense to require you to work there for a while, but if they can shitcan you, then it's a losing proposition.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  12. Re:The Price of Doing Certs by unshaven23 · · Score: 1, Insightful
    Ah, the endless loop. When employed, certs are not needed, when unemployed they are not affordable...

    You're looking at it from the wrong perspective. Simply walk up to your boss and have the following conversation:

    You: "I was talking to a customer and he was wondering if we have any certification to prove that we are as good as we claim to be."
    Boss: "Does anyone at our company have certification?"
    You: "Employee X has Cisco, and Employee Y has MSCE, but the rest of us are all uncertified."
    Boss: "Hmmmm, that should be good enough."
    You: "You know, a few weeks back I read about LPI certification, and a lot of our customers are showing intrest in linux as of late. I checked out the example exams and they're not that difficult. It might be handy to have that in our company as well."
    Boss: "Let me think about it."

    Then stay on his good side, and make regular inquiries about the certification. If all goes well, you should be able to enroll for the exam in about a week or 2.

    This gives you two advantages:

    1. You are less likely to be fired next crisis, as the company has invested in your certification, and that certifaction goes with you if they throw you out.
    2. If you should get fired, you can always mention it on your resume, as many employers love the free certified staffmember to improve the company image.
  13. Three Anecdotes - All True-Third wheel training. by Anonymous Coward · · Score: 1, Insightful

    " An instructor in an SQL Server class related the tale about a forklift operator who got laid off. He kept seeing job ads for "MCDBA" and asked around to find out what that meant. He didn't have the cash to actually take the courses but he bought the books and passed the exam (through luck, I guess) on the 14th attempt. He landed a job making $160K per year and kept it for six months before they realized he didn't know beans. He ended up $80K richer, though."

    That's one of the things I like about OSS. You don't have to "fake it". You can go get your books and "real software", with "eBay hardware", and practice to your hearts content. Want to learn Java? No problem. Want to learn EJB? No problem. Build your own CISCO network. So is there any material out there for the person who wants to take that route to certification? Or to a career for that matter?

  14. I hope theyre really tough by mnmn · · Score: 2, Insightful

    I hope those certs dont just become anoter set of certs you can have after 3 weeks of exam crams. They should be able to seperate the boys from the men the way CCIE does.

    I think we desperately need tough Linux certs to aim for, certs which will in time be respected enough to be of greater weight than the college degrees. Right now theres no standard way for a company to look for a highly skilled linux technician who can be creative, knowledgeable and original in solving problems. They just go for students from the best universities who have taken lots of java pascal and ada courses.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky