Jumpstart on Solaris 10 - things to start
in [Solaris]
|
From: BertieBigBollox on 29 Sep 2009 05:48 Trying to get Solaris 10 set up as a jumpstart server. Done it before successfully on Solaris 9 but never on Solaris 10. I understand that system processes are a little different on 10 with the introduction of services. I've created /tftpboot directory, edited inetd.conf to allow tftp (and then run inetconv). If I do inetadm now it does appear to have added tftp to the bottom. Rebooted. Should I be able to see the tftp and in.rarpd services using ps-aef now. Or not?
From: Casper H.S. Dik on 29 Sep 2009 06:06 "BertieBigBollox(a)gmail.com" <bertiebigbollox(a)gmail.com> writes: >Trying to get Solaris 10 set up as a jumpstart server. Done it before >successfully on Solaris 9 but never on Solaris 10. >I understand that system processes are a little different on 10 with >the introduction of services. >I've created /tftpboot directory, edited inetd.conf to allow tftp (and >then run inetconv). If I do inetadm now it does appear to have added >tftp to the bottom. Rebooted. >Should I be able to see the tftp and in.rarpd services using ps-aef >now. Or not? Not tftp, it is started by inetd when there's a call to tftp. You can test whether it is enabled by using svcs: % svcs '*tftp*' STATE STIME FMRI online Sep_23 svc:/network/tftp/udp6:default Rarp should be run, but by enabling "rarpd": svcadm enable rarp en possibly also bootparams: svcadm enable bootparams Note that you can also use DHCP which I personally find easier and which is required, IIRC, for x86 clients. Casper -- Expressed in this posting are my opinions. They are in no way related to opinions held by my employer, Sun Microsystems. Statements on Sun products included here are not gospel and may be fiction rather than truth.
From: BertieBigBollox on 29 Sep 2009 06:44 On Sep 29, 11:06 am, Casper H.S. Dik <Casper....(a)Sun.COM> wrote: > "BertieBigBol...(a)gmail.com" <bertiebigbol...(a)gmail.com> writes: > >Trying to get Solaris 10 set up as a jumpstart server. Done it before > >successfully on Solaris 9 but never on Solaris 10. > >I understand that system processes are a little different on 10 with > >the introduction of services. > >I've created /tftpboot directory, edited inetd.conf to allow tftp (and > >then run inetconv). If I do inetadm now it does appear to have added > >tftp to the bottom. Rebooted. > >Should I be able to see the tftp and in.rarpd services using ps-aef > >now. Or not? > > Not tftp, it is started by inetd when there's a call to tftp. You > can test whether it is enabled by using svcs: > > % svcs '*tftp*' > STATE STIME FMRI > online Sep_23 svc:/network/tftp/udp6:default > > Rarp should be run, but by enabling "rarpd": > > svcadm enable rarp > > en possibly also bootparams: > > svcadm enable bootparams > > Note that you can also use DHCP which I personally find easier and which > is required, IIRC, for x86 clients. > > Casper > -- > Expressed in this posting are my opinions. They are in no way related > to opinions held by my employer, Sun Microsystems. > Statements on Sun products included here are not gospel and may > be fiction rather than truth. Casper, Thanks. It appears to be as easy as that. Its actually a Sol9 sparc (single card machine) install that the jumpstart server, a laptop, is going to be used for. We used to have an old laptop running sol9 as the jumpstart but this is being replaced with a newer model. Though it would be an ideal time to upgrade the server to Sol10. Getting the network card working wasnt easy though. What I did then was tar copy the /jumpstart directory from my old Sol9 jumpstart laptop to me new one, Unfortunately, our application cards still need to be Sol 9.
From: BertieBigBollox on 29 Sep 2009 06:49 I also copied the /tftpboot directory off the sol 9 laptop onto the new sol 10 one. Not sure if that was correct.
From: hume.spamfilter on 29 Sep 2009 08:53
In alt.solaris.x86 BertieBigBollox(a)gmail.com <bertiebigbollox(a)gmail.com> wrote: > then run inetconv). If I do inetadm now it does appear to have added > tftp to the bottom. Rebooted. Rebooting isn't really necessary. > Should I be able to see the tftp and in.rarpd services using ps-aef > now. Or not? Not in.tftpd; you wouldn't see it under inetd, either. inetd handles the port, and just fires off the services it manages as needed. inetadm (startd) on Solaris works the same way. (As does inetd on any other Unix...) To get in.rarpd running, you'll need to 'svcadm enable' network/rarp. Then you should be able to see it running. -- Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/ |