On 2011-10-13 16:51, ~Stack~ wrote:
> I am attempting to build a group of systems that boot off of PXE and
> auto-install with a kickstart file. I previously used a bundled package
> that for certain reasons is no longer applicable to the new system. So I
> am learning a lot about what happened behind the scenes of the bundled
> package.
>
> This particular stumbling block is: I have a mixed environment of 32bit
> and 64bit machines. I would like for the kickstart menu to auto-pick
> 32bit or 64bit. Is this possible?

Not with the kickstart alone.  The install kernel's architecture must 
match that of the install tree, so your DHCP server has to supply 
kernels and boot options that match that of the architecture you want to 
install.

If you set up a pxelinux-based PXE-boot system then you can do things 
such as display a menu (boot normally, install x86-64, install i386) for 
a few seconds, skip directly to a chosen action using a hardware 
address-specific symlink on your TFTP server, or choose an action based 
on the result of a simple hardware probe.  Then you could use the same 
DHCP range for every system.

If your server can supply systems with a 
"method=http://10.1.1.11/scientificlinux/6.1/$basearch/os" directive for 
the correct architecture (whether via different DHCP options or a 
pxelinux system) then you can use a common kickstart file for both 
architectures by writing the architecture-specific bits to a file in 
%pre and %including it in the right place:

firewall --enabled --ssh
install
rootpw --iscrypted mypasswordhash
auth  --useshadow  --passalgo=sha512
# ...
reboot

%include /tmp/repos

%pre
basearch=`uname -i`
cat << EOF > /tmp/repos
url --url="http://10.1.1.11/scientificlinux/6.1/$basearch/os"
repo --name=sl-security 
--baseurl=http://10.1.1.11/scientificlinux/6.1/$basearch/updates/security
EOF
%end

%packages --nobase
openssh-clients
%end

-- 
Garrett Holmstrom