Jarod Wilson wrote :
On Friday 14 March 2008 09:15:02 am Gerrard Geldenhuis wrote:
anaconda adds these lines at build time to the eth devices. We have a
sript in the kickstart that configures bonding and remove these lines
from the eth0 and eth2 devices.
What for? Bonding works just
On Wed, Mar 12, 2008 at 10:59:26AM +0200, Pasi Kärkkäinen wrote:
On Tue, Mar 11, 2008 at 05:07:46PM -0400, rhelv5-list@redhat.com wrote:
- Update iSCSI
- Added iSNS client: isns-utils
- Added iSCSI Boot Firmware Table (iBFT) support to boot
iSCSI root
List,
Are they any recommended strategy or cook book for hardening a RHEL5 Server
box. I did the usual, limit access to tty's, eliminated unneeded services
and applications and password aging. Your help will be appreciated. Thanks.
--
Kennie J. Cruz Gutierrez
[EMAIL PROTECTED]
Matthias Saou [EMAIL PROTECTED] writes:
Jarod Wilson wrote :
...slighty OT, but worth mentioning ;-)
Now the other problem I'm having is to get Xen to use VLAN interfaces on
top of the bonded interfaces... not working as expected either yet, and
the Xen network scripts don't make that easy
Thanks for the piece of wisdom... Again, I'm following the rules of my
employer and will forward this information for further evaluation. My intent
is to hardened the core OS (RHEL5) and without creating a flame war.
On Mon, Mar 17, 2008 at 9:37 PM, John Summerfield
[EMAIL PROTECTED] wrote:
On Mon, Mar 17, 2008 at 7:37 PM, John Summerfield
[EMAIL PROTECTED] wrote:
Kennie Cruz wrote:
List,
Are they any recommended strategy or cook book for hardening a RHEL5 Server
box. I did the usual, limit access to tty's, eliminated unneeded services
and applications and password
