For readers of IBMMAIN, IBMVM, and Linux390 who
are interested in the no-charge education via webcast
(aka Live Virtual Classes).
Here's a PDF flyer with details:
http://www.vm.ibm.com/education/lvc/lvcv0820.pdf
Wednesday, August 20th at 11:00 AM EDT.
There is no charge to participate in this tec
Stahr, Lea wrote:
Thanks! The firewall was active by default, and I now get a connection
after shutting it down.
Better to configure the firewall properly than to shut it down (except,
maybe, for testing the hypothesis).
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
-- Adv
Let me try this again...
For those of you who are near San Francisco Bay area this Friday
and who are interested in hearing z/VM and Linux presentations.
The next Baybunch meeting is on Friday August 8 at
IBM San Francisco - 425 Market St.
Send an RSVP email to Karen Reed at [EMAIL PROTECTED]
M
For those of you who near San Francisco Bay area this Friday
and who are interested in hearing z/VM and Linux presentations.
The next Baybunch meeting is on Friday August 6 at
IBM San Francisco - 425 Market St.
Send an RSVP email to Karen Reed at [EMAIL PROTECTED]
Meet with the Baybunch user gro
Mark Post wrote:
On 8/6/2008 at 3:51 PM, in message <[EMAIL PROTECTED]>, Matt Gourley
<[EMAIL PROTECTED]> wrote:
-snip-
I've already tried running an fsck on the filesystem. Because I can't
write to it, I wound up shutting down and logging off the problem
system, LINKing its 201 disk MR to
Once your are up I would check the syslog and see what caused the read
only mount.
'Where ever you go - There you are!! '
Richard (Gaz) Gasiorowski
Global Solutions & Technology
Principal Lead Infrastructure Architect
845-773-9243 Work
845-392-7889 Cell
[EMAIL PROTECTED]
Computer Sciences Corpo
Mark Post wrote:
On 8/6/2008 at 3:51 PM, in message <[EMAIL PROTECTED]>, Matt Gourley
<[EMAIL PROTECTED]> wrote:
-snip-
I've already tried running an fsck on the filesystem. Because I can't
write to it, I wound up shutting down and logging off the problem
system, LINKing its 201 disk MR to
>>> On 8/6/2008 at 3:51 PM, in message <[EMAIL PROTECTED]>, Matt Gourley
<[EMAIL PROTECTED]> wrote:
-snip-
> I've already tried running an fsck on the filesystem. Because I can't
> write to it, I wound up shutting down and logging off the problem
> system, LINKing its 201 disk MR to another runn
OK, there was an error during boot and the root filesystem was
mounted read only to prevent damage.
Remount the root filesystem as read/write. There's an
explicit mount option especially for this (which means
that you're not the first person to ever have this
problem, so don't despair
Mark Post wrote:
On 8/6/2008 at 3:28 PM, in message <[EMAIL PROTECTED]>, Matt Gourley
<[EMAIL PROTECTED]> wrote:
One of our Linux images was booted on Monday for the first time since
March. During the boot, we started getting error messages telling us
that / was a read-only file system:
>>> On 8/6/2008 at 3:28 PM, in message <[EMAIL PROTECTED]>, Matt Gourley
<[EMAIL PROTECTED]> wrote:
> One of our Linux images was booted on Monday for the first time since
> March. During the boot, we started getting error messages telling us
> that / was a read-only file system:
Is this repeat
>>> On 8/6/2008 at 3:27 PM, in message
<[EMAIL PROTECTED]>, "Stahr,
Lea" <[EMAIL PROTECTED]> wrote:
> Thanks! The firewall was active by default, and I now get a connection
> after shutting it down.
Umm, don't do that. Restart the firewall, then go into YaST -> Network
Services -> Remote Admin
Hi,
VNC 4.1.2 should work. Here are a few things to verify:
1. Verify the server is listening on port 5901. From the server, run:
# netstat -pan | grep vnc | grep 5901
You should get a result like:
tcp 00 0.0.0.0:5901 0.0.0.0:* LISTEN 7123/Xvnc
If you see this, the server is up
Thanks! The firewall was active by default, and I now get a connection
after shutting it down.
Lea Stahr
zVM, Linux and zLinux Administrator
Navistar, Inc.
630-753-5445
[EMAIL PROTECTED]
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Gasiorowsk
One of our Linux images was booted on Monday for the first time since
March. During the boot, we started getting error messages telling us
that / was a read-only file system:
Waiting for device /dev/dasdb1 to appear: ok
rootfs: major=94 minor=5 devn=24069
rootfs: /sys/block/dasdb/dasdb1 major=
Check you most likely have the Linux Firewall active
'Where ever you go - There you are!! '
Richard (Gaz) Gasiorowski
Global Solutions & Technology
Principal Lead Infrastructure Architect
845-773-9243 Work
845-392-7889 Cell
[EMAIL PROTECTED]
Computer Sciences Corporation
Registered Office: 3170
Thanks for the 'vmcp q md 201 loc' command. A new one for me and it
indicates the server is indeed using the volsers I want it to use.
OK, it was me who used the same labels in Linux as for VM. From what you
are saying I can label a volume as LNX001 in VM (cpfmtxa) but label it
0201 in Linux (dasd
We have 2 SLES10 SP1 servers. When I start yast2 on the first linux, the
xterm screen shows a long scrolling list of selections, and its slow. On
the second linux, the Control Center display is compact and all on one
screen, and its faster. Where should I look for the cause of the
differences?
On Wed, Aug 6, 2008 at 6:19 PM, Bauer, Bobby (NIH/CIT) [E]
<[EMAIL PROTECTED]> wrote:
> dasd(eckd): 0.0.0201: 3390/0A(CU:3990/01) Cyl:3338 Head:15 Sec:224
The 3338 cylinders suggests that you have (wisely) given the Linux
guest a mini disk starting at cylinder 1, so cylinder 0 is for CP to
do its
I have a new SuSE 10 SP1 guest. I have started the VNCSERVER on Linux. I
cannot connect to it, the connections timeout from W2000 viewers. I am
using VNC 4.1.2. I have looked at the RealVNC site and cannot find the
problem. I do not know what is supplied with Linux. Should I try the
newer 4.4 viewe
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
> Behalf Of Fargusson.Alan
> Sent: Wednesday, August 06, 2008 1:00 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: C language question
>
> This code is depending on a particular implementation of the
> IO functio
I found a work-around. In the "main" file, I put a
FILE *msgout;
outside of the "main" routine (file level?) and initialized msgout in
main().
In the other file (parser.y), I put
extern FILE *msgout;
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Cove
On Aug 6, 2008, at 12:52 PM, McKown, John wrote:
Well, I am trying to compile a program on Linux, so maybe...
Anyway, I got (didn't write) a program off of the Internet. It is
actually the output from yacc. There is a statement which does not
compile:
FILE *msgout=stderr;
error: initializer e
This code is depending on a particular implementation of the IO functions.
This should probably be done by putting a #define msgout stderr in some include
file.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
McKown, John
Sent: Wednesday, August 06, 2008 10
Hi John,
See below...
>
> Well, I am trying to compile a program on Linux, so maybe...
>
> Anyway, I got (didn't write) a program off of the Internet. It is
> actually the output from yacc. There is a statement which does not
> compile:
>
> FILE *msgout=stderr;
>
> error: initializer element is
Well, I am trying to compile a program on Linux, so maybe...
Anyway, I got (didn't write) a program off of the Internet. It is
actually the output from yacc. There is a statement which does not
compile:
FILE *msgout=stderr;
error: initializer element is not constant
I'm not really very good wit
We have been naming all of our Linux volumes LNX* and decided that was a bit
naïve. It seemed simple enough to FDR the 5 volumes labeled LNX0* associated
with one server to 5 volumes labeled FAW0*, change the VM directory and use the
new volumes.
It appears to work but during the boot I see:
27 matches
Mail list logo
