Stefan Kopp writes:
> > > more minidisks). I only have to reboot Linux and the
> > > disks are online.
> >
> > You don't have to reboot Linux !!!! It was answered
> > here yesterday, use
> > echo "add device range=xxx-yyy" >> /proc/dasd/devices
>
> Ooops, sorry, you're right. I've always thought I have to reboot when I've
> updated the user.direct because the new adresses were not active. Now I've
> spend some time with the bookmanager, nice thingy. A "#cp define mdisk" returns
> "Invalid option - MDISK", which I've solved with the entry "OPTION DEVMAINT"
> for the designated z/VM user. Now I can enter "#cp define mdisk 205 1 1500
> xyz" - wohaa - Linux recognizes the new disk.
Ouch, you don't want to do that. DEFINE MDISK is intended for a
privileged user to bypass the table of "real" minidisks and just
carve out any extent at all from a device. Dangerous stuff and
rarely needed. Take that OPTION DEVMAINT off the directory entry
because all you need to do is
CP LINK * 205 205 W
on the Linux guest and it will pick up the changes to the directory
which were made behind its back (adjust link mode to taste). This
will also trigger Linux into noticing the presence of the new disk
and it will bring it online (if it's in the list of eligible DASD
devices and hasn't has a "set device range=... off" done on it).
Regards,
--Malcolm
--
Malcolm Beattie <[EMAIL PROTECTED]>
Linux Technical Consultant
IBM EMEA Enterprise Server Group...
...from home, speaking only for myself
