I have deep Linux background so I was asking these questions. Redhat Anaconda (installer) uses Kickstart system and generates /root/anaconda-ks.cfg file which is the kickstart file that you can use for later installations. Also as far as I have seen Kickstart seems to be more flexible but I have to admit that I haven't used Jumpstart as much as Kickstart.
But it is good to hear that new installer will provide these functionalities. On 7/23/07, Dave Miner <Dave.Miner at sun.com> wrote: > > Mike Gerdts wrote: > > On 7/21/07, Omer Faruk Sen <omerfsen at gmail.com> wrote: > >> Hi, > >> > >> Does jumpstart profile file created during installation with Sparc > DVD/CD so > >> I can use it for later use (i mean reinstalling server using this > profile) ? > > > > No such profile is created. > > > > One will be by the new installer. > > >> If yes where is the location of it? > >> > >> By the way is there any visual jumpstart profile creator? > > > > Not to the best of my knowledge. I think that this was something that > > was (is?) considered for the next generation installer. A design > > document for it was circulated a year or so ago. > > > > Yes, we do intend to provide one. > > >> Thanx for replies, > > > > Thanks for asking. This is certainly an area that could use some > > work. In comparison to Kickstart with Red Hat, the configuration of > > jumpstart seems rather disjoint and complicated. I'm quite fond of > > the fact that anaconda generates a ks.cfg file that will can be used > > to create identical servers or serve as a basis for configuring others > > that are nearly identical. > > > > For some platforms, N1 System Manager may be an option to consider at > the moment. > > http://www.sun.com/software/products/system_manager/index.xml > > Dave > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/install-discuss/attachments/20070723/4be57fe3/attachment.html>
