Stephen Powell <[EMAIL PROTECTED]> wrote on 16.07.2008 21:46:51:
> > A "How zLinux boots" paper which describes not only how Linux does
> > things, but how its fits into the VM/CMS/zOS world and compares and
> > contrasts those booth paths with Linux's, and with a nice glossary
> > that translates
Stephen Powell <[EMAIL PROTECTED]> wrote on 15.07.2008 22:51:17:
> I know about the /boot/bootmap file, but I assumed that it contained
data
> only - location information for the kernel and initial RAM disk. From
> what you're telling me, it sounds like what you call the "second stage
> loader" o
Stephen Powell <[EMAIL PROTECTED]> wrote on 14.07.2008 20:58:36:
> The problem is that the IPL records (other than the first two) are being
> written, architecturally speaking, to the wrong place. I don't know
where
> zipl is writing its IPL records, other than the first two, but I am
> assuming
Stephen,
as the current maintainer of zipl I'm trying to understand the reasoning
behind your enhancement requests. The way I understand it you want to be
able to use zipl on a CMS formatted disk to enable it for IPL. zipl does
support CMS formatted disks (although not with the DIAG access meth
[EMAIL PROTECTED] wrote on 08.10.2007 14:25:25:
> I got exactly the same fsck error during boot and I'm fairly sure there
are
> no configuration errors as I checked several times both during and after
> the installation.
> - /etc/fstab is correct
> - except for the fsck failure, the system boot
[EMAIL PROTECTED] wrote on 08.10.2007 12:32:50:
> I've reproduced the issue and my suspicion is that either the boot
loader or
> the kernel is failing to release /dev/dasda1 after the kernel and/or
initrd
> have been loaded which leads to fsck concluding that it is mounted.
Judging from the da
6 matches
Mail list logo
