The "problem" is that one cannot boot from an unpartitioned CKD disk
(LDL) even though one can boot from an unpartitioned FBA disk.
Partition tables are not required for other disks and bootstraps.  Why
should they be required for mainframe disks and bootstraps?

Anyway ... I am hopeful that Boeblingen can fix it faster than any of
us would-be contributors because they invented 'zipl' in the first
place.  Also, they already fixed it to work with unpartitioned FBA, so
someone took a big step in the right direction.

CDL is related, but is a different ... er, uh ... "problem".  Fixing
the bootstrap ('zipl') won't fix that.

THANK YOU for your work on 'parted'.  Having full S/390 support there
will be terrific.  Maybe I can now talk you into contributing to GRUB
in the other direction.  (ie: so that it will work with unpartitioned
disks like other PC boostraps do)

-- R;   <><
Rick Troth
Velocity Software
http://www.velocitysoftware.com/





On Thu, Jan 6, 2011 at 14:22, Stephen Powell <zlinux...@wowway.com> wrote:
> On Thu, 06 Jan 2011 09:03:46 -0500 (EST), Richard Troth wrote:
>> ...
>> The problem with mainframe labelling (the req for an IBM volser) is
>> that it panders to the bad behaviour of a certain other mainframe op
>> sys.  Also, we're mixing labelling with partitioning.  They are not
>> the same thing, though CDL accommodates both.
>>
>> It is presumptuous, and increasingly incorrect, to expect that users
>> partition everything on other platforms.  In fact, there are growing
>> numbers of cases where users/customers DO NOT partition physical
>> media.
>>
>> Windows assumes partitioning (except where it is forced to know
>> better).  Too bad for Windows.  z/OS assumes IBM volsers.  Too bad for
>> z/OS.  This is Linux.  We should be able to bypass the complexities
>> and ... Keep It Simple.  Partitioning is a layer of complexity.  Where
>> it is needed, fine.  Where it is not needed, let us turn it off.
>
> Hello, Rick.
>
> I have seen this thread running for some time now, and I'm getting
> more and more confused.  What, exactly, is the "problem" that you
> are trying to "solve"?  I have recently completed work on enhancements
> to GNU parted to support all combinations of DASD type (CKD and FBA)
> DASD format (cdl, ldl, CMS non-reserved, and CMS reserved) and DASD
> driver (ECKD, FBA, and DIAG) supported by the Linux kernel; so I am
> reasonably familiar with the landscape here.  I have not had any problems.
> Can you please state your problem in a manner simple enough for a
> dunder head like me to understand?
>
> --
>  .''`.     Stephen Powell
>  : :'  :
>  `. `'`
>   `-
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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/
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/

Reply via email to