> The requirement that a version upgrade requires a full re-install and
then
> copying of the data is one of the big issues I see with bringing Linux
> into
> a System z shop and having experienced z folks work on it.
If you mixed application and data with system files, you'd have the same
problem on any IBM OS as well. If you maintain a clear separation by
design, then total replacement/upgrade of Linux is as straightforward as
it is with z/OS.
I think the problem is more with building the level of experience of how
to maintain a system so that total replacement works than the OS itself.
Mother's First Law ("thou shalt not mix your stuff with IBM's stuff")
applies here -- you'd never put user data on your MVS sysres or in the
IBM-supplied libraries; ditto here.
It's not a fault of the OS. The tools do what you tell them to do. The
defaults aren't as mature, but that's not the tool's fault. If you have
a good set of conventions on how you handle data and application
configuration, then it's easy. If you don't, then it's hard. Those old
MVS/SP systems that have migrated have developed those conventions to an
art; now it's time to do the same for Linux.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
