S390utils on RHEL contains the lsdasd command, which shows this.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Gentry, Stephen
Sent: Tuesday, January 29, 2008 10:48 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Mapping Minidisks to File Systems
Coming into this a bit late, so sorry if I missed the point...
On Red Hat, there's a supplied kernel-devel package that has JUST ENOUGH
of the kernel source to allow you to build third-party modules. You
only really need the full source package if you're going to rebuild the
kernel itself, or mod
I've been watching the OQO for a couple of years now. The only thing
holding me back has been the price. There are a number of similar
devices in the UMPC form factor.
I DID buy a mini-pc a couple of years ago that runs Linux and Hercules
very well. It's about the size of a CD player, but that
One of my personal fantasies is to run zOS under Hercules on an OQO.
Licensing issues aside, THAT would be cool!
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Alan Cox
Sent: Friday, November 30, 2007 8:18 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINU
Met him once, a few years back, when we were doing Linux-on-z the first
time. Nice guy, very smart. Wore wrist braces because of carpal tunnel
problems. Hope he's doing better with that.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
David Andrews
Sent
ry and practice are different."
On 10/26/07 10:59 AM, "Hall, Ken (GTI)" <[EMAIL PROTECTED]> wrote:
> Is your dasd driver a module, and are you using an initrd?
>
> If this is the case, the range is taken from /etc/modprobe.conf in the
> initrd, not
Is your dasd driver a module, and are you using an initrd?
If this is the case, the range is taken from /etc/modprobe.conf in the
initrd, not /etc. You need to rebuild the initrd and reboot.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Ron Henry
Sent
We're getting ready to try it with EMC DMX. IBM has been very
supportive, but we have a contract with them.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Collinson.Shannon
Sent: Tuesday, October 23, 2007 10:22 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [LI
When we first tried Linux in an LPAR, about 3 months ago, we were
concerned about this. The LPAR we were using was defined for another
purpose, and had access to 12,000+ DASD devices. We went to IBM, and
they recommended CIO_IGNORE. I tested that under VM, and it appeared to
work, but when we tr
It works in 2.6.9 in RHEL4 using ext2online.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Kyle Smith
Sent: Tuesday, July 31, 2007 10:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] LVM/Ext3 extend
Now that I think about it, it was after 2.6
Udev should handle this automatically. Like I said in the previous
note, however, it can take up to 10 seconds for the device node to
appear. Race conditions of this type appear to be common during
rc.sysinit, and also affect fcp devices, particularly when you use them
in combination with LVM and
There's a delay between the time the module gets loaded and udev notices
and creates the device node. This has bit us on other devices (tape,
fcp) as well. We've had some discussions with Red Hat about it, and
there's supposed to be some kind of fix in RHEL 4.5 or 5.0.
-Original Message
Runs very well under Fedora 7, as long as you build it there.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
John Summerfield
Sent: Thursday, June 28, 2007 9:20 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Hercules 3.05 announcement
Jay Mayna
I have device-mapper-multipath-0.4.5-16.1.RHEL4, but based on what I saw, I
don't see how this can be fixed without an update to the kernel driver. The
driver at the U4 level doesn't export vendor and model info into sysfs, so
there doesn't appear to be any way for device-mapper-multipath to id
I spent a lot of time going around with this. The problem seemed to come down
to that with the kernel I'm using (2.6.9-42.0.8), the dasd driver doesn't
provide vendor and model info in sysfs, so device-mapper-multipath can't match
up the devices with a rule set. The newer driver in RHEL5 does
Here's what we were told:
Without NPIV, the FCP CHPID acts like a shared HBA, and all LUNS are
visible to all virtual machines in all LPARs. Only one OS instance can
use a given LUN, however. If another tries, the LUN will appear busy.
WITH NPIV, the system assigns an arbitrary virtual WWPN to
nal Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Brad Hinson
Sent: Tuesday, June 05, 2007 11:45 AM
To: LINUX-390@vm.marist.edu
Subject: Re: RHEL 4 - FCP - tape drives
On Tue, 2007-06-05 at 09:29 -0600, Mark Post wrote:
> >>> On Tue, Jun 5, 2007 at 9:3
We just went through this.
First, you need the lin_tape package from IBM. That has the
device-specific drivers for the tape drives. You might have to find the
source RPM and rebuild it to get a version that matches your kernel.
The zcfp.conf file has five fields, but only three are meaningful.
The disk issue is most likely the parameter passed to the DASD driver in
modprobe.conf. I think all of the distros handle it the same way.
Remember, if you change the address list, and you're using an initrd,
you might have to rebuild the initrd.
On the listserv title, send a note to [EMAIL PROTE
The tzdata RPM is a noarch, so a version from any distro that's even
close should work. I had been asked to look into this, and I was
watching for the change to RHEL4, but there has never been any mention
in the changelog for the package.
So I did a quick search, and found out about using the zdu
The sounds are burned into my brain. The difference between the '33
with local echo (Tzchunk), remote-echo (as used with PDP8) Tchunk,
and no echo (as used with PDP8 logging into TSS8) Tzzz Tzzz Tzzz...
Oh well, enough of that..
-Original Message-
From: Linux on 390 Port [mailto:[E
Nope, sold it. Wish I hadn't.
-Original Message-
From: Tom Duerbusch [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 27, 2006 4:13 PM
To: Hall, Ken (GTI); LINUX-390@VM.MARIST.EDU
Subject: Re: Installed package differences (minor off-topic digression)
"Discribe the sou
Wish I still had my ASR33, although I don't miss the LA30.
I was trying to describe the unique sounds of a Teletype to my
15-year-old son the other day.
>>-- db (whose ASR33 and LA36 are working just fine, thank you.)
If you are not an
Same thing happens on RHEL4, and it confused me at first.
Shared libraries & such are installed twice, so you can run both 32 and
64 bit binaries on the 64 bit versions. The 32 bit libraries go in
/usr/lib, and the 64 bit ones in /usr/lib64.
This can produce some interesting problems if package
Suse distributed Bastille with SLES8 and SLES9 (IIRC), but it didn't
work. When I called for support, I was told it was known to be broken,
and not supported on 390/z.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Stephanie A Maginn
Sent: Thursday, Dece
Actually, in it's original form (on 3090 or 9021, IIRC), Expanded
storage was physically different memory. It was slower, and therefore
cheaper. As real storage got cheaper, it was positioned as a
paging-avoidance mechanism until the OS could be enhanced to address
more real storage.
HDS used th
Assuming these are Samba shares under Linux, there's a mechanism in
Samba to map users between the Windows client and Samba. Check the
Samba doc for details.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Brown, Larry J.
Sent: Thursday, November 02, 20
The autologin patch wasn't part of SLES8 when I was using that, but it's in
RHEL4. I don't know about SLES9 or 10. Check the man page for mingetty to
make sure. To enable, just change the line in /etc/inittab from:
1:2345:respawn:/sbin/mingetty console --noclear
to:
1:2345:respawn:/sbin/min
DVD's should be able to convert to ISO files. I've gotten DVD ISO images of
Fedora that mount just like CD ISOs, and burn onto DVD-Rs.
You still might need a Linux-x86 box somewhere in there though, to avoid
case-mangling issues with Windows.
> -Original Message-
> From: Linux on 390 P
Considering we're using both, I'd assume so.
There's a minor bug in the FCP implementation though. Red Hat is working on it.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Smith, Ann (ISD, IT)
> Sent: Thursday, August 31, 2006 12:13 PM
> To: LINUX-39
Red Hat has also been very cooperative with us on our extended POC study.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Ceruti, Gerard G
> Sent: Thursday, August 31, 2006 2:43 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] SLES vs RHEL
>
Okay, RHEL4 is 2.6.9-42.0.2 (can they get any more digits?) as of today's
update.
Looks like they're leapfrogging. My FC5 x86 machine is 2.6.17. I forget
whether Red Hat said they would be going that high in RHEL5 (probably not), but
if they are doing it for Intel, they'll be doing it on z.
>
> If you're paying for SLES and yast doesn't work, whinge and complain
> about it:-) I do think it has some bugs, and some components may be a
> little frail (I got openldap set up, and then broke it, but OTOH I got
> openldap set up much more easily than on RHEL or Debian or FC).
>
Don't get
My experience with Yast has not been good. Maybe it's better now, but when I
used it, it tended to break things and hide shadow copies of configuration
files where we couldn't find them, then write over our customized REAL files
when we least expected. After having to fix a couple of broken sy
006 11:37 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4 - NOT
>
>
> If you're running under VM, make the swap devices a virtual
> disk. They
> can handle a significantly higher load than the real disk.
>
All I can tell you is from our experience.
When we first looked at Linux a few years back (2002 or so), Red Hat didn't
have a usable s390/zSeries distribution. We started with SLES7, and moved to
SLES8. It wasn't till (relatively) recently, with RHEL3 for zSeries, that Red
Hat had anything wo
I tracked down a copy of the actual report from the performance guy, and it
turns out we've been (partially) barking up the wrong tree. Sorry for the
confusion.
The real story is that the large swap partition DEVICE was 100% BUSY during
part of the test. The original summary report said 100
M
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4
>
>
> Does 'Teamquest' run on the websphere machine? If so, don't discount
> the possibility that it caused the problem.
>
> Hall, Ken (GTI) wrote:
>
UX-390] Swap partition "filling up" on RHEL4
>
>
> Hall, Ken (GTI) wrote:
> > Here's how it looks NOW. Can't speak for the time of the failure.
> You stated, one swap device is full and another is not (at the time of
> failure). Where do you get that data from
more info
then.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Alan Cox
> Sent: Wednesday, August 30, 2006 9:06 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4
>
>
> Ar Mer, 20
Here's how it looks NOW. Can't speak for the time of the failure.
MemTotal: 1345376 kB
MemFree: 6968 kB
Buffers: 73984 kB
Cached: 134016 kB
SwapCached: 10784 kB
Active:1110932 kB
Inactive: 105864 kB
HighTotal: 0 kB
HighFree:0
We've been doing some load testing with WAS on RHEL4 under VM, and the other
day something weird came up.
The machine is defined with 1.3 gb. storage under zVM 5.2, and about 1.5 gb.
swap space in two partitions: One about 1 gb. (dasdf), and the other about .5
gb. (dasdd)
We use a product cal
You can resize ext2 and ext3 filesystems while mounted with ext2online.
It's a standard part of RHEL4. I don't know about other distributions.
We've used it, and it works fine.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Carsten Otte
Sent: Monday, Augu
You might want to keep in mind a scene from the movie "Dogma":
Jay: Guys like us just don't fall out of the **cking sky, you know.
[Rufus falls out of the sky]
Jay: Beautiful, naked, big-titted women just don't fall out of the sky, you
know.
> -Original Message-
> From: Linux on 390 P
into CP
> READ, after (the default) 15 minutes, CP will force it off.
> Try killing
> your 3270 emulator after reconnecting, seeing CP READ, and waiting 15
> minutes. I think you'll find out the guest "goes away."
>
>
> Mark Post
>
> -Original M
I wonder what we're doing differently. I just tried this with my test server
several times, and it disconnected properly each time, leaving the guest
running.
When I logged back ON though, the session went to CP READ and the server was
partly locked up until I satisfied the read.
> -Ori
Maybe if there's no network, like you forgot to change the IP address before
moving the machine to a different subnet.
I've recovered quite a few unreachable machines using the 3270 console. It
just requires some familiarity with line-mode commands.
> -Original Message-
> From: Linux o
Make sure you have "CP SET RUN ON" in the PROFILE EXEC for the machine.
Sounds to me like it's going into CP READ when it disconnects.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Rich Smrcina
> Sent: Thursday, June 29, 2006 11:30 AM
> To: LINUX
Red Hat (RHEL4) is simple, compared to SLES. I think there are only two or
three files involved, compared to like 6 or 7 on SLES.
We did this quite a bit because of the way we cloned systems, and Yast wasn't
an option because all we had after the clone was the 3270 console.
> -Original Mes
For SLES9, don't forget /etc/hosts, and if your subnet changed,
/etc/sysconfig/network/routes.
There may also be a host name in /etc/inews_mail_gateway.
If you're using Postfix for mail, /etc/postfix/main.cf.
You might also have to delete ssh keys in /etc/ssh. Basically, delete any file
with
Depends on which distro and version you're using. SLES7 is different from
SLES8 and SLES9, and they're different from RHEL.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Mike Lovins
> Sent: Wednesday, May 17, 2006 10:22 AM
> To: LINUX-390@VM.MARIST.
> along the model of other commands chmod, chroot, ....
>
> Richard Hitt[EMAIL PROTECTED]
>
> Hall, Ken (GTI) wrote:
>
> >Assuming cchccwdev is a program, Red Hat doesn't have it, so
> here's the "manual" procedure, which should work on a
e!
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Ranga Nathan
> Sent: Wednesday, May 10, 2006 4:58 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Is it possible to move an LVM from guest to
> guest?
>
>
>
&
Unmount the filesystem, and run "vgexport" for the volume group. Then take the
volume offline via sysfs, and detach it from the guest (This assumes you're on
the 2.6 kernel. With 2.4 it's a little more complicated).
Repeat the process in reverse on the other system, doing a vgimport on the
ot
Mount options NOATIME and NODIRATIME
But I don't see those on the current Reiser doc pages.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Phil Tully
> Sent: Thursday, April 27, 2006 1:28 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Wha
gt;
> To the best of my knowledge it is SLES 7. It was installed
> so long ago that
> I can't remember. Any help will be gratefully received!
>
> Loren Charnley, Jr.
> IT Systems Engineer
> Family Dollar Stores, Inc.
> [EMAIL PROTECTED]
> (704) 847-6961 x 2000
>
&
Is this SLES7? I wrote a script way-back-when that handles this, but it's
customized for our configuration. At least I can identify the files involved
though.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Loren Charnley, Jr.
> Sent: Wednesday, Apr
18 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Fw: [LINUX-390] GPFS
>
>
> On 4/12/06, Hall, Ken (GTI) <[EMAIL PROTECTED]> wrote:
>
> > IIRC, UnionFS was part of the core of the Levanta "virtual
> server" product, when we looked at it in 2
IIRC, UnionFS was part of the core of the Levanta "virtual server" product,
when we looked at it in 2003-2004. The idea was that you installed each
product group in a separate filesystem, and then layered them onto each other
to produce custom-tailored images. Obviously, they had it working on
FTP clients and servers are supposed to handle this transparently. If you send
in ASCII or "text" mode, the proper end-of-line protocol should be
automatically used on the receiving system. In binary mode, of course, you're
on your own. RPM packages should obviously always be sent in binary m
Just a suspicion, but I think Bernard may be thinking of
/proc/sys/kernel/hostname, which does show zero length, but when displayed,
contains the host name. I think Ryan (and I) were looking at the program
/bin/hostname, which on my machine is 15464 bytes.
> -Original Message-
> From:
I think you hit on it. For some reason my /bin/hostname file is
> completely empty. In another image it looks like a binary file.
>
> Any idea how to rebuild it?
>
> Thanks,
> Ryan
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Be
Try running "which hostname" to make sure you're picking up the right program.
On my Red Hat system, it's in /bin. (We used to run Suse, so I'm familiar with
that too, I just don't have a sample Suse system anymore.)
Then run rpm -qf `which hostname` to find out which package it belongs to. O
My guess would be you're using a Windows FTP server on your laptop, and this
doesn't work. You either need to use an FTP server or NFS on Linux. The
problem has to do with Windows being rather casual about case-sensitivity in
file names.
> -Original Message-
> From: Linux on 390 Port
They even had one that was selling for $50, with a $50 rebate a couple of years
ago. Made a dandy Christmas present.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Alan Altmark
> Sent: Friday, February 10, 2006 2:23 PM
> To: LINUX-390@VM.MARIST.EDU
>
Just as an FYI on this topic, I bought some combo USB/Firewire cards at a local
PC show a while back. They had no identifiable brand name that I can recall,
but they came in blue boxes, and were fairly cheap ($15-$25).
They DID NOT work. Using USB 2.0 with my iPod gave all sorts of errors.
F
a bit of a
shock though. :)
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Carsten Otte
> Sent: Thursday, November 03, 2005 11:32 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Redhat Linux 2.4.9 Hanging
>
>
>
> Carsten Otte
> Sent: Thursday, November 03, 2005 11:10 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Redhat Linux 2.4.9 Hanging
>
>
> Hall, Ken (GTI) wrote:
> > We used to see behavior like this on our SLES8 systems,
> when too many images were brought up
We used to see behavior like this on our SLES8 systems, when too many images
were brought up at once. It seemed to be related to contention for the disks
because we'd reboot the images independently and they'd come up fine, and never
seemed to hang on individual reboots.
Try staggering the aut
I tried a little, but the iSCSI driver package and the Linux kernel never quite
seem to be at compatible levels. I believe I got it to compile, but couldn't
get any farther.
I haven't tried recently though.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf
We used LVM for all filesystems except the root FS. Since the volume group
"virtualization" is activated by the SYSVINIT scripts, /boot, /lib, /bin and
/etc have to be on "native" disk.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
> Behalf Of Eli
> Criffield
In the "more than you wanted to know" department, I have sitting on my
semi-junk pile an old Sony Optical disk drive that came off a Sun Sparcstation
clone. It uses 600 mb. optical cartridges that only support a 1024 byte
sector. It was originally supported by SunOS (the precursor to Solaris),
I had Nagios up for quite a while. It's not too bad once you understand it.
I'd be happy to look at the drafts.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> David Boyes
> Sent: Friday, August 12, 2005 11:49 AM
> To: LINUX-390@VM.MARIST.EDU
> Subjec
In this case though, it's going to depend on how the installer is doing the
mounts. If it's issuing a separate mount for each CD image, unless the server
allows subdirectories to be mounted under a parent export, it's not going to
work. That's how I remember Linux working.
> -Original Mes
Try exporting the individual subdirectories. I've run across this sort of NFS
weirdness before. You can only directly mount the exported directory, not the
ones under it.
I know someone is going to tell us it isn't supposed to work this way, but I've
been down this road before.
> -Origin
75 matches
Mail list logo
