Bug#486549: The single partition present on a CMS minidisk is not supported (s390/s390x only)

2008-07-15 Thread Stephen Powell
I have just been informed by the current maintainer of zipl that CMS minidisks are now supported by zipl as a /boot partition, provided that the dasd_diag driver is not used for the /boot partition. This is a minor technical correction to previous information stated in the problem log. It does

Bug#486528: Please enhance mke2fs to respect the RECOMP area of CMS minidisks

2008-07-14 Thread Stephen Powell
Peter, I tried your scenario and it works as you say. I can use a CMS minidisk, RESERVEd or non-RESERVEd, as a /boot partition. I can even use the dasd_diag driver against it, provided I don't run zipl. (If I need to run zipl, I can switch to the dasd_eckd driver, then run zipl, then switch

Bug#486528: Please enhance mke2fs to respect the RECOMP area of CMS minidisks

2008-07-09 Thread Stephen Powell
DASD is an acronym for Direct Access Storage Device. It is a storage device in which the blocks can be accessed randomly, in any order, without reading the blocks in between. In the history of mainframes, a DASD device was not necessarily a disk device. At one time, there were drum devices too,

Bug#486528: Please enhance mke2fs to respect the RECOMP area

2008-07-09 Thread Stephen Powell
One thing I forgot to mention. CMS minidisks in EDF format have four possible block sizes: 512, 1024, 2048, and 4096. (Oh dear, I've introduced another undefined acronym. EDF stands for Enhanced Disk Format. It is the only format of CMS minidisk that is currently supported. There is an older

Bug#486528: Please enhance mke2fs to respect the RECOMP area

2008-07-09 Thread Stephen Powell
It looks like our updates are crossing in the mail. Sorry about that. I'll try to answer your additional questions. The following is an oversimplification, but it gets the point across. A CMS minidisk on a CKD device has the following logical format: - /dev/dasda

Bug#486528: Please enhance mke2fs to respect the RECOMP area of CMS minidisks

2008-07-08 Thread Stephen Powell
I'm sorry, but I have absolutely no idea what this means. From the rationale it sounds like s390 stashes some kind of label or bootable area at the end of a minidisk, which is visible to the Linux program accessing the device file, and that mke2fs is supposed to somehow recognize the

Bug#486549: The single partition present on a CMS minidisk is not supported (s390/s390x only)

2008-07-07 Thread Stephen Powell
All the above is complete Greek too me because I don't have any context. And it sounds like you already did the hard part: you managed to get it working. That means you are the expert now. Tell us *in detail* what is missing and what manual steps were required to get it supported. Then

Bug#486549: The single partition present on a CMS minidisk is not supported (s390/s390x only)

2008-07-07 Thread Stephen Powell
I need to correct an error in my previous e-mail. In my previous e-mail, I said that the dasd_diag_mod driver could only be used with CMS minidisks. As it turns out, that is not true. The dasd_diag_mod driver can also be used with minidisks formatted with the Linux disk layout (ldl). Such a

Bug#484516: X does not restore video mode properly when switching to a virtual console or terminating

2008-06-21 Thread Stephen Powell
Goglin [EMAIL PROTECTED] Subject: Re: Bug#484516: X does not restore video mode properly when switching to a virtual console or terminating To: Stephen Powell [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Saturday, June 21, 2008, 2:02 AM Stephen Powell wrote: Package: xserver-xorg-core Version

Bug#486526: Please enhance zipl to support booting from the RECOMP area of a CMS minidisk

2008-06-16 Thread Stephen Powell
Package: s390-tools Version: 1.5.3-1 Severity: wishlist Please enhance zipl to support booting from the RECOMP area of a CMS minidisk. (This will also require an enhancement to mke2fs to respect the RECOMP area of a CMS minidisk when making a file system on it.) Rationale: Currently, only

Bug#486528: Please enhance mke2fs to respect the RECOMP area of CMS minidisks

2008-06-16 Thread Stephen Powell
Package: e2fsprogs Version: 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 Severity: wishlist This is an enhancement request that applies to the s390 and s390x architectures only. Currently, when mke2fs is run against the single implicit partition of a CMS minidisk, and the minidisk has been formatted

Bug#486549: The single partition present on a CMS minidisk is not supported (s390/s390x only)

2008-06-16 Thread Stephen Powell
Package: partman-base Version: 105 This bug applies only to the s390 and s390x architectures. The single partition implicitly created on a z/VM minidisk by the CMS FORMAT command (and optionally, the CMS RESERVE command) is not recognized by partman. mke2fs, mkswap, etc. recognize such a

Bug#485967: c3270 man page specifies incorrect screen size for model 3 3270 terminals

2008-06-12 Thread Stephen Powell
Package: c3270 Version: 3.3.4p6-3.3 The man page for the c3270 package, c3270.1.gz, incorrectly states that the screen size for a model 3 3270 terminal is 30 rows deep. This is incorrect. A model 3 terminal is actually 32 columns deep. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED]

