On 02/10/2016 03:56 PM, Mark Post wrote:
>> > Don't purge the old one. Just DEFSYS/DEFSEG the new one and save it. If
>> > the old one isn't being used, it will automatically be purged. If it is,
>> > it will be purged when the last person finishes using it.
> Yes, that's what I tried first. The question is, how do I populate the new
> segment before the old one is purged?
You're trying to change the address of the segment, correct?
Need to make that clear if that is the case, because typically "save a
new segment" is at the same addr.
If that were not the case, updating a segment via DCSSBLK (driver in
Linux) is painless.
+ set it to writable
+ make your changes (e.g. if it holds a filesystem, just
add/delete/rename)
+ set it to read-only
Historically, I would do the DEFSEG and SAVESEG manually. But now ...
why bother? Kernel does all the tedium for me.
I don't recall if I had to explicitly save the updated segment.
Everything was handled via the magical pseudo files under /proc or /sys.
(It has been a while and none of my guests presently have a shared seg
defined so I'm a little fuzzy and vague.)
This is, of course, for a segment that's being re-defined at the same
address.
-- R; <><
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
