James, Take a look at the utfwadm command. This will allow you to copy in a new firmware file. The command handles putting it into the /tftpboot structure and updating the Sun Ray servers DHCP configuration entries.
For example, if a have a new firmware file "beta3.1-P2" in /tmp and wanted to update the firmware for just a single terminal on a shared 192.168.1.0 subnet, I would run: utfwadm -A -f /tmp/beta3.1-P2 -e 080020f5aa36 -N 192.168.1.0 Paul On 02/09/05, James Cuff <[EMAIL PROTECTED]> wrote: > > Hi folk, [just finished with the iTunes and gin (ahem) :-)] > > So, my earlier post about wheely mice, and Otto's great reply made me dig > out the new 3.1beta, but a few strings|grep|whatever have not helped > me out so much. > > Anyone know what I ought to put in "option SunRay.NewTVer" for dhcpd.conf > to take the new CoronaP3 firmware from the 3.1 beta correctly? > > I just don't fancy upgrading the whole shooting match on the server (as > you saw in my last post, the 150 is pretty much part of the family), I > just want to try out the new DTU firmware to see if that bloody wheel > works, as I did by hand for the last patch: > > NOTE: The DTU firmware delivered in this patch has the following version > identification string > > 3.0_118979-01_2005.05.25.15.17 > > > But I just can't seem to find it in the beta. I did force it with the > wrong params and get the 150 DTU to fetch it via tftp: > > Sep 1 23:39:09 douglas in.tftpd[26653]: RRQ from 192.168.1.114 filename > CoronaP3.080020F0B9F5 > > but, no wheel... so I think I must have the wrong NewTVer string. > > Best regards, > > J. > > > > _______________________________________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/sunray-users > _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
