Hi!
http://www.redbooks.ibm.com/redpieces/abstracts/sg246694.html
I've read in this redbook:
In kernel versions greater than 2.6.9, the I/O scheduler can be selected
at runtime using the /sys/block/dev/queue/scheduler interface (where dev
is the DASD device number).
Is it possible to use
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Istvan Nemeth
Sent: Monday, October 03, 2005 08:21 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: New redbook draft for Linux on zSeries
Hi!
http://www.redbooks.ibm.com/redpieces/abstracts/sg246694.html
Your initrd file is corrupted, possibly due to not having enough free space in
/boot while applying maintenance. We ran into this, and received the same error
message. Note that the install / maintenance process where the actual error
occurs produces no error messages or codes, and will happily
On Monday, 10/03/2005 at 08:06 EST, Nix, Robert P. [EMAIL PROTECTED]
wrote:
Your initrd file is corrupted, possibly due to not having enough free
space in
/boot while applying maintenance. We ran into this, and received the
same error
message. Note that the install / maintenance process where
I have to make a new SLES9 installation server because I'm upgrading the
current sles8 server I use for that to sles9. I get this message:
vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root /sles9root
nfs server reported tcp not available, falling back to udp
Using NFS over UDP can
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of James Melin
Sent: Monday, October 03, 2005 8:45 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Getting an odd message when trying to NFS mount the
sles9root tree
I have to make a new SLES9 installation
Just a reminder that it is time to get your reservations in to me if you
plan to attend the MVMRUG meeting in Columbus, Ohio on October 28. I may be
a bit biased, but I think we have another very good agenda. You can review
it and register at http://www.mvmrug.org/nextmtg.html. Our host is very
On Oct 3, 2005, at 8:45 AM, James Melin wrote:
I have to make a new SLES9 installation server because I'm
upgrading the
current sles8 server I use for that to sles9. I get this message:
vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root /
sles9root
nfs server reported tcp not
I have to make a new SLES9 installation server because I'm
upgrading the current sles8 server I use for that to sles9. I
get this message:
vadnais:~ # mount -t nfs
gsop23nnn09:/cd_images/SLES9/sles9root /sles9root nfs server
reported tcp not available, falling back to udp Using NFS
over
This is a temporary situation and it's an old dusty/crusty linux
installation that is getting replaced as soon as this temporary move of the
SLES9 installation server is accomplished.
David Boyes
[EMAIL PROTECTED]
e.net
I see you've gotten several replies. But no one
specifically addressed this part of the message you're getting:
Using NFS over UDP can cause data corruption.
I think it would be more accurate to say
Using NFS over UDP with '-o soft'
can cause data corruption.
By default,
Product Announcement posting for NJE/IP Bridge
Barnard Software, Inc. (BSI) is pleased to announce the general
availability of NJE/IP Bridge. NJE/IP Bridge is developed by Sine Nomine
Associates and marketed by BSI.
NJE/IP Bridge allows you to interconnect NJE communication services on
We have support through IBM. The ETR was closed and has fallen off my radar,
but the gist of the response was make /boot bigger. They did say that they'd
forward to Novell the fact that maintenance can fail without any error
indication, but as the ETR was closed, we'll never know if this is
Thanks again
I ran mkinitrd and zipl and the system came up without a problem. I'll look
into increasing /boot.
Bob Bates
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Nix, Robert P.
Sent: Monday, October 03, 2005 1:26 PM
To: LINUX-390@VM.MARIST.EDU
14 matches
Mail list logo
