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."
That this certification is worth more than my SCO Master ACE. Cheers,
Step 1. Write code. Step 2. ??? Step 3. Profit!
From the Novell site:
the test
The Novell Practicum test for the Novell Certified Linux Engineer (Novell CLE) will require you to prove your Novell Nterprise Linux Services knowledge in a "real life" setting. Your knowledge of both Linux and Novell Nterprise Linux Services will be tested.
The practicum is basically a remote connection to a live server bank with Linux installed. Using the remote access session, you will be given a scenario with tasks to complete. These tasks will include configuring Novell Services on Linux, performing basic Linux tasks, and may even get into some troubleshooting.
You will need to perform these tasks just as you would in a real environment. You will be evaluated automatically on each of the servers and will you receive a pass or fail exam result. The length of the exam is estimated to be about two hours.
There is no "written" test anticipated at this time.
For once, there is nothing written, and you actually have to demonstrate proficiency! No more "wannabes" (*cough*MCSE*cough*) merley memorising and getting the Certification.
libertarianswag.com
I was checking the SCO website and came across their "SCO certified IP lawyer" certification webpage.
What do you guys think? Worth getting?
Novell had a Internet track to the CNE years ago, back in the days when Netscape Enterprise Web Server ran on Netware. The classes were horrible and I feel bad for anyone that paid to take them.
It appears from the website that this is just a single 5-day course on Novell Nterprise Services for Linux (Netware File and Print and Directory Services running on Linux), not a course on SuSE or Ximian. They suggest (but do not require) that you get a LPI certification first before taking the class.
It's kind of a stretch that they are calling this a Certified Linux Engineer, since there is no actual Linux training involved, just training on Novell's product running on Linux. In fact, the course material says that you should know Linux before taking the course.
So, unfortunately this seems like yet another empty certification, and shame on Novell for calling someone a Certified Linux Engineer when all they did was take a 5-day course on one of Novell's Linux products.
- "When you want something with all your heart, the entire universe conspires to give it to you" -Paulo Coelho
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.
Can't Slashdot think up any new jokes? Of course not.
... so only the "/her" part was new)
OK, here's something new...
Q. Why did the MSCE cross the road?
A. Someone told him/her to.
Q. Why did the Certified Linux Eng. cross the road?
A. Someone told him/her not to.
(ok
All sigs should be as funny as possible, but no funnier.
or for only $1250 you can sign up for *my* course where we even show you how to build your own software from source code with the magic of "configure, make, make install"
Egads, you've never worked in an environment with more than one server, have you? If I caught one of my guys doing that, I'd either fire him (if at my civilian job) or Article 15 him (if at my Reserve unit). Never, never, ever run "configure,make,make install", take a few extra steps and build an actual package, *then* install the software. This way you can:
* back out easily. 'rpm -e' or 'pkgrm' are easier than grepping through the Makefiles for all of the installed programs and piping that to 'find / -name $1 -exec rm' or whatever.
* copy the package to other servers and install quickly and easily. This allows you create once, install anywhere, and you can even script the installation process.
* avoid overwriting existing files. Any decent package manager will complain if the target file(s) already exists.
God invented whiskey so the Irish would not rule the world.
This has been available for at least 6 months now. Sleep well.
open (SIG, "</dev/zero"); $sig = <SIG>; close SIG;