Thanks! That does look very helpful. And easier to understand than
Amanda!
Scott Chapman
John Summerfield
summer@computerdatasa To: [EMAIL PROTECTED]
fe.com.au cc:
Sent by: Linux on
At 14:33 27-01-03 -0800, Marcy Cortes wrote:
Any one else been through this? How much does it want? The README
says 1.3G is sufficient for a 31-bit install.
And you did select that formatted disk as the one to hold your / filesystem?
You did not by mistake tell YaST to put all on your 60 MB
On Monday 27 January 2003 17:31, Scott Chapman wrote:
Performance needs to be tracked from VM's perspective, and maybe
from Linux's. Therefore some sort of VM monitor like RTM (not
necessarily a recommendation!) or Velocity Software's product is
probably required. I believe Candle also has
On Wed, 2003-01-22 at 09:23, John Summerfield wrote:
As I understand it, Linux, Alan and a few others are here in Perth just now.
Linus ITYM 8)
And yes we had a very good technical event in Australia (LCA2003) while the press were
all looking the other way. They missed Linus (in a penguin suit
Postgresql chosen in preference to O and D.
http://www.computerworld.com.au/idg2.nsf/All/2ADD84E6EBCEADE9CA256CB30075FA01!OpenDocument
--
Cheers
John.
Join the Linux Support by Small Businesses list at
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Rob wrote:
Any one else been through this? How much does it want? The README
says 1.3G is sufficient for a 31-bit install.
And you did select that formatted disk as the one to hold your / filesystem?
You did not by mistake tell YaST to put all on your 60 MB swap disk?
It comes back and says
The missing word was running. And I'm talking about DRA backups here, of
perhaps multiple hundreds of Linux/390 instances on z/VM. In this scenario,
a full volume backup of the entire z/VM system, read-only minidisks or
otherwise, is _very_ useful. It allows me to run one set of tapes, get the
Bill,
The problem was patched in 2.2.5, so 2.2.6 should have the fix incorporated.
Samba 2.2.7 had some nice fixes for printing support (better automatic
downloading of drivers to Windows clients, etc.) included, so I would
recommend going to that version if you choose to upgrade it.
Mark Post
There _had_ to be some pictures taken of that. If you happen to see one on
the 'net (or have one of your own), I'd appreciate the URL. :)
Mark Post
-Original Message-
From: Alan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 8:18 AM
To: [EMAIL PROTECTED]
Subject: Re: A bit
Doug,
What does your /etc/printcap file look like? The error you get looks as
though that file's not quite right.
Mark Post
-Original Message-
From: Doug Clark [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 10:11 PM
To: [EMAIL PROTECTED]
Subject: Re: samba config help needed
Hi all, im downloading Redhat 7.1, but now im not sure about the 64 or 31
bits, im downloading it from:
ftp.redhat.com/pub/redhat/linux/7.1/en/os/s390x/, in the 7.2 directory i
only found s390, and looking at the mirror list
(http://www.redhat.com/download/mirror.html) i see that the directory is
Hi all, im downloading Redhat 7.1, but now im not sure about the 64 or
31 bits, im downloading it from: ...
Alex:
I would recommend you get the 7.2 31-bit version. Very few applications
need 64-bit yet (mySAP.com comes to mind) and most vendor software is
only supported on the 31-bit version
Alex,
You've almost got it right. s390x is 64 bits, s390 is 31 bits. The latest
GA 64-bit release is the 7.1/s390x version. The latest GA 31-bit release is
7.2/s390. When the mirror.html file was updated, it was done incorrectly.
All versions were changed to 8.0, even though that doesn't
7.2 is at
ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/s390/
Bill
-Original Message-
From: Alex Leyva [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 11:29 AM
To: [EMAIL PROTECTED]
Subject: Redhat 7.1, 7.2, 8.0, s390, s390x?
Hi all, im downloading Redhat 7.1, but now im
On Tuesday 28 January 2003 08:29, you wrote:
Hi all, im downloading Redhat 7.1, but now im not sure about the 64 or 31
bits, im downloading it from:
ftp.redhat.com/pub/redhat/linux/7.1/en/os/s390x/, in the 7.2 directory i
only found s390, and looking at the mirror list
Jim:
But what will happen when the applications will need 64 bits?
how dificult the migration will be?
thanks
On Tue, 28 Jan 2003, Jim Elliott wrote:
Hi all, im downloading Redhat 7.1, but now im not sure about the 64 or
31 bits, im downloading it from: ...
Alex:
I would recommend you
A HOWTO document on www.linuxvm.org describes how to use V-disk for
swap. I followed the instruction as outlined on RedHat 7.2, but failed
when issuing dasdfmt command: I received the following message:
dasdfmt -b 4096 -y -f /dev/dasdb
dasdfmt: Unsupported disk type
/dev/dasdb is not an ECKD
But what will happen when the applications will need 64 bits? how
dificult the migration will be?
Alex:
Good question. The decision is do you want to run supported vendor
software now or avoid a migration in the future. I don't expect the
migration to be difficult, but I can't speak from
Dave Myers wrote:
What do these commands show before you start the actual rpm installs.
cat /proc/dasd/devices
0201(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 600840
blocks, 2347 MB
0202(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 600840
blocks, 2347 MB
mount
rootfs
There is no need to run dasdfmt against a vdisk. Just mkswap and swapon
and it works.
Mark Post
-Original Message-
From: Abdel Gharzita [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 11:33 AM
To: [EMAIL PROTECTED]
Subject: Vdisk for swap on RH 7.2
A HOWTO document on
On Tue, 28 Jan 2003, Alex Leyva wrote:
Hi all, im downloading Redhat 7.1, but now im not sure about the 64 or 31
bits, im downloading it from:
ftp.redhat.com/pub/redhat/linux/7.1/en/os/s390x/, in the 7.2 directory i
only found s390, and looking at the mirror list
A fuller reply would have stated...
The original HOWTO was written for SuSE 7.0, which had a 2.2.16 kernel. I'm
not positive (I didn't write the HOWTO) the dasdfmt was really needed there.
In the 2.4 kernel series, the DASD driver has been changed significantly.
It should not be necessary to run
I know you're already aware of the README warning (I appended below for
other to see).
But, it sure looks to me like you're running into the warning in that 5th
paragraph,
where is states:
Only after you have used 'dasdfmt', can you then accept the DASD
Module Parameter Setting using the
Everyone,
Thanks for your help. The command in the smb.conf did not match the name
I had in the printcap file.
Doug
-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 7:51 AM
To: 'Linux on 390 Port'; 'Doug Clark'
Subject: RE: samba config
That works! Thanks Mark.
If I need to have this swap on whenever Linux is ipled, do I still need
to do mkswap and the swapon?
What's the equivalent to SuSE's /sbin.init.d/boot on RH?
Thank you
Abdel Gharzita
Pace Univerity
Abdel,
What some people have done is capture the swapfile signature that gets
written (at 7766 octal??), and written that to a CMS file on the guest's 191
disk. Then, just before the guest IPLs Linux, it writes that signature out
to the vdisk. Then, the only thing that needs to be done in the
On Tue, Jan 28, 2003 at 12:53:07PM -0500, Abdel Gharzita wrote:
That works! Thanks Mark.
If I need to have this swap on whenever Linux is ipled, do I still need
to do mkswap and the swapon?
What's the equivalent to SuSE's /sbin.init.d/boot on RH?
Well, what we generally do is IPL CMS, do
Greetings;
Don't know about SuSE, but mkswap and swapon works just fine
on my TurboLinux 2.2.16 kernel. Maybe with 2.2.x you could
dasdfmt a FBA device even though it wasn't necessary,
or it just ignored you silently!
Good Luck!
Dennis
Post, Mark K
Dave wrote:
I don't see any partitions in your displays.
What does cat /proc/partitions show??
I did the load module without the accept yet and then
came in with SSH to root and then did the dasdfmt, fdasd,
then hit the accept button.
Here's what cat /proc/partitions says:
major minor #blocks
hmmm...you did it the way I did it then
and when you use yast2 to mount / to /dev/dasda1 that seem to work ok?
Dave Myers
Denver Solutions Group
Senior Systems Engineer
Office Phone: (303) 996-7112
Cellular Phone: (303) 619-0782
Home Office: (303) 948-0027
Fax:
Dave wrote:
hmmm...you did it the way I did it then
and when you use yast2 to mount / to /dev/dasda1 that seem to work
Yep, that seemed to work and the DASD appeared under the
Partitions area, but still in the sw area it said there
was not enough space.
I still haven't heard back from
uhuhmy initial contact with SuSE support did no go too well.
They kept asking for a 14digit product code before they would give me
support
and they couldn't communicate to me where exactly that code resides.
By the time we sent 3 or 4 emails back and forth...I had worked my way
through
my
Mark,
Here are the steps I did to get V-disk work on Redhat 7.2 ( thanks to you)
- Add a MDISK statement to Linux directory:
MDISK 0151 FB-512 V-DISK 3 MR LINUX SWAP DASD
- Add the following to linux PROFILE EXEC:
QUEUE '1'
QUEUE 'LXSWAP'
'FORMAT 151 E ( BLK 4096'
IF RC 0 THEN
I have some source files that I compile and link together to make a shared
library (called sharedLib.so). They share a global variable called, for
example, GlobalVar which is defined in one of the source files (called
sharedMain.c). I then have another set of source files that I compile and
link
The -Bsymbolic flag appears to do what I need.
For some reason, we can not get our HiperSockets to work. We are trying to
use virtual hipersockets, but I was wondering if it would be better to use
actual Physical HiperSockets. I really need some help. From examples
within the PROFILE TCPIP (DEVICE LINK, HOME and GATEWAY) to the IFCONFIGs
On Tue, Jan 28, 2003 at 05:37:08PM -0600, Ketchens, LeMarr T. (RyTull)
wrote:
For some reason, we can not get our HiperSockets to work. We are trying to
use virtual hipersockets, but I was wondering if it would be better to use
actual Physical HiperSockets. I really need some help. From
On Tuesday 28 January 2003 17:52, you wrote:
On Tue, Jan 28, 2003 at 05:37:08PM -0600, Ketchens, LeMarr T. (RyTull)
wrote:
For some reason, we can not get our HiperSockets to work. We are trying
to use virtual hipersockets, but I was wondering if it would be better to
use actual Physical
On 28.01.2003 at 16:18:43, Matt Zimmerman [EMAIL PROTECTED] wrote:
When initial configuration runs (when you telnet into it),
http://192.168.0.1:3128 will be given as the _default_ proxy address, but
you are prompted to change it and it is not used for anything until after
this point.
We have not gotten to the point of implementing Hipersockets yet but we are
planning to. In reading about them, I ran into a list of will not do's. In
that list was IP broadcast traffic, an ARP requirement. Is this still the
case? If not, can someone please tell me the appropriate redbook(s)
On Wed, Jan 29, 2003 at 01:34:25PM +1000, Vic Cross wrote:
On 28.01.2003 at 16:18:43, Matt Zimmerman [EMAIL PROTECTED] wrote:
When initial configuration runs (when you telnet into it),
http://192.168.0.1:3128 will be given as the _default_ proxy address, but
you are prompted to change it
41 matches
Mail list logo
