Please refer to:
http://www.ibm.com/developerworks/linux/linux390/whatsnew.html
... for the 2009-01-08 change summary:
> snIPL V2.1.4 with bug fixes and enhancements
* end of message
Mit freundlichen Grüßen / Kind regards
Gerhard H
Thanks for all those who responded. I installed SLES10 SP2 and that fixed
the problem. There must have been some incompatibitlities with z/VM 5.4 and
SP1 base.
Regards,
Jihad K. Kawkabani
IT Systems Engineer Consultant
Voice: 440.395.0740
Network: 575.0740
Cell: 440.465.2969
Ron
Is anyone running SLES 8 on zVM 5.3 on a z10? We are planning to upgrade to a
z10 and I reviewed some of the archives but did not find anyone mentioning they
run SLES 8 on a z10. We did find that SLES 8 is not certified by IBM for z10
but we would still like to know if anyone has run SLES 8.
Al
Anything new in this area?
TIA
-
Please consider the environment before printing this email and any
attachments.
This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain
information which is pr
>>> On 1/8/2009 at 11:10 AM, Sterling James wrote:
> Anything new in this area?
> TIA
Not that I have seen.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu wi
Is there any better way, in a bash script, to pipe both stdout and stderr
from an application other than using a subshell? So far the only way that
I've thought of to do it is:
(command parm1 ... 2>&1) | othercommand
--
Q: What do theoretical physicists drink beer from?
A: Ein Stein.
Maranatha!
>>> On 1/8/2009 at 12:36 PM, John McKown wrote:
> Is there any better way, in a bash script, to pipe both stdout and stderr
> from an application other than using a subshell? So far the only way that
> I've thought of to do it is:
>
> (command parm1 ... 2>&1) | othercommand
Just:
command parm1
Al,
We have several SLES 8 instances running on z/VM 5.3 RSU 801 on a z/10. We
did not encounter any problems after upgrading the processor or the z/VM
operating system.
Charles LeDuff
Systems Programmer
WPS Health Insurance
Phone: (608) 223-5818
Email: charles.led...@wpsic.com
"Alan Schil
On Thu, 8 Jan 2009, Mark Post wrote:
> >>> On 1/8/2009 at 12:36 PM, John McKown wrote:
> > Is there any better way, in a bash script, to pipe both stdout and stderr
> > from an application other than using a subshell? So far the only way that
> > I've thought of to do it is:
> >
> > (command parm
On Thursday 08 January 2009 14:13, John McKown wrote:
>Well, shoot. That never even occurred to me. What I thought that would do
>was:
>
>Change stderr to go where stdout currently goes, then change stdout to go
>into the pipe. I based this on the fact that if I do:
>
>command 2>&1 1>x.tmp
>
>Then
Thus, if you want the behaviour you described in the above command,
you could do the following:
command parms 2>&1 | cat >file.tmp
which would put everything in the file file.tmp
Erik Johnson
On Thu, Jan 8, 2009 at 1:30 PM, Edmund R. MacKenty
wrote:
> On Thursday 08 January 2009 14:13, John Mc
Does this failure to behave as one might hope perhaps constitute a bug
in a widely used admin utility?
Erik Johnson
On Wed, Jan 7, 2009 at 4:00 PM, Larry Ploetz wrote:
> On 1/7/09 1:44 PM, John Summerfield wrote:
>>
>> I see no reason logrotate should not handle sparse files well when
>> copying
On 1/8/09 9:36 AM, John McKown wrote:
Is there any better way, in a bash script, to pipe both stdout and stderr
from an application other than using a subshell? So far the only way that
I've thought of to do it is:
(command parm1 ... 2>&1) | othercommand
Others have answered the question, but
On 1/8/09 12:21 PM, Erik N Johnson wrote:
Does this failure to behave as one might hope perhaps constitute a bug
in a widely used admin utility?
Hmmm...I think so, now that you mention it...at least, I know I'd prefer
logrotate to keep sparse files sparse.
- Larry
--
On Thu, 8 Jan 2009, Edmund R. MacKenty wrote:
> On Thursday 08 January 2009 14:13, John McKown wrote:
> >Well, shoot. That never even occurred to me. What I thought that would do
> >was:
> >
> >Change stderr to go where stdout currently goes, then change stdout to go
> >into the pipe. I based this
I've been trying out the sles 9 (sp4 here) upgrade to sles10 sp2 process. All
goes well if using SSH.
But, I'd really like to use VNC (much easier to navigate those yast package
selection panels)...
We've got a boat load of servers that need to be upgraded and I need lots of
folks doing it :)
16 matches
Mail list logo