Re: Keeping up with the changes

Kaj Niemi <kajtzu@xxxxxxx> · Mon, 30 Jan 2012 18:12:45 +0000

Using ksdevice=bootif or ksdevice=link when kickstarting makes one not care about interface naming. The link parameter is problematic if you have a crapload of interfaces connected and need to make sure a specific card is the one that is booted from while bootif uses whatever interface you have defined as the PXE interface. Works well in my experience.
As for other vendors I'm not sure.

I deal with vendor specific things (hp asm, dell omsa, etc.) only after kickstart has finished in a firstboot -type installation script where the vendor is determinted by using dmidecode. :-)

Kaj

On Jan 30, 2012, at 16:46, Cole, Jim wrote:

Is this applicable for all HW vendors with RHEL 6u2 or just Dell? If you work with a variety of vendors like I do..thats a concern. I don’t want to try to deal with determining the vendor during the kickstart.

Thanks!
Jim Cole
Senior Technical Engineer
McKesson Provider Technologies
jim.cole@xxxxxxxxxxxx
Office: (515) 619-9820
Live Meeting URL:  Here
Conference #: (877) 684-9625 Participant code: 732158

From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Kaj Niemi
Sent: Monday, January 30, 2012 10:27 AM
To: Discussion list about Kickstart
Subject: Re: Keeping up with the changes

I believe this is mentioned at least by:

- Dell in their release notes for each platform
- Dell PowerEdge blogs, Meaningful names for network devices in RHEL 6.1 on Dell systems ...
- Dell OS And Application notes, http://en.community.dell.com/techcenter/os-applications/w/wiki/red-hat.aspx
- Dell whitepapers, http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf
- RedHat in their technical notes for RHEL 6u1 and 6u2 (pages 7, 189)

etc.

From my POV there wasn't much to change and now the name of the interface (em1) corresponds to interface labeled Gb1 on the back of the server.

Kaj

On Jan 30, 2012, at 10:37, Moray Henderson wrote:

From: Kaj Niemi [mailto:kajtzu@xxxxxxx] 
Sent: 29 January 2012 01:40

You did not mention which rhel version you are using but interfaces on dells in rhel 6.1 will show up as em1, em2, etc. by default instead of eth0, eth1. Both dell and redhat mention it in their docs.

Pretty soon I’m going to have to start updating the software I develop and maintain for RHEL 6.  Apparently, I’m going to have to rewrite the entire set of perfectly-working network code because many (but not all) of my customers use Dells.  What’s the best place to keep up with changes like this - to learn not just what they are, but the reasons for them and the lists of exactly what hardware combinations produce which responses in the OS?

Moray.
“To err is human; to purr, feline.”
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list

_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list

Attachment:
smime.p7s

Description: S/MIME cryptographic signature
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list