On Mon, 2008-02-04 at 13:56 -0600, Nicolas Williams wrote: > What about class action scripts that can't run in alternate boot / LU?
Well, JDS doesn't have any so an example would help me picture it. I would normally recommend using class action scripts when it's simple enough to be scriptable and then there should be no problem with altroot or LU. > Does not providing a post-run mode for class action scripts mean that > postrun scripts will be more complicated than they have to be? I don't see why they would be, but that's probably because I can't think of a good example for the CAS that needs a post-run mode (or I misunderstand you question). The problem that postrun tries to solve is updating binary files or updating text files based on information extraced from binary files. We have binary executables to do the work, we just need to execute them at the right time. The postrun scripts themselves tend to be very simple, for example: ( echo 'test -x /usr/bin/scrollkeeper-update || exit 0'; echo '/usr/bin/scrollkeeper-update' ) | $BASEDIR/lib/postrun -b -u -c JDS Laca
