.
>
> So it seemed that bootparams was more of a read-only table.
>
>
>
>
>
> --
>
> *From: *"Jarrod B Johnson"
> *To: *"xCAT Users Mailing list"
> *Sent: *Tuesday, April 2, 2013 8:41:32 AM
> *Subject: *Re: [xc
ing list" Sent: Tuesday, April 2, 2013 8:41:32 AMSubject: Re: [xcat-user] Help with old-style provisioning
For example sake, I presume RHEL 6.3, modify as appropriate.if noderes.netboot=xnba, it's in /tftpboot/xcat/xnba/nodes/Otherwise if noderes.netboot=pxe in /tftpboot/pxelinux.cfg/I
disk,
you should be able to place it into /install/drivers/rhels6.3/x86_64 and
have the 'right thing' happen.
From: Russell Auld
To: xCAT Users Mailing list
Date: 04/01/2013 07:54 PM
Subject: Re: [xcat-user] Help with old-style provisioning
I'm good with that pa
:Re: [xcat-user] Help with old-style provisioning
I'm good with that part, but what I'm after is the lower level stuff like
"kcmdline" and the Anaconda stuff.
Where are the Anaconda stage one configuration files?
From: "Jarrod B Johnson"
To: "xCA
escribes in detail the way xCAT works with the old-style $os-$arch-From: Russell Auld To: xCAT-Users Date: 04/01/2013 09:05 AMSubject: [xcat-user] Help with old-style provisioning
Is there any documentation that describes in detail the way xCAT works with the old-style $os-$arch-$provmethod-$profile
both being omitted is checked for as the more specific matches
are not found) in the respective 'platform' directories ('rh/' for redhat
for example)
From: Russell Auld
To: xCAT-Users
Date: 04/01/2013 09:05 AM
Subject: [xcat-user] Help with old-style provisioning
Is there any documentation that describes in detail the way xCAT works with the
old-style $os-$arch-$provmethod-$profile provisioning system?
We use "nodeset install=compute" and I would like to fully understand
how xCAT decides what gets done to the nodes.
