I would hardly call that being lazy. If you're fortunate enough (in an LPAR situation) to have consecutive device addresses, it makes perfect sense. In a z/VM environment, of course, you're not limited by real addresses, so specifying DASD addresses it completely up to you and the z/VM systems programmer.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Kyle Smith Sent: Friday, December 22, 2006 9:00 AM To: [email protected] Subject: Re: Changing DASD addresses Sorry, you're right. I get lazy and just do ranges, in which case the lower device number would be presented to the kernel first. ks On 12/22/06, Mark Post <[EMAIL PROTECTED]> wrote: > > No. The _first_ device number presented to the kernel becomes dasda. The > second becomes dasdb. It has nothing to do with what device numbers are > higher or lower than others. You can have something like > dasd=0150,0149,0160,0123 > That will give you: > 0150 = dasda > 0149 = dasdb > 0160 = dasdc > 0123 = dasdd > > > Mark Post ---------------------------------------------------------------------- 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
