For #3 and #5, you'd have to ask our friends in Germany about the change. For #3, lsdasd -c (or lsdasd --compat) will show you the old output. For #5, use lsqeth, which is also part of SLES 10 and RHEL 5 (and probably SLES 9 and RHEL 4, but I don't remember and didn't check..)
On Fri, Feb 13, 2009 at 4:29 PM, Michael MacIsaac <[email protected]> wrote: > Mark, > >> Speaking of SLES11... I was recently asked if I knew of any SLES11 Beta > testers for System z. >> I said I didn't, so I thought I'd ask if anyone out there (aside from > IBM folks) is testing. > > I wouldn't go as far as to say I'm (we're) testing, but we do have a copy > of RC3 installed. > > We did run into an apparent bug during install. (As I understand it) if > you uncheck all package groups except "base" so as to get a minimal > installation, there are too few X Window System RPMs to complete the > install. (I need to follow up to see if my colleague opened a bugzilla > defeect as requested). > > Other than than, it seems to run fine (as with just about all Linux > distros :)). Some random observations: > > 1) /etc/sysconfig/network/ifcfg-* is quite different - on SLES 10, I'd see > something like /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.0600 where > the NIC address, 0600 is incorporated into the file name. But now on > SLES11, I see /etc/sysconfig/network/ifcfg-eth0. > > 2) The contents are totally different: > BOOTPROTO='static' > IPADDR='x.y.z.207/25' > BROADCAST='x.y.z.255' > STARTMODE='onboot' > NAME='OSA Express Network card (0.0.0600)' > > 3) lsdasd output is totally different: e.g. > # lsdasd > Bus-ID Status Name Device Type BlkSz Size Blocks > ============================================================================== > 0.0.0100 active dasda 94:0 ECKD 4096 1565MB 400680 > 0.0.0102 active dasdb 94:4 ECKD 4096 586MB 150120 > 0.0.0103 active dasdc 94:8 ECKD 4096 586MB 150120 > 0.0.0105 active dasdd 94:12 ECKD 4096 586MB 150120 > 0.0.0104 active dasde 94:16 ECKD 4096 586MB 150120 > 0.0.0101 active dasdf 94:20 ECKD 4096 781MB 200160 > (but /proc/dasd/devices is the same (so use that if you're scripting!)) > > 4) The PARMFILE is the same - Amen! (except of course you'll want to point > to the SLES 11 install ISO via the "Install" variable - so a new PARMFILE > file type is needed - I use "PARM-S11" > > 5) /proc/qeth is no longer there, what's up with that? > > So (1) and (2) will totally break the clone.sh script in the SLES > Virtualization Cookbook and boot.findself script in the "Read only root" > (4322) Redpaper. > > Off topic, but related: I'd like to come up with a boot.findself (or your > favorite boot.name) that first determines if it's on a RHEL 5, SLES 10 or > SLES 11 system - and then does the Right Things find its PARMFILE (with > specific FILETYPE) on its CMS 191 disk and then modifies the networking > info accordingly. This seems to be the best model - and such a script > could be Most Versatile for cloning. (Has anyone already written that by > chance?) > > Hope this helps. > > "Mike MacIsaac" <[email protected]> (845) 433-7061 > > ---------------------------------------------------------------------- > 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 > -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY ---------------------------------------------------------------------- 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
