RE: Installation Question
Thank you. I am now in the SSH session. I have made it to Configure Disks and am not sure what the format of the address is. I have two volumes 108E and 108F and I tried 0.0.108E but that failed. Any suggestions? On the first menu on SSH I chose Start Installation. Should I have chosen to Start a Shell? Thanks, Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Tuesday, December 22, 2009 5:47 PM To: debian-s390@lists.debian.org Subject: RE: Installation Question Martin, Larry D wrote: All goes well until the install asks which site I want to use. I chose ftp.us.debian.org (and a couple of others) and I get ...site either not available or does not contain a valid release... The ftp.us.debian.org mirror works perfectly for me (using the same CD). Sounds as if you don't have an internet connection because of incorrect networking setup. But that's hard to tell without knowing the actual errors. Did you already switch to using an SSH session to complete the installation, or are you still using the text interface from the console? If you're still on the console you can see them by choosing Execute a shell from the installer's main menu and typing 'cat /var/log/syslog'. If you're using SSH, you can see the syslog by starting a second session and choosing the Start shell option and then use either cat or nano to view the syslog. If you need help, please copy and paste the full syslog (if possible). -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
It appears that Debian does not think the disks are usable because they are reachable from another partition. When I did the IOCDS for our machine I actually had the two volumes for Linux reachable from four LPARs. One of the four is linux, one is inactive, one has the volumes offline, and the last one is a coupling facility LPAR. Does anyone have an IOCDS that shows 3390's properly defined for Debian? Or any other suggestions? The disks are definitely reachable from the LPAR into which I am loading Linux. Thanks, .Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Wednesday, December 23, 2009 9:33 AM To: debian-s390@lists.debian.org Subject: Re: Installation Question hint how to reply correctly on mailing lists A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? /hint Martin, Larry D wrote: I am now in the SSH session. I have made it to Configure Disks and am not sure what the format of the address is. I have two volumes 108E and 108F and I tried 0.0.108E but that failed. Any suggestions? No idea. For me the available dasds have always been listed and I could just select them. AFAICT the last format should be correct. You may have to check that the devices really are available. I don't think I can help much with this. Maybe this walktrough of an installation in the Hercules s390 emulator will help for reference: http://www.josefsipek.net/docs/s390-linux/hercules-s390.html On the first menu on SSH I chose Start Installation. Should I have chosen to Start a Shell? I assume you mean Start menu, but that's correct. The shell is available mainly for troubleshooting. You can use it to enter commands manually, check the syslog, etc. You should only have *one* menu SSH session open, but you can have multiple shell sessions if you want. Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
On 2009-12-23, Larry Martin wrote:
It appears that Debian does not think the disks are usable because
they are reachable from another partition.
When I did the IOCDS for our machine I actually had the two volumes
for Linux reachable from four LPARs. One of the four is linux, one
is inactive, one has the volumes offline, and the last one is a
coupling facility LPAR.
Does anyone have an IOCDS that shows 3390's properly defined for Debian?
Or any other suggestions? The disks are definitely reachable from the
LPAR into which I am loading Linux.
Thanks, .Larry
Larry,
I'm not sure what you mean by reachable. Do you mean shared? Here
are some excerpts from our IOCP statements for a z890 (2086) with an IBM
DS6800 1750-511 RAID box for our DASD, which is attached to the host via
four FICON chpids. The RAID box defines 512 devices: 6100-61FF and
6300-63FF. 6100-6112 and 6300-6312 (38 devices) are emulated 3390-9
devices. The rest are 3390-3 devices. None of these devices support
PVA. These are IOCP statements generated by HCD/HCM running under z/OS,
which are slightly different in format from the native IOCP format. But
you'll get the idea.
--
TITLE 'SYS1.IODF01 - 2006-10-10 12:08:22 '
*
ID NAME=DOLC01,UNIT=2086,MODEL=A04,MODE=LPAR,LEVEL=H040331, *
SCR='DOLC01 06-10-1012:08:22SYS*
1IODF01 '
RESOURCE PARTITION=((CSS(0),(MVSPROD,1),(MVSTECH,3),(MVSTEST,2*
),(ZOSPROD,4),(ZVMPROD,5))),MAXDEV=((CSS(0),64512)),*
DESCL=('MVS PRODUCTION LPAR','','MVS TES*
T LPAR','',''),USAGE=(OS,OS,OS,OS,OS)
.
.
.
CHPID PATH=(CSS(0),20),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=120
CHPID PATH=(CSS(0),21),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=121
.
.
.
CHPID PATH=(CSS(0),30),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=130
CHPID PATH=(CSS(0),31),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=131
.
.
.
CNTLUNIT CUNUMBR=6100,PATH=((CSS(0),20,30,21,31)),*
UNITADD=((00,256)),SHARED=N,CUADD=1,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 Control Unit',UNIT=1750
IODEVICE ADDRESS=(6100,256),UNITADD=00,CUNUMBR=(6100),STADET=Y*
,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 mod-9 mod-3s',UNIT=3390
CNTLUNIT CUNUMBR=6300,PATH=((CSS(0),21,31,20,30)),*
UNITADD=((00,256)),SHARED=N,CUADD=3,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 Control Unit',UNIT=1750
IODEVICE ADDRESS=(6300,256),UNITADD=00,CUNUMBR=(6300),STADET=Y*
,SERIAL='13-AFALA',
DESC='DS6800 1750-511 mod-9 mod-3s',UNIT=3390
--
The above IOCP definitions use the ESCON Multi-Image Facility (EMIF)
to allow the DASD devices to be shared by all LPARs. (EMIF works for
FICON as well as ESCON.)
If a normal mainframe operating system, such as z/OS or z/VM, can see
the DASD, then Linux should be able to see it too. If not, then you're
probably doing something wrong in the installation. If I remember right,
there is an initial screen which displays all the DASD devices it
recognizes. You have to explicitly select all the devices you are going
to use on that screen, though some of them may be pre-selected. Then
there is another screen later on where you can create partitions,
assign mount points, etc. If you don't select the devices on the first
screen, they won't be available on the second screen.
Also, keep in mind that (a) the Debian installer supports only CKD DASD
devices and (b) the Debian installer supports only the cdl format
(compatible disk layout). You said that your devices were 3390s, which
are CKD devices; so that should be OK.
I do all of my Linux installs in a virtual machine under z/VM, not natively
in an LPAR as you are attempting to do; so I don't really know how much
more help I can be if you are running into an LPAR-environment-specific
problem.
Regards,
Steve
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: Installation Question
Steve,
Thanks.
If I remember right,
there is an initial screen which displays all the DASD devices it
recognizes.
Unfortunately the list is empty (recognizes none) and then prompts me to enter
an address, which, of course fails.
Thanks again, ..Larry
-Original Message-
From: Stephen Powell [mailto:zlinux...@wowway.com]
Sent: Wednesday, December 23, 2009 11:41 AM
To: debian-s390@lists.debian.org
Subject: RE: Installation Question
On 2009-12-23, Larry Martin wrote:
It appears that Debian does not think the disks are usable because
they are reachable from another partition.
When I did the IOCDS for our machine I actually had the two volumes
for Linux reachable from four LPARs. One of the four is linux, one
is inactive, one has the volumes offline, and the last one is a
coupling facility LPAR.
Does anyone have an IOCDS that shows 3390's properly defined for Debian?
Or any other suggestions? The disks are definitely reachable from the
LPAR into which I am loading Linux.
Thanks, .Larry
Larry,
I'm not sure what you mean by reachable. Do you mean shared? Here
are some excerpts from our IOCP statements for a z890 (2086) with an IBM
DS6800 1750-511 RAID box for our DASD, which is attached to the host via
four FICON chpids. The RAID box defines 512 devices: 6100-61FF and
6300-63FF. 6100-6112 and 6300-6312 (38 devices) are emulated 3390-9
devices. The rest are 3390-3 devices. None of these devices support
PVA. These are IOCP statements generated by HCD/HCM running under z/OS,
which are slightly different in format from the native IOCP format. But
you'll get the idea.
--
TITLE 'SYS1.IODF01 - 2006-10-10 12:08:22 '
*
ID NAME=DOLC01,UNIT=2086,MODEL=A04,MODE=LPAR,LEVEL=H040331, *
SCR='DOLC01 06-10-1012:08:22SYS*
1IODF01 '
RESOURCE PARTITION=((CSS(0),(MVSPROD,1),(MVSTECH,3),(MVSTEST,2*
),(ZOSPROD,4),(ZVMPROD,5))),MAXDEV=((CSS(0),64512)),*
DESCL=('MVS PRODUCTION LPAR','','MVS TES*
T LPAR','',''),USAGE=(OS,OS,OS,OS,OS)
.
.
.
CHPID PATH=(CSS(0),20),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=120
CHPID PATH=(CSS(0),21),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=121
.
.
.
CHPID PATH=(CSS(0),30),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=130
CHPID PATH=(CSS(0),31),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=131
.
.
.
CNTLUNIT CUNUMBR=6100,PATH=((CSS(0),20,30,21,31)),*
UNITADD=((00,256)),SHARED=N,CUADD=1,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 Control Unit',UNIT=1750
IODEVICE ADDRESS=(6100,256),UNITADD=00,CUNUMBR=(6100),STADET=Y*
,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 mod-9 mod-3s',UNIT=3390
CNTLUNIT CUNUMBR=6300,PATH=((CSS(0),21,31,20,30)),*
UNITADD=((00,256)),SHARED=N,CUADD=3,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 Control Unit',UNIT=1750
IODEVICE ADDRESS=(6300,256),UNITADD=00,CUNUMBR=(6300),STADET=Y*
,SERIAL='13-AFALA',
DESC='DS6800 1750-511 mod-9 mod-3s',UNIT=3390
--
The above IOCP definitions use the ESCON Multi-Image Facility (EMIF)
to allow the DASD devices to be shared by all LPARs. (EMIF works for
FICON as well as ESCON.)
If a normal mainframe operating system, such as z/OS or z/VM, can see
the DASD, then Linux should be able to see it too. If not, then you're
probably doing something wrong in the installation. If I remember right,
there is an initial screen which displays all the DASD devices it
recognizes. You have to explicitly select all the devices you are going
to use on that screen, though some of them may be pre-selected. Then
there is another screen later on where you can create partitions,
assign mount points, etc. If you don't select the devices on the first
screen, they won't be available on the second screen.
Also, keep in mind that (a) the Debian installer supports only CKD DASD
devices and (b) the Debian installer supports only the cdl format
(compatible disk layout). You said that your devices were 3390s, which
are CKD devices; so that should be OK.
I do all of my Linux installs in a virtual machine under z/VM
RE: Installation Question
On 2009-12-23, Marry Martin wrote: Unfortunately the list is empty (recognizes none) and then prompts me to enter an address, which, of course fails. Thanks again, ..Larry When you get to the screen that is supposed to show the recognized dasd devices, and nothing shows up, open another SSH session in another window on your desktop. Login as installer using the password that you specified earlier, but don't run the installer menu. Instead, escape to a shell. First of all, make sure that the dasd drivers are loaded # lsmod You should see both dasd_mod and dasd_eckd_mod as loaded modules. If not, manually load them with modprobe. If that doesn't work, you've got serious problems. Did you mess with the installer components to be downloaded? Did you deselect some of them? If both modules are loaded, issue # cd /sys/bus/ccw/devices # ls -Al|more You should see a directory listed for each device number recognized, regardless of whether it is dasd or not. It will be of the form 0.0., where is a hexadecimal number. (Note that hex digits a-f are lower case!) See if the device is listed there. If it is, cd to that directory. For example, # cd 0.0.108e # ls -Al You can check the values of these variables with cat. For example, # cat online If it responds with 0, then the device was recognized, but it is offline. Check the use_diag and readonly variables to make sure they are zero as well, then try to set the device online with # echo 1 online Then verify that it came online with another # cat online This time, it should say 1, which means that it is online. If this works, do the same for your other volume: # cd ../0.0.108f . . . If that works, then come back to the original install session, select Back, then invoke that step again. With luck, it will find the dasd devices now. P.S. Please do not attach my entire original e-mail at the end of your next posting. Just quote the relevant portions with the character above your response. Also, please try to keep your input lines to a maximum of 80 characters. Thanks. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: Installation Question
Thank you. I downloaded and started the install. All goes well until the install asks which site I want to use. I chose ftp.us.debian.org (and a couple of others) and I get ...site either not available or does not contain a valid release... What site should I chose to complete the install? Thanks again, Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Monday, December 21, 2009 4:13 PM To: debian-s390@lists.debian.org Subject: Re: Installation Question On Monday 21 December 2009, Frans Pop wrote: Martin, Larry D wrote: The iso directory for s390 is empty (as far as I can tell) again this week. Unfortunately the server that hosts the Debian Installer images for s390 looks to be down today, which means that the server that builds the CD images could not download them and so the weekly CD build failed. There's nothing much I can do about that. Sorry for the inconvenience. I've just created a bootable s390 CD for Lenny. You can download it from: http://cdimage.debian.org/cdimage/unofficial/fjp/ Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
Martin, Larry D wrote: All goes well until the install asks which site I want to use. I chose ftp.us.debian.org (and a couple of others) and I get ...site either not available or does not contain a valid release... The ftp.us.debian.org mirror works perfectly for me (using the same CD). Sounds as if you don't have an internet connection because of incorrect networking setup. But that's hard to tell without knowing the actual errors. Did you already switch to using an SSH session to complete the installation, or are you still using the text interface from the console? If you're still on the console you can see them by choosing Execute a shell from the installer's main menu and typing 'cat /var/log/syslog'. If you're using SSH, you can see the syslog by starting a second session and choosing the Start shell option and then use either cat or nano to view the syslog. If you need help, please copy and paste the full syslog (if possible). -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: Installation Question
The iso directory for s390 is empty (as far as I can tell) again this week. Thanks, .Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Wednesday, December 16, 2009 11:59 AM To: debian-s390@lists.debian.org Subject: Re: Installation Question Martin, Larry D wrote: The S390 directory appears to me to be empty this week. Yes, unfortunately there was a build error this week (which sometimes happens for daily and weekly builds). The images should be back next Monday. There was stuff there last week (can I point to that?). Afraid not. Full CD/DVD images just take too much space to keep multiple versions around. Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Re: Installation Question
Martin, Larry D wrote: The iso directory for s390 is empty (as far as I can tell) again this week. Unfortunately the server that hosts the Debian Installer images for s390 looks to be down today, which means that the server that builds the CD images could not download them and so the weekly CD build failed. There's nothing much I can do about that. Sorry for the inconvenience. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Installation Question
On Monday 21 December 2009, Frans Pop wrote: Martin, Larry D wrote: The iso directory for s390 is empty (as far as I can tell) again this week. Unfortunately the server that hosts the Debian Installer images for s390 looks to be down today, which means that the server that builds the CD images could not download them and so the weekly CD build failed. There's nothing much I can do about that. Sorry for the inconvenience. I've just created a bootable s390 CD for Lenny. You can download it from: http://cdimage.debian.org/cdimage/unofficial/fjp/ Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: Installation Question
On December 21, 2009, Larry Martin wrote: The iso directory for s390 is empty (as far as I can tell) again this week. Thanks, .Larry According to the web page http://cdimage.debian.org/cdimage/weekly-builds/, problems with the weekly builds should be reported on another list: debian...@lists.debian.org. I cannot find evidence in your original posting that this list was CC-ed; so you might want to put a posting on that list complaining that none of the s390 architecture weekly builds exist. Here is an excerpt from the above web page: -- Problems? If you encounter any problems with these images, please check the Debian CDs FAQ. The most common complaint at the moment is about wrongly-sized or corrupt DVD ISO images, which is normally a bug in your http download program. If your problem is not covered by the above FAQ, please report it to the debian...@lists.debian.org mailing list. -- (I checked the FAQ. The subject, all the files for architecture xyz are missing is not one of the topics covered in the FAQ.) I'd report the problem myself; but I use the VM reader images from generic, not the CD images, to do my installs. Therefore, you have a greater vested interest to make some noise on the other list than I do. So I'll let you do it. :-) Regards, Steve -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Installation Question
Martin, Larry D wrote: The S390 directory appears to me to be empty this week. Yes, unfortunately there was a build error this week (which sometimes happens for daily and weekly builds). The images should be back next Monday. There was stuff there last week (can I point to that?). Afraid not. Full CD/DVD images just take too much space to keep multiple versions around. Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: Installation Question
Thanks..Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Wednesday, December 16, 2009 11:59 AM To: debian-s390@lists.debian.org Subject: Re: Installation Question Martin, Larry D wrote: The S390 directory appears to me to be empty this week. Yes, unfortunately there was a build error this week (which sometimes happens for daily and weekly builds). The images should be back next Monday. There was stuff there last week (can I point to that?). Afraid not. Full CD/DVD images just take too much space to keep multiple versions around. Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Re: Installation Question
Frans Pop wrote: Hm. Except that for Lenny (stable) we haven't had any new CD builds since it was fixed. That will only happen at the next stable point release (which is overdue). The weekly built CD for Squeeze [1] should work though and should be usable to install Lenny too. You'll need to change the debconf priority to medium before the mirror selection step to get a choice of which release to install. Given the low frequency of stable release updates, perhaps I should ask if the fix for Debian bug #550898 is scheduled to be included in the next update, both in the Debian installer and in the regular stock kernels. This fix is an s390/s390x-specific fix. An upstream developer promised me that he would get this fix in the next kernel release, which at the time was going to be 2.6.33. But since stable Debian releases tend to go with even numbered kernel releases, the earliest upstream version which contains this fix that Debian actually uses is likely to be 2.6.34. That might not even be available in Squeeze. I'd really like to see this fix in production as soon as possible. Until that happens, I will have to build custom kernels. I requested this in bug report number 550898, but no-one responded. I have a patch for this available on my web site now: http://www.wowway.com/~zlinuxman/dasd_diag.diff If you cut and paste the version in the problem log you may have problems applying the patch due to tab versus space issues. The version on my web site applies just fine even without resorting to the -l option of patch. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Installation Question
Martin, Larry D wrote: Does anyone know if the problem installing Debian on zSeries from CD-ROM has been corrected? Yes, it has. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
