Bill Anderson wrote:
I took the RHCE exam in 2000 and passed it without taking any of the classes. I had been playing with linux and Redhat for several years. I'll be retaking it next month in Raleigh.On Mon, 2003-02-10 at 09:43, Ted Gervais wrote:On Monday 10 February 2003 10:03 am, Rechenberg, Andrew wrote:I would have to agree with Robert here. The best way to study for the RHCE is just work with Red Hat Linux everyday and think of things to break and then fix them. I've been using Red Hat since 1998 and took my RHCE in late 2001 on RH7.2 and I found that my everyday use of Linux helped more than any written material that I looked through before the exam. If you have been working with Red Hat and/or Linux for a while, the RH300 Rapid Track course is excellent and is good exam preparation if you or your employer can afford it (no I don't work for Red Hat ... yet ;) ).
Thanks Andy for offering your thoughts on getting ready for the RHCE. And if particular mentioning the RH300 Rapid Trace course.
I think that most of us here on the RH list work daily with our systems but don't try and break and solve things. That is a good point, and something I am going to try and do more. Mind you, I normally break a lot of things without meaning to break them, and than I sit in grief for about a week trying to fix it. But, your point is well taken. If you can fix it, than I bet that RHCE exam will seem a bit easier..
Just a side note:
You can use either User-Mode Linux of VMWare to provide yourself with
"breakable" boxen. Fixing broken things is "must-have-xp (experience)".
Like I tell my students ...
"In the old days, there was plenty of opportunity to get 'experience',
and that's how we learned. Nowadays, things are so much more stable
and/or documented that it takes additional effort."
:^)
I've been thinking about making a nice list of things to break, making a
program to manage it, and then provide random breakages to help get
fix-it experience. In my copious spare time, of course. ;^)
Speaking of vmware. It would be nice to come up with a library of "broken" images that people could download and try to fix. Of course, they'd have to be seriously stripped down because few people would want to download a several hundred meg file just to figure out how to get into a system without a password file or something like that! I've got vmware so I could see how small of an image I could come up with.
Gordon
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
