On Tue, Oct 06, 2020 at 11:57:10AM +0200, Konstantin Maksimov wrote:
> Are there any plans to add security updates for debian 9 for s390?
> http://security.debian.org/debian-security/dists/stretch/updates/main
No. Debian 9 reached it's EOL date in july. Debian LTS currently
support Stretch, but
On Thu, Sep 17, 2020 at 11:38:46AM +0200, Andreas Tille wrote:
> The package has built before and the latest changes are:
> Am I
> missing something?
It built months before, with a lot of other changes surrounding it.
E.g. glibc
On Fri, Apr 27, 2018 at 05:37:25AM +0200, John Paul Adrian Glaubitz wrote:
> Since there are still some repositories that we need for debian-ports
> in the attic, I was wondering whether we should take care of the
> attic stuff and move it over to salsa or github.
Could you show a list? Just
On Wed, Jan 24, 2018 at 01:24:06PM +0100, Emilio Pozuelo Monfort wrote:
> Our baseline is z10, and z196 is newer. So if upstream now requires z196, we
> have three options:
>
> - Revert / fix that so upstream works with z10 again
> - Remove nodejs from s390x
> - Bump our baseline
>
> See go and
On Tue, Jun 13, 2017 at 09:38:44AM +0200, Ole Streicher wrote:
> I am slowly re-starting the packaging of IRAF (still not officially
> announced yet). When porting to s390x, I however run into a strange
> error: IRAF needs a small piece of assembler code (kind-of longjump for
> Fortan), which John
Hi Doug
On Fri, Dec 02, 2016 at 10:44:05AM -0500, Doug Torrance wrote:
> On 12/02/2016 09:26 AM, Bastian Blank wrote:
> >You know, Debian actually has a s390x porter machine. You can use it to
> >test such problems.
> Yeah, I've used porterboxes in the past.
Hi Doug
On Thu, Dec 01, 2016 at 09:37:23AM -0500, Doug Torrance wrote:
> Thanks for your reply!
> I've changed all the shorts to uint16_t's -- hopefully this works!
You know, Debian actually has a s390x porter machine. You can use it to
test such problems.
Regards,
Bastian
--
Actual war is a
On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote:
> I'd like to ask for your help with looking at the problems building
> libsecret on s390x. It's currently the only (release-)architecture
> not building and blocking testing migration for a long time. :(
What was the result of
On Mon, Aug 25, 2014 at 10:52:47AM +0200, Michael Holzheu wrote:
On Sun, 24 Aug 2014 20:43:30 +0200
Bastian Blank wa...@debian.org wrote:
And -fno-delete-null-pointer-checks seems to be the correct option.
From the gcc man page:
-fdelete-null-pointer-checks
In some environments
Control: tag -1 confirmed
On Tue, Feb 25, 2014 at 08:14:12AM -0500, Reinhard Tartler wrote:
Nevertheless, dear s390x porters, please help with fixing this issue.
Some digging shows that relocations are broken in the version running
via yorck:
| Dump of assembler code for function
On Fri, Nov 22, 2013 at 04:50:23PM +0100, Michael Meskes wrote:
On Thu, Nov 21, 2013 at 03:24:13PM +0100, Bastian Blank wrote:
Okay. The reason is the stray -fpic. On s390* this restricts the
shared lib to 2^11-1 bytes. And the last setting wins.
Got it. I changed the Makefile to not use
On Thu, Oct 10, 2013 at 01:37:30PM +0200, Michael Meskes wrote:
On Sun, Oct 06, 2013 at 06:11:42PM +0200, Bastian Blank wrote:
On Sun, Oct 06, 2013 at 04:27:29PM +0200, Michael Meskes wrote:
The log is here:
https://buildd.debian.org/status/fetch.php?pkg=postgres-xcarch=s390ver=1.1
On Sun, Oct 06, 2013 at 04:27:29PM +0200, Michael Meskes wrote:
The log is here:
https://buildd.debian.org/status/fetch.php?pkg=postgres-xcarch=s390ver=1.1-1stamp=1378820737
It uses -fpic instead of -fPIC.
Bastian
--
I'm a soldier, not a diplomat. I can only tell the truth.
On Mon, Jul 01, 2013 at 11:42:44AM +0200, Matthias Klose wrote:
Is this change coordinated with Bastian?
I have not been contacted by Aurelian. I've not seen anything on this
matter from him.
Bastian
--
A Vulcan can no sooner be disloyal than he can exist without breathing.
On Thu, Jun 13, 2013 at 02:51:43PM +0200, Matthias Klose wrote:
GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM porters).
GCC 4.8 seems fine on s390x, it can build a running Linux kernel. On
s390 something weird happened
On Sun, May 20, 2012 at 10:22:58PM +0200, Philipp Kern wrote:
you cannot reinterpret a size_t as an int. size_t might be unsigned, might
have another length, etc. On 64bit big endian you fill the top bits and
leave the lower ones untouched, because size_t is 64bit. So yeah, that code
was
On Wed, May 16, 2012 at 03:15:14PM +0100, Jon Dowland wrote:
My package 'bup' has not made it to testing due to FTBFS on s390: #664185
The test suite allocates too much memory. Nothing mythical about it.
_Why_ it does this it up to you to find out.
I've asked upstream about it and they don't
retitle 664185 bup: Maps large amounts of memory, FTBFS on s390
thanks
On Wed, May 16, 2012 at 04:53:58PM +0200, Bastian Blank wrote:
On Wed, May 16, 2012 at 03:15:14PM +0100, Jon Dowland wrote:
My package 'bup' has not made it to testing due to FTBFS on s390: #664185
The test suite allocates
severity 594127 important
thanks
On Thu, Aug 26, 2010 at 02:17:48PM -0400, Stephen Powell wrote:
The previous post shows that a *must* directive is being violated.
Therefore, setting severity to serious.
Don't play bts ping-pong.
Bastian
--
Earth -- mother of the most beautiful women in the
On Mon, May 24, 2010 at 12:51:36PM +0400, Mike Kirjanov wrote:
We have a problem with the fsiucv-3.0.0 driver compilation under Debian
(squeeze/sid ):
Please provide a link and show that it was updated in the last 12
months. The kernel API is not supposed to be stable, so every new
version
On Tue, May 18, 2010 at 03:47:58AM +0300, Faidon Liambotis wrote:
It seems that on consecutive runs of the test case[1] in question, it aborts
at different points each time and even succeeds in one in five runs or so.
Moreover, while the combined assert() condition fails, separate assert()
On Thu, Mar 25, 2010 at 10:46:28AM -0400, Stephen Powell wrote:
The only thing I know of that changed recently is the switch
to a 64-bit kernel by the build server for s390. (I am just a regular
Joe Schmoe user. I'm not a Debian package maintainer, Debian Developer,
or any other kind of
On Sun, Jan 24, 2010 at 09:53:10PM +0100, Frans Pop wrote:
I've created a (temporary) git repository that includes all changes
relative to the current 1.6.2-1 version:
git clone alioth.debian.org:git/s390-tools.git
The location of the package is currently
[ Bastian Blank ]
* New upstream version. (closes: #566649)
* Use 3.0 (quilt) source format.
* Use debhelper compat level 7.
* Set section to admin.
* Don't install the scripts dbginfo.sh, scsi_logging_level and zfcpdbf.
* Install ipl tools.
[ Frans Pop ]
* lstape, chccwdev: use bash
On Wed, Jan 27, 2010 at 07:38:05PM +0100, Frans Pop wrote:
Bastian Blank wrote:
Did you consider also enabling vmur as requested by Adam and Stephen?
Not yet, but it is on the list.
If you like I can try pushing some of our fixes (and maybe the zipl
optional patch?) upstream.
The later
On Sun, Oct 11, 2009 at 02:24:50PM +0200, Bastian Blank wrote:
The addresses are specified this way:
| #ifndef __s390x__
| #define IPL_DEVICE(*(unsigned long *) (0x10404))
| #define INITRD_START (*(unsigned long *) (0x1040C))
| #define INITRD_SIZE (*(unsigned long
reassign 544838 libc6-dev 2.6-26
thanks
On Fri, Sep 04, 2009 at 08:35:34PM +0700, Theppitak Karoonboonyanan wrote:
That is, it's available for loader, but not for linker, despite the fact
that utmpx.h is still shipped for applications to call.
What would s390 porting team suggest? Is
On Thu, Sep 03, 2009 at 11:32:14AM +0200, Martin Grimm wrote:
So as long as there is no easy manual way to provide anonymized figures
without installing software on our production servers we can't deliver
such data :-(
Hmm. You could collect the /var/lib/dpkg/status files and do a
mass submit
On Mon, Aug 31, 2009 at 01:01:24PM -0400, Michael Casadevall wrote:
I think a bigger question is where do you find hardware where you can
get remote root on;
I know at least two posibilites
- IBM provides access for evaluation purposes and
- OSDL provides access for project work.
Bastian
--
Hi folks
The s390 port was released with Lenny. However it is not in the best
condition. There are mainly two problems which needs attention, lack of
manpower and a 64 bit userland.
The first problem is the worst. Currently only Frans Pop and I do work
on it. Frans only does the
On Thu, Aug 20, 2009 at 07:09:44AM +0200, Mike Hommey wrote:
On Wed, Aug 19, 2009 at 04:33:32PM +0200, Bastian Blank wrote:
If I understand this correctly, this would need the modification off all
library packages to implement biarch semantic.
... which will be needed anyways. So your choice
On Wed, Aug 19, 2009 at 01:16:36PM +0200, Matthias Klose wrote:
I did speak with Martin Zobel at Debconf on how to get there, having two
proposals:
- define a new sparc64 port, and bootstrap this one using the 32bit port.
This is rather easy. I already did a s390x bootstrap using this
On Wed, Aug 19, 2009 at 01:55:24PM +0200, Matthias Klose wrote:
On 19.08.2009 13:42, Bastian Blank wrote:
On Wed, Aug 19, 2009 at 01:16:36PM +0200, Matthias Klose wrote:
I did speak with Martin Zobel at Debconf on how to get there, having two
proposals:
- have an inplace-transition
On Mon, Aug 03, 2009 at 03:06:38PM -0300, Peter Senna Tschudin wrote:
I've uploaded files to the System Z but kernel was not able to mount
the initrd.
Which way do you used to upload the files (which exactly?) to the Z? Do
you use z/VM?
The most strange is that normally after the
On Tue, Aug 04, 2009 at 10:37:12AM -0300, Peter Senna Tschudin wrote:
Which way do you used to upload the files (which exactly?) to the Z? Do you
use z/VM?
I uploaded the files using x3270-x11. See screenshots below. Yes I do use
z/VM.
Are you sure that the default record format is fixed?
On Fri, Feb 20, 2009 at 01:16:14PM +0100, Florian Bilek wrote:
Just would like to know how to enabale additional dasd that was added later
after the finalisation of the installation. When I start Debian only the
DASD that was configured during installation is online.
Take a look into
On Thu, Jan 08, 2009 at 03:06:04PM -0600, Adam Thornton wrote:
So, is there something I'm doing wrong?
Not that I spot anything.
This is a perfectly normal (if
slow) z/VM development system (yes, it's actually emulated, but for all
that, IBM still
On Thu, Oct 16, 2008 at 01:31:46AM -0300, [EMAIL PROTECTED] wrote:
debian:~# hwup ccw 0.0.0800
Configuring device 0.0.0800: already configured.
/etc/sysconfig/scripts/hardware/hwup-ccw-group: line 69: echo: write
error: Operation not permitted
Which version of sysconfig-hardware is this? If
On Mon, Sep 22, 2008 at 04:10:01PM -0400, [EMAIL PROTECTED] wrote:
This works just fine in Etch, but fails in Lenny. A device cannot be taken
offline dynamically.
I fail to see what s390-tools or the chccwdev tools have to do with this
problem.
On Mon, Aug 25, 2008 at 04:59:59PM -0400, THOMAS DELANY wrote:
Can anyone out there give me a little nudge in the right direction for
getting Debian running on a Z9 in an LPAR?
I have tried both Etch and Lenny without any success. I am trying to
install from a tape image that I can IPL. I
On Thu, Jun 19, 2008 at 10:35:47AM +0200, Frans Pop wrote:
Quite probably it will need some extentions to support FCP, but I think it
should be relatively straightforward. If you figure out what/how, please
send a patch (by opening a wishlist bug report against the
sysconfig-hardware
On Sat, May 10, 2008 at 11:51:19PM +0200, Bastian Blank wrote:
Linux/s390 uses s390 and s390x. But the correct way on a Debian system
is to use dpkg-architecture outside and the architecture specific
defines like __s390__ inside the compiler.
The following seems to work.
| #if defined
On Sat, May 10, 2008 at 12:08:35PM -0300, Antonio Terceiro wrote:
So we would only have to get (and I'm sorry, I'm completely lost in
this area) the proper CPU string for s390 and add it here. Blindly
asking Google makes me believe the proper string for the submitter's
environment (64-bit
Package: libc6
Version: 2.7-10
Severity: important
On Wed, May 07, 2008 at 09:34:12AM +0200, Matthias Klose wrote:
the build failure on s390 is unexpected; is it possible to extract a
test case?
| java: pthread_mutex_lock.c:71: __pthread_mutex_lock: Assertion
`mutex-__data.__owner == 0'
On Mon, Jan 07, 2008 at 09:29:20AM +0100, Torsten Werner wrote:
one of our buildd reports s390x instead of s390 for 'uname -m'. Am I
correct that both architectures have a 32 bit userland and not 64 bit?
Yes. The correct way to determine the debian architecture is
dpkg-architecture, not uname.
On Mon, Jan 07, 2008 at 12:19:22PM +0100, Torsten Werner wrote:
On Jan 7, 2008 11:05 AM, Bastian Blank [EMAIL PROTECTED] wrote:
The correct way to determine the debian architecture is
dpkg-architecture, not uname.
But a software that is portable to many operating systems will
probably
On Tue, Sep 11, 2007 at 03:04:00PM -0700, GaryR wrote:
Well, something IS bizarrely wrong. I get the same error. Is there
something wrong with the disk I have allocated for root? It is a
minidisk of 1000 cylinders on a real 3390 Mod 3. I CMS formatted it,
and did a RESERVE LNX200 MDISK B
On Tue, Sep 11, 2007 at 06:42:17PM -0300, Gustavo Noronha wrote:
[Please CC me and Ronaldo, we're not subscribed to this list]
Please set Mail-Followup-To in the mails.
I am helping to asses the viability of running Zope/Plone on Debian
GNU/Linux Etch in an IBM zSeries. I've searched the
On Fri, Sep 07, 2007 at 08:34:39AM -0700, GaryR wrote:
I have purchased the Etch s390 DVD's and am having a problem with the
installer.
Which DVD's? Installation from optical media should work but is mostly
untested.
RAMDISK: Compressed image found at block 0
No filesystem could mount root,
On Fri, Sep 07, 2007 at 01:28:09PM -0700, GaryR wrote:
Kernel command line: root=/dev/ram0 ip=off ro debian-installer/
locale=C
This is wrong. Neither root= nor ip= is listed in the supplied parmfile.
The content is:
| ro debian-installer/locale=C
checking if image is initramfs...it isn't
On Fri, Jun 15, 2007 at 09:23:44AM -0400, Reinaldo wrote:
does anyone know what is the ID of the RAID partition type in fdasd?
There is none.
Bastian
--
Beam me up, Scotty, there's no intelligent life down here!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
On Wed, Mar 14, 2007 at 12:33:53PM +, Mark Brown wrote:
According to buildd.debian.org[1] powertweak 0.99.5-16 was built
successfully for s390 over a month ago but the packages have still not
appeared in the archive. Could you please have a look and see what's
going on there?
According
On Sat, Jan 20, 2007 at 01:20:10AM -0600, Manoj Srivastava wrote:
Looking at the build logs, I see the test pwd-long failed on
s-390. I need help diagnosing the problem, and was wondering if
someone could help getting this resolved.
The relevant bug report is #380552, which was
On Mon, Dec 25, 2006 at 11:40:02PM +0100, Frans Pop wrote:
S/390: add Bastian Blank
S/390: remove Gerhard Tonn, he stepped back
Bastian
--
But Captain -- the engines can't take this much longer!
signature.asc
Description: Digital signature
On Sun, Sep 17, 2006 at 09:44:39PM -0400, José Parrella wrote:
a) Current versions of binutils and gcc in Sid interoperate badly (which
seems possible and actually other -already solved- bugs give hints on
this direction, like #376832)
Nope, this was s390x specific assembler instructions for
On Fri, Mar 24, 2006 at 07:35:24PM -0600, Stephen Frazier wrote:
It would seem that for a hot plug CTC device. You would set it up to
test for the presence of the other one of the pair. If they are not both
present then dont do anything. Thus in your example when 0A00 became
available
On Fri, Mar 24, 2006 at 02:38:05PM +0100, Frans Pop wrote:
I've not been able get udev to set up the hardware though.
I've created a file '/etc/sysconfig/hardware/config-ccw-0.0.0a00' with:
CCWGROUP_CHANS=(0.0.0a00 0.0.0a01)
but that does not seem to do anything.
Hmm, I think I know the
On Fri, Mar 24, 2006 at 03:40:46PM +0100, Frans Pop wrote:
I guess you mean that ctc will be loaded as part of the processing of
/sys/bus/ccw/devices/0.0.0a00 so loading it manually in /etc/modules is
no longer needed?
Exactly.
But there is another problem left: A race condition happens if
On Fri, Mar 24, 2006 at 04:23:46PM +0100, Bastian Blank wrote:
# echo /sys/bus/ccw/devices/0.0.0a00/uevent
Should be
# echo /sys/bus/ccw/devices/0.0.0a00/uevent
Bastian
--
It would be illogical to kill without reason.
-- Spock, Journey to Babel, stardate 3842.4
On Thu, Mar 16, 2006 at 04:13:21PM +0100, Frans Pop wrote:
Only problem was that the network interface did not come up. Trying to
manually start it resulted in:
You need a 2.6.16-rc5 kernel and sysconfig-hardware.
The new kernel properly loads the network modules, the later is used to
On Thu, Mar 16, 2006 at 07:23:40PM +0100, Frans Pop wrote:
I see that the experimental kernel image does not depend on
sysconfig-hardware. Should it (to ensure that users upgrading from Sarge
will have it installed)?
Hmm. It is no dependency as the kernel can work without. Also it needs a
On Thu, Mar 16, 2006 at 07:33:59PM +0100, Bastian Blank wrote:
Hmm. It is no dependency as the kernel can work without. Also it needs a
converter for chandev to the new config format.
Which will only work automaticaly in the easiest config: only one
device/type as there is not longer any order
On Tue, Feb 07, 2006 at 12:13:03AM +0100, Frans Pop wrote:
- switch to 2.6 for installations
If I understand Bastian correctly this mainly requires automatic
configuration. I think he started that with his last s390-tools upload.
dasd configuration support is still missing in that IIUC.
Hi folks
I finaly finished a rudimentary hardware configuration. It have some
similarities with the redhat and suse sysconfig. (This was the simplest
schema I found.)
You can find the sources via
https://lophos.multibuild.org/svn/sysconfig/trunk.
It currently lacks documentation, but the
Hi folks
I wrote a TODO[1] and RfC for a possible etch release of the s390 port
about 2 months ago, and did not get any usefull reply.
As I'm the last person working on the core (and lack of time), there is
a large need for help. The main problems are currently hardware
configuration and
On Wed, Dec 21, 2005 at 02:53:54PM -0300, Jerônimo Bezerra wrote:
I am Jeronimo and I work at one University in Brazil and here we have a
S/390. We installed the Debian Woody 3.0 some time ago, and now we have
make a another installation with Sarge 3.1, and if possible, using a
kernel 2.6. Is
On Sat, Nov 19, 2005 at 12:12:51PM +0100, Sven Luther wrote:
I disabled the dasd patch in parted 1.6.23, because it didn't apply cleanly,
and there where some changes which made it non-trivial for me to fix it, i
asked you on irc to look at it, and think i also mailed here, but nothing
Hi folks
As s390 is currently not in a good shape, I tried to produce a list of
things which needs to be done for a possible etch release of this
architecture. Please provide some feedback.
Hardware configuration
==
In linux 2.6, the complete hardware configuration on s390 is
On Sun, Nov 13, 2005 at 12:44:40PM -0500, Daniel Jacobowitz wrote:
What kernel is the build daemon running? Does it have threading
problems? I don't think glibc 2.3.5 has ever successfully autobuilt on
s390.
It was built on debian01 which runs 2.6.11.
Bastian
--
Youth doesn't excuse
On Sun, Nov 13, 2005 at 02:04:45PM -0500, Daniel Jacobowitz wrote:
On Sun, Nov 13, 2005 at 07:30:47PM +0100, Bastian Blank wrote:
On Sun, Nov 13, 2005 at 12:44:40PM -0500, Daniel Jacobowitz wrote:
What kernel is the build daemon running? Does it have threading
problems? I don't think
-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Don't use va_list more than once.
+
+ -- Bastian Blank [EMAIL PROTECTED] Tue, 11 Oct 2005 07:22:00 +
+
htp (1.15-2) unstable; urgency=low
* Fixed memory problems in s390
--- htp-1.15.orig/src/streams.c
+++ htp-1.15/src
On Sun, Oct 09, 2005 at 02:14:28PM +0200, Kevin Glynn wrote:
The first file we try to compile is
giving a dynamic type error. Since this works successfully on
(nearly) all other platforms I am thinking the emulator must be
corrupt.
It is not built on powerpc,
On Sun, Oct 09, 2005 at 04:47:53PM +0200, Bastian Blank wrote:
I am seeing similar issues on m68k, which I have access to but
progress is slow (e.g. package builds fine with gcc 3.3 but fails with
most recent gcc 4.x).
Ah, that looks like problems with undefined behaviour
Hi folks
I've started a wiki page to start collecting info for the s390 requalification
for etch:
http://wiki.debian.org/s390EtchReleaseRecertification
On Sat, Oct 08, 2005 at 09:07:38PM +0200, Frans Pop wrote:
Actually, this should be easy. You probably need only one or two examples
of production installations to have hundreds of users...
I know about BfF (Bundesamt für Finanzen). About 150 Guests on two
machines with sarge and 1500 users.
On Mon, Sep 26, 2005 at 05:25:55PM +0200, Gerhard Tonn wrote:
Due to lack of time I am not able to do the s390 porting work anymore. I
am looking for someone
who is interested to take over the s390 port.
I'm interrested in taking over the s390 port.
Bastian
--
The best diplomat I know is a
On Fri, Sep 30, 2005 at 09:33:09AM -0500, Adam Thornton wrote:
It's not clear to me that the buildd
maintainer's duties exactly are, or, critically, how much time per
week it takes.
I'm able to handle the buildds. I already did that some time ago.
Bastian
--
On Fri, Mar 25, 2005 at 08:56:24PM -0800, Steve Langasek wrote:
Can someone do a recompile binNMU of these
packages for s390, to spare the trouble of rebuilding on all architectures?
The recompiles are on my todo.
Bastian
--
Live long and prosper.
On Fri, Mar 18, 2005 at 06:36:29PM -0600, Carlo U. Segre wrote:
I am at a loss to figure out what might be wrong here so I can't even file
a bug. It looks like on the s390 there is a version of wxWindows 2.5
which is being used instead of the current Debian version 2.4.
wxWindows always
On Sun, Nov 21, 2004 at 02:28:10PM -0500, Patrick Finnegan wrote:
Any ideas?
Use a new version of the installer.
Bastian
--
There are certain things men must do to remain men.
-- Kirk, The Ultimate Computer, stardate 4929.4
signature.asc
Description: Digital signature
I just found a serious problem with woody-sarge upgrades on s390. zipl
from s390-utils 1.3.1 uses an ioctl which was introduced somewhere after
patch 10 for 2.4.21 (it works properly with debian 2.4.27 which is
based on patch 15).
The complete error is:
| unknown ioctl: 1268
| Error: Could
The linux 2.6.8 kernel image for s390 got accepted.
This images are built with initrd enabled. This makes it possible to IPL
via zfcp but you have to specify the options for dasd and/or zfcp in
/etc/modprobe.d.
Also there is currently nothing to configure the network devices via
sysfs, this have
I released linux 2.4.27 for s390. The uploaded packages are available
from http://raptor.debian.org/kernel/debian/. Please test them as we
want to release sarg with 2.4.27.
Bastian
--
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, Day of
Try:
On Tue, Aug 10, 2004 at 08:28:16PM +0200, Matthias Urlichs wrote:
debian31.tdf
@TDF
/daten/hercules/kernel31.debian fixed recsize 1024
/daten/hercules/parmfile31.debian fixed recsize 1024
/daten/hercules/initrd31.debian fixed recsize 1024
TM
TM
EOT
Bastian
--
Beauty is
Package: ftp.debian.org
Version: N/V
Please remove the following s390 kernel patch and images packages from
unstable:
* kernel-patch-2.4.19-s390
* kernel-image-2.4.17-s390
* kernel-image-2.4.19-s390
Bastian
--
You can't evaluate a man by logic alone.
-- McCoy, I, Mudd, stardate
Hi folks
s390 was not released as part of beta3. The reason is easy: there is no
working partitioner because anything in d-i relays on the ability of
parted to read the disklabel.
The remain is easy
- network device support for chandev is working except iucv.
- dasd support seems to work.
What
Package: kernel-patch-2.4.21-s390
Version: 2.4.21.10-3
Severity: grave
linux-2.4.21-vmparms.diff breaks ipl from reader.
Bastian
--
Hailing frequencies open, Captain.
signature.asc
Description: Digital signature
On Sat, Feb 28, 2004 at 02:41:28PM +, Martin Michlmayr wrote:
Are those packages needed? Can someone co-maintain them?
They are horrible outdated but needed until the new packages are
accepted.
Bastian
--
Leave bigotry in your quarters; there's no room for it on the bridge.
Hi folks
As IBM don't release patches for not-so-broken kernels, both holes in
plain 2.4.21 seems to be exploitable on s390, I tried to merge the hole
patch into 2.4.25.
It works fine with vm minidiscs and QDIO Guest LANs.
http://raptor.debian.org/kernel/linux-2.4.25-s390-unofficial.diff.bz2
On Tue, Feb 17, 2004 at 10:34:06AM +0200, Riku Voipio wrote:
I am trying to trace the kdebase build failure a little more,
but I would need a s390 chroot with kdebase build depends
installed (apt-get build-dep kdebase). Is this possible to
arrange?
Try raptor.d.o.
Bastian
--
The idea of
On Tue, Dec 09, 2003 at 01:16:09PM -0500, Rodney S. Clayton wrote:
I have a running Debian s/390 system that is using VCTCA's for
connectivity. I would like to download the QDIO module and add this kind
of NIC.
I have been unable to fine the driver for Debian or the directions for
setting
On Fri, Oct 10, 2003 at 03:19:42AM -0500, Branden Robinson wrote:
After the s390-specific commits I made today, Bastian seems to have had
a successful build of a (modified) 4.3.0-0pre1v3.
no, it failes on usr/X11R6/lib/X11/doc/README.dps (xfree86-common)
bastian
--
The heart is not a logical
On Wed, Oct 08, 2003 at 11:50:43AM +1000, Daniel Stone wrote:
* s390 has never tried to build XFree86 4.3.0 as far as I can tell.
Bastian Blank attempted several times, got tripped up by the DRI foolery and
other NOT_BUILDING_XF86_SERVER fun, and ended up giving up.
After getting enough
On Wed, Sep 10, 2003 at 04:32:25PM -0400, Daniel Jacobowitz wrote:
Ncurses now tries to build a 64-bit library. But it looks like the
S/390 build daemon can't _run_ 64-bit binaries? Do I need to make it
do this as a cross-compile instead?
none of the s390 autobuilders run 64bit kernels.
On Wed, Jun 25, 2003 at 12:27:11PM +0200, Kasza Karoly wrote:
My question is: Is it possible to run debian in 64 bit mode?
If it is, does 64bit deb packages exists?
64bit glibc packages and 64bit compilers exists but no 64bit kernel.
Or do you plan to
On Wed, Dec 18, 2002 at 09:48:55AM +0100, Gerhard Tonn wrote:
The complete toolchain, gcc-3.2, binutils and glibc, has been enabled for
biarch support recently. This means that you can compile and link 64 bit
applications in unstable using the -m64 flag. As soon as the modutils are
also
On Sun, Dec 08, 2002 at 06:53:42PM +0100, Russell Coker wrote:
In the main root of raptor.debian.org.
Or am I supposed to do all development in chroot's?
the main root is a little bit problematic. i want to move the machine to
a 64bit kernel. it needs new modutils and i don't want to rebuild
On Sun, Dec 08, 2002 at 09:30:58PM +0100, Russell Coker wrote:
[...]
i try to compile the test program. first it isn't c, so i need to fix
it. i compile it with gcc 3.2 and -D_FILE_OFFSET_BITS=64.
it seems to work fine.
| $ ./test ./test1 1000
| Seeking to 1000
| $ ls -al test1
|
hi folks
i'm currently working on a s390x port of debian.
now we are able to release them, but the question is, do we need them?
or should we use a 64 bit kernel with a 31 bit userland like sparc does.
bastian
--
Bones: The man's DEAD, Jim!
pgpVaKrlTggb6.pgp
Description: PGP signature
On Mon, Sep 16, 2002 at 01:18:13PM -0500, Dennis Wicks wrote:
Thanks, but I am not up to the s390x yet.
I am still running in a 32-bit world!
the patch is the same for 31 and 64 bit.
bastian
--
War isn't a good life, but it's life.
-- Kirk, A Private Little War, stardate
100 matches
Mail list logo
