Hi Dave,
Yes bootp is the depreciated DHCP predecessor both of which are
different than the Sun bootparams stuff - thank you!
Well my thought was someone could easily load the Solaris media
into a spare partition (i.e. coopt another OS' swap partition for a bit)
and load the bits to install on to disk (say from a downloaded iso), but
without having to actually install Solaris (a lot easier to ask a customer
give us around 3 gigs on a disk for a little while than, "Hey install this
whole OS." However, as it's widely documented how to serve JumpStart bits
off Solaris (vs. some other OS) it would be relatively similar and
straight forward was the hope.
I'm afraid despite my system administration work I may not realize
quite all that'd be needed to do this (i.e. I'm not sure what package
provides and serves /etc/bootparams which is needed even for a PXE boot I
believe).
So, my thought was if the live CD has NFS, TFTP, DHCP (instead of
bootp - since a DHCP server can serve bootp requests), and
whatever serves bootparams then one could use the live CD as an ad hoc
JumpStart server pretty easily and for someone in say the Try & Buy
program without a DVD drive, ad hoc is their key requirement. Similarly,
from a sys. admin. perspective being able to provide a quick JumpStart
server can be helpful too.
Thank you,
Clay
On Fri, 14 Sep 2007, Dave Miner wrote:
> Clay Baenziger wrote:
> > I think having NFS and and TFTP services on the live CD (since BootP was
> > being included too) would be very useful for our customers who get
> > machines with out DVD drives. This would allow them to setup a
> > JumpStart server relatively easily. Unfortunately DHCP is
> > large, so they would probably have to provide that on their own, but TFTP
> > is pretty small and necessary:
>
> I'm not sure I see how this CD is helpful to such a situation; it won't
> have anything on it that resembles the media contents
> setup_install_server is designed to use. Can you elaborate on what
> you're thinking?
>
> (nit: you meant bootparams above, not BOOTP, which is the parent of DHCP
> and thus a different protocol entirely).
>
> Dave
>
