"David A. Bandel" <[EMAIL PROTECTED]> writes:
> Bryan J. Smith wrote:
> > Please, please understand the real considerations that LPI has to make.
> > If not, then you should argue to have Matt's job. They are pretty damn
> > big shoes to fill to get things done (I surely do not want it).
>
> I turned that offer down before Kara Pritchard had the job. I know a
> headache when I see one.
LMAO. We're talking migraine territory at times (and, usually, not from the
techie side ;).
>
> Wish you'd make up your mind. I don't need in depth knowledge of any
> boot loader. But for the two x86 disk boot loaders, I need at least one
> question so the information (at a basic level) is taught. Not tested,
> not taught.
Yep. That's pretty close to correct. The important thing to remember for
LPIC-1 is whom we are testing. Does a junior need to know grub _and_ lilo?
probably not. Does a junior need to be aware of both? probably. know both?
possibly not.
definitely by LPIC-2 both need coverage.
I did like one comment in this thread which I'm going to follow up on in a
second e-mail. The rest was quite informative and/or entertaining, though ;)
> > As I said in my first post, I agree that many of these concepts are
> > "advanced" when you start talking about how boot loaders work, where
> > LILO differs, etc... Stuff that isn't even remotely a consideration for
> > LPIC-1. I stated that LILO should be left at a basic level for LPIC-1,
> > possibly identification only, and said it's more "advanced" to get into
> > the differences and the boot concepts that ultimately will be involved.
>
> Even if it's only identification, it will have to be taught. Most of
> the posters want NO LILO tested at all.
And most of the posters aren't thinking like an LPIC-1. They're making it a
little too personal and are probably LPIC-2 or higher (and thinking that
way).
I should point out one other goal of LPIC-1 in this new incarnation. It
isn't an ADMINISTRATOR cert. It is a certification for people needing strong
technical knowledge of the Linux system. This includes developers, DBAs,
power users and admins (and some other marginalized groups I'm not thinking
of right now).
It's at the LPIC-2/3 levels that LPI really focuses on the administrator.
This is also why you'll see most system services have been moved to the
LPIC-2 level.
Only essential (to all; not just administrators) services like syslog and ntp
are covered. plus essential cups for local use and enough mail to get e-mail
off of your local system.
> I don't ask much, but I do ask basics. NFS booting, redboot (I use it
> on all the embedded systems, mostly arm and mips based), that's
> definitely LPIC 2 or even 3.
You got it. with the caveat from above.
> Include LILO or no in LPIC-1 is the question. I've supported LPIC since
> day one since I need a way to evaluate if someone can do a job or not. I
> make no assumptions about optional software, mysql/postgres, myriad web
> servers, mail servers, etc. The test should obviously include some general
> info on mail, web, sql, but I don't expect specific, detailed knowledge at
> that level, just how to stay out of trouble and recognize some basic
> things. I need to know if the individual can work from a command line and
> do basic tasks -- upgrading a kernel and rebooting is a basic task to me.
> If an admin can't take a running server and upgrade the kernel and reboot
> (regardless of whether it is running lilo or grub), and the "certification"
> hasn't tested that, then that cert does me no good as evaluation criteria.
You definitely got it. You sure you don't want this job? :)
What I like about LPIC-1 (in Apr, 2009, that is) is that it is a great basis
for anyone that wants to be a linux techie. It exposes candidates to a
little bit of everything from system installation, maintenance, security,
scripting, SQL, networking, etc...
Someone with an LPIC-1 isn't pigeon-holing themselves into admin roles. They
can use these skills to become great developers in linux, if they like. I'll
share a horror story sometime about a "php" developer from a partner company
(we managed the servers but not the web app). He uploaded an update which
included logging CC info to a log directory. This directory had 777
permissions (yes, a "php on windows" developer) and was accessible to the
world through said web server.
Hmm, I guess I just shared the story :)
Moral: even developers should know about their underlying platform...
if they like their jobs.
Regards,
--
g. matthew rice <[EMAIL PROTECTED]> starnix care, toronto, ontario, ca
phone: 647.722.5301 x242 gpg id: EF9AAD20
http://www.starnix.com professional linux services & products
_______________________________________________
lpi-examdev mailing list
lpi-examdev@lpi.org
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
