firstboot again: how is it that "reconfig" ever gets run?

[Robert P. J. Day]

  ok, now i'm just confused.  in following through the logic behind
firstboot, i got to /usr/share/firstboot and, ultimately,
/usr/share/firstboot/firstbootBackend.py, which does pretty much what
i expected -- turns off firstbooting via two separate operations:

  1) chkconfig --del firstboot
  2) putting "RUN_FIRSTBOOT=NO" in /etc/sysconfig/firstboot

first, i don't see why anything has to be deactivated via *two*
different operations.  this is just confusing and unnecessary.

  more to the point, though, once you've chkconfig-deleted the
firstboot service, how will it ever be invoked again if you boot and
add the "reconfig" parameter to the kernel command line?  or
alternatively touch the file /etc/reconfigSys?

  i just tested this on a fairly new FC3 system and it did exactly
what i suspected -- adding that parameter at boot time accomplishes
nothing since firstboot is never even invoked to check for that
request.

  is this what's supposed to happen?

rday