>>> On 8/22/2008 at 4:45 PM, in message
<[EMAIL PROTECTED]>, Alan
Altmark <[EMAIL PROTECTED]> wrote:
-snip-
> That's the error you get when the virtual machine hasn't activated the
> integrated linemode console interface.
I know this isn't (necessarily) your area of expertise, but do you have an
On Friday, 08/22/2008 at 03:56 EDT, Mark Post <[EMAIL PROTECTED]> wrote:
> There should probably be a bug filed against the newer doc, because when
I try
> to follow the sample on a z/VM 5.1 system, I get this back:
> 00: HCPPCX6531E The operating system will not accept commands from the
service
>
>>> On 8/22/2008 at 2:40 PM, in message <[EMAIL PROTECTED]>, Brad Hinson
<[EMAIL PROTECTED]> wrote:
> Mark Post wrote:
> On 8/22/2008 at 1:29 PM, in message <[EMAIL PROTECTED]>, Brad
> Hinson
>> <[EMAIL PROTECTED]> wrote:
>> -snip-
>>> Note: The %
>>> is an escape character to '#cp vi vmsg'
On Friday 22 Aug 2008, Marcy Cortes wrote:
> From /etc/sysconfig/yup
>
> # There are two options, to get the ID:
> #
> # 1. use the Machine ID: this value is in
> #/etc/zmd/deviceid
> #on the machine you registered with.
> #
> # 2. go to the Novell Customer Center and request
> #"mi
On Friday 22 Aug 2008, Mark Post wrote:
> >>> On 8/22/2008 at 8:52 AM, in message
> > I have set YUP_ID and YUP_PASS to the values in /etc/zmd, so what have I
> > missed?
>
> That looks like the registration failed for some reason. What does "rug
> sl" and "rug ca" show you?
# rug sl
Waking up Z
Mark Post wrote:
On 8/22/2008 at 1:29 PM, in message <[EMAIL PROTECTED]>, Brad Hinson
<[EMAIL PROTECTED]> wrote:
-snip-
Note: The %
is an escape character to '#cp vi vmsg' which sets input to lowercase.
Otherwise root= is sent as ROOT=, which Linux doesn't like very much.
Hmm. Not on my SLE
>>> On 8/22/2008 at 1:29 PM, in message <[EMAIL PROTECTED]>, Brad Hinson
<[EMAIL PROTECTED]> wrote:
-snip-
> Note: The %
> is an escape character to '#cp vi vmsg' which sets input to lowercase.
> Otherwise root= is sent as ROOT=, which Linux doesn't like very much.
Hmm. Not on my SLES10 SP1 sys
I always liked doing my own keypunching -- and I can **still** code
better if I scribble the corrections on a fanfold listing!
("multiprocessing": two 360-30's with 14KB (!) DOS supervisors which
everybody said was too big)
Douglas
Re: [LINUX-390] Distribution ages, was: Linux version
Does zipl display a boot menu? If so, you'll need to pass root= to
zipl, not IPL. For example, at a prompt like this:
00: zIPL v1.5.3 interactive boot menu
00:
00: 0. default (linux)
00:
00: 1. linux
00:
00: Note: VM users please use '#cp vi vmsg '
00:
00: Please choose (default will boot in
>>> On 8/22/2008 at 12:51 PM, in message
<[EMAIL PROTECTED]>,
"Walters, Gene P" <[EMAIL PROTECTED]> wrote:
> Ok, I restored my root partition back to the way it was this morning.
> Basically I was going to add DASD, so I took the guest down. I added
> the dasd to the user direct, and re-ipl'd. W
Thanks. I think I'll add the Gentoo picture to my screensaver -- maybe
I can relabel it for something ubiquitous which comes out of the northwest
:)
Douglas
(personal opinions only, and all that ... :) )
[LINUX-390] Linux Motivational Posters
Neale Ferguson
to:
LINUX-390
08/22/2008 09:35
Thats what happens when you do it from memory instead of looking it up. :(
LOADPARM is limited to 8 characters.
Try "IPL 1490 PARM root=/dev/dasd1" That should allow 64 characters.
Walters, Gene P wrote:
HCPCLT1013E An invalid operand was supplied for LOADPARM -
ROOT=/DEV/DASDA1
--
Stephen Fr
Normally, for most products, IBM tests them on the new release before the
availability date. If it
runs with no problems then it is supported from day 1. If they have to change
something then support
may be later. If it is easy to fix they may support it (with the fix) from day
1.
Marcy Cortes
HCPCLT1013E An invalid operand was supplied for LOADPARM -
ROOT=/DEV/DASDA1
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Stephen Frazier
Sent: Friday, August 22, 2008 1:01 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: IPL parms
Did you try - "IPL 1490 LO
Please see http://www.redhat.com/security/data/openssh-blacklist.html
Note: This applies to any systems downloading packages/updates from
*non* Red Hat sources. If you receive your updates from Red Hat
Network, this does not apply.
Thanks,
--
Brad Hinson <[EMAIL PROTECTED]>
Sr. Support Engineer
Did you try - "IPL 1490 LOADPARM root=/dev/dasd1" ? What happened?
Walters, Gene P wrote:
May I should have phrased my question better, I'm losing my mind. Is
there a way to pass a Linux boot parm, when typing IPL from VM,
such as IPL 1490 root=/dev/dasda1
--
Stephen Frazier
Information
May I should have phrased my question better, I'm losing my mind. Is
there a way to pass a Linux boot parm, when typing IPL from VM,
such as IPL 1490 root=/dev/dasda1
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
van Sleeuwen, Berry
Sent: Friday, A
Have to do some 2009 planning...
How long is it typically between the availability of the next release of
SLES (or RHEL for that matter) before IBM will support WAS, DB2, MQ
Series on it?
Marcy
"This message may contain confidential and/or privileged information. If
you are not the addressee
Ok, I restored my root partition back to the way it was this morning.
Basically I was going to add DASD, so I took the guest down. I added
the dasd to the user direct, and re-ipl'd. When it started coming back
up, instead of loading the init from dasdb1, which was what it was doing
before, it tri
>From /etc/sysconfig/yup
# There are two options, to get the ID:
#
# 1. use the Machine ID: this value is in
#/etc/zmd/deviceid
#on the machine you registered with.
#
# 2. go to the Novell Customer Center and request
#"mirror credentials" to get updates to all your
#systems wit
>>> On 8/22/2008 at 10:08 AM, in message
<[EMAIL PROTECTED]>,
"Walters, Gene P" <[EMAIL PROTECTED]> wrote:
> I guess I should have been paying more attention to the list before I
> added more DASD to one of my guests. Yes, I have done exactly this,
> except I compounded it. Thinking I was smart,
Gene,
"IPL 190 PARM AUTOCR" or whatever parm you'd like to have. Or in case of
a guest OS such as VM "IPL CLEAR LOADPARM 0009".
Regards, Berry.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Walters, Gene P
Sent: vrijdag 22 augustus 2008 18:33
To:
Is it possible to put in IPL parms when you type IPL in VM?
--
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/h
>>> On 8/22/2008 at 8:52 AM, in message <[EMAIL PROTECTED]>,
Robin Atwood <[EMAIL PROTECTED]> wrote:
-snip-
> Thanks for the pointer. I have activated the product and configured yup as
> documented but when I run it I get a lot of messages:
-snip-
> I have set YUP_ID and YUP_PASS to the values in
Unless this changed in 2.6 the block devices go through VFS, and the blocks get
cached by the VFS layer.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Mark Perry
Sent: Thursday, August 21, 2008 11:07 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Root filesys
I was not referring to the page cache. The block devices still go through VFS,
and the blocks get cached by the VFS layer.
I can't say I have read the latest kernel source, so I could be wrong if this
changed in 2.6.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
I guess I should have been paying more attention to the list before I
added more DASD to one of my guests. Yes, I have done exactly this,
except I compounded it. Thinking I was smart, I mounted the disk to
another instance, changed the way it was mounted, to by-path, in the
fstab, and did a mkini
On Thursday, 08/21/2008 at 03:14 EDT, Kris Van Hees <[EMAIL PROTECTED]>
wrote:
> Check out the AUTOLOG and XAUTOLOG commands.
Focus on XAUTOLOG, not AUTOLOG.
Alan Altmark
z/VM Development
IBM Endicott
--
For LINUX-390 subscribe
A nice parody of those nauseating motivational posters:
http://www.besttechie.net/forums/Linux-Humor-t14545.html
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message
Didn't you mean that someone else could make punching mistakes for you?
Kevin
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
John Summerfield
Sent: Friday, August 22, 2008 8:39 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Distribution ages, was: Linux ver
Here we go again ...
I remember using Hollerith punched card machines. They were little
things where you had to punch the zone (10, 11, 12?) and the numeric #
to create coded alpha and numerics on the cards. No IBM 026 or 029 card
punches in those days. If we made a mistake on the Hollerith, w
On Friday 22 August 2008 08:13, Stahr, Lea wrote:
>I have a SLES 8 system that is coming up with /var not mounted. When I
>run a fsck /dev/dasdd1 on it I receive the following:
>fsck.reiserfs /dev/dasdd1 failed (status 0x10). Run manually!
>
>Anything I can do to save it?
Umm... You could try run
On Friday 22 Aug 2008, Mark Post wrote:
> The first part of my article at
> http://www.zjournal.com/index.cfm?section=article&aid=992 talks about how
> you register your system. If you follow those directions, the setup is
> done for you by the tools.
Thanks for the pointer. I have activated the
Mark Perry wrote:
Evans, Kevin R wrote:
This is getting like Monty Python .
One guy says "When we were young, we used to eat the leather from our
shoes". The other guy says "You had shoes?".
OS/360 - some of you guys make me feel young, thanks ;-)
You must be around 60, either that or your s
Robin Atwood wrote:
On Thursday 21 Aug 2008, John Summerfield wrote:
Evans, Kevin R wrote:
Kinda makes one realize how long z/OS (or its ancestors) has been
around, doesn't it?
MFT?
There was something called PCP that predated MFT but I am happy to say I never
worked on it! :D See: http://e
I have a SLES 8 system that is coming up with /var not mounted. When I
run a fsck /dev/dasdd1 on it I receive the following:
fsck.reiserfs /dev/dasdd1 failed (status 0x10). Run manually!
Anything I can do to save it?
Lea Stahr
Senior Systems Engineer
zVM, Linux and zLinux
Navistar,
> I expect the problem is using 'dd' for the copying may not get the
> magic signatures
Also 'dd' expects a dasdfmt'd disks or it loses its way. Another approach
might be to try dasdfmt'ing the disk before 'dd'.
"Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061
---
Rob van der Heij wrote:
I expect the problem is using 'dd' for the copying may not get the
magic signatures that makes the disk a CDL format, so the driver ends
up seeing it as LDL and gets things misaligned. But you should be able
to notice that when the new system is booting.
This is not the c
Fargusson.Alan wrote:
Doing a dd on a device goes through the cache, so in this case the cache can't
be the problem.
This is not the case. In fact, the page cache is indexed by address
spaces and each file as well as each block device has its own address
space. Consequently, Linux cannot tell t
On Thursday 21 Aug 2008, John Summerfield wrote:
> Evans, Kevin R wrote:
> > Kinda makes one realize how long z/OS (or its ancestors) has been
> > around, doesn't it?
>
> MFT?
There was something called PCP that predated MFT but I am happy to say I never
worked on it! :D See: http://en.wikipedia.
40 matches
Mail list logo
