Re: [Linux/390] Problem to find packages (under z/VM 5.3.0 on a Z800 2066)
On Wed, 16 May 2012 12:58:12 -0400 (EDT), Christian Boitet wrote:
>
> Hi Philipp, Stephen, 16/5/12
>
> maybe you remember us trying to install Debian
> Linux for s390 (31 bits) on a H30 (MP3000) last
> year?
Yes, I remember. You were trying to install Lenny: the last
release that supported 31-bit kernels.
The proper place for this discussion is the debian-s390 mailing
list, not private e-mails; so I have copied that list. I am
subscribed to the list; so you needn't CC me.
>
> The bug in the installer was never found nor
> corrected, so that we settled for a CentOS
> version, that installed immediately.
>
> We have now moved to a Z800 (2066) under z/VM 5.30.
> We are trying to install Debian Linux for x390
> (or s390x?, in any case 64 bits).
Debian's implementation of Linux for s390/s390x works differently
than most other distribution's implementation. In most (all?)
other distributions, s390 and s390x are separate architectures.
Debian, up to now, has taken a hybrid approach. The architecture
designation is s390. The kernel has s390x in it's name somewhere,
but is considered as belonging to the s390 architecture. The
kernel executes in 64-bit mode, but the user space is still 31-bit.
I seem to remember that a 64-bit user space was one of Debian's
release goals for Wheezy, but I do not know what the current
status of that goal is. Philipp knows much more about this than
I do. But in any case, if you're installing the stable release
(Squeeze), the architecture should be s390, not s390x, even though
you are running on a z-architecture box.
>
> This time, the installer worked immediately (I
> mean, sending the 3 files to the reader and
> IPLing from there).
> However, when we reach the point where packages
> shouold be installed from a mirror, it blocks,
> telling us that "this architecture is not
> supported".
> It was some time after the installer told us to
> leave the 3270 emulated terminal and continue
> using ssh (we did, from a PC and the from a Mac,
> but got always the same error message).
>
> We got always the same error message, although we
> tried 5 or 6 mirrors, in particular:
>
> ftp.fr.debian.org
> (debian.proxad.net) /debian/ /debian/
> amd64 armel armhf hurd-i386 i386 ia64
> kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc
> s390 s390x sparc
>
> ftp2.fr.debian.org
> (ftp.oleane.net) /debian/ /debian/
> amd64 armel armhf hurd-i386 i386 ia64
> kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc
> s390 s390x sparc
>
> ftp2.de.debian.org/debian/ amd64 armel armhf
> hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386
> mips mipsel powerpc s390 s390x sparc
>
> The mirrors seem to have the necessary archives,
> but the subdirectories and archives have names
> like "Contents-s390.gz" and not
> "Contents-s390x.gz".
See my comments above. For now, use s390 as your architecture
designation, not s390x, especially if you're installing the stable
release (Squeeze). s390x definitely will not work for Squeeze.
Wheezy, maybe. I don't know what the status of that project is.
But Squeeze, definitely not. At some point later on in the install,
you will be asked to select a kernel. At that point, you will be
offered only 64-bit kernels. But the user space is still 31-bit.
>
> Achille (in copy) is a fan of Debian (on PC) and
> has tried to help, to no avail.
>
>
> Is there a simple solution to get the s90x packages in our configuration?
Yes. See my comments above.
>
> Thanks & regards,
>
> Christian & Jean-Claude
--
.''`. Stephen Powell
: :' :
`. `'`
`-
Reply to: