|
I have a linux PXE server serving up BIOS flash images, utility boot
disks, linux live images and the Unattended server. I submitted a question
regarding setting up the database earlier. I thought that the DB would be the
answer to my problems, but I’ve run into so many snags. I don’t like that Unattend wants to partition and format the
drive before I pick the OS. This doesn’t make any sense to me, as
different OSes (and OS distribution points) may require different partitioning
schemes entirely. I’m learning a little bit about config.pl and how
lookups work, but all my problems stem from install.pl, which is significantly
complicated by my lack of understanding the perl methodologies used. It’s
mainly with the order in which things are done, and I understand it’s all
done this way for a reason. I just wish it didn’t completely smash my
scheme. Right now, install.pl asks for the ComputerName, FullName, OrgName, a
partitioning scheme, a format, and an MBR. And it will partition and format the
drive before even considering which OS to use. I would very much like something
like this: OS/ w2ksp4a/i386/… w2ksp4b/i386/… w2ksp4c/i386/… Site/ w2ksp4a.txt w2ksp4b.txt w2ksp4c.txt When a system boots off the network and I selected Unattended, our
assembly guys don’t need to be prompted for anything other than which OS folder
to use. It would load the right unattend.txt file based on the name of the OS
dir. This file includes all the partitioning and formatting options. If there
is a conflict with this method on a fundamental basis, please let me know as I
have to find something else. The more I use unattended, the more I realize it’s
probably designed more for the system administrator who has re-installed office
workstations WAY too many times. I’m using it to deploy brand new
machines that subsequently get shipped out. I hope I can find a way to make
this work. -Jimmy |
