Re: RPM troubles

[Tim Verhoeven]

On Mon, 6 May 2002, Mike Spaniol wrote:

> I'm trying to install the openssh package on my linux guest machine.
> When I run the rpm command to install the package, it looks to me as
> though it works, but I can't find that it installed anything.
>
> Here's a ls command of everything in my directory where I stored
> the openssh package I downloaded.
>
> [root@linuxtst openssh]# ls -l
> total 824
> -rw-r--r--   1 root root   838269 Apr 15 17:21 openssh-3.1p1-1.src.rpm
>
> Here's the response I get from my rpm command.
>
> [root@linuxtst openssh]# rpm -ivh openssh-3.1p1-1.src.rpm
> openssh ##
> [root@linuxtst openssh]#
>
> Is there a log somewhere I can look in to see what's not happening?  What
> should I try next?
>
> Thanks for your help.

I've seen you've been able to install it using the tar files that were
contained in the source rpm.

This isn't the prefered way of installing new software on a rpm based
distribution. Using the tar/make/make install method doesn't take
advantage of the rpm's dependencies, easu upgrade/remove,... It also
doesn't register openssh as installed (for rpm ofcourse) which means other
rpms that have openssh as a prereq will fail, even if it is installed.

How to install a src rpm the rpm way. Well you first do

rpm --rebuild xxx.src.rpm

This will build a binary rpm for your system (eg xxx.s390.rpm) and put in
into RPMS/s390 directory of the rpm base directory (/usr/src/redhat for RH
or /usr/src/packages fo SuSE).

Then you can install that with the normal rpm -ivh or -Uvh.

Also a good place to look for binary rpms is www.rpmfind.net and it
mirrors.

Regards,
Tim

--
===
Tim Verhoeven
Linux & Open Source Specialist
GSM : 0496 / 693 453  + e-business solutions
Email : [EMAIL PROTECTED]   + consulting
URL : www.sin.khk.be/~dj/ + Server consolidation
===

Antwort: Re: network problems during installation

[Tim-Chr. Hanschen]

Hi,

i read the z800 redbook and followed the installation routine for QDIO
mode. I launched the echo and insmod commands and started the network.

Everything worked fine... well, it seems that everything worked fine. The
modules were loaded and the network seems to be up.

SuSE Instsys (none):/ # ifconfig
eth0  Link encap:Ethernet  HWaddr 00:00:00:00:00:00
  inet addr: 10.96.68.35  Mask:255.255.255.0
  UP RUNNING NOARP MULTICAST  MTU:1492  Metric:1
  RX packets:33 errors:0 dropped:0 overruns:0 frame:1
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:100
  RX bytes: 1934 (1.8 Kb)   TX byte:0 (0.0b)
  Interrupt: 209
loLink encap: Local Loopback
  inet addr: 127.0.0.1  Mask:255.0.0.0
  UP LOOPBACK RUNNING MTU:16436  Metric:1
  RX packets:8 errors:0 dropped:0 overruns:0 frame:0
  TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes: 592 (592.0 Kb)   TX byte:592 (592.0b)

The problem is, that I cannnot ping or telnet to the machine, so I cannot
continue the installation.

Any suggestions?

TIA,
  - Tim -






Rob van der Heij <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 29.04.2002 11:57:11

Bitte antworten an Linux on 390 Port <[EMAIL PROTECTED]>

Gesendet von:  Linux on 390 Port <[EMAIL PROTECTED]>


An:   [EMAIL PROTECTED]
Kopie:
Thema:Re: network problems during installation


At 09:07 29-04-02 +0200, you wrote:
>Hi Rob,
>
>how does the echo command have to look like? Something like:
>
>   echo ??? >> /proc/chandev

echo qeth0,0x35a0,0x35a1,0x3512 > /proc/chandev
echo add_parms,0x10,0x35a0,0x35a2,portname:OSAE > /proc/chandev
echo reprobe > /proc/chandev

But again, read in the Device Drivers book about how to do this.

Re: no lcs moudle found with REDHAT 7.2

[Rob van der Heij]

I have not installed it yet, but when I checked the
various parts in the 31-bit Rawhide version it does not
look like it already uses the lcs driver sources.

>What could I do if I do not have a Linux system?

Note that it can be any Linux system, not just on S/390.

You're sort of right in that you don't have to do this
with Rawhide, more that you CAN NOT do it with Rawhide.
The IBM provided OCO modules are closely bound to the
kernel level, and IBM did not provide a version that
works with the Rawhide kernel. If you would want to run
Rawhide in an LPAR you need to use either CTC's to your
z/OS or z/VM system, or a chpid into a CISCO router.

Rob

Newbie alert/question!

[Todd Booher]

For someone who has no mainframe experience and no access to an
S390, is running a linux/s390 distro on top of hercules a good way to
learn the procedures necessary to install/run/maintain linux on the S390?

What distro of linux should I run on hercules?  I've seen images for
debian but it looks like Suse is the preferred distro for the 390.

By the way, seeing Alan Cox post here certainly gives a good impression
of the momentum behind the linux/S390 movement.


Thanks for the help,

Todd Booher
Senior LAN Analyst
Mazda North American Operations
[EMAIL PROTECTED] 

Re: no lcs moudle found with REDHAT 7.2

[Makhijani, Beena]

Hi,

The instructions on DeveloperWorks seem to indicate that you need a Linux
system somewhere before you can install the OCO OSA modules.  What could I
do if I do not have a Linux system?  I was under the impression that by
using the rawhide code, I do not have to install the OCO modules, but I
guess that was not correct.

Thanks,
Beena

