SAVESEG also requires class E. The /save function of the driver was designed assuming the Linux machine has class E privileges (from my reading of the code), as it automatically issues the DEFSEG and SAVESEG for you. If you don't want to give the Linux image class E, then the DEFSEG and SAVESEG both have to be done manually elsewhere.
Thanks for correcting me. I was mixing things up with my idea to move SAVESEG to a new privclass and assign that to Linux. Things start to get tricky. While method 2. may have some unplanned elegance from the developer point of view, I certainly believe method 1 is more useful when you have to deal with real world issues like security and systems management. I also think it would be less confusing for people who are used to dealing with CMS applications.
Rob
