Mark,
I double checked everything and it seems OK.
it is a Machine ESA,
Q CPLEVEL gives the following result :
z/VM Version 4 Release 3.0, service level 0201 (64-bit)
Generated at 05/09/02 17:30:26 CDT
IPL at 05/18/03 12:45:22 CDT
and uname -m : s390x
Herve
-Ursprüngliche Nachricht-
V
Make sure you have specified the portname correctly in your
/etc/chandev.conf file. Something like:
noauto;qeth0,0x1000,0x1001,0x1002;add_parms,0x10,0x1000,0x1002,portname:GBE0
>From the "Device Drivers and Installation Commands" manual:
PORT_NAME
Must be specified for each OSA-Express CH
Harold,
You say the OSA-E "was not initially defined to the newly created Linux
lpar. Even after correcting that problem, we have tried, with no success, to
get this device working on Linux." What, exactly, did you do to correct
that problem? If it was a dynamic reconfiguration of the LPAR, I be
On Mon, 28 Jul 2003, Thomas David Rivers wrote:
> > If you're going to use a shell script, I think you will find this model
> > both faster and safer: faster because the cat command is superflous, and
> > safer because it keeps the original, "just in case."
> >
> > mv ${file{ ${file}~
> > sed <${f
> If you're going to use a shell script, I think you will find this model
> both faster and safer: faster because the cat command is superflous, and
> safer because it keeps the original, "just in case."
>
> mv ${file{ ${file}~
> sed <${file}~ >${file} \
>-e "s/ *$//"
>
> I've not tested mine e
We installed Linux in a partition on a 9672-R46 mainframe last week in a LPAR
configuration (non-zVM). We were able to configure and use our OSA-2 card without any
problems as an LCS device, but we have been unsuccessful in getting our OSA-Express
running (in QDIO mode).
The OSA Express is shar
On Mon, 28 Jul 2003, McKown, John wrote:
> Well, just because I know that everybody is dying of curiousity about what
> I've done. I created the shell script:
>
> #!/bin/sh
> cut -c1-72 $1 | sed -e 's/\ *$//' >$2
>
> I invoke it in a subdirectory with:
>
> for i in *;do ../nonum.sh $i $i.ext;done
On Mon, 28 Jul 2003, McKown, John wrote:
> > -Original Message-
> > From: Guillaume Morin [mailto:[EMAIL PROTECTED]
> > Sent: Monday, July 28, 2003 12:35 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Stripping trailing blanks?
> >
> >
>
>
>
> >
> > The problem is actually the predictible
On Tue, Jul 29, 2003 at 06:30:32AM +0800, John Summerfield wrote:
> man perlfunc
perldoc -f chomp
--
- mdz
On Mon, 28 Jul 2003, McKown, John wrote:
> Alan,
> I don't know if it is "normal", but I always do a
>
> chmod 1777 /tmp
>
> Would that address the security concern? Or is "world readable" the main
> concern? I really HATE 777 and will generally not allow it unless forced
> into it by some weird r
On Mon, 28 Jul 2003, Post, Mark K wrote:
> John,
>
> You can specify multiple things for sed to do on each record:
> sed -e 's/\(.\{0,72\}\).*/\1/' -e 's/ *$//' infile > outfile
You can do that, yes, but I prefer something that sprains the brain
less.
Some people beaver away endlessly, it seems,
On Mon, 28 Jul 2003, Thomas David Rivers wrote:
> John,
>
> There's a simpler way... (perl is, typically, overkill.)
> To strip the blanks from a file, just use "sed":
>
> cat $file | sed "s/ *$//" > /tmp/strip.$$
> mv /tmp/strip.$$ $file
Well.
He already has a working Perl scri
On Tue, 29 Jul 2003, John Summerfield wrote:
> On Mon, 28 Jul 2003, Adam Thornton wrote:
>
> > On Mon, 2003-07-28 at 09:58, McKown, John wrote:
> > > I don't have REXX on my SuSE SLES7. This is a minimal system which I
> > > downloaded from the Internet quite some time ago for use at home under
>
On Mon, 28 Jul 2003, Adam Thornton wrote:
> On Mon, 2003-07-28 at 09:58, McKown, John wrote:
> > I don't have REXX on my SuSE SLES7. This is a minimal system which I
> > downloaded from the Internet quite some time ago for use at home under
> > Hercules/390 (just for my learning how to install). W
Well, just because I know that everybody is dying of curiousity about what
I've done. I created the shell script:
#!/bin/sh
cut -c1-72 $1 | sed -e 's/\ *$//' >$2
I invoke it in a subdirectory with:
for i in *;do ../nonum.sh $i $i.ext;done
Where I replace ".ext" with something like ".jcl" or ".a
> Understand increases, thanks. I guess it would be "better" if, somehow,
> /tmp
> could refer to a different filesystem or directory for each individual
> user.
> UNIX on OS/390 does have something like this. A different kind of symlink
> which is dependant on the userid. Or perhaps, setup /tmp/$
You may be interested to know that there is currently a debate on exactly
this subject raging on the Debian Developer list. It does however seem to
have come to a conclusion after a week or so.
David
"McKown, John"
<[EMAIL PROTECTED]To: [EMA
> -Original Message-
> From: Guillaume Morin [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 28, 2003 12:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Stripping trailing blanks?
>
>
>
> The problem is actually the predictible file name in a world-writable
> directory. An attacker could cre
> I don't know if it is "normal", but I always do a
> chmod 1777 /tmp
This is the default permission ...
> Would that address the security concern? Or is "world readable" the main
> concern? I really HATE 777 and will generally not allow it unless forced
> into it by some weird requirement.
The
Alan,
I don't know if it is "normal", but I always do a
chmod 1777 /tmp
Would that address the security concern? Or is "world readable" the main
concern? I really HATE 777 and will generally not allow it unless forced
into it by some weird requirement.
--
John McKown
Senior Systems Programmer
U
On Llu, 2003-07-28 at 16:44, Henry, Jeff (J.) wrote:
> A nominee for the "Useless use of cat" award:
>
> cat $file | sed "s/ *$//" > /tmp/strip.$$
>
> vs.:
>
> sed "s/ *$//" < $file > /tmp/strip.$$
Can I nominate your alternative for one line security hole of the week
8)
That did it. Thanks Alan. You know, I'd never needed to add the
primary_router parm before. I read about it in the Device Drivers manual,
but the OSA I was using configured as OSD was routing just fine until a few
weeks back. There was a microcode update about a month ago -- I wonder if
a micro
Herve,
I forwarded your question on to our z/VM support team, and got this answer:
1. Make sure the CP directory entry for the guest says "MACHINE ESA" in it.
2. Make sure your z/VM is running in 64-bit mode: "Q CPLEVEL"
3. Make sure you have the 64-bit Linux/390 code: "uname -m" and look for
s390
John,
You can specify multiple things for sed to do on each record:
sed -e 's/\(.\{0,72\}\).*/\1/' -e 's/ *$//' infile > outfile
For column-specific stuff, you can also use the cut command:
cut -c1-71 infile | sed -e 's/ *$//' > outfile
Mark Post
-Original Message-
From: McKown, John [
David,
That works too. Unfortunately the subject: line is incomplete because I must
strip out anything in columns 73-80 (if there's anything there), then the
trailing blanks. I guess that:
sed 's/\(.\{0,72\}\).*/\1/' outfile
would work too. What I'm actually doing is something like:
ftp all memb
Which can be shortened by two more keystrokes to
sed 's/ *$//' $file > /tmp/strip.$$
Mark Post
-Original Message-
From: Henry, Jeff (J.) [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2003 11:45 AM
To: [EMAIL PROTECTED]
Subject: Re: Stripping trailing blanks?
-snip-
A nomine
Neale Ferguson has updated his 390Debugging document. To refresh everyone's
memory, the file is "a PDF document consisting of the doc. found in the
kernel source tree that pertains specifically to S/390 (32/64):
- 390Debugging.txt by DJ Barrow
- S/390 debugging facility
- Common I/O layer
- Common
>
>John,
>
> There's a simpler way... (perl is, typically, overkill.)
>To strip the blanks from a file, just use "sed":
>
>cat $file | sed "s/ *$//" > /tmp/strip.$$
>mv /tmp/strip.$$ $file
>
>This cats the file named "$file" - strips the blanks and writes
>the output in the file nam
On Mon, Jul 28, 2003 at 11:21:58AM -0400, Thomas David Rivers wrote:
> John,
>
> There's a simpler way... (perl is, typically, overkill.)
> To strip the blanks from a file, just use "sed":
>
> cat $file | sed "s/ *$//" > /tmp/strip.$$
> mv /tmp/strip.$$ $file
s/"/'/g . Otherwise t
On Mon, Jul 28, 2003 at 10:05:26AM -0500, Adam Thornton wrote:
> I believe the Perl function chomp does what you want.
>
> so:
>
> while (<>) {
> chomp;
> print;
> }
Nope, chomp() will only delete a single trailing \n.
For those who like to count rivets, what it really does is rem
John,
There's a simpler way... (perl is, typically, overkill.)
To strip the blanks from a file, just use "sed":
cat $file | sed "s/ *$//" > /tmp/strip.$$
mv /tmp/strip.$$ $file
This cats the file named "$file" - strips the blanks and writes
the output in the file named /tmp/stri
On Mon, 2003-07-28 at 10:27, McKown, John wrote:
> Is there a simple way to strip blanks from all the lines in a file?
You might also try:
sed 's/\ *$//' outfile
--
David Andrews
A. Duda and Sons, Inc.
[EMAIL PROTECTED]
On Mon, 2003-07-28 at 09:58, McKown, John wrote:
> I don't have REXX on my SuSE SLES7. This is a minimal system which I
> downloaded from the Internet quite some time ago for use at home under
> Hercules/390 (just for my learning how to install). When I told management
> (bad John!) they decided th
On Mon, Jul 28, 2003 at 09:27:09AM -0500, McKown, John wrote:
> Is there a simple way to strip blanks from all the lines in a file? What I
> am doing is downloading members from my various PDSes. Some of these member
> contain the "standard" sequence number in columns 73-80. I am using Perl to
> st
I don't have REXX on my SuSE SLES7. This is a minimal system which I
downloaded from the Internet quite some time ago for use at home under
Hercules/390 (just for my learning how to install). When I told management
(bad John!) they decided that this was excellent since there would be NO
capital out
Hi John,
Since you already know REXX (and it's a great string handling language) why
not just use Regina REXX? If you are running a SuSE distribution it's
probably already installed:
regina -h
Michael Coffin, VM Systems Programmer
Internal Revenue Service - Room 6030
Constitution Avenue,
Thanks. I hadn't thought of anchoring the pattern to the end of the line.
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Applications & Solutions Team
+1.817.255.3225
This message (including any attachments) contains confidential information
intended for a specific individual and
On Mon, 28 Jul 2003, McKown, John wrote:
> Is there a simple way to strip blanks from all the lines in a file? What I
> am doing is downloading members from my various PDSes. Some of these member
> contain the "standard" sequence number in columns 73-80. I am using Perl to
> strip these off. After
Is there a simple way to strip blanks from all the lines in a file? What I
am doing is downloading members from my various PDSes. Some of these member
contain the "standard" sequence number in columns 73-80. I am using Perl to
strip these off. After stripping off the sequence numbers, I would like
Hello,
My software (XFB/CFT for linux/390) doesn't receive the SIGALARM signal
while doing a msgrcv() system call.
This problem occurs in an LPAR of a D/T7060 (MP/3000), but it doesn't occurs
in
another LPAR of the same machine.
The only difference between the 2 LPAR is the use of NFS in the bad o
On Fri, Jul 25, 2003 at 07:40:29AM -0500, Marist EDU wrote:
> We are currently using CheckPoint Firewall SecuRemote to provide remote
> access to our road-warrior users. Really, the only access they need is
> tn3270. Is anyone aware of an open source, secure way I could provide them
> access.
>
>
41 matches
Mail list logo
