persistent or not?

ie, if you pass args to me, do I write them to the config file,
or use them for that session only?

I assume you want the former, though the latter is more consistent
with the way commandline arguments typically work.

does:

new install, no commandline argument
   exp: fire up config dialog, record proxy settings and user them, write
networkSetup=1

new install, proxy specified on commandline:
  exp: no config dialog, record proxy settings and user them, write networkSetup=1

existin install (networkSetup=1), no commandline bahaviour:
  exp: no config dialog, use proxy settings if available

existing install (networkSetup=1), proxy specified on commandline:
  exp: no config dialog, use proxy settings, dont record



sound like what you'd expect it to do?

I changed my mind, if you specify an proxy, it gets recorded
as the default proxy.

A little ugly, but doing otherwise will change too much code

changed my mind again, should exhibit the behaviour mentioned above
now.

should be fix in 2.7.13 or higher

well, rhn_register should only be run once, so sending it there should be
permanent.  as for up2date, I don't have much preference either way; I can
easily send proxy info to it, too, or not.

the semantic of "if info is on command line, set permanently" works for me. 
which is it now?  can I get RPMs of the latest to test?

up2date will grab proxy info from rhn_registers config if
it hasnt been ran before.

I'd prefer not adding anymore commandline options to up2date if
at possible.

rpms will be in 7.3-HEAD as soon as porkchop unbreaks itself

I belive this is implemented in a workable fashion. Closing.