Ryan,
Yes, add the following line to the
/etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-* files
QETH_LAYER2_SUPPORT="1"
and blank out an optional QETH_OPTIONS= parameter if you done things like
"fake_ll" or so.
In the z/VM system config, add the keyword "ETHERNET" to, or replace "IP
" with "ETH
RPN01 wrote:
When you get down to just 3270 access, the sed command is your friend. Do it
once to the terminal, if the file isn't too big, and check your results,
then use > to put the results into a new file, rename the old, rename the
new, and then start the cycle over again...
Where possible
Thanks David, I'll check it out. I hear there is a zLinux client coming
out in Q1 09 for IBM VTS TS7740 which would be useful.
David Boyes <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
08/12/2008 07:05 AM
Please respond to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: IBM
On Tue, Aug 12, 2008 at 9:18 PM, RPN01 <[EMAIL PROTECTED]> wrote:
> The linemode console is much more versatile, and the only time you'll
> actually sit at it is when you're in trouble; at any other time, you'll just
> walk away from it and use a ssh or telnet (not advised) connection.
>
> Learn a
Fargusson.Alan wrote on 08/12/2008 05:42 PM:
> An entry that is by-id looks like this:
>/dev/disk/by-id/ccw-HTC.xx..zz-part1 ...
>
> The ... part is the ID of the storage system, I don't know what
> the part is, and the zz is related to the physical device
> number. Th
An entry that is by-id looks like this:
/dev/disk/by-id/ccw-HTC.xx..zz-part1 ...
The ... part is the ID of the storage system, I don't know what the
part is, and the zz is related to the physical device number. This breaks
cloning since the mount will try to mount ba
> OK, that makes sense now (ties the term to my Red Hat knowledge).
Please
> give an example of what you (or YaST) mean by by-path and by-ID.
Bad (by-ID): /dev/disk/by-id/ccw-IBM.1300018873.0280.07-part1
Good (by-path): /dev/disk/by-path/ccw-0.0.abdc-part1
---
Thanks for pursuing this -
-Original Message-
From: Ryan McCain [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 12, 2008 3:42 PM
To: Linux on 390 Port
Subject: Layer 3 to Layer 2 on the VSWITCH
With the help of people on this list, I've confirmed it's definitely the
VSWITCH being set to
OK, that makes sense now (ties the term to my Red Hat knowledge). Please
give an example of what you (or YaST) mean by by-path and by-ID.
Thanks-
Douglas Wooster
Fargusson.Alan wrote on 08/12/2008 02:37 PM:
> No, this is by device name. It works fine unless you add a device
> with a lower devic
Being a Linux and not a mainframe guy, I'm still trying to learn 'ed' in case I
get stuck with only 3270 access to my Linux guest. Here's a superb list of sed
one liners that should come in handy:
http://student.northpark.edu/pemente/sed/sed1line.txt
Ryan
-
With the help of people on this list, I've confirmed it's definitely the
VSWITCH being set to layer 3 that isn't allowing broadcast connections (which
in turn doesn't allow me to run DHCPD) on the guest SLES 10 VM.
My next question is, how does one convert the VSWITCH from layer 3 to layer 2?
> This isn't exactly news. It's been discussed here before, along with
the
> recommendation to use by-path for new installs.
Yes, I know. This is just about the tenth time I've had someone trip
over it, and I think it merits more attention on a slightly shorter
timeframe; the way to get that atte
Hi Mark,
*checkinstall make install* doesn't actually installs anything, only creates
the RPM package.
On Tue, Aug 12, 2008 at 1:46 PM, Mark Pace <[EMAIL PROTECTED]> wrote:
> So you end up doing an RPM install over the source install you just
> completed?
>
> --
> Mark Pace
> Mainline Informati
As near as I can tell, the problems created by a 3270 console outweigh the
benefits. Sure, you have a nifty 3270 interface that acts like z/VM and
z/OS, but you can't run the image disconnected, you can't spool the messages
from the console, and you have to sit there and clear the screen when it
fi
Check your settings in putty; It prefers version 1 of the protocol, but most
systems now use version 2. In the list of setup pages, the setting appears
in one of the last ones. Don't even set it to dynamically go between 2 and
1; it'll still pick 1 every time and fail. Set it to 2.
--
Robert P. Ni
When you get down to just 3270 access, the sed command is your friend. Do it
once to the terminal, if the file isn't too big, and check your results,
then use > to put the results into a new file, rename the old, rename the
new, and then start the cycle over again...
--
Robert P. Nix Mayo
>>> On 8/12/2008 at 9:21 AM, in message
<[EMAIL PROTECTED]>, David
Boyes <[EMAIL PROTECTED]> wrote:
> A safety reminder: If you're planning to replace disk subsystems, make
> sure your Linux guests (particularly any SLES 10 or above) guests do NOT
> use by-ID paths in /etc/fstab. Fix this BEFORE
No, this is by device name. It works fine unless you add a device with a lower
device number then the device number for /dev/dasda1.
For example: if /dev/dasda1 is device 200, and you add a device number 150,
then 150 becomes /dev/dasda1, and 200 becomes /dev/dasdb1. This causes 150 to
become
>>> On 8/12/2008 at 6:43 AM, in message
<[EMAIL PROTECTED]>, Michael
MacIsaac <[EMAIL PROTECTED]> wrote:
> Mark,
>
> I just read in the Sept Linux journal (p94) there is a tool called
> checkinstall - the Tech Tip starts "If the program you want to install
> doesnt have a package for your distro
>>> On 8/12/2008 at 6:03 AM, in message
<[EMAIL PROTECTED]>, Mark Pace
<[EMAIL PROTECTED]> wrote:
> I'll ask - at which point in my steps do you do the rpmbuild? Does it
> replace the ./configure, make, make install?
Yes, but the rpmbuild is usually done while in the SPECS directory.
Mark Po
My fstab list things thusly:
/dev/dasda1 / ext3acl, user_xattr
1 1
Is that device path notation?
Jon
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Adam Thornton
Sent: Tuesday, August 12, 2008 1:25 PM
To: LINUX
Lea, let Yast do all the work.
Try "yast dasd"
Or, "yast2 dasd" on a graphical VNC session...
Best regards,
__
Clovis Pereira
zVM & zOS Support - SWS
Maintenance and Technical Support Services
MTS Brazil
phone: 55-11-2132-3399
[EMAIL PROTECTED]
On Aug 12, 2008, at 12:07 PM, Fargusson.Alan wrote:
Is there a consensus on what should be used?
YAST gives me five choices. I don't understand some of them:
Device name: I think this one is a problem if you add a device that
has a lower device number then an existing device.
Volume label: T
> Is there a consensus on what should be used?
> Device path: This looks like the best option to me.
And you would be correct.
> Any down side to
> this?
It looks "weird" to old-school Unix heads, but it's simple to figure out
once you understand it and it works equally well on all architectur
Yes, I ran the dasd_configure a few minutes ago and it worked. I will
now do the rest, thanks everyone.
Lea Stahr
zVM, Linux and zLinux Administrator
Navistar, Inc.
630-753-5445
[EMAIL PROTECTED]
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Bruce Hay
by-path is what we do
I couldn't find any down side to it - unless you like to change virtual
addresses in your VM directory entry randomly or something like that :)
Marcy
"This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to rece
Maybe you want to use the dasd_configure script which is part of
s390-tools on SLES? This is what I've used:
dasd_configure 0.0.0123 1 0
The comments in this script say the usage is:
dasd_configure
And, as mentioned, after you add the disk(s), run mkinitrd and zipl.
The script creates the ha
Is there a consensus on what should be used?
YAST gives me five choices. I don't understand some of them:
Device name: I think this one is a problem if you add a device that has a lower
device number then an existing device.
Volume label: This might be a good way to go. This will probably bre
Lea,
Just vary it online (chccwdev -e 0.0.) and then mkinitrd and zipl.
Marcy
"This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
The disk was defined in the VM directory for the Linux guest but was not
picked up during the boot. On SLES 8 we added them ZIPL.CONF but the
SLES 10 ZIPL.CONF file does not contain the disk range on the PARAMETERS
statement.
Lea Stahr
zVM, Linux and zLinux Administrator
Navistar, Inc.
630-753-544
Two questions that anyone who is new enough to need your reminder will ask are:
What default do you suggest?
When changing it, how should it be changed?
The old timers here will know the answers.
David Boyes wrote:
A safety reminder: If you're planning to replace disk subsystems, make
sure you
So you end up doing an RPM install over the source install you just
completed?
On Tue, Aug 12, 2008 at 12:36 PM, Mauro Souza <[EMAIL PROTECTED]> wrote:
> Regarding checkinstall, I used it for years, and it saves a lot of work.
>
> Install it, and use it to create a RPM package.
> Do the normal wa
That doesn't add a disk, it enables (think: vary online) an existing disk.
Mauro Souza wrote:
I usually add a dasd using
chccwdev -e 0.0.0123
have you tried it?
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com
Regarding checkinstall, I used it for years, and it saves a lot of work.
Install it, and use it to create a RPM package.
Do the normal way to extract, configure and make the sourcecode, then use
checkinstall to create the rpm:
[EMAIL PROTECTED]:/tmp/whatever-source-dir# ./configure && make && che
I usually add a dasd using
chccwdev -e 0.0.0123
have you tried it?
On Tue, Aug 12, 2008 at 11:37 AM, Stahr, Lea <[EMAIL PROTECTED]> wrote:
> I am trying to add disk to SuSE SLES 10. In SLES 8, I did a MAKEDEV to
> create the device file, then did a format and a mkswap. I have no
> MAKEDEV script
A safety reminder: If you're planning to replace disk subsystems, make
sure your Linux guests (particularly any SLES 10 or above) guests do NOT
use by-ID paths in /etc/fstab. Fix this BEFORE the new disk goes in,
both RH and SuSE (Debian, too), or your guests will not be able to find
their filesyst
We have been running nthe for years on linux on system z.
Never any problems.
Gerard
>>
[EMAIL PROTECTED]:~> nthe -help
THE 3.3B1 10-July-2006 Copyright 1991-2006 Mark Hessling. All rights
reserved.
THE is distributed under the terms of the GNU General Public License
and comes with NO WARRANT
It should be on DVD 1 and in /suse/noarch directory. SuSE's site
http://www.novell.com/products/linuxpackages/server10/s390x/makedev.html
states you do not need unless you are using FHS.
'Where ever you go - There you are!! '
Richard (Gaz) Gasiorowski
Global Solutions & Technology
Principal L
I am trying to add disk to SuSE SLES 10. In SLES 8, I did a MAKEDEV to
create the device file, then did a format and a mkswap. I have no
MAKEDEV script (I did a FIND on it). How can I make a device file for a
new DASD?
Lea Stahr
zVM, Linux and zLinux Administrator
Navistar, Inc.
630-753-5445
[EMAI
> Has anyone had success using IBM Tape Manager for z/VM with RHEL5 ? Is
> there a zLinux command interface available for zVM?
None of the VM tape managers has a Linux client AFAIK. Seems like a
no-brainer given where IBM is pushing VM, but all the products pretty
much seem to be in maintenance mo
Mark,
I just read in the Sept Linux journal (p94) there is a tool called
checkinstall - the Tech Tip starts "If the program you want to install
doesnt have a package for your distro, you can use checkinstall to make
one." See http://asic-linux.com.mx/~izto/checkinstall/
I've never tried it, but
And what about THE which is strictly source and not and RPM. There is no
SPEC file for it.
On Mon, Aug 11, 2008 at 1:52 PM, Neale Ferguson <[EMAIL PROTECTED]>wrote:
> Or just cd /usr/src/packages/SPECS and rpmbuild -bb .spec
>
> That way you get an RPM you can install and keep track of. (This as
I'll ask - at which point in my steps do you do the rpmbuild? Does it
replace the ./configure, make, make install?
On Mon, Aug 11, 2008 at 1:52 PM, Neale Ferguson <[EMAIL PROTECTED]>wrote:
> Or just cd /usr/src/packages/SPECS and rpmbuild -bb .spec
>
> That way you get an RPM you can install an
43 matches
Mail list logo
