> I can think of the following alternative places and I'd like to hear
> your opinion on whether you consider them appropriate and if you would
> have looked in that place for general information about the IPL process:

> - man page for zipl or zipl.conf
> - "Device Drivers, Features and Commands" book [1]
> - Linux on System z developerWorks web page [2]

I agree with you that enhancements to existing documents would be better
than a separate, stand-alone document.

I think the basic information should go in the zipl man page.  Since
zipl.conf does not reference the /boot/bootmap file, its man page
probably doesn't need to be altered.

For example, I think the /boot/bootmap file and its contents for different
types of DASD devices and formats should be documented in the man page
for zipl.  A description of when you would need to re-run zipl would be
a good idea too.  For example, if the kernel image, initial ramdisk image,
or the bootmap file is altered, copied to different blocks, or renamed,
one needs to re-run zipl.  This is particularly important since most
users on the i386 platform now use grub instead of lilo.  Grub does not
need to be re-run for these kinds of changes, as lilo and zipl do.

Background information, such as a more detailed explanation of
the physical structure of different disk formats and how their use under
Linux differs from their use under the native operating system for which
they were designed probably belongs in "Device Drivers, Features, and
Commands".  But the zipl man page should contain a reference to it.
A glossary of terms is already contained in "Device Drivers, Features,
and Commands," and any missing terms can be added.
A reference to "Principles of Operation" for a general description of the
IPL process would also probably be good.

I would probably not have looked on the developerWorks web page if I were
searching for this kind of information, unless it showed up as a hit in
a general internet search engine.  That's my two cents worth.



      



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to