Bug#484509: The initial video mode selected by boot parameter vga is not respected by console-tools

2008-06-04 Thread Stephen Powell
Package: console-tools Version: 1:0.2.3dbs-65 This bug applies only to the i386 architecture. I booted a stock Debian Linux kernel (linux-image-2.6.18-6-686) using the vga boot parameter to select an initial video mode. I used vga=ask, then selected the desired mode from a menu. In my case,

Bug#484516: X does not restore video mode properly when switching to a virtual console or terminating

2008-06-04 Thread Stephen Powell
Package: xserver-xorg-core Version: 2:1.1.1-21etch4 X does not restore the video mode properly when switching to a virtual console or terminating. To reproduce this problem, start the X server. Switch to a virtual console via Ctrl+Alt+Fn, where n = 1 to 6. Now change the text video mode using

Bug#467308: Bug # 467308 appears to be proxy-related

2008-05-28 Thread Stephen Powell
I am experiencing the same symptoms. From some other posts I've seen on the Internet, this bug appears to be proxy-related. I have not been able to reproduce the problem when apt connects to the Internet directly. It's only when apt connects to the Internet via a proxy that the problem occurs.

Bug#481514: Poor mouse configuration with debian-installer

2008-05-16 Thread Stephen Powell
Package: installation-reports Boot method: CD-ROM Image version: etch 4.0r1 Date: May 3, 2008 Machine: Dell Inspiron 4400 Processor: Intel Pentium 4 Memory: 512M Partitions: 4 (1 Windows NTFS, 1 Linux swap, 1 root (/), 1 home (/home)) Output of lspci -nn and lspci -vnn: N/A Base System

Bug#451981: Link rot in etch s390 installation guide

2007-11-19 Thread Stephen Powell
package: installation-guide Debian GNU/Linux Installation Guide (etch, S/390 architecture, English) Chapter 3, Before Installing Debian GNU/Linux Section 3.3, Information You Will Need Topic 3.3.1, Documentation Subtopic 3.3.1.3 S/390 Hardware References URL:

Bug#450723: -z secure switch has no effect if -n switch is also used

2007-11-09 Thread Stephen Powell
Package: ftp-ssl Version: 0.17.12+0.2-6 When the ftp command supplied in the ftp-ssl package is invoked with both the -n and the -z secure switches, the -z secure switch has no effect. The AUTH SSL command is not sent to the remote server and no SSL negotiation takes place. Use of the -n switch

Bug#447755: s390 installer doesn't support CMS minidisks; tries to mount partitions in wrong order

2007-10-23 Thread Stephen Powell
Package: installation-reports Boot method: VM reader Image version: /dists/etch/main/installer-s390/20070308etch1/images/generic/* Date: 2007-10-19 Machine: ESA/390-mode virtual machine under z/VM 5.2.0 Processor: 2086 (z/890) IFL (real processor) Memory: 512M (virtual machine memory)

<    1   2   3   4