-Original Message-
From: Rob van der Heij [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 04, 2002 12:59 AM
To: [EMAIL PROTECTED]
Subject: Re: no lcs moudle found with REDHAT 7.2


At 18:48 03-05-02, Miller, Ila wrote:

>What kind of information is Red Hat expecting at the Please enter any
>parameters you need to pass to the channel device layer?  Do I need to deal
>with these OCO modules if I install Red Hat linux in an S/390 LPAR?  I was
>hoping this would be an easy do.

Yes, you especially need the OCO module in LPAR. When you're on VM you
can have the VM TCP/IP stack do the 'hard work' and talk IUCV or CTC
to it, but on LPAR you have to do what your hardware does.

IBM did release the source code for the LCS driver, and RedHat put that
in the Rawhide of the 64 bit distribution, but at that time not yet in
the 31 bit (and you can hardly blame them for giving priority to the
paying customers when we can try the stuff out for free).

It is fairly easy to merge the OCO modules into the RedHat supplied
initrd following the instructions on DeveloperWorks. Do remember to
put a ramdisk_size=10240 or so in your parmfile.

Rob

3270-console reboot bug fixed

[Richard Hitt]

Hello.

If you're using a 3270 console with linux-390 you may have noticed that
when you give the "reboot" command your system typically goes into a
disabled loop.  Here's a patch to cure the problem.  It should apply
cleanly on any 2.4.7, 2.4.9, or 2.4.17 kernel tree.  Alan, Martin,
whoever is appropriate, I'd be grateful if you could accept this patch
into your forthcoming work.

 start of patch
diff -urN -X dontdiff linux/drivers/s390/char/tubtty.c 
linux-3270fix/drivers/s390/char/tubtty.c
--- linux/drivers/s390/char/tubtty.cMon May  6 13:52:35 2002
+++ linux-3270fix/drivers/s390/char/tubtty.cMon May  6 13:12:21 2002
@@ -603,12 +603,20 @@
 static void
 tty3270_bh(void *data)
 {
-   long flags;
tub_t *tubp;
+   ioinfo_t *ioinfop;
+   long flags;
struct tty_struct *tty;

-   tubp = data;
-   TUBLOCK(tubp->irq, flags);
+   ioinfop = ioinfo[(tubp = data)->irq];
+   while (TUBTRYLOCK(tubp->irq, flags) == 0) {
+   if (ioinfop->ui.flags.unready == 1)
+   return;
+   }
+   if (ioinfop->ui.flags.unready == 1 ||
+   ioinfop->ui.flags.ready == 0)
+   goto do_unlock;
+
tubp->flags &= ~TUB_BHPENDING;
tty = tubp->tty;

 end of patch

Dick Hitt   [EMAIL PROTECTED]

Re: The mainframe is back ...

[Gregg C Levine]

Hello from Gregg C Levine
I should emend that post. It isn't the author who got back to me, it is
two staffers, or even Editors at the magazine. DRAT
---
Gregg C Levine [EMAIL PROTECTED]

"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of
> Gregg C Levine
> Sent: Monday, May 06, 2002 8:04 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [LINUX-390] The mainframe is back ...
> 
> Hello from Gregg C Levine
> How many of you, decided to respond to the writer, regarding feedback?
I
> did, and both the editor, and the author got back to. Since I am
> advisedly not an expert in the field, that I know all of you, are, but
I
> did mention the merely obvious, in the feedback column. It looks as if
> my response to the editor did the trick, the writer has gotten back to
> me. I don't know if I should be happy, or what.
> ---
> Gregg C Levine [EMAIL PROTECTED]
> 
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke."  Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
> 
> 
> 
> > -Original Message-
> > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf
> Of
> > Post, Mark K
> > Sent: Thursday, May 02, 2002 5:33 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [LINUX-390] The mainframe is back ...
> >
> > I just wish the writer had gotten more of her facts right.  Sigh.
> Even the
> > ones who try to write positive articles come across as ignorant
hacks.
> >
> > Mark Post
> >
> > -Original Message-
> > From: paultz [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 02, 2002 5:04 PM
> > To: [EMAIL PROTECTED]
> > Subject: The mainframe is back ...
> >
> >
> > ... according to ESJ.  Of course we already knew this.
> >
> > Enjoy
> > http://www.esj.com/departments/article.asp?EditorialsID=59

Re: The mainframe is back ...

[Gregg C Levine]

Hello from Gregg C Levine
How many of you, decided to respond to the writer, regarding feedback? I
did, and both the editor, and the author got back to. Since I am
advisedly not an expert in the field, that I know all of you, are, but I
did mention the merely obvious, in the feedback column. It looks as if
my response to the editor did the trick, the writer has gotten back to
me. I don't know if I should be happy, or what.
---
Gregg C Levine [EMAIL PROTECTED]

"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of
> Post, Mark K
> Sent: Thursday, May 02, 2002 5:33 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [LINUX-390] The mainframe is back ...
> 
> I just wish the writer had gotten more of her facts right.  Sigh.
Even the
> ones who try to write positive articles come across as ignorant hacks.
> 
> Mark Post
> 
> -Original Message-
> From: paultz [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 02, 2002 5:04 PM
> To: [EMAIL PROTECTED]
> Subject: The mainframe is back ...
> 
> 
> ... according to ESJ.  Of course we already knew this.
> 
> Enjoy
> http://www.esj.com/departments/article.asp?EditorialsID=59

Re: RPM troubles

[Mike Spaniol]

Thanks Mark.

That got me looking.  I found the tar file so I tarred it to break it
apart and then I could run the rest of the install process.

Thanks for your help.


Mike Spaniol
Blackwell North America, Inc.
6024 SW Jean Rd., Bldg. G
Lake Oswego, OR   97035
(503) 684-1140 Ext. 1231

[Announce] Systems/C++ for mainframe Linux.

[Thomas David Rivers]

Just a quick announcement...  hopefully, a shortened version
of this will not be too intrusive.


Today, Dignus announces Systems/C++ for Linux - the first ANSI-98
standard C++ for mainframe linux.  Systems/C++ also includes
(pre-built) the de-facto STLport C++ standard libraries and Standard
Template Library.


For more information  - please visit http://www.dignus.com, you'll
find a pointer to the press release on the first page.


And... now... we return you to your regular programming.

- Thanks! -
- Dave Rivers -

--
[EMAIL PROTECTED]Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com

Re: RPM troubles

[Post, Mark K]

Mike,

You are installing a source RPM (SRPM), not a binary one.  Installing an
SRPM puts things into /usr/src/redhat/SPECS and /usr/src/redhat/SOURCES, and
that's all.  Unless you want to build it from source (which can be
educational), then you need to find something that looks like
openssh-3.1p1-1.s390.rpm.

Mark Post

-Original Message-
From: Mike Spaniol [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 06, 2002 5:33 PM
To: [EMAIL PROTECTED]
Subject: RPM troubles


Hello,

I'm trying to install the openssh package on my linux guest machine.
When I run the rpm command to install the package, it looks to me as
though it works, but I can't find that it installed anything.

Here's a ls command of everything in my directory where I stored
the openssh package I downloaded.

[root@linuxtst openssh]# ls -l
total 824
-rw-r--r--   1 root root   838269 Apr 15 17:21
openssh-3.1p1-1.src.rpm

Here's the response I get from my rpm command.

[root@linuxtst openssh]# rpm -ivh openssh-3.1p1-1.src.rpm
openssh
##
[root@linuxtst openssh]#

Is there a log somewhere I can look in to see what's not happening?  What
should I try next?

Thanks for your help.


Mike Spaniol
Blackwell North America, Inc.
6024 SW Jean Rd., Bldg. G
Lake Oswego, OR   97035
(503) 684-1140 Ext. 1231

Re: GFS anyone?

[Jon R. Doyle]

Send a note to [EMAIL PROTECTED] tell him I sent you. I am sure Michael
will be open with you on what they are doing and have done.

GFS and the LVM are great stuff IMHO.

Regards,

Jon

Jon R. Doyle
Sendmail Inc.
6425 Christie Ave
Emeryville, Ca. 94608


   (o_
   (o_   (o_   //\
   (/)_  (\)_  V_/_



On Mon, 6 May 2002, Lionel Dyck wrote:

> Is anyone using GFS under z/VM Linux?
>
> 
> Lionel B. Dyck, Systems Software Lead
> Kaiser Permanente Information Technology
> 25 N. Via Monte Ave
> Walnut Creek, Ca 94598
>
> Phone:   (925) 926-5332 (tie line 8/473-5332)
> E-Mail:[EMAIL PROTECTED]
> Sametime: (use Lotus Notes address)
> AIM:lbdyck
>

RPM troubles

[Mike Spaniol]

Hello,

I'm trying to install the openssh package on my linux guest machine.
When I run the rpm command to install the package, it looks to me as
though it works, but I can't find that it installed anything.

Here's a ls command of everything in my directory where I stored
the openssh package I downloaded.

[root@linuxtst openssh]# ls -l
total 824
-rw-r--r--   1 root root   838269 Apr 15 17:21 openssh-3.1p1-1.src.rpm

Here's the response I get from my rpm command.

[root@linuxtst openssh]# rpm -ivh openssh-3.1p1-1.src.rpm
openssh ##
[root@linuxtst openssh]#

Is there a log somewhere I can look in to see what's not happening?  What
should I try next?

Thanks for your help.


Mike Spaniol
Blackwell North America, Inc.
6024 SW Jean Rd., Bldg. G
Lake Oswego, OR   97035
(503) 684-1140 Ext. 1231

GFS anyone?

[Lionel Dyck]

Is anyone using GFS under z/VM Linux?


Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598

Phone:   (925) 926-5332 (tie line 8/473-5332)
E-Mail:[EMAIL PROTECTED]
Sametime: (use Lotus Notes address)
AIM:lbdyck

Re: Strange DASD errors on shared /usr

[Wolfe, Gordon W]

Thanks to Jay Brenneman and Rob Van der Heij.  This problem is solved.

"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: Robert J Brenneman
> Reply To: Linux on 390 Port
> Sent: Monday, April 29, 2002 10:37 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Strange DASD errors on shared /usr
>
> I believe there is also a read only switch to be placed in the parmfile
> for
> dasd which is mounted under VM as read only.
> Something like the following:
> dasd=7080,7081(ro)   root=/dev/dasda1 ro noinitrd
>
> that will tell the dasd driver that 7081 is really really read only, It
> wont update acces times and what not. This would be in addition to the
> line
> in the fstab which states:
> /dev/dasdb1   /usr   ext2   ro  0  0
>
> Note that if you have your dasd as a range like so: dasd=900-910(ro)
> the (ro) applies to the entire range. So you may want to do something like
> this: dasd=900-905,906-910(ro)
>
> You of course have to re run silo / zipl to make the changes stick , as
> well as re-IPL the linux image.
>
>
> Jay Brenneman
>
>
>
>
>
>
>   "Wolfe, Gordon W"
>[EMAIL PROTECTED]
>   oeing.com>   cc:
>   Sent by: Linux onSubject:  Re: Strange DASD
> errors on shared /usr
>   390 Port
>   <[EMAIL PROTECTED]
>   IST.EDU>
>
>
>   04/29/02 12:02 PM
>   Please respond to
>   Linux on 390 Port
>
>
>
>
>
> Thanks, Rob.
>
> I'll have to wait for the weekend to give this a try, but I think it will
> solve the problem.
>
> "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: Rob van der Heij
> > Reply To: Linux on 390 Port
> > Sent: Saturday, April 27, 2002 1:24 AM
> > To:   [EMAIL PROTECTED]
> > Subject:  Re: Strange DASD errors on shared /usr
> >
> > >Indeed I do.  First thing I checked.  Here's my line out of /etc/fstab:
> > >
> > >/dev/dasdc1 /usr  ext2ro 1
> > 0
> >
> > You need to do both. On your LinuxA you
> >   mount /usr -o ro,remount
> >   sync;sync
> > and then you can boot up the others provided they have the
> > /etc/fstab as you show above.
> >
> > If you have not mounted /usr on LinuxA as ro before, the
> > ext2 filesystem appears dirty to the other guests and they
> > will try to e2fsck the disk before mounting, even ro.
> >
> > Rob
> >
> >
>
>

Re: many Linux guests under vm. how to manage.

[John Summerfield]

> If they ( the developers ) were trying to target a product for the Linux/390
> community, I would hope that they would not try to develop and test those
> products just willy nilly even in the uncontrolled environment where they
> are not getting what they think that they need.
>
> When we buy a product for our production systems we hope (perhaps blindly)
> that the vendor produced that product on, or reasonably near, the target. Or
> is Linux so smooth to allow a vendor to be able to develop and test on
> Linux/Intel and then sell to Linux/390?
>
> I would expect to see something like Hercules engines popping up if the
> users (Linux Admins / Developers) do not get the control that they want
> because they think that they need it [key word think].
>
> We havent even gotten to an accepted direction and already have several
> flavors of Linux, both distribution and platform.


Here at home I have a LAN. I have this setuo:
Dugite, K6-I/500, server
Possum, PII/233, a workstation (mostly) for my wife.
Numbat, Athlon 1.4.

My data is all stored on Dugite.

The Athlon is good for building software on. It's also good fur running Hercules.

If I had a genuine S/390 round, it might still make sense to run Hercules on my Athlon 
and compile my S/390 programs on it.

Whether I test on numbat or on the S/390 mainframe is a separate issue, and if I test 
on numbat then the QA folks should still use the real thing.

The cost of the Athlon system unit (without disk) was comparable to the cost of a 
complete low-end Celeron or Duron system.
--
Cheers
John Summerfield

Microsoft's most solid OS: http://www.geocities.com/rcwoolley/

Note: mail delivered to me is deemed to be intended for me, for my disposition.

==
If you don't like being told you're wrong,
be right!

Re: many Linux guests under vm. how to manage.

[Rick Troth]

On Fri, 3 May 2002, Rich Blair wrote:
> 1. Give each development group their own Linux.   ...

> 2. We (IBM syprogs) micromanage each Linux -   ...

I'm very much in the #1 camp.
In fact,  I would not stop at the group level
but would go so far as to give every  *user*  their own Linux.
(This does not mean that they would all be instanciated or launched
only that they would be defined.)

To keep sanity,  there has to be a lot of filesystem sharing.
This not only saves mental clarity but saves resources.

Re: many Linux guests under vm. how to manage.

[John Summerfield]

[EMAIL PROTECTED] said:
> I'm unclear as to why any Hercules engines would pop up at all...


I think a flock of penguins on emulated S/390 is a good way to go for
development and it's in this context I think it's worth looking at.

As others have noted, S/390 is an expensive source of CPU power. PCs are cheap,
and PCs equipped with Hercules cost no more for software. Ad Linux and the
software cost hasn't changed.

I can install Linux on a PC in about ten minutes, and I could install Linux on a
hundred (after they're attached to the LAN) about as fast as I could go round
them booting them off a floppy (or CD with a floppy image). It would make no
significance difference equip them all with Hercules and a standard L/390 image.

Even quicker, "Here's your floppy. Set the BIOS up so, boot thus floppy, go get
you coffee, return to the PC and remove the floppy. When it says LOGIN, it's
ready."



--
Cheers
John Summerfield

Microsoft's most solid OS: http://www.geocities.com/rcwoolley/

Note: mail delivered to me is deemed to be intended for me, for my disposition.

==
If you don't like being told you're wrong,
be right!

Test Message, Please Ignore.

[Konkol, Josh]

 .~.
 /V\
/( )\
^^-^^

Re: Using Secuser and send to shutdown linux image???

[Lionel Dyck]

I understand everything you've coded with the exception of the pipe
statement. What does it do?

Also is there a way to detect when the image has halted so that it can be
removed (using force image log)?

thx

Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598

Phone:   (925) 926-5332 (tie line 8/473-5332)
E-Mail:[EMAIL PROTECTED]
Sametime: (use Lotus Notes address)
AIM:lbdyck



"Richard Feldman (WFF)" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
05/06/2002 09:25 AM
Please respond to Linux on 390 Port


To
[EMAIL PROTECTED]
cc

bcc

Subject
Using Secuser and send to shutdown linux image???



To: LINUXLST--WFFCAL   Linux 390 Discussi

Subject: Using Secuser and send to shutdown linux image???

We simply use secuser and cp send:
/* Program to 'halt' linux machine prior to system shutdown */
'Pipe cms id() | specs w1 | var user'
'SET SECUSER LNXDNS01 'user
Address Command 'CP SEND LNXDNS01 ROOTID'
'SLEEP 5 SEC'
Address Command 'CP SEND LNXDNS01 ROOTPW'
'SLEEP 5 SEC'
Address Command 'CP SEND LNXDNS01 halt'
'SET SECUSER LNXDNS01 RESET'

The 'Set secuser' command needs priv A or C.
Use address command so the command is sent lower case.

Regards,

Richard Feldman
Systems Programmer, Technical Services
Kelly, Douglas / Westfair Foods  Ltd.
Ph:(403)291-6339 Fax:(403)291-6585 E-Mail:[EMAIL PROTECTED]
*** Forwarding note from EX009177--WFFCAL   05/06/02 09:34 ***
To: LINUXLST--WFFCAL   Linux 390 Discussi

From: Lionel Dyck (SMTP:[EMAIL PROTECTED])
Subject: Using Secuser and send to shutdown linux image???
I ran across secuser and send while reading this weekend and have tried to
create a rexx exec that I could use to automate the shutdown of a linux
image but I can't seem to get the login to work.  Has anyone an example of
doing something like this under z/vm that they would be willing to share?

thanks

Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598

Phone:   (925) 926-5332 (tie line 8/473-5332)
E-Mail:[EMAIL PROTECTED]
Sametime: (use Lotus Notes address)
AIM:lbdyck

Re: Using Secuser and send to shutdown linux image???

[Lionel Dyck]

Terrific - thanks - that works great.

Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598

Phone:   (925) 926-5332 (tie line 8/473-5332)
E-Mail:[EMAIL PROTECTED]
Sametime: (use Lotus Notes address)
AIM:lbdyck



"Richard Feldman (WFF)" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
05/06/2002 09:25 AM
Please respond to Linux on 390 Port


To
[EMAIL PROTECTED]
cc

bcc

Subject
Using Secuser and send to shutdown linux image???



To: LINUXLST--WFFCAL   Linux 390 Discussi

Subject: Using Secuser and send to shutdown linux image???

We simply use secuser and cp send:
/* Program to 'halt' linux machine prior to system shutdown */
'Pipe cms id() | specs w1 | var user'
'SET SECUSER LNXDNS01 'user
Address Command 'CP SEND LNXDNS01 ROOTID'
'SLEEP 5 SEC'
Address Command 'CP SEND LNXDNS01 ROOTPW'
'SLEEP 5 SEC'
Address Command 'CP SEND LNXDNS01 halt'
'SET SECUSER LNXDNS01 RESET'

The 'Set secuser' command needs priv A or C.
Use address command so the command is sent lower case.

Regards,

Richard Feldman
Systems Programmer, Technical Services
Kelly, Douglas / Westfair Foods  Ltd.
Ph:(403)291-6339 Fax:(403)291-6585 E-Mail:[EMAIL PROTECTED]
*** Forwarding note from EX009177--WFFCAL   05/06/02 09:34 ***
To: LINUXLST--WFFCAL   Linux 390 Discussi

From: Lionel Dyck (SMTP:[EMAIL PROTECTED])
Subject: Using Secuser and send to shutdown linux image???
I ran across secuser and send while reading this weekend and have tried to
create a rexx exec that I could use to automate the shutdown of a linux
image but I can't seem to get the login to work.  Has anyone an example of
doing something like this under z/vm that they would be willing to share?

thanks

Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598

Phone:   (925) 926-5332 (tie line 8/473-5332)
E-Mail:[EMAIL PROTECTED]
Sametime: (use Lotus Notes address)
AIM:lbdyck

Re: Using Secuser and send to shutdown linux image???

[Rick Troth]

 ...
> said, you then need to get concerned with the default PIPE separator stage
 ...

You could probably deal with that issue like this:

/* REXX */
Parse Arg cline
'PIPE VAR CLINE | SPEC /SEND SUSE0001 / 1 1-* N | CP | CONSOLE'
Exit rc

> I guess by even mentioning EXECIO I'm showing my "age".  :)

;-)

- R

Re: Using Secuser and send to shutdown linux image???

[Rick Troth]

> I ran across secuser and send while reading this weekend and have tried to
> create a rexx exec that I could use to automate the shutdown of a linux
> image but I can't seem to get the login to work.  Has anyone an example of
> doing something like this under z/vm that they would be willing to share?

See other postings by Mike C. and me for REXX examples.
Also,  you may want to run a console shell of some sort.
Mike K. has one,  and I believe there are others.
Mine is included here  (sans the /etc/inittab change required):

#!/bin/sh
#
#
# Date: 2000-Sep-16 (Sun)
#
#

#
# argument #1 can be a console filespec:
CONSOLE="$1"
if [ -z "$CONSOLE" ] ; then CONSOLE=/dev/console ; fi

#
# set the prompt string:
PS1=`hostname`
#PS1="$PS1 # "
PS1="$PS1 \\\$ "
export PS1

#
# set the shell to something safe:
SHELL=/bin/sh
if [ -x /sbin/sh ] ; then SHELL=/sbin/sh ; fi

#
# add a couple important things to command search PATH var:
if [ -d /usr/bin/X11 ] ; then PATH="$PATH:/usr/bin/X11" ; fi
if [ -d /usr/local/bin ] ; then PATH="$PATH:/usr/local/bin" ; fi
export PATH

#
# now run that shell:
exec $SHELL -i 0<$CONSOLE 1>$CONSOLE 2>$CONSOLE

Using Secuser and send to shutdown linux image???

[Richard Feldman (WFF)]

To: LINUXLST--WFFCAL   Linux 390 Discussi

Subject: Using Secuser and send to shutdown linux image???

We simply use secuser and cp send:
/* Program to 'halt' linux machine prior to system shutdown */
'Pipe cms id() | specs w1 | var user'
'SET SECUSER LNXDNS01 'user
Address Command 'CP SEND LNXDNS01 ROOTID'
'SLEEP 5 SEC'
Address Command 'CP SEND LNXDNS01 ROOTPW'
'SLEEP 5 SEC'
Address Command 'CP SEND LNXDNS01 halt'
'SET SECUSER LNXDNS01 RESET'

The 'Set secuser' command needs priv A or C.
Use address command so the command is sent lower case.

Regards,

Richard Feldman
Systems Programmer, Technical Services
Kelly, Douglas / Westfair Foods  Ltd.
Ph:(403)291-6339 Fax:(403)291-6585 E-Mail:[EMAIL PROTECTED]
*** Forwarding note from EX009177--WFFCAL   05/06/02 09:34 ***
To: LINUXLST--WFFCAL   Linux 390 Discussi

From: Lionel Dyck (SMTP:[EMAIL PROTECTED])
Subject: Using Secuser and send to shutdown linux image???
I ran across secuser and send while reading this weekend and have tried to
create a rexx exec that I could use to automate the shutdown of a linux
image but I can't seem to get the login to work.  Has anyone an example of
doing something like this under z/vm that they would be willing to share?

thanks

Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598

Phone:   (925) 926-5332 (tie line 8/473-5332)
E-Mail:[EMAIL PROTECTED]
Sametime: (use Lotus Notes address)
AIM:lbdyck

Re: Using Secuser and send to shutdown linux image???

[Coffin Michael C]

Hi Rick,

Yup, Diag/DiagRc will both do the trick too - I've never been a fan of the
Diag/DiagRc syntax however.  I originally used PIPE to do this, but as I
said, you then need to get concerned with the default PIPE separator stage
(I suppose setting it to some character which cannot be entered via the
keyboard might do the trick - probably ought to do that instead of EXECIO as
well).

I guess by even mentioning EXECIO I'm showing my "age".  :)

Michael Coffin, VM Systems Programmer
Internal Revenue Service - Room 6527
 Constitution Avenue, N.W.
Washington, D.C.  20224

Voice: (202) 927-4188   FAX:  (202) 622-3123
[EMAIL PROTECTED]



-Original Message-
From: Rick Troth [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 06, 2002 12:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Using Secuser and send to shutdown linux image???


On Mon, 6 May 2002, Coffin Michael C wrote:
> You're going to need to SEND those Linux commands in lower case (by
default
> they will be upper cased).   Use EXECIO to pass the command to CP   ...

I have to recommend Diag(08,'SEND'...) or Diagrc(08,'SEND'...) instead. This
is probably the Pipelines fiend in me:  even though I'm
not using Pipes in this case,  I have an anti-EXECIO thing now.   ;-)

> /*Send commands to Linux on SUSE0001 in mixed case*/
> Trace Off
> Address Command
> Parse Arg Command
> 'EXECIO 0 CP (SKIP STRING SEND SUSE0001' Command
> Exit Rc

/*Send commands to Linux on SUSE0001 in mixed case*/
Trace Off
Parse Arg Command
Parse Value Diagrc(08,'SEND SUSE0001' Command ,
With 1 Rc 10 . 17 Rs '15'x .
If Rs ^= "" Then Say Rs
Exit Rc

Re: Using Secuser and send to shutdown linux image???

[Rick Troth]

On Mon, 6 May 2002, Coffin Michael C wrote:
> You're going to need to SEND those Linux commands in lower case (by default
> they will be upper cased).   Use EXECIO to pass the command to CP   ...

I have to recommend Diag(08,'SEND'...) or Diagrc(08,'SEND'...) instead.
This is probably the Pipelines fiend in me:  even though I'm
not using Pipes in this case,  I have an anti-EXECIO thing now.   ;-)

> /*Send commands to Linux on SUSE0001 in mixed case*/
> Trace Off
> Address Command
> Parse Arg Command
> 'EXECIO 0 CP (SKIP STRING SEND SUSE0001' Command
> Exit Rc

/*Send commands to Linux on SUSE0001 in mixed case*/
Trace Off
Parse Arg Command
Parse Value Diagrc(08,'SEND SUSE0001' Command ,
With 1 Rc 10 . 17 Rs '15'x .
If Rs ^= "" Then Say Rs
Exit Rc

Re: Using Secuser and send to shutdown linux image???

[Coffin Michael C]

You're going to need to SEND those Linux commands in lower case (by default
they will be upper cased).   Use EXECIO to pass the command to CP in lower
case (I'd say use PIPE, but you'll run into trouble if you pass verticle
bars, for example as a stage separator in LINUX, PIPE will think they are
his...).

/*Send commands to Linux on SUSE0001 in mixed case*/
Trace Off
Address Command
Parse Arg Command
'EXECIO 0 CP (SKIP STRING SEND SUSE0001' Command
Exit Rc

This little exec sends command to userid SUSE0001, but you could have a
'common' command interface that accepts the target Linux machine as the
first argument, so you could do:

Parse Arg Linux Command
Upper Linux
'EXECIO * CP (SKIP STRING SEND' Linux Command

And then you could use one common command interface for all of your Linux
machines.

Michael Coffin, VM Systems Programmer
Internal Revenue Service - Room 6527
 Constitution Avenue, N.W.
Washington, D.C.  20224

Voice: (202) 927-4188   FAX:  (202) 622-3123
[EMAIL PROTECTED]



-Original Message-
From: Lionel Dyck [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 06, 2002 11:34 AM
To: [EMAIL PROTECTED]
Subject: Using Secuser and send to shutdown linux image???


I ran across secuser and send while reading this weekend and have tried to
create a rexx exec that I could use to automate the shutdown of a linux
image but I can't seem to get the login to work.  Has anyone an example of
doing something like this under z/vm that they would be willing to share?

thanks

Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598

Phone:   (925) 926-5332 (tie line 8/473-5332)
E-Mail:[EMAIL PROTECTED]
Sametime: (use Lotus Notes address)
AIM:lbdyck

Using Secuser and send to shutdown linux image???

[Lionel Dyck]

I ran across secuser and send while reading this weekend and have tried to
create a rexx exec that I could use to automate the shutdown of a linux
image but I can't seem to get the login to work.  Has anyone an example of
doing something like this under z/vm that they would be willing to share?

thanks

Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598

Phone:   (925) 926-5332 (tie line 8/473-5332)
E-Mail:[EMAIL PROTECTED]
Sametime: (use Lotus Notes address)
AIM:lbdyck

Re: many Linux guests under vm. how to manage.

[Alan Cox]

> that the vendor produced that product on, or reasonably near, the target. Or
> is Linux so smooth to allow a vendor to be able to develop and test on
> Linux/Intel and then sell to Linux/390?

Varies by codebase. You certainly need to test on /390 but a very large
amount of code required no fixes for S/390. There are -zero- changes to the
nethack codebase for S/390 Linux for example.

Alan

Re: many Linux guests under vm. how to manage.

[Duff Sr., David]

If they ( the developers ) were trying to target a product for the Linux/390
community, I would hope that they would not try to develop and test those
products just willy nilly even in the uncontrolled environment where they
are not getting what they think that they need.

When we buy a product for our production systems we hope (perhaps blindly)
that the vendor produced that product on, or reasonably near, the target. Or
is Linux so smooth to allow a vendor to be able to develop and test on
Linux/Intel and then sell to Linux/390?

I would expect to see something like Hercules engines popping up if the
users (Linux Admins / Developers) do not get the control that they want
because they think that they need it [key word think].

We havent even gotten to an accepted direction and already have several
flavors of Linux, both distribution and platform.

> -Original Message-
> From: Nix, Robert P. [mailto:[EMAIL PROTECTED]]
>
> I'm unclear as to why any Hercules engines would pop up at all...
>
> Wouldn't it be more reasonable to assume that the users would
> just install
> Linux images native to whatever platform they had? There's
> nothing magic
> about the 390 platform in relation to Linux that would make
> the end user
> want to emulate it. The fact is that Linux will run, by
> itself on probably
> any platform they had.
>
> The user isn't asking for a Linux/390 image. And the single user isn't
> probably asking for multiple Linux images. They just want a
> Linux to do some
> specific task. Intel or 390; doesn't matter to them. Single
> image on the
> iron, or multiple virtual guests; again, it doesn't matter to
> the user, as
> long as he gets "his" Linux. He isn't worried about economy
> of scale; his
> scale is "1".
>
> What the user is interested in is the ease of use of the
> Linux system he
> receives. No matter if the need is real or perceived, he's
> probably going to
> want to control the Linux software that lives there. If he
> can't get that
> control from you, he'll use real hardware to get it. And
> you'll have lost
> your economy, and your credibility with your user.
>
> Now, there are some users that will jump at the chance to
> have you manage
> their Linux image so that they can get on with the business of their
> application. And they'd appreciate that even if they were
> running on an
> Intel. Make use of that, and show them that having their
> Linux managed by
> you is an advantage. Maybe the others will take notice and
> things will drift
> your way over time
>
> 
> Robert P. Nixinternet: [EMAIL PROTECTED]
> Mayo Clinic  phone: 507-284-0844
> 200 1st St. SW page: 507-255-3450
> Rochester, MN 55905
> 
> "In theory, theory and practice are the same,
>  but in practice, theory and practice are different."
>
>
> > -Original Message-
> > From: Nick Laflamme [SMTP:[EMAIL PROTECTED]]
> > Sent: Monday, May 06, 2002 8:11 AM
> > To:   [EMAIL PROTECTED]
> > Subject:  Re: many Linux guests under vm. how to manage.
> >
> > John Summerfield wrote:
> >
> > > [EMAIL PROTECTED] said:
> > > >  Some of your users, I'm sure, need complete control of
> their Linux
> > > > image to make sure they know how real live customers
> would work with
> > > > their product. You have to offer these users this
> option, or they'll
> > > > go behind your back to get this kind of access. Do you
> really want a
> > > > flock of Hercules-powered penguins in your shop? :-)
> > >
> > > And what is wrong with a flock of Penguins on Hercules?
> > >
> > > It doesn't have to be hard to manage.
> >
> > My point, which I clearly didn't make well enough, is that
> if the original
> > poster
> > doesn't offer a way for his clients to control their own
> Linux images, the
> > users
> > will put up their own Linux images on servers (boxes) the
> IS organization
> > doesn't
> > control, and they'll lose the economies of scale they may
> aspire to by
> > going to
> > Linux guests under VM.
> >
> > In other words, if he doesn't offer a "full control" option
> he won't have
> > as many
> > "Linux guests under vm. how to manage", which is, after
> all, the subject
> > of the
> > note.
> >
> > The question isn't whether there's anything wrong with
> running Linux under
> > a
> > Hercules image; the question is how many Hercules images
> would spring up
> > outside
> > the data center, away from the VM system they mean to use
> as the rookery
> > for the
> > Penguins.
> >
> > Nick
>

Re: Developerworks and patches for 2.4.17

[Sergey Korzhevsky]

06.05.2002 16:28:00 James Melin  wrote:

>Is there a list of the patches and what each one does? I have poked around
>on the developerworks site but I am not really finding what I consider a
>concise list. I understand there are several patches you should really put
>on after installing the 2.4.17 distribution so you have  a stable kernal
>from which to work.

http://oss.software.ibm.com/developerworks/opensource/linux390/exp-2_4_17.shtml



WBR, Sergey

Re: Samba causes kernel to abend

[Coffin Michael C]

Hi Mark,

Actually, I liked the "good old days" of VM (prior to SES) better.  You
simply accessed your disks (source, PUT, local mods, object code) and could
just FILELIST by module name, or by PTF number (it was the filetype).  I
don't need all the overhead of SES and have never really liked it.  Besides,
when you build a text deck on VM there SHOULD be comments in the text
showing which PTF's were applied, so you can usually look right in the
object text deck to see what's been applied.

Just my opinion, I know a lot of people (now!) love SES.  I've just never
really become one of them.

Michael Coffin, VM Systems Programmer
Internal Revenue Service - Room 6527
 Constitution Avenue, N.W.
Washington, D.C.  20224

Voice: (202) 927-4188   FAX:  (202) 622-3123
[EMAIL PROTECTED]



-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 03, 2002 10:11 AM
To: [EMAIL PROTECTED]
Subject: Re: Samba causes kernel to abend


I can hear the boos and hisses already, but this is where something like
SMP/E and SES comes in handy.  This reminds me of the bad old days of VM
when the only way to figure out what fixes you had on was to look at the
source code files.  Ugh.

Mark Post

-Original Message-
From: Michael MacIsaac [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 03, 2002 9:41 AM
To: [EMAIL PROTECTED]
Subject: Re: Samba causes kernel to abend


> How can I tell what patches are already on if any?
Hmm - good question - write it down somewhere and don't lose that paper :))
(that is only slightly sarcastic)

A few more hints:
1) The command uname -a or more specifically uname -v tells you when the
kernel was last rebuilt:
  # uname -v
  #1 SMP Fri Nov 23 19:45:36 CET 2001

2) SuSE has the directory /usr/src/linux-2.4.7/Documentation/s390
which has the files:
  # ls *.readme
  linux-2.4.7-s390-1.readme  linux-2.4.7-s390-kerntypes.readme
  linux-2.4.7-s390-2.readme  linux-2.4.7-s390.readme
>From this we inferred that patches 0, 1 and 2 are applied

3) Look for patch files in /usr/src - of course this does not tell you if
they have been applied or if the kernel has been rebuilt.
  # ls /usr/src/*.diff
  /usr/src/linux-2.4.7-s390-3.diff  /usr/src/linux-2.4.7-s390-4.diff Then
you can at least try to apply the diffs to see if they've already been
applied.

There's gotta be a more scientific way - I defer to the more powerful
wizards on this list.


  -Mike MacIsaac,  IBM   [EMAIL PROTECTED]   (845) 433-7061

Re: many Linux guests under vm. how to manage.

[Nix, Robert P.]

I'm unclear as to why any Hercules engines would pop up at all...

Wouldn't it be more reasonable to assume that the users would just install
Linux images native to whatever platform they had? There's nothing magic
about the 390 platform in relation to Linux that would make the end user
want to emulate it. The fact is that Linux will run, by itself on probably
any platform they had.

The user isn't asking for a Linux/390 image. And the single user isn't
probably asking for multiple Linux images. They just want a Linux to do some
specific task. Intel or 390; doesn't matter to them. Single image on the
iron, or multiple virtual guests; again, it doesn't matter to the user, as
long as he gets "his" Linux. He isn't worried about economy of scale; his
scale is "1".

What the user is interested in is the ease of use of the Linux system he
receives. No matter if the need is real or perceived, he's probably going to
want to control the Linux software that lives there. If he can't get that
control from you, he'll use real hardware to get it. And you'll have lost
your economy, and your credibility with your user.

Now, there are some users that will jump at the chance to have you manage
their Linux image so that they can get on with the business of their
application. And they'd appreciate that even if they were running on an
Intel. Make use of that, and show them that having their Linux managed by
you is an advantage. Maybe the others will take notice and things will drift
your way over time


Robert P. Nixinternet: [EMAIL PROTECTED]
Mayo Clinic  phone: 507-284-0844
200 1st St. SW page: 507-255-3450
Rochester, MN 55905

"In theory, theory and practice are the same,
 but in practice, theory and practice are different."


> -Original Message-
> From: Nick Laflamme [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, May 06, 2002 8:11 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: many Linux guests under vm. how to manage.
>
> John Summerfield wrote:
>
> > [EMAIL PROTECTED] said:
> > >  Some of your users, I'm sure, need complete control of their Linux
> > > image to make sure they know how real live customers would work with
> > > their product. You have to offer these users this option, or they'll
> > > go behind your back to get this kind of access. Do you really want a
> > > flock of Hercules-powered penguins in your shop? :-)
> >
> > And what is wrong with a flock of Penguins on Hercules?
> >
> > It doesn't have to be hard to manage.
>
> My point, which I clearly didn't make well enough, is that if the original
> poster
> doesn't offer a way for his clients to control their own Linux images, the
> users
> will put up their own Linux images on servers (boxes) the IS organization
> doesn't
> control, and they'll lose the economies of scale they may aspire to by
> going to
> Linux guests under VM.
>
> In other words, if he doesn't offer a "full control" option he won't have
> as many
> "Linux guests under vm. how to manage", which is, after all, the subject
> of the
> note.
>
> The question isn't whether there's anything wrong with running Linux under
> a
> Hercules image; the question is how many Hercules images would spring up
> outside
> the data center, away from the VM system they mean to use as the rookery
> for the
> Penguins.
>
> Nick

Re: many Linux guests under vm. how to manage.

[Nick Laflamme]

John Summerfield wrote:

> [EMAIL PROTECTED] said:
> >  Some of your users, I'm sure, need complete control of their Linux
> > image to make sure they know how real live customers would work with
> > their product. You have to offer these users this option, or they'll
> > go behind your back to get this kind of access. Do you really want a
> > flock of Hercules-powered penguins in your shop? :-)
>
> And what is wrong with a flock of Penguins on Hercules?
>
> It doesn't have to be hard to manage.

My point, which I clearly didn't make well enough, is that if the original poster
doesn't offer a way for his clients to control their own Linux images, the users
will put up their own Linux images on servers (boxes) the IS organization doesn't
control, and they'll lose the economies of scale they may aspire to by going to
Linux guests under VM.

In other words, if he doesn't offer a "full control" option he won't have as many
"Linux guests under vm. how to manage", which is, after all, the subject of the
note.

The question isn't whether there's anything wrong with running Linux under a
Hercules image; the question is how many Hercules images would spring up outside
the data center, away from the VM system they mean to use as the rookery for the
Penguins.

Nick

Developerworks and patches for 2.4.17

[James Melin]

Is there a list of the patches and what each one does? I have poked around
on the developerworks site but I am not really finding what I consider a
concise list. I understand there are several patches you should really put
on after installing the 2.4.17 distribution so you have  a stable kernal
from which to work.