Re: Bug#281394: env2debconf doesn't work on s390
On Mon, Nov 15, 2004 at 11:26:24AM -0500, Post, Mark K wrote: I don't know why, but I was aware that only _certain_ variables would get set. That's why I wound up modifying the Red Hat installer to parse /proc/cmdline instead, for the Slack/390 installer. That works every time, and I got tired of trying to figure out what variables would get picked up and which ones wouldn't. ;) The kernel removes all vars it knows about and passes on the remaining ones into env. For sure something changing over time... greetings, Florian La Roche -- 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
Re: More on Fedora...
On Tue, Jan 06, 2004 at 05:12:02PM -0500, Post, Mark K wrote: No, Red Hat 7.2 came with rpm-4.0.3 (I just checked), so it should work. If you want to experiment with Fedora Core rpms (http://download.fedora.redhat.com/) and setup a snapshot of the current Fedora development: You can try running an update from RHL7.2 via e.g. yum or rpm itself. (yum would help to automatically find the right set of rpms, otherwise you have to experiment a bit.) Or maybe try a for i in *.rpm ; do rpm2cpio $i | cpio -i -d; done to get a mostly working chroot setup. greetings, Florian La Roche
Re: RHEL v3.0 oddness
On Thu, Dec 04, 2003 at 12:04:23PM -0600, Wilson, Eric wrote: Has anyone seen this kind of oddness before: A look at the process table does not show the processes listening and owned by init, things like root sshd or portmap: Please look in bugzilla.redhat.com #110895 for a fix. greetings, Florian La Roche
Re: hertz timer on rhel3
Put a different way, Why should I have to modify the kernel since I can get a distribution that will let me turn the jiffy pop off? That's a good way to end a discussion on public mailinglists. greetings, Florian La Roche
Re: Getting gcc Ada to build
On Sat, Nov 22, 2003 at 08:38:53PM -0500, Post, Mark K wrote: Does anyone know what patches/magic incantations are necessary to get gcc to build the Ada compiler on Linux/390? When I build gcc, Ada never gets built. You need an existing Ada compiler. Maybe just extract the debian one or the Red Hat one, then compile your own with that. greetings, Florian La Roche
Re: Tivoli client for RH EL3 AS beta on s390?
On Wed, Sep 24, 2003 at 06:59:06AM -0400, Daniel Jarboe wrote: Thanks Phil, Any idea when this will be available? The only compat's I see on the redhat ftp site for taroon/s390 are compat-db and compat-pwdb. Management does not want to get too in depth with moving sample workloads to evaluate the new platform without a tivoli client working. You can register via Red Hat Network to get updates for this beta. Details should be in the release notes for the beta. I have also uploaded the newest rpms to http://people.redhat.com/laroche/ greetings, Florian La Roche
Re: [rhelv3-announce-admin@redhat.com: Announcing Red Hat Enterprise Linux 3 (Taroon) Beta 2 Public Availability]
On Wed, Aug 27, 2003 at 08:03:10AM -0600, Ferguson, Neale wrote: Using anonymous FTP to ftp.redhat.com/pub/linux/beta/taroon is rejected as the permissions on taroon is rwxr-x---. Yes, it is still getting pushed out. Sorry for the extra delay, Florian La Roche -Original Message- FTP Availability Installable binary ISO images, RPM packages, and source RPMs are also available at: ftp://ftp.redhat.com/pub/redhat/linux/beta/taroon
[rhelv3-announce-admin@redhat.com: Announcing Red Hat Enterprise Linux 3 (Taroon) Beta 2 Public Availability]
FYI - Forwarded message from [EMAIL PROTECTED] - From: [EMAIL PROTECTED] Subject: Announcing Red Hat Enterprise Linux 3 (Taroon) Beta 2 Public Availability To: [EMAIL PROTECTED] Date: 26 Aug 2003 16:32:56 -0400 Red Hat is pleased to announce the general availability of Red Hat Enterprise Linux 3 (Taroon) Beta 2. Beta 2 contains a large number of installer and package bug fixes and updates since Beta 1. If you have an existing Taroon Beta 1 installation, Red Hat strongly recommends that you simply bring your system up to date on a regular basis using Red Hat Network as described below. A full re-installation with Beta 2 ISOs is required only for testing of installer-related bug fixes. This is a public beta. Please feel free to forward this announcement to anyone within or outside your organization who may be interested in testing this beta release. Red Hat Enterprise Linux 3 is the next generation of our comprehensive suite of Linux operating systems -- designed for mission-critical enterprise computing and certified by top enterprise software vendors. More information on the current Red Hat Enterprise Linux 2.1 product line is available at http://www.redhat.com/software/rhel/. This announcement includes details on obtaining the beta software, reporting bugs, and communicating with Red Hat and other testers via mailing lists during the beta period. Red Hat Enterprise Linux 3 Beta 2 is available for the following architectures: - x86 (i686/Athlon 32-bit) - ia64 (Intel Itanium2 64-bit) - x86_64 (AMD64 64-bit) - ppc (IBM iSeries and pSeries 64-bit) - s390 (IBM S/390 31-bit) - s390x (IBM zSeries 64-bit) Red Hat Enterprise Linux 3 Beta 2 is available in two variants: - Red Hat Enterprise Linux AS * Designed for server applications, includes the core operating system as well as network server packages * Available for x86, ia64, x86_64, ppc, s390, s390x - Red Hat Enterprise Linux WS * Designed for workstation applications, includes the core operating system as well as desktop productivity, development, communications, and network client packages * Available for x86, ia64, x86_64 A third variant, Red Hat Enterprise Linux ES, designed for mid-range server applications, has an identical package set to Red Hat Enterprise Linux AS at Beta 2. General users interested in the ES product should test the AS Beta 2 release. Red Hat Enterprise Linux 3 Beta 2 contains a wide range of new features, including but not limited to the following: - Kernel based on 2.4.21 with numerous scalability enhancements: * Native Posix Threading Library (NPTL) * Thread Local Storage Futex APIs * Per-device locks for block IO * Memory management enhancements: RMAP VM large pages support * O(1) scheduler * Hyperthreading scheduler * Integrated Summit chipset support * NFS performance stability enhancements * Large Translation Buffer pages - hugetlbfs * Ext3 updates for performance and stability * Semtimedop b semaphores with time limitation * Fine-grain process accounting (x86 only) * ACPI 2.0 (Itanium2 AMD64 only) * Many driver updates and additions - 4GB/4GB Kernel/User Memory Split (x86 hugemem kernel only) * Support for up to 64GB on x86 * 4GB of virtual address space for kernel and almost 4GB for each user process on x86 - Development Environment * gcc 3.2.3 tool chain * gcc ssa tool chain included as a technology preview * gcj / libgcj (Java gcc compiler front-end) * gdb 5.3.90 - including multi-threaded core dump and gcore * glibc 2.3.2 * Eclipse 2.1 Developer Environment - Improved I/O subsystem * 64-bit SCSI/Fibre Channel DMA support * Up to 256 SCSI devices * VaryIO support (permits larger I/O transfers) * Serial ATA support - SATA1 (for Intel PIIX/ICH ATA ICH5) * Hotplug PCI framework (x86 and ia64 only) * Asynchronous I/O on sockets * Expanded Asynchronous I/O for disks support - Desktop enhancements * XFree86 4.3.0 * Bluecurve (tm) graphical user interface (Unified GNOME/KDE look and feel) * OpenOffice.org 1.0.2 office productivity suite * Ximian Evolution 1.4.4 * Mozilla 1.4 - Improved serviceability * Logical Volume Manager (LVM1) support * Kernel crash dump and analysis enhancements * Configurable application core dump paths * Code profiling support included in the kernel (OProfile) * Support for diskless systems - Networking Enhancements * Improvements to channel bonding * Failover bandwidth aggregation for servers w/ multiple NICs * More complete kernel IPv6 support * Kernel IGMP V2 and V3 support * Samba 3.0 (Beta) * Apache 2.0 web server * Red Hat Content Accelerator update - Security enhancements * Filesystem ACLs * General purpose cryptographic API in the Kernel * Position Independent Executables * Kernel support for ipsec on IPv4 - Red Hat Cluster Manager enhancements *
Re: Installing Debian 3.0r1 (woody) on Hercules/390
I can't figure out this problem, I spent about 3 hours last night trying to configure vsftpd correctly and got nowhere. I noticed that the ftp method Please note, this might open up a security problem and should only be done on safe/firewalled systems: If you change the home directory of the ftp user in /etc/passwd to /, you can use anonymous ftp to all your data. Normally you only see files within /var/ftp/. If possible, just make sure to put the necessary files within /var/ftp/, then you should be able to see them with normal ftp (no user/passwords given). greetings, Florian La Roche
Re: [rhelv3-announce-admin@redhat.com: Announcing Red Hat Enterprise Linux 3 (Taroon) Beta 1 Public Availability]
On Wed, Jul 30, 2003 at 12:14:13PM -0400, [EMAIL PROTECTED] wrote: I haven't found any item that is not already covered in the below announcement. You may test and report any mainframe bugs you find. How about install doc for s390? I didn't see a location... is it on the CD's? Or should one go with the 7.2 s390 install doc? Parts of readme/release-notes are s390-only. Documentation now also has s390-specific additions, but this has not been pushed out onto the ftp-server. greetings, Florian La Roche
[rhelv3-announce-admin@redhat.com: Announcing Red Hat Enterprise Linux 3 (Taroon) Beta 1 Public Availability]
I haven't found any item that is not already covered in the below announcement. You may test and report any mainframe bugs you find. greetings, Florian La Roche - Forwarded message from [EMAIL PROTECTED] - From: [EMAIL PROTECTED] Subject: Announcing Red Hat Enterprise Linux 3 (Taroon) Beta 1 Public Availability To: [EMAIL PROTECTED] Date: 29 Jul 2003 11:15:06 -0400 Red Hat is pleased to announce the general availability of Red Hat Enterprise Linux 3 Beta 1 (Taroon). This is a public beta. Please feel free to forward this announcement to anyone within or outside your organization who may be interested in testing this beta release. Red Hat Enterprise Linux 3 is the next generation of our comprehensive suite of Linux operating systems -- designed for mission-critical enterprise computing and certified by top enterprise software vendors. More information on the current Red Hat Enterprise Linux 2.1 product line is available at http://www.redhat.com/software/rhel/. This announcement includes details on obtaining the beta software, reporting bugs, and communicating with Red Hat and other testers via mailing lists during the beta period. Red Hat Enterprise Linux 3 Beta 1 is available for the following architectures: - x86 (i686/Athlon 32-bit) - ia64 (Intel Itanium2 64-bit) - x86_64 (AMD64 64-bit) - ppc (IBM iSeries and pSeries 64-bit) - s390 (IBM S/390 31-bit) - s390x (IBM zSeries 64-bit) Red Hat Enterprise Linux 3 Beta 1 is available in two variants: - Red Hat Enterprise Linux AS * Designed for server applications, includes the core operating system as well as network server packages * Available for x86, ia64, x86_64, ppc, s390, s390x - Red Hat Enterprise Linux WS * Designed for workstation applications, includes the core operating system as well as desktop productivity, development, communications, and network client packages * Available for x86, ia64, x86_64 A third variant, Red Hat Enterprise Linux ES, designed for mid-range server applications, has an identical package set to Red Hat Enterprise Linux AS at Beta 1. General users interested in the ES product should test the AS Beta 1 release. Red Hat Enterprise Linux 3 Beta 1 contains a wide range of new features, including but not limited to the following: - Kernel based on 2.4.21 with numerous scalability enhancements: * Native Posix Threading Library (NPTL) * Thread Local Storage Futex APIs * Per-device locks for block IO * Memory management enhancements: RMAP VM large pages support * O(1) scheduler * Hyperthreading scheduler * Integrated Summit chipset support * NFS performance stability enhancements * Large Translation Buffer pages - hugetlbfs * Ext3 updates for performance and stability * Semtimedop b semaphores with time limitation * Fine-grain process accounting (x86 only) * ACPI 2.0 (Itanium2 AMD64 only) * Many driver updates and additions - 4GB/4GB Kernel/User Memory Split (x86 bigmem kernel only) * Support for up to 64GB on x86 * 4GB of virtual address space for kernel and almost 4GB for each user process on x86 - Development Environment * gcc 3.2.3 tool chain * gcc ssa tool chain included as a technology preview * gcj / libgcj (Java gcc compiler front-end) * gdb 5.3.90 - including multi-threaded core dump and gcore * glibc 2.3.2 * Eclipse 2.1 Developer Environment - Improved I/O subsystem * 64-bit SCSI/Fibre Channel DMA support * Up to 256 SCSI devices * VaryIO support (permits larger I/O transfers) * Serial ATA support - SATA1 (for Intel PIIX/ICH ATA ICH5) * Hotplug PCI framework (x86 and ia64 only) * Asynchronous I/O on sockets * Expanded Asynchronous I/O for disks support - Desktop enhancements * XFree86 4.3.0 * Bluecurve (tm) graphical user interface (Unified GNOME/KDE look and feel) * OpenOffice.org 1.0.2 office productivity suite * Ximian Evolution 1.4.3 * Mozilla 1.4 - Improved serviceability * Logical Volume Manager (LVM1) support * Kernel crash dump and analysis enhancements * Configurable application core dump paths * Code profiling support included in the kernel (OProfile) * Support for diskless systems - Networking Enhancements * Improvements to channel bonding * Failover bandwidth aggregation for servers w/ multiple NICs * More complete kernel IPv6 support * Kernel IGMP updated from V2 to V3 * Samba 3.0 (Beta) * Apache 2.0 web server * TUX web accelerator update - Security enhancements * Filesystem ACLs * General purpose cryptographic API in the Kernel * Position Independent Executables * Kernel support for ipsec on IPV4 - Red Hat Cluster Manager enhancement * Multinode high availability clustering with new GUI Current features, packages, and naming are subject to change before the final release. The Red Hat Enterprise Linux development team would like to encourage you to test
Re: Call for testers: kaffe-1.1.0 on s390-linux
On Thu, Jun 12, 2003 at 10:53:45AM -0700, Dalibor Topic wrote: hi all, kaffe 1.1.0 [1] was released a few days ago, and I've been testing it on as many platforms as I could get my hands on ;) Getting my hands on a s90-linux box seems to be somewhat hard, so it would be nice if someone here had some spare time to ./configure make make check kaffe on a s390-linux machine and report the results back to the kaffe mailing list on [EMAIL PROTECTED] Stops for me with: stringParsing.c: In function `pushFrame': stringParsing.c:113: incompatible types in assignment environment: gcc-3.2.3-7 glibc-2.3.2-50 ./configure --with-threads=unix-jthreads Needed patch: --- kaffe-1.1.0/config/s390/linux/md.h +++ kaffe-1.1.0/config/s390/linux/md.h @@ -23,4 +23,9 @@ extern void init_md(void); #defineINIT_MD() init_md() +#define SIGNAL_ARGS(sig, sc) int sig, struct sigcontext sc +#define SIGNAL_CONTEXT_POINTER(scp) struct sigcontext * scp +#define GET_SIGNAL_CONTEXT_POINTER(sc) (sc) +#define SIGNAL_PC(scp) scp-eip + #endif Dunno how much further time I can find for this the next days... greetings, Florian La Roche
Re: X11 SSH tunneling + Gnome desktop
Gnome works in WeirdX quite nicely, and weirdmind. Its not stunningly bandwidth efficient but it works. Gnome is supposed by several non Linux vendors on non Linux systems and any case it didn't run on a basic server without extensions is considered a bug Some of the problems with non-XFree86 servers are hard to debug. ;-) On the other side Linux is getting much better to cooperate with the hardware and software around it... greetings, Florian La Roche
Re: SLES 8
I just read a CERT advisory for YASB. In the Vendor Comments, Red Hat is working on it. When we have a fix the advisory will be posted to ... The Sendmail Consortium has fixes. No comments from anyone else, I don't know whether they were asked. http://people.redhat.com/laroche/ has src.rpms with appropriate patches included and you might want to change errata within the spec file to compile this for different Red Hat Linux releases. Official errata rpms for this are still within our QA department and should be released shortly. It is really bad for QA departments as well as for many sysadmins if such security problems show up on a sunny and nice saturday. ;-) greetings, Florian La Roche
Re: API to get fullpath name
On Wed, Mar 05, 2003 at 06:46:55PM -0500, Ferguson, Neale wrote: How do I, within a program, get the full pathname of the program I'm executing? argv[0] will have the command name but not necessarily the full pathname. You can also look at /proc/pid/exe or if argv[] only has partial information you can search PATH and match possible applications against device/inode information from /proc/pid/maps. greetings, Florian La Roche
Re: mingetty and console output
On Sun, Jan 12, 2003 at 11:31:44AM +0100, Florian La Roche wrote: On Sun, Jan 12, 2003 at 12:09:53PM +0200, Tzafrir Cohen wrote: Hi I have an init script that writes output to the console (I've ruled out redirecting its output to a file or to network syslog for various reasons) The trouble is that as soon as mingetty starts, I can no longer see the output of that script. You could change mingetty to not use vhangup() to invalidate the filehandels to the console. Normally daemon programs should use syslog or file logging, but vhangup() on /dev/console also looks a bit odd. I have not been good at releasing updated mingetty versions. The one in debian is still the one released in 1996. ;-) Last summer I made a re-release by just applying the patches that have been applied to version shipped with Red Hat Linux and named the result mingetty-1.0. Over the last days I have again looked at the source and adapted it to more current Linux releases. http://people.redhat.com/laroche/ contains a new version that also has a --novhangup option that should take care about the above things and I have queued a couple of further things like reading a config file and also allowing automatic logins in different ways that I hope to add soon and release at the same location... greetings, Florian *feature release of mingetty* La Roche
Re: so correct me if I am wrong
On Fri, Feb 21, 2003 at 10:55:40AM -0500, Post, Mark K wrote: Eric, It depends on how you define current. Red Hat has put some updates out there for their Linux/390 platforms, but not as many has they have for their Intel ones. There was a thread a little while back about the lack of security updates for their Linux/390 platforms. Since they do put out the SRPMs (source RPMs), you can download those and build the binary for installation, but that can be, ummm, a chore, and it certainly chews up CPU time for packages of any size. (I'm currently in the process of re-building glibc 2.2.5, and it's going on 24 hours of wall clock time. Open Office took me about a _month_, on a much bigger machine that this one.) Hello Mark, OpenOffice is one of the very few rpms within Red Hat Linux that has not yet mainframe patches merged in. If you have patches for the current rpm in rawhide, I'll try to get OO included for rawhide binary rpms. ;-) I think we had OO running internally within RH, but not merged these things into our official development sources AFAIK. Will check on this next week... Next would then be to look at startup times for OO and how much time you can save by using the nice prelinking framework that Jakub Jelinek has put together, including the mainframe arch. greetings, Florian La Roche
Re: Compilation Failure in gdb 5.2.1
On Tue, Feb 18, 2003 at 06:23:59PM -0500, Post, Mark K wrote: I'm getting a compilation error on my SuSE 7.0 system. I've upgraded to gcc 3.2, binutils 2.12.90.0.15, and glibc 2.2.5, so asking SuSE for help is not going to go very far. What I'm seeing is this: gcc -c -O2 -fsigned-char-I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode -I../bfd -I./../bfd -I./../include -I../intl -I./../intl -DMI_OUT=1 -DUI_OUT=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized thread-db.c thread-db.c: In function `thread_db_fetch_registers': thread-db.c:804: cannot convert to a pointer type thread-db.c: In function `thread_db_store_registers': thread-db.c:837: cannot convert to a pointer type make[1]: *** [thread-db.o] Error 1 make[1]: Leaving directory `/usr/src/packages/BUILD/gdb-5.2.1/gdb' make: *** [all-gdb] Error 2 Back in December of 2001, Nish Deodhar reported the same problem with gdb 5.1, and talked about the changes he made to get it to compile. Jim Blandy from Red Hat/Cygnus asked him a few questions about what he'd done, but the gdb 5.2.1, and 5.3 source doesn't reflect those changes. So, I have to assume that they weren't considered a good fix by the gdb maintainers. I manually re-compiled the module with --save-temps. If anyone could help me figure out what needs to be done to get this to compile, I would appreciate it. All src.rpms we push out to ftp://ftp.redhat.com/pub/redhat/linux/rawhide/ SRPMS/SRPMS/ contain our newest mainframe support, so maybe the following packages contain what you are looking for: - binutils-2.13.90.0.18-6 - glibc-2.3.1-46 - gcc-3.2.2-1 - gdb-5.3post-0.20021129.12 For gdb specifically you could also take the source rpm from Red Hat Linux 8.0 x86, as that has been based on gdb-5.2.1 and did compile for me at the time we released RHL8. greetings, Florian La Roche
Re: mingetty and console output
On Sun, Jan 12, 2003 at 08:56:36PM +, Alan Cox wrote: On Sun, 2003-01-12 at 19:54, Post, Mark K wrote: There is no analog to virtual consoles in Linux/390. In the kernel this is true. In user space you can run multiple parallel sessions on a vtxxx terminal with 'screen', including disconnecting them and leaving them running, logging in somewhere else and reattaching (sort of as VMS provides) mingetty uses vhangup() to invalidate all accesses to a tty and in general all daemon programs should either use syslog or log to a file. You can easily change mingetty to not call vhangup() for the /dev/console on mainframe, or you can directly call bash on the console and not call mingetty at all. greetings, Florian La Roche
Re: How to move a Linux system to another DASD volume
On Wed, Jan 08, 2003 at 04:18:39PM +1100, BAKER, Craig wrote: Greetings, We have just added a Shark DASD subsystem to our z800 and we now want to move our ThinkBlue64 Linux System to it from our existing DASD. The approach that I took was to backup the filesystem using tar then restore it to the new DASD. Then I updated zipl.conf on the new DASD and ran zipl against it. When I boot from the new DASD it gets past recognising the new DASD and mounts the root filesystem then I get Kernel Panic: unable to load init try passing init= to the kernel. rsync -avx --delete / /new_dasd might also be a good way to copy things. This copy stops at mount point boundaries. So what else do I need to do to make this work? To copy a root partition you might have to edit /etc/fstab and /etc/zipl.conf in the new system. I suspect you are not using an initrd to boot, that could also need to be modified. greetings, Florian La Roche Thanks in advance Craig Baker ** This e-mail message (along with any attachments) is intended only for the named addressee and may contain information that is confidential or privileged. If you are not the intended recipient you are hereby notified that any dissemination, copying or use of any of the information is prohibited. If you have received this e-mail message in error, please notify us immediately by return e-mail and delete all copies of the original message and attachments. ** *** This E-Mail has been checked for viruses ***
Re: What to ask RedHat presenters about SuSE on OS/390 vs Redhat?
On Mon, Nov 11, 2002 at 09:38:16AM -0500, David Boyes wrote: I don't think that Red Hat is new to non-IA32 archs at all. I'm sure I'm getting my years wrong, but they did have an Alpha and Sparc port throughout the late 1990s. At least until 2000, I believe. I remember talking with a customer just after RH discontinued the Sparc port, and the RH person in the room casually said if you'd buy 600 copies at full price, they'd bring it back. ftp.auroralinux.org contains a real nice and stable sparc port of Red Hat Linux 7.3. It has many sparc fixes in it as well as some important errata rpms past the release. Should be a real nice start and in general you can easily recompile further errata rpms released for x86. Red Hat Linux is very modular and in general easily ported to new archs, the question is more the demand for such ports. greetings, Florian La Roche
Re: MTU size
On Thu, Aug 22, 2002 at 03:58:41PM +0200, Moloko Monyepao wrote: Where do I change my MTU size to come up the same as the VM one during IPL/BOOTING of the Linux system. I have done a manual ifconfig on Linux to 1500 and changed my VM site to 1500 the errors keep on increasing. /etc/sysconfig/network-scripts/ifcfg-iucv0: MTU=1400 greetings, Florian La Roche
Re: make errors, but rpms written. cause for concern?
On Tue, Jul 30, 2002 at 10:05:18AM -0400, [EMAIL PROTECTED] wrote: rh7.2. Trying to upgrade glibc 2.2.4-24.2 to glibc 2.2.4-27... rebuild from srpm with a few errors, but ultimately the s390.rpms were written. I think I have added newer glibc s390 patches, but didn't include the fixups that have been done to the glibc tests. greetings, Florian La Roche
new glibc/gcc releases
http://people.redhat.com/drepper has nice information on more recent glibc-2.3 and gcc-3.1 changes going on wrt performance tuning. Also Jakub Jelinek has implemented S/390 support for prelinking some time ago. greetings, Florian La Roche
Re: glibc 2.2.5 make install problem
i actually want to compile the glibc 2.2.5 i have a gcc 3.1 and binutils 2.12.90.0.4 i have applied the S390-may2002 patches on all of them the gcc and binutils had no problems in compiling and installing. when i launch the make for glibc, i get this error : [...] sorry, it's a french redhat. the errors should be : ../sysdeps/unix/sysv/linux/s390/s390-32/sysdep.S: Assembler message ../sysdeps/unix/sysv/linux/s390/s390-32/sysdep.S:82: ERROR: backward reference to an unknown target 0: we tried to look at this file but we didn't see anything. Works fine for me based on Red Hat Linux 7.3 if you add gcc 3.1 and binutils 2.12.90.0.4 and also use some rawhide rpms to get updates to compile with gcc-3.1. Are you using the glibc-2.2.5 from Red Hat Linux 7.3? That's working fine for me and even newer CVS versions of glibc don't have much newer mainframe things added (at least a few days ago). greetings, Florian La Roche
Re: Nedit - slick but no 390 port :
On Thu, May 30, 2002 at 06:43:09AM -0700, Lionel Dyck wrote: Here is what I get with that file: syslbd@mlnxd001:~/nedit-5.3RC1-source make linux (cd util; make -f Makefile.linux libNUtil.a) make[1]: Entering directory `/home/syslbd/nedit-5.3RC1-source/util' cc -O -I/usr/X11R6/include -DUSE_DIRENT -DUSE_LPR_PRINT_CMD -c -o DialogF.o DialogF.c DialogF.c:33: Xm/Xm.h: No such file or directory DialogF.c:34: Xm/MessageB.h: No such file or directory DialogF.c:35: Xm/DialogS.h: No such file or directory DialogF.c:36: Xm/PushB.h: No such file or directory DialogF.c:37: Xm/PushBG.h: No such file or directory DialogF.c:38: Xm/SelectioB.h: No such file or directory make[1]: *** [DialogF.o] Error 1 make[1]: Leaving directory `/home/syslbd/nedit-5.3RC1-source/util' make: *** [linux] Error 2 Apparently I'm missing some other file ?? openmotif first. Source rpms from Red Hat Linux 7.3 seem to work fine for me. greetings, Florian La Roche
Re: RH72 telnet
Others can tell you how to allow root to telnet in, but I won't, cause I like you. :) I hold you in high esteem, also, but if I were to do something to cause you NOT to like me ... THEN would you tell me :) ? (Remember ... this is only a 'temporary' thing, right?). BTW, ARE you saying I could create user accounts that could telnet in? Using ssh is best, right? Any other user account is ok. A real quick and bad hack is to rm -f /etc/securetty, then you can login as root. Another is to change the pam requirements and delete pam_securetty for telnet. You did hear warnings that using ssh is best, right? cu, Florian La Roche
Re: RPM question
On Thu, May 23, 2002 at 12:34:40PM -0400, Dave Myers wrote: I tried installing the glibc-common-2.2.4-20.s390.rpm from the RH 7.2 updates FTP site. I get this if I use: rpm -Uvh glibc-common-2.2.4-20.s390.rpm error: failed dependencies: glibc-common = 2.2.4-19a is needed by glibc-2.2.4-19a AndI get this if I use: rpm -ivh glibc-common-2.2.4-20.s390.rpm file /usr/share/i18n/charmaps/VISCII.gz from install of glibc-common-2.2.4-20 conflicts with file from package glibc-common-2.2.4-19a ...so do I have to go find the 2.2.4-19a RPM first and install that one before this one?? If so, where do I get that one, since it's not in the RH update dir?? To update all errata rpms, I personally do: - Specify kernel directly and install it in addition to the old one. rpm -ivh kernel-2.4.9-37.s390.rpm - Maybe change to boot this kernel: vi /etc/zipl.conf and zipl - Update all further rpms from the errata dir that are already installed: rpm -Fvh *.rpm The last command can fail as rpm is not yet smart enough to resolve newly added dependencies, then I use some rpm -Uvh blah and try again with rpm -Fvh *.rpm For updating only glibc, you can do rpm -Fvh glibc*.rpm nscd*.rpm and it should also work fine. cu, Florian La Roche
Re: beta version for Red Hat Linux 7.2 S/390
On Thu, May 23, 2002 at 02:52:27PM -0700, Tim Pepper wrote: On Tue 21 May at 15:18:35 +0200 [EMAIL PROTECTED] done said: Please test ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390/ and let us know about any problems left. Please also note that the latest OCO modules from IBM for the Red Hat Linux kernel 2.4.9-37 contain a special ocord.img which allows installation of Red Hat Linux via OCO drivers. Details in our docs. I'm curious...does the 390 arch kernel base itself on the same src rpm as the i386? In particular would the 2.4.9-37 for 390 include any patches that had made it into 2.4.9-31 for i386? All patches form 2.4.9-31 are included and most further patches are specific s390 patches which haven't been included in time to make .31. :-) cu, Florian La Roche TIA for any info! Tim -- * * tpepper@vato dot org * Venimus, Vidimus, * * http://www.vato.org/~tpepper * Dolavimus * *
Re: RPM question
On Fri, May 24, 2002 at 11:39:21AM -0400, Dave Myers wrote: In a message dated 5/24/2002 12:50:49 AM Mountain Daylight Time, [EMAIL PROTECTED] writes: For updating only glibc, you can do rpm -Fvh glibc*.rpm nscd*.rpm and it should also work fine. Florian, Why the nscd*.rpm I updated glibc yesterday and it did not call out this requisite?? :-) Then it seems to be fine without it. I thought there has been a requirement within nscd to specify the exact glibc version. If that has changed or if you didn't have nscd installed in the first place, everything is fine. My intention was to satisfy rpm requirements. If they don't exist, that is fine. Also these things don't make any real difference if you haven't enabled it (/etc/init.d/nscd and /etc/nscd.conf) cu, Florian La Roche
Re: beta version for Red Hat Linux 7.2 S/390
On Thu, May 23, 2002 at 10:22:50AM -0400, Post, Mark K wrote: Florian, Thanks for the response. One area is still unanswered, though. How is this update going to be stored on the FTP server? What directories will it be in? The same ones as the original GA version, or somewhere else? I ask because I'd like to be able to very clearly explain to anyone who asks, just what is what, and how to tell them apart, etc. Not discussed yet AFAIK. :-) I personally would expect a new subdirectoy leaving the old thing in place. That would then also allow a clean comparison on what the changes are. Just overwriting an existing path only creates confusion and problems. (On top of the many ftp-download problems I see for the mainframe. Only measure we took for this are md5sum files, maybe a future version can do better checks within the installer as well.) cu, Florian La Roche Thanks again. Mark Post -Original Message- From: Florian La Roche [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 12:30 PM To: [EMAIL PROTECTED] Subject: Re: beta version for Red Hat Linux 7.2 S/390 On Tue, May 21, 2002 at 09:43:12AM -0400, Post, Mark K wrote: Florian, Just so I better understand what your and Red Hat's maintenance philosophy is, could you explain whether the results of this beta will be moved into the 7.2 GA updates directory, or will a 7.2a be created, or 7.3, or something else? Just where will this be put, and how will people know that Hello Mark, Normally Red Hat only provides full releases and all updates are then available as rpm packages from the ftp-server and also via our automated update mechanism Red Hat Network (RHN). Since the mainframe needs networking during the installation phase, we are doing a special update of our base distribution of Red Hat Linux 7.2 for S/390 in addition of providing those updates also for existing users on our ftp-server. So there is no difference between updating an existing installation and installing from this newer version. cu, Florian La Roche it is different from the original 7.2 GA, etc., etc. This will be the first time I and a lot of other people have been exposed to this, and it would be very helpful if you could talk about it at some length. Thanks in advance for any insight you can provide. Mark Post -Original Message- From: Florian La Roche [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 9:19 AM To: [EMAIL PROTECTED] Subject: beta version for Red Hat Linux 7.2 S/390 The current rawhide version incorporates a lot of patches for the kernel, glibc, gcc, the installation environment etc. Please test ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390/ and let us know about any problems left. Please also note that the latest OCO modules from IBM for the Red Hat Linux kernel 2.4.9-37 contain a special ocord.img which allows installation of Red Hat Linux via OCO drivers. Details in our docs. We welcome testing of this current rawhide version, but please understand that future uploads to this url might again change to more development releases. For the real adventurous here who want to look at gcc-3.1: We have slightly tested binutils-2.12.90.0.7-1 and gcc3-3.1-1. You can compile these from ftp://ftp.redhat.com/pub/redhat/linux/rawhide/SRPMS/SRPMS/ and test them on S/390 and zSeries. This should really be done by more advanced users and only on Linux guests you can delete if things go really wrong. cu, Florian La Roche
beta version for Red Hat Linux 7.2 S/390
The current rawhide version incorporates a lot of patches for the kernel, glibc, gcc, the installation environment etc. Please test ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390/ and let us know about any problems left. Please also note that the latest OCO modules from IBM for the Red Hat Linux kernel 2.4.9-37 contain a special ocord.img which allows installation of Red Hat Linux via OCO drivers. Details in our docs. We welcome testing of this current rawhide version, but please understand that future uploads to this url might again change to more development releases. For the real adventurous here who want to look at gcc-3.1: We have slightly tested binutils-2.12.90.0.7-1 and gcc3-3.1-1. You can compile these from ftp://ftp.redhat.com/pub/redhat/linux/rawhide/SRPMS/SRPMS/ and test them on S/390 and zSeries. This should really be done by more advanced users and only on Linux guests you can delete if things go really wrong. cu, Florian La Roche
Re: beta version for Red Hat Linux 7.2 S/390
On Tue, May 21, 2002 at 09:43:12AM -0400, Post, Mark K wrote: Florian, Just so I better understand what your and Red Hat's maintenance philosophy is, could you explain whether the results of this beta will be moved into the 7.2 GA updates directory, or will a 7.2a be created, or 7.3, or something else? Just where will this be put, and how will people know that Hello Mark, Normally Red Hat only provides full releases and all updates are then available as rpm packages from the ftp-server and also via our automated update mechanism Red Hat Network (RHN). Since the mainframe needs networking during the installation phase, we are doing a special update of our base distribution of Red Hat Linux 7.2 for S/390 in addition of providing those updates also for existing users on our ftp-server. So there is no difference between updating an existing installation and installing from this newer version. cu, Florian La Roche it is different from the original 7.2 GA, etc., etc. This will be the first time I and a lot of other people have been exposed to this, and it would be very helpful if you could talk about it at some length. Thanks in advance for any insight you can provide. Mark Post -Original Message- From: Florian La Roche [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 9:19 AM To: [EMAIL PROTECTED] Subject: beta version for Red Hat Linux 7.2 S/390 The current rawhide version incorporates a lot of patches for the kernel, glibc, gcc, the installation environment etc. Please test ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390/ and let us know about any problems left. Please also note that the latest OCO modules from IBM for the Red Hat Linux kernel 2.4.9-37 contain a special ocord.img which allows installation of Red Hat Linux via OCO drivers. Details in our docs. We welcome testing of this current rawhide version, but please understand that future uploads to this url might again change to more development releases. For the real adventurous here who want to look at gcc-3.1: We have slightly tested binutils-2.12.90.0.7-1 and gcc3-3.1-1. You can compile these from ftp://ftp.redhat.com/pub/redhat/linux/rawhide/SRPMS/SRPMS/ and test them on S/390 and zSeries. This should really be done by more advanced users and only on Linux guests you can delete if things go really wrong. cu, Florian La Roche
Re: Red Hat Sites Extremely Busy
On Tue, May 07, 2002 at 10:25:52AM -0400, Post, Mark K wrote: I've been trying to connect to some/any Red Hat FTP servers/mirrors, and they're all just about saturated. Has Red Hat made something GA yesterday or today to cause this? Red Hat Linux 7.3 x86 is out. I am confident this is a good release. :-) cu, Florian La Roche Mark Post
Re: Linux shutdown on VM
On Tue, Apr 30, 2002 at 12:53:51PM -0400, Sivey,Lonny wrote: I have a RedHat 7.2 system I would like to logoff when a shutdown is done. I added vmhalt=logoff to the kernel parameters, but, this seems to have no affect. What am I missing? Hello Lonny Sivey, I've had a quick look into the kernel source and this should be ok. (I remember that I posted some time ago this feature is disabled in the kernel, but I was wrong on that.) Maybe you use the power-off variant and everything works fine with the vmpoff= option for you? cu, Florian La Roche Thanks, Lonny _ Lonny Sivey System Support Division OCLC Online Computer Library Center, Inc. 6565 Frantz Rd, Dublin, OH 43017 (614) 764-6013 FAX (614) 718-7200 mailto:[EMAIL PROTECTED] _
Re: Red Hat 7.2 - install by tape?
On Fri, Apr 26, 2002 at 12:55:14PM -0700, Makhijani, Beena wrote: Thanks Mark, Mike, and Florian for your responses. Florian, please forgive my ignorance, but I need some clarification: Is applying the rpm at http://people.redhat.com/dsainty/ equivalent to applying the updates at ftp://ftp.redhat.com/pub/redhat/linux/updates/7.2/en/os/s390 that Mike mentioned? i.e. I will still have the problem Mike noted about not being able to insmod the qdio/qeth driver? And if so, can someone tell me what it means to not be able to insmod the qdio/qeth driver? (I am new to UNIX). Also, the site http://people.redhat.com/dsainty/ seems to be about Windows NT/2000 and Linux. Is that the right site for the rpm? Keep the kernel at the same level, then the binary-only networking drivers from IBM should continue working with it. Only update the samba rpm, make sure you update to a s390 rpm, not a Intel version. cu, Florian La Roche Thanks, Beena
Re: VNC and its web server and its creators
On Sat, Apr 27, 2002 at 10:34:14AM +0200, Rob van der Heij wrote: At 20:51 26-04-02 -0400, Gregg C Levine wrote: Yet. So, what is the current version of VNC that was compiled for the big iron/big penguin community? Feel free to pick up some at ftp://ftp.iae.nl/pub/users/rvdheij/vnc/ Despite Ross' posting the patches to their list, the VNC folks never included the s390 patches in their code. ftp://ftp.redhat.com/pub/redhat/linux/rawhide/SRPMS/SRPMS/vnc-3.3.3r2-28.src.rpm contains the newest version of vnc from Red Hat and the above s390 patches have also been extended to s390x. rpm --rebuild vnc-3.3.3r2-28.src.rpm should work fine... cu, Florian La Roche
Re: Red Hat 7.2 - install by tape?
On Fri, Apr 26, 2002 at 08:17:18AM -0400, Michael MacIsaac wrote: I am new to Linux (and UNIX) but need to do a proof-of-concept for using Linux on S390 for file and print serving. I was planning to use Red Hat 7.2 Be warned - using the GA code, the kernel will oops when you first write to a Samba share. You will want to apply the updates (However, if you apply the updates you will not be able to insmod the qdio/qeth driver, so you must be using a different network driver - hopefully this issue will be resolved soon). Please ask IBM about this. They can provide working modules on a case by case basis. The samba issue can also be cured by new rpms from http://people.redhat.com/dsainty/, but overall we recommend applying new errata rpms we release from Red Hat, since the kernel patches fix many s390 problems, many s390-specific problems etc. cu, Florian La Roche Florian La Roche Tel.: +49-711-96437-460 head of development EMEA Tel.: +49-172-6373899 Red Hat GmbH Fax.: +49-711-96437-111 Hauptstaetterstr. 58 Email: [EMAIL PROTECTED] D-70178 Stuttgarthttp://www.redhat.de/ GA code is at: ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/s390/ Updates are at: ftp://ftp.redhat.com/pub/redhat/linux/updates/7.2/en/os/s390/ Install GA, download all update RPMs to a directory and do rpm -Fvh * Then modify zipl.conf to pick up the new kernel # cd /etc # diff zipl.conf zipl.conf.orig 5c5 image=/boot/vmlinuz-2.4.9-31 --- image=/boot/vmlinuz-2.4.9-17 # zipl reboot. -Mike MacIsaac, IBM [EMAIL PROTECTED] (845) 433-7061
Re: your own x86 mainframe
On Fri, Apr 19, 2002 at 05:02:57PM -0400, Gary A. Ernst wrote: Is this a Fixed (DASD Driver) 2.4.x kernel ??? Last time I tried to install RedHat Linux/S390 under hercules I had the well known Dasd problem under hercules. 2.2.x kernels work fine as well as Millenux 64bit 2.4.x. hercules has a workaround for this, I haven't checked if our kernel is also fixed. cu, Florian La Roche
Re: RH 7.2 Install Issues
+ insmod netiucv.o iucv=$TCPIP
netiucv: Invalid delimiter '$'
NETIUCV driver Version: 1.12 initialized
I cannot find where/how this is output within the source. :-(
netiucv.c:
printk (KERN_NOTICE netiucv: IUCV network driver LEVEL \n);
on the other side I see ctcmain.c:
static void print_banner(void) {
static int printed = 0;
char vbuf[] = $Revision: 1.46 $;
char *version = vbuf;
if (printed)
return;
if ((version = strchr(version, ':'))) {
char *p = strchr(version + 1, '$');
if (p)
*p = '\0';
} else
version = ??? ;
printk(KERN_INFO CTC driver Version%s initialized\n, version);
printed = 1;
}
Based on another whole bunch of tests I ran, it appears to be a bug in the
netiucv.o module that doesn't show up when IUCV support is compiled into the
kernel itself.
Something very strange, or I am looking at the wrong source here.
Florian, is there any chance you could build an install kernel with IUCV
support compiled in for Chet to test under VIF?
Probably best to create a custom kernel and change the initrd to not load
the iucv driver?
Anybody able to get this running at all? What happens with the rawhide
version?
cu,
Florian La Roche
Re: FBA for Jay [was: Re: How to pre-allocate a 4GB File?]
On Thu, Apr 18, 2002 at 01:04:28PM -0500, Jay Maynard wrote: On Thu, Apr 18, 2002 at 12:44:13PM -0500, Adam Thornton wrote: Note that CD can be presented as FBA *today* on some S/390. Specifically, for P/390 (and presumably for Multiprise) a CD image, a .iso file, can be configured to the S/390 as an FBA. Yup. Works on a Multiprise too, as Dave Jones can attest. And, for that matter, on Hercules. (Which is one reason I want .iso files to install Linux/390 from...it can't be any slower than an FTP install over a Hercules CTC.) Jay Maynard, if the author of hercules wants to have this, I'll reconsider this for the next rawhide upload. :-) At least our 64bit version already has iso images available, so you might already test with those if you have enough RAM/CPU available. cu, Florian La Roche
Re: compile error with 31-bit RedHat 7.2
On Tue, Apr 16, 2002 at 01:43:48PM -0400, Tung-Sing Chong wrote: Florian, Thanks for your respond. add this as a patch to the kernel src.rpm and then rebuild the -- Do you mean rebuilding the kernel with 2.4.9-31 source tree and compile my file again? Anyway I did the following ways and got the same error: 1 - applied kernel-2.4.9-31.s390.rpm, modutils-2.4.13-0.7.1.s390.rpm, kernel-source-2.4.9-31.s390.rpm and kernel-headers-2.4.9-31.s390.rpm. IPLed the system with shipped 2.4.9-31 kernel and compiled the testvm.c from /usr/src/linux2.4.9-31 tree. 2 - Rebuilt the kernel with the 2.4.9.-31 updates. IPLed the system with the rebuilt kernel and compiled the testvm.c from /usr/src/linux2.4.9-31 tree. However when I changed the Makefile in the directory /usr/src/linux2.4/drivers/s390/net to include the testvm.o and did the make modules, the testvm.c was complied with only warning (no undeclared error). I did this on both 2.4.9-17 and 2.4.9-31 kernel and trees. And I was also able to insmod the testvm.o with no error. This is a good possibility to compile a module matching one kernel. Though there is no guarantee that one module can be used for the 4 different kernel versions that we ship with Red Hat Linux. Your above method works fine for a fast development cycle, but if you want to distribute the modules to other people, you should compile the module against all four kernel versions we ship and that can be most easily be done by using the source rpm, adding this new module and recompiling the whole kernel. cu, Florian La Roche (I do not have to do this on SuSE SLES-7.0). The changed (in bold) /usr/src/linux2.4/drivers/s390/net/Makefile: -- # # S/390 network devices # O_TARGET := s390-net.o list-multi := ctc.o export-objs := iucv.o fsm-s390.o ctc-objs := ctcmain.o ctctty.o testvm.o obj-y += iucv.o fsm-s390.o obj-$(CONFIG_CTC) += ctc.o obj-$(CONFIG_IUCV) += netiucv.o include $(TOPDIR)/Rules.make ctc.o: $(ctc-objs) $(LD) -r -o $@ $(ctc-objs) My scaled down (only have #includes and #defines) testvm.c: Too bad, I thought I could see the whole source. :-) :-) /*/ /*/ /* Debug defines */ /* #define DEBUG 1 */ /* #define DEBUG_MORE */ #define MODULE /* includes */ #include linux/module.h #include linux/autoconf.h #if defined(CONFIG_MODVERSIONS) !defined(MODVERSIONS) # define MODVERSIONS #endif #ifdef MODVERSIONS # include linux/modversions.h #endif #include linux/kernel.h #include linux/config.h #include linux/errno.h #include linux/socket.h #include linux/sched.h #include linux/time.h #include linux/string.h #include linux/net.h #include linux/mm.h #include linux/interrupt.h #include linux/proc_fs.h #include linux/init.h #include linux/poll.h #include linux/inet.h #include linux/skbuff.h #include linux/unistd.h #include linux/if_arp.h #include linux/route.h #include net/protocol.h #include net/sock.h #include net/inet_common.h #include asm/io.h #include asm/system.h #include asm/ebcdic.h #include linux/version.h We are currently working on porting an application on to 2.4 kernel. We did that for SuSE-SLES 7.0 (2.4.7) and now we like to work on the Redhat distribution. Any help will be greatly appreciated. Thanks, Chong Tung-Sing Chong Software Engineer VM development, IBM S/390 Software Endicott, NY T/l : 852-5342 Outside Phone: 607-752-5342 E-mail: [EMAIL PROTECTED] Florian La Roche [EMAIL PROTECTED]@VM.MARIST.EDU on 04/12/2002 04:57:35 PM Please respond to Linux on 390 Port [EMAIL PROTECTED] Sent by:Linux on 390 Port [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: compile error with 31-bit RedHat 7.2 On Fri, Apr 12, 2002 at 03:38:16PM -0400, Tung-Sing Chong wrote: Hi, I been trying to compile a test c file on my 31-bit RedHat 7.2 and I got the /usr/src/linux-2.4.9-31/include/asm/pgalloc.h:225: 'machine_flags_Rsmp_69afa35e' undeclared (first use in this function) error. Please see the following: I'd advise to add this as a patch to the kernel src.rpm and then rebuild the complete kernel to build kernel modules. Or unpack the kernel, select your correct config cp linux/configs/* linux/.config; make oldconfig; ... and build your modul in that tree. Or just send your testvm.c file here... :-) cu, Florian La Roche [root@lxssl6 linux-2.4]# make /usr/src/linux-2.4/drivers/s390/net/testvm.o gcc -D__KERNEL__ -I/usr/src/linux-2.4.9-31/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -Wno-unused -pipe -fno-strength-reduce -c -o /usr/src/linux-2.4/drivers/s390/net/testvm.o /usr/src/linux-2.4/drivers/s390/net/testvm.c In file
Re: OK who messed with the redbook?
On Mon, Apr 15, 2002 at 12:32:30PM -0400, Greg Smith wrote: James Melin wrote: If anyone feels like e-mailing me the PDF of the redbook with* the hercules stuff in it, please do. Try ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/s390/docs/ or a related mirror site. ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390/utils/hercules/ also has sample config files and a recent cvs version of hercules, which has really improved a real lot during the recent months. A nearly complete install of Red Hat Linux takes about 5 1/2 hours for me on a 1800 Mhz AMD machine. :-) Most applications work reasonable fast, but I wouldn't recommend this for real development. Looking/testing/evaluation should be ok with this. cu, Florian La Roche
Re: RedHat 7.2 31-bit w/IBM LCS
On Wed, Apr 03, 2002 at 12:28:38PM -0500, Larry Heath wrote: Florian, What would it take to incent RedHat to generate the 31-bit ramdisk (and kernel) with the IBM LCS code integrated?? Hello Larry Heath, ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390/ contains new images with: - kernel-2.4.9-31.1 - GPL lcs driver for a more Open Source platform thanks to IBM - current s390 patches - would support installation of OCO modules from a second initrd - new installation support with a current anaconda - most updates for 7.2 are already included So this includes all stable updates as well as some goodies, but please keep in mind that this is a totally unsupported rawhide version that might just disappear, change unstable, break your hardware etc. Official updates for Red Hat Linux 7.2 mostly done, only the kernel and the new install support need some more time. The above rawhide version should ensure it is tested within enough different setups. We've got lots of free coffee! Install rawhide and let us know if anything is not working. Thanks, Florian La Roche P.S.: The cvs version of hercules also supports LCS...
Re: ESCON CTCs for a RH 7.2 LPAR install
On Thu, Apr 04, 2002 at 12:38:19PM -0500, Dave Myers wrote: In a message dated 4/3/2002 5:53:46 PM Mountain Standard Time, [EMAIL PROTECTED] writes: Paul, If you're going to be going to the Red Hat 7.2, you need to specify the chandev parameter twice, once as CHANDEV= and once as chandev= Mark Post huh...I missed this oneis this a definite requirement? What's the symptom if you don't do this? chandev= is used for the kernel running during the installation. CHANDEV= is used for the configuration written into the installed system. (Might be /etc/zipl.conf or /etc/chandev.conf.) cu, Florian La Roche
Re: How to update critical files?
On Thu, Apr 04, 2002 at 07:49:15AM +0200, Rob van der Heij wrote: I'm about to program changes to critical files. How does one do that in a reliable way? On CMS one would do it like this: - create a new file out of the current one - rename current to backup with NOUPDIR option - rename new to current The NOUPDIR prevents update on disk, so the next rename effectively does both in one go. When writing the directory to disk CMS itself creates the new one, and does a final write to swap between the old and new one. If anytime during this process the light would go out, I would still have a consistent disk (either with or without the change). How do you do this with Linux. I suppose I should minimize the window by creating a new file and then do the renames. But the way dirty pages are written to disk I could end up with a disk that has the new directory but not the new file? I don't think I can tell Linux to commit the change to disk, so should I do a sync before the renames and assume that the two renames short after each other will be written out in a single I/O operation? Write into a new temporary filename that is in the same directory, then rename into the final filename. Catch some important signals like HUP and TERM and add cleanup routines to your program. You can use special temporary filenames in case no cleanup is possible and they stay on the filesystem. With some more efford, make sure you create a new temporary dir for each possible filesystem and create your new files in it. Then rename the files out of this dir into the final destination. cu, Florian La Roche
Re: 32 bit binaries loadable in zSeries GA's from Red Hat/SuSE?
On Thu, Mar 21, 2002 at 09:01:54AM -0500, James Tison wrote: I'm running ThinkBlue 7.1a, an early zSeries Linux release. It won't load ELF32 binaries. Can anyone report if ELF32 *and* ELF64 binaries are loading on the newer pre-GA distros from either Red Hat or SuSE? This might explain some of the (64 bit) tags on ld.so.1, for example, I've seen in the Red Hat binary RPMs Hello James Tison, Older Red Hat Linux beta versions contained glibc-emu31* rpms providing this support, newer versions now have compat-* rpms which provide this. At the moment we only support glibc/libstdc++ and e.g. no ncurses libs or further libs. This should cover IBM JDK, DB2 and Websphere. Now is the right time to raise your voice about missing bits wrt to our existing 31bit compat support. What apps do you want to run with it? :-) cu, Florian La Roche
Re: [Redhat-s390-list] RedHat 7.2 Kernel Compile Failure
On Thu, Mar 21, 2002 at 10:58:07AM -0500, Wainwright, Oliver (Exchange) wrote: Where do I get the kernel-source SRPM? I checked the official RedHat 7.2 s390 5 CD set, the kernel-2.4.9-17.src.rpm under SRPMS did not contain the include for math-emu. If you install a src.rpm as root, your files are normally copied into /usr/src/redhat/SPECS and /usr/src/redhat/SOURCES. If you start rpm -bb /usr/src/redhat/SPECS/kernel-2.4.spec, the kernel will be unpacked below /usr/src/redhat/BUILD and the result should show up in /usr/src/redhat/RPMS/s390/. If you start a rpm -bp /usr/src/redhat/SPECS/kernel-2.4.spec your kernel will be available in /usr/src/redhat/BUILD/kernel-2.4/linux. You can then also manually compile/install it liked you are used with the tree in /usr/src/linux. cu, Florian La Roche Please advise. -Original Message- From: Post, Mark K [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, March 20, 2002 5:33 PM To: '[EMAIL PROTECTED]' Subject:RE: [Redhat-s390-list] RedHat 7.2 Kernel Compile Failure Yes, this is a known problem with the kernel-source RPM. You will need to install the kernel SRPM (note the difference) to be able to recompile your kernel. Mark Post -Original Message- From: Wainwright, Oliver (Exchange) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 20, 2002 4:31 PM To: '[EMAIL PROTECTED]' Cc: #LinuxMF Subject: [Redhat-s390-list] RedHat 7.2 Kernel Compile Failure I am having a problem recompiling my kernel. I have all packages installed and am running redhat 7.2 s390, kernel is 2.4.9-17. I appear to be missing the includes directory under my source tree. I have received the error on two different servers. Please advise. make -C arch/s390/math-emu fastdep make[2]: Entering directory `/usr/src/linux-2.4.9-17/arch/s390/math-emu' /usr/src/linux-2.4.9-17/scripts/mkdep -D__KERNEL__ -I/usr/src/linux-2.4.9-17/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -Wno-unused -pipe -fno-strength-reduce -I. -I/usr/src/linux-2.4.9-17/include/math-emu -w -- math.c qrnnd.S sfp-util.h .depend realpath(/usr/src/linux-2.4.9-17/include/math-emu) failed, No such file or directory make[2]: *** [fastdep] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.9-17/arch/s390/math-emu' make[1]: *** [_sfdep_arch/s390/math-emu] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.9-17' make: *** [dep-files] Error 2 oliver wainwright unix engineering bear stearns co, inc. landline: 973-793-7567 fax: 973-793-2530 Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *** ___ Redhat-s390-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-s390-list ___ Redhat-s390-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-s390-list Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *** ___ Redhat-s390-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-s390-list
Re: Questions on latest RedHat Beta
Couple of questions on this latest beta: 1. Noticed a /ISO directory with ISO filenames that begin with 7.1. Are these really this latest beta release and can I FTP them and use them for install? Yes. Newer ones should be available next monday. 2. Noticed in the /update directory very recent RPMs (openssh, zlib to name a few). SHould those be installed, instead of the ones in /RedHat/RPMS An update is fine, the next version will already include them per default. 3. The doc in README, RELEASE-NOTES and /docu don't seem to be up-to-date and accurate, but yet the email above says there are many bug-fixes for the installation (are there newer README and RELEASE-NOTES some where??) What things are not accurate? 4. What is GOLD-MASTER ? We are still working on this. greetings, Florian La Roche
Re: Red Hat Linux for zSeries
On Fri, Mar 15, 2002 at 09:52:51AM +0100, Ursula Biskup wrote: -fix for samba problems Does this concern this one: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=58737 ?? Hello Ursula Biskup, I have heard that disabling dnotify fixes the problems. This can either be done by using the kernel from zSeries as currently available in the rawhide upload or by patching the samba rpm to disable it. It would help us if we get more success reports with those fixes, then we can look into providing official updates from Red Hat. It has been discussed in this list some time ago But the problem with Samba still seems not to be fixed! What versions of samba/kernel are you currently using? Or anybody else who has been concerned has come over this problem? Thanks, Florian La Roche Thanks in advance for any help Uschi Biskup -Urspr|ngliche Nachricht- Von: Linux on 390 Port [mailto:[EMAIL PROTECTED]]Im Auftrag von Florian La Roche Gesendet am: Dienstag, 12. Mdrz 2002 12:40 An: [EMAIL PROTECTED] Betreff: Red Hat Linux for zSeries We have uploaded our current beta to: ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390x/ Some of the changes: - kernel contains: - GPL lcs driver is now included - fix for samba problems - order2-3 patch from IBM - many bug-fixes for the installation - all rpms are now compiled with the newest binutils patch from IBM - htdig/squid plus some other rpm updates We'd be very interested to hear about remaining problems and get feedback about the current version. We don't expect any larger patches between now and gold-master, but only further testing can prove this right or wrong. greetings, Florian La Roche Florian La Roche Tel.: +49-711-96437-460 head of development EMEA Tel.: +49-172-6373899 Red Hat GmbH Fax.: +49-711-96437-111 Hauptstaetterstr. 58 Email: [EMAIL PROTECTED] D-70178 Stuttgarthttp://www.redhat.de/
Re: ipl tape
I red RedBook, but, at least, in my case, it doesn't work. May be they try to use tapes only with DEVFS? Maybe try the following patch to assign it to some other major number: --- linux/drivers/s390/char/tapechar.h.nodevfs Thu Aug 16 17:20:15 2001 +++ linux/drivers/s390/char/tapechar.h Thu Aug 16 17:21:55 2001 -17,7 +17,8 #define TAPECHAR_H #include linux/config.h #define TAPECHAR_DEFAULTMODE 0020644 -#define TAPE_MAJOR0/* get dynamic major since no major officialy defined for tape */ +/* #define TAPE_MAJOR0 get dynamic major since no major officialy defined for tape */ +#define TAPE_MAJOR 37 /* Umm... we need to create device nodes in /dev... */ /* * Prototypes for tape_fops */ cu, Florian La Roche #mknod /dev/rtibm0 c 254 0 (first rewinding character device) #mknod /dev/ntibm0 c 254 0 (first non-rewinding character device) #mknod /dev/btibm0 b 254 0 (first block device) #mknod /dev/rtibm1 c 254 1 (second rewinding character device) #mknod /dev/ntibm1 c 254 1 (second non-rewinding character device) #mknod /dev/btibm1 b 254 1 (second block device) How that corresponds to Sergey's success using ntibm1, I don't know. But, it may be worth a try.
Red Hat Linux for zSeries
We have uploaded our current beta to: ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390x/ Some of the changes: - kernel contains: - GPL lcs driver is now included - fix for samba problems - order2-3 patch from IBM - many bug-fixes for the installation - all rpms are now compiled with the newest binutils patch from IBM - htdig/squid plus some other rpm updates We'd be very interested to hear about remaining problems and get feedback about the current version. We don't expect any larger patches between now and gold-master, but only further testing can prove this right or wrong. greetings, Florian La Roche Florian La Roche Tel.: +49-711-96437-460 head of development EMEA Tel.: +49-172-6373899 Red Hat GmbH Fax.: +49-711-96437-111 Hauptstaetterstr. 58 Email: [EMAIL PROTECTED] D-70178 Stuttgarthttp://www.redhat.de/
Red Hat Linux for zSeries
Thanks a lot for all the feedback about our initial zSeries upload. We have made incremental updates to that version and have now a Release Candidate (RC) available from: ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390x/ This version does now go through our Red Hat Linux Quality Assurance (QA) process to test different installation paths as well as the correct functioning of the rpm packages and the Red Hat Linux kernel. Included are all the newest zSeries patches from IBM and 31bit compat libraries for e.g. IBM JDK. greetings, Florian La Roche Florian La Roche Tel.: +49-711-96437-460 head of development EMEA Tel.: +49-172-6373899 Red Hat GmbH Fax.: +49-711-96437-111 Hauptstaetterstr. 58 Email: [EMAIL PROTECTED] D-70178 Stuttgarthttp://www.redhat.de/
Re: MD Software Raid Question
In fact: Florian, you're reading this, right? This was on a Jurix box that is *still* in production in Maryland. I have finally converted my home machine to Red Hat Linux. Old stuff is still under chroot available, so if I start feeling old, I can go back playing with these things again... :-) Nice to see these things are still used and from time to time I also get email about it from all over the world. You are still missing some more advanced things about jurix like my own package management system that I used for jurix. Making updates easy and allowing to look at all the changes between the distribution itself and the installed system. Written in 1997, also has nice GPL headers, but I have not gotten around to release it. :-) Maybe I come around to it later this year... cu, Florian La Roche
Re: top
On Thu, Feb 21, 2002 at 09:57:24AM -0500, Ferguson, Neale wrote: Is there any problem with top under Linux/390 (s390/s390x)? It's performance is hideous with anything like 100 processes in the system. top usually becomes the biggest CPU user. I don't see the same on non-S390 platforms non-Linux systems probably? Some computations to gather process information take a long time and probably top is also not very intelligent on how to re-read /proc information. (Haven't actually looked into the source for these gross assumptions.) cu, Florian La Roche with equivalent numbers of processes in the system. Neale
public beta for Red Hat Linux zSeries
Good morning dear LINUX-390@ readers, we have uploaded a public beta version of Red Hat Linux for zSeries to ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390x/ You can send bug-reports to [EMAIL PROTECTED] or enter them into our bug-tracking system at http://bugzilla.redhat.com/bugzilla. The more bugs you find, the more we can possibly fix until GA. We currently think that gcc/binutils/glibc won't change anymore. Most stabilization effords will go into the kernel and the installation support. At the moment only rhsetup is working, our standard installation tool anaconda should follow ASAP. Feel free to request more features, new functionality, ... Now is the time to tell us. We will make frequent updates to this version, so please make sure you have a correct mirror from our ftp-server and not the version from yesterday. cu, Florian La Roche Florian La Roche Tel.: +49-711-96437-460 head of development EMEA Tel.: +49-172-6373899 Red Hat GmbH Fax.: +49-711-96437-111 Hauptstaetterstr. 58 Email: [EMAIL PROTECTED] D-70178 Stuttgarthttp://www.redhat.de/
Re: RedHat 7.2 ifdown hangs / kernel oops
On Fri, Feb 08, 2002 at 04:00:43PM +0100, Carsten Sommer wrote: Hi, we have a RedHat 7.2 system using an osa-express for network. If I try to reboot or manually execute /sbin/ifdown ifcfg-eth0 /sbin/ifdown hangs. The command that is causing the problem is ip -o link ls dev eth0. I have used strace to see what is going on. Ip seems to communicate with the kernel through the netlink socket and finally hangs in the recvmsg syscall. After a while I get a kernel oops. Is this a known bug? Any suggestions? Hello Carsten Sommer, Can you please provide the kernel oops for this? Wat is the md5sum of your drivers? Thanks, Florian La Roche If you need more information (strace log, kernel oops output, etc.) I can mail it. Regards Carsten -- Linux on zSeries - Team becom informationssysteme GmbH Lohbachstr. 12 58239 Schwerte - Germany Phone: +49 (0)2304 - 931-3 Fax: +49 (0)2304 - 931-401 e-mail: [EMAIL PROTECTED]
Re: Redhat CTC Problem
On Fri, Feb 01, 2002 at 12:30:55PM +0200, Moloko Monyepao wrote: I am installing Redhat 7.2 using a tape driveon an LPAR. When I include my Escon/CTC parameters in my parmfile I get the following error: CTC0: read ch 3230 (irq 107A), write (irq 107b) Proto 0 SIOCSIRADDR: No such device escon0: No such device SIOCADDRT: No such device SIOCADDRT: No such device The following is my parmfile : root=/dev/ram0 ro ip=off DASD=112a-112b CHANDEV=escon0,0x3230,0x3231 HOST=lnx1.eskom.co.za:escon0:147.110.49.17:147.110.49.13:1492 I am no expert on the S/390 devices, but I thought they are now always given the name ctc0 instead of the older escon0 name. Have you tried changing this to ctc0? cu, Florian La Roche Please assists Moloko
Re: SLES 7.2 and Java
On Fri, Feb 01, 2002 at 01:19:19PM -0500, Hines Daniel (sys1dmh) wrote: We are having the same issue - the current Java 1.3 release is for the 2.2 kernel. IBM is working on JAVA 1.3 for for the 2.4 kernel but has not gone GA yet You can still copy older libraries on your system and modify the Java wrapper scripts to use these older libs and have the rest of your system updated to the newest and greatest. Red Hat Linux 7.2 has all this prepared as far as I know, you just have to install the compat*.rpm libs. cu, Florian La Roche
Re: RH 7.2 for 390
Robis looking at tweaking the rhsetup script to allow for
installation from local hard disk. This would let you FTP the RPMs
to a linux disk, make the same disk bootable via the ramdisk,
and then you could install by IPLing that disk and getting the files from the
same local hard disk...
Rob...any progress :)
Should already be supported, though real testing as well as documentation
might not be done yet. We welcome any patches or testing of course. :-)
cu,
Florian La Roche
P.S.: Searching for mount also gives:
mkdir -p $CD1MOUNTP $CD2MOUNTP /mnt/source/CD1 /mnt/source/CD2
mount -t ext2 /dev/$ISO1DASD $CD1MOUNTP /dev/null 21
mount -t iso9660 -o loop $CD1MOUNTP/$ISO1 /mnt/source/CD1
test -d /mnt/source/CD1/RedHat/RPMS || {
umount /mnt/source/CD1 /dev/null 21
umount $CD1MOUNTP /dev/null 21
rm -rf $CD1MOUNTP $CD2MOUNTP /mnt/source/CD? /dev/null
abortinstall No Red Hat directory structure found on CD image 1.
}
if [ $ISO1DASD != $ISO2DASD ]; then
mount -t ext2 /dev/$ISO2DASD $CD2MOUNTP /dev/null 21
fi
mount -t iso9660 -o loop $CD2MOUNTP/$ISO2 /mnt/source/CD2
Red Hat rawhide update
Another update for the installation code as well as the anaconda and s390utils rpms has been done at ftp://ftp.redhat.de/pub/s390-rawhide and ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390/. If no further bug-reports come in about this version, we will push out official updates for the Red Hat Linux 7.2 for S/390 product within the next days. cu, Florian La Roche
Re: Why not IBM's Linux
On Mon, Jan 21, 2002 at 12:49:06PM -0500, David Boyes wrote: Why isn't anyone discussing going with IBM's ThinkBlue version of Linux, especially looking at 64-bit implementations? ThinkBlue's actually a separate company, not at all part of IBM. Wrt to 64 bit, there really aren't that many applications that need 64bit addressibility (SAP aside -- but then again, SAP needs all the resources you can possibly give it and then some...). Millenux has ported Red Hat Linux 7.1 to zSeries last April. They have changed two lines in our 31bit installer of that time and have added about 40 further patches to Red Hat Linux to work on zSeries. (Hmmm, our simple installer is also derived from a Red Hat Linux port for 31 bit that Millenux has done, so Red Hat definitely uses quite some work from Millenux here.) They have then improved this version by adding patches to the installer as well as updating their kernel to include ext3 and newer IBM patches. Overall a very nice and clean port of Red Hat Linux and I think still the only 64 bit port available from a ftp-server. I can only recommend to use this version... cu, Florian La Roche
Re: tape390.o unresolved symbols
/lib/modules/2.2.19/tape390.o: unresolved symbol __copy_to_user_fixup /lib/modules/2.2.19/tape390.o: unresolved symbol __copy_from_user_fixup CONFIG_MOD_VERSIONS should not be set? Florian La Roche
Re: ramdisk getting ./chroot: cannot execute /bin/ksh: No such file or directory
On Thu, Jan 17, 2002 at 05:31:18PM -0500, Dave Myers wrote: What does this error mean...coming from my RH 7.2 ramdisk system ? I see /bin/ksh in /bin and it's executable # ./chroot /mnt/sysimage ./chroot: cannot execute /bin/ksh: No such file or directory Try giving an existing shell: chroot /mnt/sysimage /bin/sh cu, Florian La Roche
Re: RC.CONFIG for RedHat
On Tue, Jan 15, 2002 at 11:45:42AM -0500, Coffin Michael C wrote: Hi Holger, True to some respect - my reason for asking is I need to automate the cloning of Linux images and to that extent I don't want to reinvent the wheel if the wheel has already been invented. The problem, as you point out, is that each distribution has a different idea of what the wheel should be. I've already fully automated the cloning and configuration of Linux images using SuSE - so I guess I'll need a RedHat distribution specific configuration tool that does the same thing (only touches, directly, a lot more files). For some cloning tasks, it makes sense to install once and just use that image for other installs. I am using Red Hat Linux Kickstart for IA32 machines, but would recommend to look at the simple installer rhsetup (which is basically a shell script to install a complete Red Hat Linux system) and its environment params to make an automated install and then write a shell script for the remaining config tasks. Modifying rhsetup should also be easy and straight-forward. Such a shell script should at least call authconfig and chkconfig for setting up the configuration and then go on with perl -pi -e and modifying the remaining text files with standard unix tools like grep/sed/cat etc. At least these are the things I use myself. :-) Good luck, Florian La Roche
Re: Linux Multicast under VM - Help?
On VM, point-to-point links are considered to be broadcast and multicast capable. We simply unicast the packet to the other end of the link (no other choice, eh?). But setting up anything else besides point-to-point is not possible, right? If VM could be changed to act like a switch, the Linux guests could be changed to work like being on a real network and support real broadcasts and multicast (even if that would just be resend internally?). Should be possible from a technical standpoint. Dunno about the performance and demand for this feature. :-) cu, Florian La Roche
Re: VMHALT and Redhat V2.4.9-17
On Mon, Jan 14, 2002 at 01:22:36PM +0100, Grimm Peter (KTPS 1) wrote: CP commands in the kernel parameter VMHALT are not executed during shutdown if 'shutdown' or 'halt' are issued from a REXX program. CP commands in the kernel parameter VMHALT are executed during shutdown if 'shutdown' or 'halt' are issued from the command prompt. This applies to RedHat Linux 2.4.9-17. The problem does not exist in Suse Linux 2.2.16. Current kernel sources only support this vmhalt kernel parameter for non-SMP kernels (At least in 2.4.18pre3 or newer kernels.). So compiling a custom kernel might be one option to resolve this issue... cu, Florian La Roche
Re: [Redhat-s390-list] Redhat demo
On Sat, Jan 12, 2002 at 02:08:09AM -0500, Post, Mark K wrote: Dave, If they've posted the GA code on their FTP server, it should be available for download by anyone. The fact that they don't have .iso images isn't particularly relevant or important. I have not previously heard anything about Red Hat requiring that they do an installation. Perhaps that is only if you want to purchase a support contract from them. Even so, that would not prevent you from doing your own installs on another image/system. They just wouldn't be willing to support those installations. Still, if you get a definite answer, I'd be interested in hearing what it is. Stuff like this is important, and I would like to make sure it gets on the linuxvm.org web site. Hello Mark Post, your summary is correct and I'll add some personal comments: Red Hat Linux is Open Source and can be downloaded from our ftp-server. If you buy the product from Red Hat, this is only available together with a support contract where Red Hat helps with the installation as well as later on supporting it if you discover defects. Not only the last release is available as Open Source from Red Hat, but also newer developments are uploaded as rawhide versions to ftp.redhat.com. This allows the development community to try out our newest versions, participate in development if they want to or just give us feedback about the current status. This allows us to provide official bug-fixes and errata updates for our last release as well as continuing high-speed development of the next release. In the case of s390 we are facing two areas that are still a bit more under development: - The kernel on s390 needs more stabilization. - The install support for Red Hat Linux needs further improvements. Quite some good feedback has been given on our product and I think we already have implemented most of them. We will try to come up with an official update for the kernel and also install support. This should also allow a much easier addition of a driverdisk that could allow a real easy way to add OCO modules to Red Hat Linux. cu, Florian La Roche Florian La Roche Tel.: +49-711-96437-460 head of development EMEA Tel.: +49-172-6373899 Red Hat GmbH Fax.: +49-711-96437-111 Hauptstaetterstr. 58 Email: [EMAIL PROTECTED] D-70178 Stuttgarthttp://www.redhat.de/ Mark Post -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:30 AM To: [EMAIL PROTECTED] Subject: [Redhat-s390-list] Redhat demo What are the Redhat ground rules for downloading and demo'ing their latest GA (i.e. the ISO images). Is anyone allowed to do this ? Are there any timeframe boundaries for demo'ing ? Also, we asked for pricing a few weeks back and got some feedback that stated that Redhat MUST do the installation. Is this true? As a consultant (needing to learn the various installation methods)...I'm sure I don't like this ! Thanks, Dave ___ Redhat-s390-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-s390-list ___ Redhat-s390-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-s390-list
Re: [Redhat-s390-list] Redhat demo
On Sat, Jan 12, 2002 at 02:32:35AM -0800, Jon R. Doyle wrote: OK, but if I bought SuSE and (SLES comes with support) I would not expect anything from Redhat. You, or Florian rather are just saying that RH has support, that right? If this is the case it would help to say that you offer it like SuSE and Turbo, nothing new, it seemed like the message was saying somehow RH only has support. Redhat is new to zSeries/enterprise (Itanium,iSeries,pSeries etc). The messae seemed to indicate that it (Redhat) was capable of something new. Hello Jon Doyle, maybe my email sounded strange as I indeed wanted to point out that a real Open Source development makes a real huge difference to the support and service you are getting from a Linux vendor. The other part is of course also true: If you think Red Hat Linux is a good platform and you want to have support, we'll be glad to offer it. While the second thing is done by many companies, the first part is often done wrong. I have created the first version of SuSE Linux 4.2 and have been working on the core part for many years. My personal understanding is that I have been able to deliver a stable core system by maintaining a real Open Source Linux version called jurix Linux and then pushing the stabilized versions into SuSE Linux. I enjoy the huge developer community behind Red Hat Linux and the close cooperation with Internet-style and Open Source style development at Red Hat. I concur with you that the s390 support in Red Hat Linux has just seen its first product and s390 support is still under development. I'll be glad to improve it as long as Red Hat management decides to invest on this as important platform for Open Source software. I know SuSE has done a real lot of work for the install process as well as many other parts of their distribution and have good results to show. Red Hat is pushing this a bit further by providing their complete distribution as Open Source and allowing anybody in the devel community to use it or even try to compete with Red Hat here. Many other distros are in fact based on Red Hat Linux and this is a good thing for Red Hat as well as the devel community and in my belief also for customers. Not doing this correctly means the devel community will be glad to live without you and I do question what you are then delivering to your customers. :-) SuSE is doing these things mostly correct and I hope they are doing the right decisions to keep things that way. Many things can be said about the current products from SuSE and from Red Hat and they both have pros and cons. This is not what I am talking about. My own focus is to drive the development of a Linux distribution and doing this with Open Source methods seems the appropriate way of doing this, just like for the Linux kernel. Providing current sources on the ftp server is a key thing for this, otherwise you are doing something else. While it is easy to come up with a Linux distribution on your own and keep updating that for a long time, I see it as something completely different if the devel community is part of your development effords. Excuse my frank words, Florian *speaking for myself* La Roche
Re: Linux network (Redhat)
On Thu, Jan 10, 2002 at 12:08:15PM -0500, Karl Tucker wrote: When installing Redhat, interrogatories are used to form the parameters of the network. For example, the the IP address to be used. This address is then stored in a file /etc/sysconfig/network-scripts/ifcfg-ctc0 (if using CTCs). Where is/are the DNS server address, the Gateway address, and the domain names stored? ifcfg* files can specify the gateway with GATEWAY=192.168.1.1. DNS-Servers are stored in /etc/resolv.conf. An interface can specify DNS-servers that should get written into /etc/resolv.conf when the interface is started: PEERDNS=yes DNS1=172.16.2.2 DNS2=172.16.2.2 Documentation for all this is in /usr/share/doc/initscripts-* cu, Florian La Roche
Re: LCS drivers for 2.4.9 ?
And among the mainframe people are some who remember the great OCO war of the late 80's, early 90's between the VM world and IBM. A compromise (of sorts) was reached where that part of VM that had always been source code would remain so and so would new features that were not related to company trade secrets. The paradigm for VM had always been the availability of source code. A lot of the innovation in the early days of VM was driven by the user world because the source code was available. Are there some history pages about these discussions? Are parts of the current VM code available from IBM? How much of that code has changed from being available then to closed source? Seems like good-old VM customers understand how important source code is for a better operating system... cu, Florian La Roche
Re: LCS drivers for 2.4.9 ?
Alan Altmark made a very cogent comment in another forum: it's a question of where we want IBM to put their resources, and taking a developer away from new function to fix old function or restructure a bunch of drivers won't Agreed. help the overall effort much. Then there's testing, etc, etc, etc -- it's not a free process to get something like this done. Open Source has lots of benefits for code review, bug hunting and testing. All those benefits are not possible for the OCO modules and thus hinder these better development practises. cu, Florian La Roche
