Post, Mark K [EMAIL PROTECTED] wrote:
I'm curious (truly) as to why you would be installing Jetty instead of
Tomcat or something along those lines. What advantages does Jetty have?
Mark Post
Mark... This is a little dated, but was covered on the peanut gallery:
On Tuesday, 03/16/2004 at 08:27 GMT, Crispin Hugo
[EMAIL PROTECTED] wrote:
I know that I should not use REXEC etc but it's the only way I know to
run a
shell in Linux that needs parameters passed to it from our VM system.
Well, let's not throw the baby out with the bath water, eh? Feel free to
We have formated a mini disk of 285 Cylinders with :
dasdfmt -b 4096 -n 0104
dev2:/mnt# less /proc/dasd/devices
0104(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096,
51300
blocks, 200 MB
Going over the numbers, the overhead from dasdfmt is startling. At
849,960 bytes a
I know this has been discussed, but what was the final outcome. Should we
use EXT2 or EXT3 block size 1024 or 4096 for space allocation on zlinux
I am getting ready to start a POC on a z-800 IFL and it looks like I am
throwing DASD at the LINUX images.
We are also looking at LVM as a way to get
On Wed, 2004-03-17 at 08:54, Davis, Larry wrote:
I know this has been discussed, but what was the final outcome. Should we
use EXT2 or EXT3 block size 1024 or 4096 for space allocation on zlinux
Depends. 1K blocks will be slower but less wasteful of space if you
have lots of files smaller than
On Wed, Mar 17, 2004 at 12:31:07AM -0500, Post, Mark K wrote:
The proper directory to look in would be defined in your httpd.conf file as
the DocumentRoot. These days, Apache tends to get shipped with files like
these in the DocumentRoot:
index.html.en
index.html.it
index.html.se
But no
I have all the pieces for FCP other than an ESS 2105 box configured for SCSI
disk we also have a Storagetek V2X2 box, but it has no FICON at this point.
We are also going to evaluate an EMC DMX box for doing file sharing between
z/OS and Solaris/Linux platforms.
At this point I will place a
Should I be letting Linux instances, under z/VM, utilize Cylinder 0?
Currently I allocate Cylinder 0 to $ALLOC$ and the rest of the volume to the
Linux image.
I CPFMTXA cylinder 0 in VM and give it a VOLSER. Then, I access the devices
under Linux and dasdfmt them, and partition them using fdasd.
Adam wrote:
Depends. 1K blocks will be slower but less wasteful
of space if you have lots of files smaller than 4K.
For SCSI devices, I would agree with you. For eckd
devices, the overhead on 1K blocks is tremendous so
what you make up from small files is lost to eckd
overhead. Also, for eckd
I do not think you should let anything other than VM itself use cyl 0. As
this is where VM keeps Vol id, disk map info, etc. $ALLOC$ is what is
some times called a place holder. The userid $ALLOC$ doesn't actually do
anything with it other than mark it or inform others that this cylinder is
after applying online updates to a new install of sles8, my /var went
from 50% to 98% used. can someone tell me where this usage is and can
it be cleaned up?
--
For LINUX-390 subscribe / signoff / archive access instructions,
I would look in /var/lib/YaST2/you/i386/update/SuSE-SLES/8/rpm/
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch
Burnet
Sent: Wednesday, March 17, 2004 1:20 PM
To: [EMAIL PROTECTED]
Subject: full /var after online updates
after
I recently completed an install of SLES8 64 bit and I was disappointed
to find that the recent SUSE kernel rpms do not include dasd_diag_mod.o.
The last s390x kernel rpm to include it was k_deflt-2.4.19-71, although
it is still present in 31 bit SLES8. I'm sure that it's removal was
probably the
You might also have a look at /var/adm/backup/rpmdb
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Post, Mark K
Sent: Wednesday, March 17, 2004 1:24 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] full /var after online updates
I would look in
thanks Mark and Ken
lots of resources used here, can these be cleaned up or is it necessary
to keep these files around?
Post, Mark K wrote:
I would look in /var/lib/YaST2/you/i386/update/SuSE-SLES/8/rpm/
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
/tmp is supposedly a throw away file system, can Linux set this up in a
memory file system like it does /proc and could/should I use VDisk for /tmp
also?
TIA,\|/
(. .)
ooO-(_)-Ooo
Larry Davis, 6-2380
--
For
You can do that. We're experimenting with using T-disk (real disk) for /tmp.
Nature and nature's laws lay hid in night:
God said, 'Let Newton Be!' and all was light. - Alexander Pope
It did not last; the Devil howling 'Ho!
Let Einstein Be!' restored the status quo.- John Collings Squire
or /var/lib/rpm
Nature and nature's laws lay hid in night:
God said, 'Let Newton Be!' and all was light. - Alexander Pope
It did not last; the Devil howling 'Ho!
Let Einstein Be!' restored the status quo.- John Collings Squire
God Rolled his dice, to Einstein's great dismay:
'Let Feynman
I depends on how you've got it set up and what controls you have in place. If you're
using VM as a hypervisor for Linux, VM has to be able to know what the volser of the
DASD is. If your linux instances have root authority not controlled by you and they
take it in mind to do a dasdfmt on a
I would not erase the rpm database backups. If you don't think you'll be
needing to re-install any of those RPMs again, then you can delete the files
from the YOU directories. If you decide you want to re-install them again,
YOU will re-download them again using wget, just as it did the first
On Wednesday, 03/17/2004 at 11:50 EST, Davis, Larry
[EMAIL PROTECTED] wrote:
Should I be letting Linux instances, under z/VM, utilize Cylinder 0?
I would recommend never allowing any guest to write on cyl 0. If the
guest writes a label that matches the label of any of your CP_OWNED packs,
you
Well, technically VM only cares if the volumes are attached to SYSTEM
(uservol include in SYSTEM CONFIG). If you use DEDICATE to assign them to
Linux guests, then VM shouldn't much care, unless one of your Linuxes
decides to label them something like 440W01 or something then watch out for
fun at
On Wed, 2004-03-17 at 12:27, Davis, Larry wrote:
/tmp is supposedly a throw away file system, can Linux set this up in a
memory file system like it does /proc and could/should I use VDisk for /tmp
also?
Not quite like /proc.
You could use VDISK, although you'd have to format and mount it as
Hi,
Has anyone else installed this product, and if so, did it run OK? One of
our developers said he installed this today, and they said it used a huge
amount of our VM cpu. I need to check with the developer to see which
version he installed, but the development team is now concerned that z/VM
Where are they getting the high CPU numbers from ? Anything from inside the
instance is a lie. They'd have to be on VM and looking at rtm or esamon or
something to see real numbers.
Marcy Cortes
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ken
Vance
Let's suppose I was stupid enough in the beginning to just ATTACH a pack to the VM
guest, install Linux and dasdfmt the entire pack. Then, I didn't use the -label on
dasdfmt and ended up with a funky VOLSER like:
q 127
DASD 0127 ATTACHED TO DARWIN
I am following Michael MacIsaac's Print Serving Solutions Using Samba
CUPs presentation
and have some config problems that I don't understand:
1. I ran the cupsaddsmb command and I see that it created
InfoPrint_1125.PPD, which looks right for my Infoprint 1125 printer.
Not sure why
For those of us playing along at home and trying to get this work, is
there a short list of mistakes one might make (or contraindications one
might overlook) in this context?
Q SIGNALS on my VM system confirms that my Linux image is waiting for a
shutdown signal.
The first time I edited
There is another consideration that makes allocating of Linux volume to a
full-pack mini or letting it use cylinder zero very undesirable. If you
regularly run FDR backups from MVS to dump the shared DASD volumes to tape,
as part of your backup procedures, your backup will fail for full-pack Linux
Hi Dave,
1. I ran the cupsaddsmb command and I see that it created
InfoPrint_1125.PPD, which looks right for my Infoprint 1125
printer.
What's in /var/lib/samba/drivers/, /var/lib/samba/drivers/W32X86/, and
/var/lib/samba/drivers/W32X86/2 or /var/lib/samba/drivers/W32X86/3?
Not
On Wed, 2004-03-17 at 21:18, David Booher wrote:
Can I still use ICKDSF: CPFORMAT LABEL UNIT(127) NVFY VOLID(LNX200) to recify it
without harming the contents of the IPL volume?
Nope. Linux also sticks the volser in the DCB's that it puts on disk.
You better use Linux' fdasd to change the
After changing /etc/inittab, mine wouldn't work the first time either. After the
reboot it seemed to be OK.
Rich Smrcina
- Original Message -
From: Nick Laflamme [EMAIL PROTECTED]
Date: Wednesday, March 17, 2004 4:04 pm
Subject: Re: SLES8 trap signal shutdown
For those of us playing
The following technique seems to work for us, with SLES8.
- In /etc/fstab:
/dev/dasdb1 /tmp ext2 defaults 0 0
- In boot.local:
# Create and mount the disk space used for /tmp
mke2fs /dev/dasdb1
mount /dev/dasdb1 /tmp
chmod o=t /tmp
chmod a+rwx /tmp
- Be sure that you have FBA support in
You need to do telinit q to force rereading of inittab.
My inittab has a slightly different line:
ca:12345:ctrlaltdel:/sbin/shutdown -y -g0
I've tested this extensively, and it works for me. You should get messages on the
console when the signal is received, even if the script isn't
On Wed, 2004-03-17 at 22:04, Nick Laflamme wrote:
The first time I edited /etc/inittab to add this, I reversed two letters
in ctrlaltdel and got an error message when I next did an init 6, so
I know I'm in the right file, and since the error message went away, I
presume I'm spelling it
In order to ask /sbin/init to re-read /etc/inittab, you can issue the command:
kill -1 1
The -1 argument sends a kill signal which causes the process to reload its config.
The 1 is the process id. init always has process id 1, as it is the first process
loaded by the kernel.
You don't
On Wed, 2004-03-17 at 22:23, Scully, William P wrote:
The following technique seems to work for us, with SLES8.
- In /etc/fstab:
/dev/dasdb1 /tmp ext2 defaults 0 0
- In boot.local:
# Create and mount the disk space used for /tmp
mke2fs /dev/dasdb1
mount /dev/dasdb1 /tmp
chmod o=t /tmp
On Wed, 2004-03-17 at 22:31, Cameron, Thomas wrote:
In order to ask /sbin/init to re-read /etc/inittab, you can issue the command:
kill -1 1
Great! Until Rich mentioned it, I never had realized init would need to
re-read the /etc/inittab to make this work...
Rob
If you're using CDL formatted volumes, this should not be the case. If you
are, and it is happening anyway, you should report a problem to IBM and FDR.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Kharnas, Simon
Sent: Wednesday, March 17,
First, a small correction. The proc file system is not a memory file
system in any way. It is an abstraction of kernel control blocks,
presented as a file system to userland.
Second, if you just want to make sure /tmp is empty after every reboot, put
an entry in one of the startup scripts to
I've added a new presentation to the web site from SHARE 102. Harold
Pritchett has contributed his Configuring BIND session. For those that
don't know, BIND (Berkeley InterNet Daemon) is the software that provides
DNS services for most of the Internet.
The presentation is located at
41 matches
Mail list logo
