Karsten Hopp píše v Čt 30. 09. 2010 v 14:02 +0200: > Am 29.09.2010 09:37, schrieb Bern VK2KAD: > > I have hit a couple of obstacles using the Hercules images. Some > > seem to > > be related to me using a Windows Hercules rather than a Linux platform. > > > > First was that the image expands into a full 3390-9 image which is > > over 8GB > > on NTFS. > > > > After dasdcopy this came back down to <500MB so it is now manageable. > > > > After just adding the volume to an existing Hercules config I found > > that the > > image must be on device 120 - I detected conflicts between Fedora and > > other > > distros I have in the same config file if the Fedora disk wasn't 120 !!. > > > > The latest glitch for me is that I cannot logon as root (or anyone for > > that > > matter) > >
> Sorry about the big DASD. We'll use a smaller one next time. or we can upload the compressed image by default and advice to use cckd2ckd to convert it to the uncompressed one if the user has enough disk space The ID of device (120 in our image) carrying the root filesystem is written in /etc/zipl.conf in the image (and stored in the bootloader) so it will always continue to boot on device 120 after finishing the initramfs phase even when you map the Fedora image under another ID. If you want to setup Fedora for other ID, then replace the "120"s in zipl.conf and rerun zipl. Dan ---------------------------------------------------------------------- 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/
