> IMO, as long as the user has to maintain the DCSS it will never catch on.
Exactly. It's beneficial, but the lack of tooling and implementation integration makes it a PITA. We got plenty of those. > The software vendor must decide what should/shouldn't go into the DCSS, > not the sysprog. When you get a service update, the DCSS needs to be re- > built automatically if the sysprog has configured its use. And I want to > configure its use in only one place. I don't want to have to say 'yes' > in File A, and then the name in File B, and for the system to load it in File > C. Compare to the trigger-based initrd auto-regeneration in modern RHEL, or similar in Debian. That's how it *should* work. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
