hi mark, i fell back to figuring out why my stand alone dump tape wouldn't
ipl. turned out it was just a write protect turned on on the tape! i
turned it off for both sadump and linux, and both ipl'ed successfully.
thanks for the reference on the device drivers manual. i had looked at
this but wasn't sure which direction to go with it. i'll see if i can get
the network going with what i've got, and if i continue to stumble i'll
install linux on a pc here as you suggest.
thanks for your help!
Robin Murray
Tel: (902) 453-7300 x4177
Cell: (902) 430-0637
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
09/10/2004 01:21 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: ipling initial linux tape
Robin,
First of all, what did you do to get the tape IPL to work? Use a .tdf
file,
or something else?
I've never worked with a 2216, so take this with some skepticism. Yes,
you
need to define an LCS interface. Then, when you IPL your Linux system,
you
will need to tell it you have an LCS interface, not an ESCON one. I
forget
which flavor of Linux you're testing, but at some point you should be
asked
for chandev.conf parameters. You'll need to provide the appropriate
device
type and device numbers as documented in IBM's "Device Drivers and
Installation Commands" book at
http://www10.software.ibm.com/developerworks/opensource/linux390/docu/l390dd
09.pdf
Chapter 12 will be a start, although most likely confusing. (I have to
re-read various sections of that book several times whenever I try to do
something new.) There should also be lots of discussion about LCS in the
mailing list archives.
The "escon0" designation it uses is simply the interface name, similar to
eth0, eth1, etc. for Ethernet devices. When you tell the installer that
you're using an LCS device, it will use a different name. (To be honest,
I
don't even remember what the interface name will be. I never had one to
play with, so that bit of information didn't stick.) The system should
tell
you, in any case.
If you want to get up to speed on Linux faster, install it on a spare PC
or
laptop laying around and play with it. When you don't need to get a
network
interface working right at the start, it's a little easier to learn stuff
when you can just start exploring.
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Robin
Murray
Subject: Re: ipling initial linux tape
well, i got the linux tape ipled! first major hurdle over.
i've been trying to figure out how to get my network enabled on the tape
system so i can ftp a better file system onto my dasd. so far all i get is
"network unavailable". we have an mp3000 with an escon connected 2216
connected to ethernet. so far, all the escon subchannels are mpc+
protocol. i gather linux will only talk lcs, so i have to define an lcs
subchannel, right? how does linux detect the correct 2216 device address
to use? during the tape ipl, it just asks what kind of interface i have, i
reply escon, and it uses "escon0" (whatever that is) and carries on. does
it autodetect it somehow?
i'm fairly new to linux (although i've done some support of various
flavours of unix over the years), so i'm a bit of a fish out of water at
the moment.
----------------------------------------------------------------------
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
