Manually update them via the firmware. The XMLRPC portion only shows you when we update the version and we haven't focused our attention on keeping this current. It's one of the final items to complete before we release. And when I say complete, it really means hooking in the builder scripts closer to this system to automatically generate binary diff updates and bump the version that you query via XMLRPC.
Scott On 10/18/05, Chris May <[EMAIL PROTECTED]> wrote: > Bill Marquette wrote: > > >On 10/18/05, Chris May <[EMAIL PROTECTED]> wrote: > > > > > >>Is there a way to get the XMLRPC to work properly or is that not fixed > >>yet. I would like mine to function, even if the server is down, is there > >>a way for me to host my own version of XMLRPC locally on my apache server? > >> > >> > > > >If what you perceive to be broken is firmware updates, then it's > >working properly, we haven't updated the version for autoupdates in a > >while. What XMLRPC function are you talking about? > > > >--Bill > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > I wanted to get the updates feature working either for the global cvs or > just off a local machine via a web server running xmlrpc. I would like > this becasue I ahve a few boxes running pfsense and want to keep them > all up to date > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
