Gordon,

What, exactly, fixed the problem?  The reason I ask is because I got an
offline email pointing out that /dev/rtibm0 and /dev/ntibm0 were both
character devices with the same major and minor numbers, and that should
_not_ work.  Was it just using the "0" suffix and not "1" that made things
happen?

Mark Post

-----Original Message-----
From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 15, 2002 12:52 PM
To: [EMAIL PROTECTED]
Subject: Re: ipl tape


Thanks.  This solved my problem.  Thanks to all who responded.

"You do not need a parachute to skydive.  You only need a parachute to
skydive twice."  -Motto of the Darwin Society
Gordon W. Wolfe, Ph.D.  (425) 865-5940
VM Technical Services, The Boeing Company


> ----------
> From:         Post, Mark K
> Reply To:     Linux on 390 Port
> Sent:         Wednesday, March 13, 2002 8:35 PM
> To:   [EMAIL PROTECTED]
> Subject:      Re: ipl tape
>
> Gordon,
>
> According to what I read in the Distributions Redbook, "ntibm0" is the
> _first_ non-rewinding tape drive, and "ntibm1" would be the second one.
> So,
> if you only have one, you should probably be using "ntibm0" as the device:
> Since Linux for S/390 distributions may not include any tape devices, the
> following commands may be used to create a Linux device for each available
> tape device:
> #mknod /dev/rtibm0 c 254 0 (first rewinding character device)
> #mknod /dev/ntibm0 c 254 0 (first non-rewinding character device)
> #mknod /dev/btibm0 b 254 0 (first block device)
> #mknod /dev/rtibm1 c 254 1 (second rewinding character device)
> #mknod /dev/ntibm1 c 254 1 (second non-rewinding character device)
> #mknod /dev/btibm1 b 254 1 (second block device)
>
> How that corresponds to Sergey's success using ntibm1, I don't know.  But,
> it may be worth a try.
>
> Mark Post
>
> -----Original Message-----
> From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 13, 2002 4:55 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ipl tape
>
>
> I  decided to use this as a basis for experimenting with tapes since we
> haven't got to that yet.  Using SuSE SLES7, I had a running system.
>
> From another VM userid on the same system,
>
> VMTAPE MOUNT SCRATCH DSN Linux.tape.test ( retpd 5 label nl
> CP GIVE 181 to LINUXSRV 181
>
> Then, from root on the linux machine
>
> insmod tape390 tape=181 Using
> /lib/modules/2.4.7-SuSE-SMP/kernel/drivers/s390/char/tape390.o
>
> From the 3270 console of the server, I see
>         T390:IBM S/390 Tape Device Driver (v1.01).
>         T390:(C) IBM Deutschland Entwicklung GmbH, 2000
>         T390:character device frontend   : built in
>         T390:block device frontend       : built in
>         T390:support for 3480 compatible : built in
>         T390:support for 3490 compatible : built in
>         T390:Using ranges supplied in parameters, disabling autoprobe
> mode.
>         TCHAR:<3> tape gets major 254 for character device
>         TBLOCK:<3> tape gets major 254 for block device cd /devmknod
> ntibm1
> c 254 1             (Confirmed /dev/ntibm1 really is there)cd /hometar
> -cvf
> /dev/ntibm1 ./patchestar: /dev/ntibm1: Cannot open: No such devicetar:
> Error
> is not recoverable: exiting nowroot@linuxsrv-/home #               (no
> additional messages on the console)
>
> Obviously, I'm doing something wrong.  Any idea what?
>
> "You do not need a parachute to skydive.  You only need a parachute to
> skydive twice."  -Motto of the Darwin Society
> Gordon W. Wolfe, Ph.D.  (425) 865-5940
> VM Technical Services, The Boeing Company
>
>
> > ----------
> > From:         Sergey Korzhevsky
> > Reply To:     Linux on 390 Port
> > Sent:         Wednesday, March 13, 2002 5:58 AM
> > To:   [EMAIL PROTECTED]
> > Subject:      I made it (Was: ipl tape)
> >
> >
> > 12.03.2002 15:29:24 Linux on 390 Port ???????(?):
> >
> > Hello Jim!
> >
> > You are almost right. I look at source code and found, that
> >
> > minor number 0 for rewinding,
> > minor number 1 for non-rewinding. For the same device, of course.
> >
> > For second device, I thing, it will be 2&3.
> >
> > Now, I can describe all the way.
> >
> > 1) insmod tape390 tape=<address>
> >
> >  Driver uses major number 254 (in my case)
> >
> > 2) cd /dev; mknod ntibm1 c  254   1
> >
> > 3) mt -f /dev/ntibm1 rewind
> >
> > 4) dd if=image of=/dev/ntibm1 bs=1024                  # write kernel
> > image
> >     mt -f /dev/ntibm1 eof 1
> > #
> > write EndOfFile mark
> >
> >  dd if=parmfile of=/dev/ntibm1 bs=1024                  # write parmfile
> >     mt -f /dev/ntibm1 eof 1
> > #
> > write EndOfFile mark
> >
> >  dd if=initrd of=/dev/ntibm1 bs=1024                        # write
> > ramdisk
> > image
> >     mt -f /dev/ntibm1 eof 2
> > #
> > write EndOfFile mark twice - for sure :)
> >
> >
> > 5)  mt -f /dev/ntibm1 rewind
> >
> > You have the correct tape. Easy :)
> >
> >
> > >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.
> > >
> >
> >
>
>

Reply via email to