QUESTION UPDATE: Can Jumpstart and Kickstart Co-Exist??

From: Chris Denneen (sunmanagers@ghostspace.com)
Date: Thu May 22 2003 - 09:12:02 EDT


OK,

With many responses I see that I was totally clear on our needs.

Currently we are using Jumpstart in our environment.
To add a client to the jumpstart server we use the command:

/opt/jumpstart/solaris8_install/Solaris_8/Tools/add_install_client \
-e <MAC> \
-p <SERVER>:/opt/jumpstart/profiles \
-c <SERVER>:/opt/jumpstart/profiles \
-i <CLIENT IP ADDRESS> <CLIENT NAME> sun4u

then boot the client with:

ok> boot net - install

When complete the server boots the disk as primary and has its static
information (hostname, ip-address) written out to the machine.
ie.
        "<CLIENT IP ADDRESS> <CLIENT NAME>">>/etc/hosts
         "<CLIENT NAME>" >>/etc/hostname.<INTERFACE>

I am looking to start rolling out some RedHat Systems in our environment
and would like to have the system installs the same (no room for human
error. ie. causing differences in the system layouts/configs).

We DO NOT run DHCP in our environment, nor do we want to.
The only thing is our Jumpstart Server is a Solaris 8 Server running,
        tftp/rpc.bootparamd (RARP request from client to server to get
        client information)

Now is there any way to by x86 Hardware (for example Dell PowerEdges),
that will allow to do network installs? Am I going to need to use a
Floppy for EVERY system I want to install?

I would like to console to a "PowerEdge" (remotely),
run a "network install" command. And it gets its IP,hostname by checking
its MAC ADDRESS on some server (ie the same way our Jumpstart works).

When done with an install I would like to be able to reboot the system
without it relying on a network connection (ie. need DHCP, BOOTP, etc)
to boot EVERYTIME.

Is this possible and how?

I am trying to rollout this Linux Environment:
  1. in the same way we have our Solaris Environment.
  2. in a centralized administration.
  3. being able to co-exist on the same subnet.
  4. without causing any possible problems with the infrastructure.

Maybe I am wrong about asking about setting up a "Kickstart" server.
I know all I will need is something to tell the PC Hardware what it's
IP,hostname will be and where to find its ks.cfg. From there everything
else can be done off the network over NFS.

So if I need to just export RedHats dist over NFS

/export/kickstart
                --> dosutils
                --> images
                --> isolinux
                --> RedHat

and add a new dir call "boot"
                --> boot

which contains all the proper information for network boot/install.
and also copy the ks.cfg inside of boot. ("boot/ks.cfg")

Thanks for everyones help in advance.

Cheers, Chris
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:27 EDT