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
11.03.2002 22:22:38 Linux on 390 Port ÎÁÐÉÓÁÌ(Á):
Thank you, Mark.
But I have one more question :)
I did next steps
1) insmod tape390 tape=290
Driver used major number 254. No devices in /dev
2) cd /dev; mknod ntibm0 c 254 0
3) tar -cvf /dev/ntibm0 some_file
Is this
Sergey,
I don't have the source for tape390.o, but if it's modeled after SCSI tape
support, the minor device number should be 128+n for a non-rewinding
device, just 128 in your case. Minors between 0-127 all rewind.
--Jim--
James S. Tison
Senior Software Engineer
TPF Laboratory /
When I issue the command to install the Webmin tool on version 7.2Suse
Linux (s390)
rpm -U webmin-0.93-1.noarch.rpm
I get the error:
Unabled to identify operating system
execution of webmin-0.93-1 script failed, exit status 2
The same thing happens with the 0.92-1 version of webmin tool
What do you think about this ?
http://news.com.com/2100-1001-857008.html
Gerard:
A fix is already available at http://www.gzip.org/zlib/ in version 1.1.4
of zlib. To quote CERT's review of the problem:
Vulnerability Note VU#368819
Double Free Bug in zlib Compression Library Corrupts
Greetings,
we would like to establish a master linux that controls (starting, stopping,
monitoring) all other linux guests on a single VM. We defined a SECUSER on each
guest to make all console output visible to this master linux. AFAIK I now have
to communicate to *MSG service via IUCV. But
On Tuesday, 03/12/2002 at 04:27 CET, Oliver Fenker
[EMAIL PROTECTED] wrote:
we would like to establish a master linux that controls (starting,
stopping,
monitoring) all other linux guests on a single VM. We defined a SECUSER
on each
guest to make all console output visible to this master
James Melin [EMAIL PROTECTED] writes:
What is the name of the file that silo creates?
It's called boot.map, in the current working directory. This
can be overridden by the map record in /etc/silo.conf.
My sysprog
wants to see
what is in this
So, if silo appeared to work, does your LPAR now IPL successfully? Or at
least _start_ to IPL, since it wasn't doing that before?
Mark Post
-Original Message-
From: James Melin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 12, 2002 9:16 AM
To: [EMAIL PROTECTED]
Subject: Re:
Post, Mark K [EMAIL PROTECTED] writes:
The silo command does not create a file, it just writes some
information
(including the ipl text found in ipleckd.boot out to the
appropriate part
of the DASD unit.
Actually, silo writes one or two files. It creates a file
called boot.map in the
I've never tried to use DHCPCD on Linux/390. Sounds a little bizarre to
me.
Still, you might try using a Linux DHCPD server and see if it handles
things
better.
If you're using an OSA in QDIO mode, virtual hipersockets in z/VM 4.2 or
CTC/IUCV links, DHCP (server or client) will not work. It
I'd like to gather your feedback on the requirement for Linux
exploiting Parallel Access Volume (PAV) support available on ESS
(Shark) storage subsystems and its competitors in the market.
In the past some customers expressed their concern about the data
throughput ESCON attachments provide,
True, but from what I could tell, his sysprog was looking for something
containing the ipltext which had to be in the right place. Looking at
boot.map or the parmfile copy wasn't going to tell him much of anything.
Mark Post
-Original Message-
From: Patterson, Ross [mailto:[EMAIL
I had numerous problems with zipl and, specifically, it's use of the
zipl.conf file. No matter how I tried to pass it parms, it kept referring
to parms in the .conf file. I finally erased the zipl.conf file and zipl
took all of my parameters (correctly, I might add) from the command line and
Mark,
All SuSE releases I've seen recently have some automated processing to
rotate logs, built in.
Control is in /etc/logfiles. Process is run out of
/etc/cron.daily/aaa_base_rotate_logs and controlled by
MAX_DAYS_FOR_LOG_FILES in /etc/rc.config.
Regards, Dougie Lawson
--
ITS Technical
What happens if you specify zipl -c /dev/null? Do the rest of your
parameters have the effect you're after?
I have a Suse 2.2.16 and 2.4.7 Linux systems that I need to assign several
Gigabytes to
for oracle databases, I have 3390 mod 9s and the 2.4.7 seems to allow this
but my
2.2.16 system gives the following errors during initialization
fsck /dev/dasdf1 ,
Parallelizing fsck version 1.19a
With z/VM SAF one can use the VMADMIN PARTITION COPY command to copy an
existing partition from one image to another which allows one to copy an
existing image's dasd to a new image. Are there any guidelines on how to
change the network information for the cloned image (suse in this case)?
A thought occurs to me so I ask this... How do I tell what DEVICE
/dev/dasda is associated with?
|-+
| | Post, Mark K |
| | [EMAIL PROTECTED]|
| | m |
| | Sent by: Linux
One thing that has concerned me w/r/t Cloning an installed image:
Won't a procedure to create new SSH/SSL keys for the copy be needed?
John R. Campbell, Speaker to Machines (GNUrd) {813-356|697}-5322
Will Work for CLAIM Codes
IBM Certified: IBM AIX 4.3
I have downloaded the tar.gz file and gone through the make
clean;./configure -s;make install process. Now how do I update the RPM
database to reflect the new version of zlib? I haven't noticed any function
of RPM to just update its database with my arbitrary data.
/Thomas Kern
/(301)903-2211
cat /proc/dasd/devices
Michael Coffin, VM Systems Programmer
Internal Revenue Service - Room 6527
Constitution Avenue, N.W.
Washington, D.C. 20224
Voice: (202) 927-4188 FAX: (202) 622-6726
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
-Original Message-
From: James
Hi,
I need to set up a Linux/390 guest with read-only file systems (and
minidisks). Has anyone done anything like this? I'd want to put the
portions of the file systems that MUST be read-write on a V-disk.
My filesystems are all on separate minidisks:
/
/home
/usr
/opt
Hi Arty,
Do you actually have a bootable Linux/390 system right now with those mount
points on separate minidisks? I was going to do that, but started looking
at ALL of the stuff that is required at boot time as an extension of the
booted disk (/) and it turned out to be more trouble than it
cat /proc/dasd/devices will give you that information:
cat /proc/dasd/devices
010F(ECKD) at (94:0) is dasda:active at blocksize: 4096, 57600 blocks,
225 MB
0100(ECKD) at (94:4) is dasdb:active at blocksize: 4096, 13500 blocks, 52
MB
0106(ECKD) at (94:8) is dasdc:active at blocksize:
and how does one delete the old ssh keys?
thx
Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598
Phone: (925) 926-5332 (tie line 8/473-5332)
E-Mail:
Arty,
I don't know. Why have /home as RO? If you're not going to let your users
have full access to them, I wouldn't create them in the first place. /tmp
and /var really need to be R/W, as large numbers of processes depend on that
fact.
Mark Post
-Original Message-
From: Arty Ecock
Terry,
During the Redbook residency, I did a test with creating a large LVM set
using 3 3390-9 volumes. I did have a couple of quirky things happen, but
nothing consistent, and nothing that looks like your problem. When you did
your dasdfmt command, how long did it take to complete? (It
When all you have is a hammer, everything you see starts to look like a nail.
Just because something can be done doesn't mean it should be done.
Oliver Fenker wrote:
Greetings,
we would like to establish a master linux that controls (starting, stopping,
monitoring) all other linux guests
John,
If you make your copy of your reference image _before_ sshd is started for
the first time, no. Or, as Ken Hall points out, you can simply delete them
before you start sshd on the new image for the first time.
Mark Post
-Original Message-
From: John Campbell [mailto:[EMAIL
Well, you really need to create a new zlib.spec file (or whatever it's
called) and give it a different version/build number than what you got from
your distribution. To get the base spec file, install the zlib SRPM from
your distribution, and modify it. Then, do an rpm -bb zlib.spec and when
Lionel,
The rm command is all you need. Depending on your version of sshd, the
files will either be in /etc/ or /etc/ssh/:
ls /etc/ssh/*key*
/etc/ssh/ssh_host_dsa_key /etc/ssh/ssh_host_key
/etc/ssh/ssh_host_dsa_key.pub /etc/ssh/ssh_host_key.pub
Mark Post
-Original Message-
I actually formatted this volume twice using YaST, maybe there is a better
way.
Or should I change the blocksize or something?
I'll attempt to do it manuallu using dasdfmt
Regards Terry
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of
Post, Mark K
Sent:
First off, thanks to all of you whom tried to help me here.
As far as I can tell, I have done everything to excruciating exactness. I
have evidence that Yast did everything it was supposed to do, as I found it
created a parmline file with the correct information in it. I have
attempted running
Apparently the email I sent Jim on this crossed with this one. In case
anyone else is interested, I decided to repeat myself here.
One way to make sure the IPL text is being written out is to print off the
first 2048 bytes of what you believe is your IPL volume. You probably used
the
PAVs have been used to a great degree by DB2 on the OS/390 side of the
zbox. I would expect that UDB on our Linux side will appreciate the
multiple exposures as well. Those of you who share read only dasd between
Linux instances will probably see a benefit also. I should think,
however, that
I got an advisory from RH about it a day or so ago.
What is there to think? It's a problem, a fix has been developed, every one
needs to put it on. My Linux distribution, Slackware, has already posted
their fix on their FTP server, and notified their security mailing list. I
guess I'll
I am trying to build gtk apps on my 390 RedHat install. I looked and
didn't see glib development support. Has anyone gone this route and
installed the gtk devel rpm(s) and built gtk apps? I am kinda new to 390
Linux and if there is a url or reference I should refer to ... I'd
appreciate
I have downloaded the tar.gz file and gone through the make
clean;./configure -s;make install process. Now how do I update the RPM
database to reflect the new version of zlib? I haven't noticed any function
of RPM to just update its database with my arbitrary data.
You install it properly
I remember some time back there was an article on a company I believe
was called Talia, that implemented an IBM Linux server consolidation
solution, but can't for the life of me find anything in my searches.
If anyone that has any info on this, I would appreciate it!
Thanks,
Paul
Joe Poole wrote:
I should think, however, that the best mediator of I/O conflicts
would be z/VM itself, working the multiple exposures on behalf
of the Linux images at a different level.
That would be true if you were running one single-threaded application on
multiple Linux guests under VM.
I remember some time back there was an article on a company I believe
was called Talia, that implemented an IBM Linux server consolidation
solution, but can't for the life of me find anything in my searches.
Telia.Net For more info just go to Google and search on IBM Telia.Net.
Here is a good
Bill,
The compat package is part of the Developer's Kit, the additional CD set
that ships with the SuSE Linux Enterprise Server 7 and can not be found on
the SLES 7 CDs themselves.
On Thu, 7 Mar 2002, William Raffloer wrote:
Jens,
We don't have this, the way we are set up is that we have
Here...
http://www-1.ibm.com/servers/eserver/zseries/os/linux/stories.html
Curiously one is missing... :(
On Tuesday 12 March 2002 03:39 pm, you wrote:
I remember some time back there was an article on a company I believe
was called Talia, that implemented an IBM Linux server consolidation
Part of the problem you will encounter is that Linux needs certain
directories available at boot time before /etc/fstab mounts any other disks.
These include, but are not necessarily limited to:
/boot
/sbin
/bin
/etc
/var
/tmp
In other words, all of these have to be on the boot volume at boot
Thanks Rich and Jim. This does the trick.
Paul,
Any time you want to find something relating to Linux/390, go to
http://linuxvm.org and especially http://linuxvm.org/Info/l390link.html
Mark Post
-Original Message-
From: paultz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 12, 2002 4:39 PM
To: [EMAIL PROTECTED]
Subject:
Gordon,
Sorry, but /boot, /var and /tmp do _not_ have to be on the root file system.
Mine aren't. Unless you play some games, /bin, /dev, /etc, /lib, and /sbin
have to be part of the root file system. Anything else can be easily put on
a different one.
~ df
Filesystem 1k-blocks
48 matches
Mail list logo
