RH033 = 44
RH131 = 36
RH253 = 24
Some of the questions were a tad cack. For those that are thinking of taking it, I'll drop my whinges in spoilers:


I had to something similar on a Banyan training course many years ago. A server had about 5 or 6 things done to it that would prevent it from booting up and starting properly. The tools available were a current system backup (these contained the OS data files only and not the OS binaries) and a known working server running the same OS revision from which you could transfer files onto removable media but of course hosting totally different data.Muttley wrote: I got my Red Hat Certified Technician qualification last year (waiting to do the next level now) and the exam is split into two parts. The first part (about 20% of the mark) you are dumped in front of a broken system (has several things wrong with it) and you have to fix it. You can do this in any way you like apart from rebuilding it. They don't care whether you use the RedHat system config tools or hack the config files by hand as long as it works.

2.6.17 is pretty old and the very most recent kernel is 2.6.24.2, plus I think vmsplice support is compiled in by default on many distributions. Nasty."This local root exploit (Debian, Ubuntu) seems to work everywhere I try it, as long as it's a Linux kernel version 2.6.17 to 2.6.24.1. If you don't trust your users (which you shouldn't), better compile a new kernel without vmsplice."




Nope. What you need to do is set up virtual mailboxes for them, ideally using some external server (LDAP, probably) to determine who gets to receive mail, and to handle authentication for mail fetch. That way, only valid users get to receive mail, and they get to use the same passwords for mail recovery as they do for other services using the LDAP server (network shares and the like).RageMatrix wrote:Does each user need to be a Linux user on the mail server?

WTF? I've tried looking for it using "find / -name "c_rehash" -print" but got nothing.configure: WARNING: Unable to locate OpenSSL's c_rehash script in the current
configure: WARNING: PATH. The c_rehash script is included in the OpenSSL
configure: WARNING: package but may not be installed on your system. Please
configure: WARNING: install the c_rehash script from OpenSSL and rerun this
configure: WARNING: configure script.
configure: error: openssl found but c_rehash was not found.
configure: error: ./configure failed for rootcerts

Ah, apparently after a bit of hunting around, I needed to install openssl-perl as c_rehash is apparently a Perl script nowgravy wrote:What linux distro you on?
I installed it all with apt-get on debian
