Greetings; (Posted to VMESA-L and VSE-L and LINUX-390)
- - Now in its seventh year! - - Includes VSE and linux/390!
I have set up a public service web page at
http://www.eskimo.com/~wix/vm/
for posting positions available and wanted for VM, VSE and linux/390.
Please visit the web
Hi Folk,
I have two Debian 2.4.17 Linux390 systems, configured with ext3 filesystems as
follows:
DEBIBASE (an image with full r/w DASD, used to maintain /usr and /usr/opt):
MDISK 150 3390 1839 750 LINUX1 MR /
MDISK 151 3390 3139 200 LINUXA MR swap
MDISK 152 33901 3338
-Original Message-
From: Alan Altmark [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 9:08 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Performance Tookit Error
On Monday, 05/23/2005 at 02:01 EST, Little, Chris
[EMAIL PROTECTED] wrote:
Trying to start the web interface. I get the
I knew I should never have taken that vacation.
I have downloaded the SLES9 and SLES9x ISO files from the Novell
website and gone through a few installations. My current installation
is a 64bit minimal system with certain specific applications added via
yast. I have done a few Online Updates
Michael,
It's been pretty well settled for some time now that you cannot have one
guest running with a disk R/W, and try to share it with others R/O.
It's just asking for trouble, such as you're seeing. Any and all
systems that have it LINKed and mounted, must have it R/O.
Also, mounting an
Hi Mark,
The intent is not to have the 'MAINTenance userid' that has them linked R/W
up and running all the time, so they should be fine R/O. But I do agree
having them as ext3 is asking for trouble, particularly when the MAINTenance
machine is up. Unfortunately, you can't just mount an ext3
Michael,
The point being that if the maintenance machine has it R/W, no other
system should be using it at that time. Once the maintenance machine
umounts the file system and is shut down and logged off VM, then the
other systems can mount it.
I mount ext3 file systems as ext2 all the time.
Howdy Folks,
Ok, one last question and then I'll go away for a while. :)
How do you change the Linux DASD label WITHOUT reformatting the disk?!?! I
have a need to reformat/change the Linux DASD label
only, but looking at DASDFMT I don't see this as an option.
I guess I'm looking for the
Hi Mark,
I got a ton of I/O errors when I tried to mount the R/O ext3 as ext2 - BUT
in fairness, that may have been because the owner was up and running and had
the disk R/W. May as well keep it ext2 for consistency across the boards.
Xip2fs looks very cool, I'll have to play with that at some
Hi:
I am trying to revive an old PC Server P/390 that I have had sitting idle for
some time. I have successfully installed VM/ESA 2.4 on it and have it running
fine. I have downloaded the disks of the latest Debian Linux/390 distribution
and am in the process of installing it under VM/ESA.
Use fdasd /dev/dasdg (no partition number)
Choose V to recreate vtoc
Betsie
Michael Coffin wrote:
Howdy Folks,
Ok, one last question and then I'll go away for a while. :)
How do you change the Linux DASD label WITHOUT reformatting the disk?!?! I
have a need to reformat/change the
Hi there!
I am trying to IPL for the first time an LPAR under a z890 using the ISO
images from SUSE (6xCD in 64 bits, version 9).
I try using my HMC, Load from CD, and then I am supposed to provide a CD to
create a temporary SUSE on the z890/LPAR.
Once I make it that far, I have the 6xISO
How do you change the Linux DASD label WITHOUT reformatting
the disk?!?! I have a need to reformat/change the Linux DASD label
only, but looking at DASDFMT I don't see this as an option.
It's not. I don't believe this is possible for the Linux tools. If this
is a CDL volume, you might be able
Hi Betsie,
Thanks. Looks like that's what I need - but now I have a new problem.
I'm trying to change the label of an ext2 disk that was formatted under SuSE
2.2.16, because when I use it on Debian 2.4.17 I see the following messages
during boot:
/dev/dasd/0154:4
register_disk_label: invalid
Use the fdasd -l command.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Coffin
Sent: Thursday, May 26, 2005 2:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Change Linux DASD Label
Howdy Folks,
Ok, one last question and then I'll go
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Coffin Michael C
Sent: Thursday, May 26, 2005 2:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Change Linux DASD Label
snip
PS: Anyone have any idea why z/OS is even mentioned in this
message?
The 2.2 kernels don't support volume labels the same way as the (later)
2.4 kernels do. 2.2 also didn't support partitioning DASD, so you could
only have dasda1, dasdb1, etc., and not dasda2, dasda3.
You might be better of creating a new volume using the (default) CDL
format, copying the data
This is with sles9 SP1.
During base install, I had DASD 104-108 configured as LVM and everything is
OK. Later, I added DASD 109, activated format it using yast and added it
to the same lvm vg. Everything looks OK until you reboot.
At boot time, during LVM activation, DASD 109 is not active,
It sounds like you didn't re-run mkinitrd. Do that, then re-run zipl.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Ifurung, [EMAIL PROTECTED]
Sent: Thursday, May 26, 2005 7:07 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Activatiing LVM at boot
19 matches
Mail list logo
