We went round on this before.
My suspicion is that they have (or had) one mirror with bad ISO images. Out of
the 12 images I downloaded, all using IE on the same machine, two were bad. I
didn't find out till I'd burned them, and couldn't mount them. I ended up
tossing out at least 4 CD's
I did mine using 256, and had no problem.
I did get several bad CD images from Novell though. We went around on that in
a previous thread.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Ferguson, Neale
Sent: Monday, December 06, 2004 2:22 PM
To: [EMAIL
]
Subject: Re: [LINUX-390] sles9 install
MP3000 mainframe in an 512MB Lpar
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Hall, Ken (IDS ECCS)
Sent: Tuesday, November 30, 2004 11:47 AM
To: [EMAIL PROTECTED]
Subject: Re: sles9 install
This sounds
We saw variations of this several times. Hanging of the 3270 CONSOLE usually
points to a dispatching problem with VM. We had other problems where the
console was responsive, but the network performance (including PING times) was
terrible. This was eventually identified and fixed by a driver
dasd_mod.ko in the
/lib/modules/2.6.5-7.97-s390/kernal/drivers/s390/block just in case
anyone is interested.
Thanks
Zoltan
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Hall, Ken (IDS ECCS)
Sent: Monday, November 29, 2004 9:17 AM
To: [EMAIL
The s390x version is true 64 bit. It needs a processor capable of supporting
that.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
Behalf Of Tom
Duerbusch
Sent: Tuesday, November 30, 2004 2:50 PM
To: [EMAIL PROTECTED]
Subject: [LINUX-390] Which Suse 9.0 CD?
You shouldn't really have to do anything special if you use the built-in
install scripts and yast.
The default install process seems to set nearly everything up properly. One
thing it could do better is tell you when you need to reboot. Once, I thought
yast had just died, but it ended
I got fairly far along last night, without trouble. It's just SLOW on my setup.
The ramdisk is 64 mb., as defined in the PARMFILE, and my storage is defined at
256mb.
I was using the NFS install, but it may have died near the end due to a network
error with the emulated CTC. I'll take a
Interesting. I got a good copy of CD5 on the first try, CD1 on the second, but
it took 4 tries to get a good version of CD2. The first 3 copies of CD2 had
the same checksum, but bad. All of the S390x images were fine though. It
almost looks like they've got a mirror with a couple of
:[EMAIL PROTECTED] Behalf Of
Adam Thornton
Sent: Tuesday, November 23, 2004 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] SLES9 Evaulation Download - ISO problems?
On Nov 23, 2004, at 7:00 AM, Hall, Ken (IDS ECCS) wrote:
Started to install under Hercules last night
AM, Hall, Ken (IDS ECCS) wrote:
Do you mean tape marks between files are needed? Or shouldn't be
there?
Should not be there in 3.0 and later versions of Hercules; Hercules
changed tape handling in 3.0.
I moved the boot files over from the CD under Linux, but still got
either full
Did anyone else have trouble with the ISO images? Specifically, discs 1
and 2 from the S390 set. It took me two tries to get disc 1 and four
tries to get disk 2, before the MD5SUMs matched.
I could buy a random corruption, but the first 3 tries for disc 2 showed
the same (bad) checksum.
The actual ISO files are labeled RC5. Is this the latest version, or
something behind? Has the actual GA version been released yet?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Post, Mark K
Sent: Thursday, November 18, 2004 12:15 PM
To: [EMAIL
.
-Cameron
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Hall, Ken (IDS ECCS)
Sent: Thursday, November 18, 2004 10:23
To: [EMAIL PROTECTED]
Subject: Re: SLES9 Evaulation Download
The actual ISO files are labeled RC5. Is this the latest
version
received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Hall, Ken (IDS ECCS)
Sent: Thursday, November 18, 2004 09:23
, Ken (IDS ECCS) wrote:
The actual ISO files are labeled RC5. Is this the latest
version, or
something behind? Has the actual GA version been released yet?
RC5 is the one and only GA version. ;-)
--
Joerg Reuter
http://yaina.de/jreuter
And I make
I asked SuSE about this long ago, after I had similar trouble. Apparently they
couldn't get it to work either, so they don't support it.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Terry Spaulding
Sent: Wednesday, October 20, 2004 1:50 PM
To:
The files end up in subdirectories under /usr/src/packages. The Source tarball will
be in SOURCES there, and the spec file in SPECS.
You can do rpm -bp on the spec file to uppack and patch the source tree into the BUILD
directory.
-Original Message-
From: Linux on 390 Port
John's motto, going all the way back to high school:
John Campbell, spelled like on the can: S - O - U - P
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Lucius, Leland
Sent: Thursday, May 13, 2004 11:16 AM
To: [EMAIL PROTECTED]
Subject: Re:
It worked for us pretty much as advertised.
Have you tried issuing the signal with the console logged on so you can watch the
messages?
Or use a program like track.
You should get a message from the kernel that the signal was caught even if the script
doesn't run:
09:06:05 CAD: Sending
SHUTDOWN, these notes will aim them in the right direction.
Nick
Hall, Ken (IDS ECCS) wrote:
Mine (working) is:
ca:12345:ctrlaltdel:/sbin/shutdown -y -g0
Should work either way though.
-Original Message-
From: Post, Mark K
Sent: Tuesday, April 27, 2004 2:14 PM
We're running 2.2.8a on several servers and I've never seen this.
What we HAVE seen is that if the server loses contact with the LDAP server that
contains the user/UID mappings, often the smbd processes hang. I'm not sure if the
problem is in smbd, nscd, or
nss_ldap.
In any case, Windows
A couple of scripts have been posted to automatically take care of this. If nobody
else has the short one handy, I'll try to find mine.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Betsie Spann
Sent: Thursday, April 22, 2004 12:39 PM
To: [EMAIL
Right. The script I wrote, which is a little less elegant, uses /proc/dasd/devices,
and builds nodes for only active devices.
# $Id: dasdnode,v 1.1 2003/05/19 17:36:03 root Exp $
grep active /proc/dasd/devices | while read DASDENT ; do
DEV=${DASDENT:27:6}
if [ ! -b /dev/$DEV -a ${DEV:0:4} =
Uou also need to get the heirarchy in the PAM files just right, so it passes local
accounts, and sends others to LDAP properly.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Post, Mark K
Sent: Wednesday, April 21, 2004 11:19 AM
To: [EMAIL PROTECTED]
I tried Bastille from SLES8 some time ago, and it didn't work. I opened a problem
with SUSE, and here's the response I got:
As part of our evaluation of SLES8 as an internet-facing platform, I attempted
to run the RPM-provided bastille against our standard-build server.
[..]
Unfortunately,
Linux on zSeries is too wordy. We need a shorter version, such as Lonz, Linonz,
or some such.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
Behalf Of Jim
Elliott
Sent: Tuesday, April 13, 2004 9:59 AM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390]
] Interesting article on zLinux on groklaw
On Tuesday, 04/13/2004 at 10:10 AST, Hall, Ken (IDS ECCS)
[EMAIL PROTECTED] wrote:
Linux on zSeries is too wordy. We need a shorter version, such as
Lonz,
Linonz, or some such.
The problem with trying to build an abbreviation is that it doesn't
Never heard of nrpep, but I got nrpe working. What's the problem?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Ranga Nathan
Sent: Monday, April 05, 2004 9:44 PM
To: [EMAIL PROTECTED]
Subject: [LINUX-390] Nagios plug-in nrpep
Has anyone got nrpep
referenced is applicable, and has fixed the
problems many people
on this list have had with SLES8, since it acted differently
than previous
SUSE platforms.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Hall,
Ken (IDS ECCS)
Sent: Thursday
on this list have had with SLES8, since it acted differently
than previous
SUSE platforms.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Hall,
Ken (IDS ECCS)
Sent: Thursday, April 01, 2004 4:18 PM
To: [EMAIL PROTECTED]
Subject: Re: new
: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Hall,
Ken (IDS ECCS)
Sent: Friday, April 02, 2004 8:20 AM
To: [EMAIL PROTECTED]
Subject: Re: new disk for linux
The kernel modules (dasd_mod.o and dasd_eckd_mod) are in the
initrd, but the
DASD parm is picked up from the BOOT
I think that applies to both of us. :)
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Post, Mark K
Sent: Friday, April 02, 2004 12:08 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] new disk for linux (CORRECTION)
I think I'm getting my
Using the modular driver for the disk makes sense on Intel, where there are so many
possible variations, but why bother for Z? How many different disk devices do we
have? Two? (ECKD, and FBA)
Seems like a pointless complication, even if it's hidden from most users.
-Original
?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Adam Thornton
Sent: Friday, April 02, 2004 1:15 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] new disk for linux (CORRECTION)
On Fri, 2004-04-02 at 11:37, Hall, Ken (IDS ECCS) wrote:
Using
I think you added the device to the wrong file. I usually add it to /etc/zipl.conf,
then run zipl. I believe zipl copies zipl.conf to the /boot files (among other
things).
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Scorch Burnet
Sent: Thursday,
about how to update that.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Hall,
Ken (IDS ECCS)
Sent: Thursday, April 01, 2004 3:47 PM
To: [EMAIL PROTECTED]
Subject: Re: new disk for linux
I think you added the device to the wrong file
scp -q -i ~ken/.identity -B file remote:file
What's so hard? FTP may be the lowest common denominator, but it's not the only
solution.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
David Boyes
Sent: Tuesday, March 23, 2004 8:53 PM
To: [EMAIL
in your z/OS and
CMS servers?
/Thomas Kern
/301-903-2211
-Original Message-
From: Hall, Ken (IDS ECCS) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 08:08
To: [EMAIL PROTECTED]
Subject: Re: NJE functionality using a linux server?
scp -q -i ~ken/.identity -B file
Does this mean OpenSSL and OpenSSH will build under USS? I had mixed results trying
to build Open Source products there, it's not exactly a high-profile platform.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Michael MacIsaac
Sent: Wednesday, March
/dev/vg1/usr /usr reiserfs noatime,nodiratime1 2
This is for a reiser filesystem, obviously. YMMV.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Dave MYERS
Sent: Wednesday, March 24, 2004 9:13 AM
To: [EMAIL PROTECTED]
I came into the discussion a little late, so I had to read back to find out exactly
what the problem was. You're right, but it seems like adding scp (or even rcp)
capability to USS/zOS would make
more sense than trying to back-port something like NJE to Linux just for yet another
file transfer
Fragile: All the more reason for IBM to come up with an official version.
I only suggested site submit and lpr/lpd as stopgap substitutes for the
functionality. For printing, I can see MANY better alternatives than an NJE
variation. There's no point to sending the
report to a Linux system
I know, but that world is disappearing fast, and IBM seems to be adapting everywhere
else. I agree with you, it's long past time the printing mess should be cleaned up,
and zOS and zVM should join
the rest of the world.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL
True. I was thinking the same thing. It isn't hard to wrap the hard stuff to hide
the details.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Alan Cox
Sent: Wednesday, March 24, 2004 11:03 AM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] NJE
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
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
I used to do the add device, but I found it's only necessary if the device isn't in
the range specified in zipl.conf at boot time. If it's predefined, you get some
messages on the console, and the
device magically appears.
The steps you need to do are:
1) Create the minidisk and attach to the
[mailto:[EMAIL PROTECTED] Behalf Of
Nick Laflamme
Sent: Thursday, March 11, 2004 12:06 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] Dynamically adding minidisks
Summary: things are changing, but I can't tell if it's
progress or not.
Hall, Ken (IDS ECCS) wrote:
I used to do the add device
-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Nick Laflamme
Sent: Thursday, March 11, 2004 12:06 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] Dynamically adding minidisks
Summary: things are changing, but I can't tell if it's
progress or not.
Hall, Ken (IDS ECCS) wrote
Reiser filesystems can be extended while mounted (online), but can only be shrunk
while unmounted.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
Behalf Of Rob
van der Heij
Sent: Thursday, March 11, 2004 4:11 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390]
You need:
fdasd /dev/dasd${i}
Between the dasdfmt and pvcreate to create the partition.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Carlos Palmarante
Sent: Friday, March 05, 2004 1:49 PM
To: [EMAIL PROTECTED]
Subject: [LINUX-390] pvcreate
hi
Many of these products spray files over lots of directories, not just /usr. The lowly
nss_ldap, for example, puts it's shared library in /lib, but puts a symlink in
/usr/lib. Doc files go in the
usual places, and there are manual pages, etc. When I first started making RPM's, I
used to miss
You can also easily customize tripwire to ignore files you KNOW are going to change.
Simplifies the process of weeding through the list.
Also catches those cases where make install fiddles with config files.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf
Yes, we confirmed this some time ago. The number of stripes HAS to equal the number
of physical volumes in the LV.
You can have a VG of, say, 10 PV's, with two striped LV's, 5 and 5 (both 5 stripes) or
6 and 4 (6 and 4 stripes), but if you want all 10 PV's in one LV, it has to be 10
stripes.
I found tripwire to be useful in identifying added files when creating or updating
complex RPM's. Run it before doing make/make install, and again after, and you get a
list of files added and
changed.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
The idea behind RPM is that you wrap the configure/make process with an RPM spec file,
and let RPM do it, then package up the resulting files. Of course, making the spec
file is a project in itself.
If you know all of the files that make up your package, you COULD make a skeleton spec
file
Right, you can use nodeps to force an install, but if the original packages are
dependent on things like specific level shared libraries, you might find they don't
work quite right after.
You could have done rpm --erase --nodeps to remove mysql without removing the
dependent packages.
You
-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Hall,
Ken (IDS ECCS)
Sent: Wednesday, February 18, 2004 9:47 AM
To: [EMAIL PROTECTED]
Subject: Re: RPM question
-snip-
You could also take the spec file from the old version of
mysql and use it
to build a new package
There's a show stopper...
Why would it not fill the track?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
Behalf Of Jim
Sibley
Sent: Wednesday, February 18, 2004 12:03 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] dasdfmt with a 1K block size - still not
Well, anyway, the original intent was to reclaim some of the space lost to file
tails by using a smaller blocksize, but it sounds like we'd lose more than we'd gain.
Mike was asking about this on our behalf. We had noticed that we weren't getting as
much space using ext3 as we had with reiser.
Unfortunately, we needed a quicker solution. We've been working on and off for about
a year trying to get fcp working with no luck. (The problems have all been on the
hardware side.)
The info about block sizes, etc. couldn't have come at a better time. We just had a
meeting to discuss how
Like I said, the problems have all been on the hardware side. The guys who manage it
haven't been able to get the port names, etc. properly defined so we can see them.
Our attempts have been
intermittent with long delays in between due to other priorities.
So by hardware, I guess I actually
I had to add the ctrlaltdel line to /etc/inittab. I also made a modification to the
/etc/init.d/halt script to issue hcp logoff at the end. For some reason, the
options in zipl.conf caused me
problems, but I forget exactly why.
-Original Message-
From: Linux on 390 Port
Here's the response I got from Suse on my question about Bastille:
many thanks for your enquiry to SuSE S/390 support.
You wrote:
As part of our evaluation of SLES8 as an internet-facing platform, I attempted
to run the RPM-provided bastille against our standard-build server.
[..]
I tried the Bastille RPM that came with SLES8, and it flat didn't work. When I opened
an issue with Suse for it, they told me it wasn't supported. I didn't bother to ask
why they included the RPM at
all.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
This came in yesterday under our Maintenance agreement. You need a maintenance code
to download the RPM.
Title: Optional package to convert to EAL3+ certified system
http://sdb.suse.de/en/psdb/html/5e43d0905ffbbf40e12ee5695e44c495.html
Looks like you haven't created the partition:
fdasd -a /dev/dasdd
dasdd is the whole disk
dasdd1 is the first partition created by fdasd. dasdd2 would be the second, but
supposedly that doesn't work.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
Behalf Of
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Hall, Ken (IDS ECCS)
Sent: Monday, January 26, 2004 12:31 PM
To: [EMAIL PROTECTED]
Subject: Re: adding DASD in SuSE8
Looks like you haven't created the partition:
fdasd -a /dev/dasdd
dasdd
I'm monitoring disk space remotely using a script that calls getsnmp, but that's only
because check_snmp couldn't do what I needed. There's no reason you shouldn't be able
to retrieve any MIB element
as long as you know the OID and format. I picked up a MIB browser called getif
that's been
- CPU and Memory monitoring?
MIB? (Men In Black?) . OID element? Sorry, could you expand?
I got the Corotona 2 from Parallelgraphics.com. Nice to see that the
download installs for both IE and Mozilla.
Hall, Ken (IDS ECCS) [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED
It's not that hard to manage large numbers of devices.
We have Samba servers that are 64 physical volumes. 6 for the system, and two LVM
volumes of 28 3390-9 disks for a total of 2x204 gb. We decided on two filesystems
instead of one big one in case one
gets corrupted. We can restore the bad
Linux lnx26t 2.6.0 #4 SMP Fri Jan 2 13:54:46 EST 2004 s390 unknown
lnx26t:~ #
Progress is made. There's no LVM, and I can't figure out how to get the network
devices connected. (Something to do with sysfs and dynamic enabling that isn't very
well documented.)
I'll keep at it though.
That did it (with variations, since I'm using hipersocket guest LAN).
Much appreciated.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Ferguson, Neale
Sent: Monday, January 05, 2004 1:22 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] 2.6 kernel on
Modprobe made my 2.6 kernel oops. I'm sure I used it successfully at least once, but
when I tried to use it to install ccwgroup/qdio/qeth_mod, I got a nasty oops and hang.
Insmod works fine though.
Anyone know what happened to the HZ_TIMER option? It seems to have gone away.
-Original
It shouldn't be needed. When we ran into this, it didn't do any damage, we just ended
up with the same filesystem mounted in two places.
The usual cause of the problem is a device missing from the configuration. LVM won't
activate an incomplete VG, but instead of giving an error, it mounts
That's exactly what we saw. You shouldn't have to do anything.
Most likely a physical volume is missing from the inactive VG. If you can get all
volumes properly online, the next time the system boots, it should be back to normal.
Another possibility is that one physical volume in the VG has
I wonder how this will work with Levanta, which uses a common copy of the code for
multiple servers. Only configuration files and data are unique to each instance.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Thomas David Rivers
Sent: Tuesday,
Did you run quotacheck on that filesystem?
The sequence is:
1) Add usrquota option to fstab
2) Run quotacheck to create the quota file
3) Run quotaon to enable quotas.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Alikhani
Sent: Sunday, December 14, 2003
We just saw a presentation from IBM along these lines. Try contacting Len Santalucia
at IBM in New York.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
Behalf Of Ann
Smith
Sent: Friday, December 12, 2003 3:55 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390]
Is this SuSE SLES8? tcpdump is broken there, you need the fix from SP3.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Cornelia Huck
Sent: Wednesday, December 10, 2003 1:04 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] tcpdump question
Your
Still looks like the same problem. I can't find my notes on it, but it was an
incompatibility between tcpdump and the network driver for 2.4.19. It was fixed in
the SuSE SP3 version of tcpdump.
IBM had given us a circumvention. If you post-process the trace like this, it works.
(Assuming
In the SLES7 2.4.7 kernel, the timer patch added an option called (IIRC) hz_timer
to the kernel that could be enabled at kernel build time. SuSE supplied two different
kernels, one with the
feature enabled, the other disabled.
The patch was enhanced somewhere between 2.4.7 and 2.4.19 (SLES8)
, it can lock your guest during very long i/o's.
I've heard of it happening with the creation of large tars.
with us, it was
running verifies against a 70gig database.
-Original Message-
From: Hall, Ken (IDS ECCS) [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 10:45 AM
This is a fairly complicated question. Openldap 2.1 on SLES8 added a number of
wrinkles to this. Assuming the list isn't interested in a lot of back-and-forth on
this, email me privately with info
on exactly what you're seeing and I'll try to help.
-Original Message-
From: Linux on
I don't think I'd want to depend on a zLinux system under VM as a stable time source.
I seem to recall that Linux only sets the software clock to match VM at boot time, and
occasionally misses clock
interrupts (especially at high load), causing the software clock to drift over time.
I know
, November 20, 2003 7:57 AM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] SuSE SLES8 SP3 ISO images
Other than downloading all the files individually is there
another way to
get SP3 ?.
Regards
Gerard
-Original Message-
From: Hall, Ken (IDS ECCS) [mailto:[EMAIL PROTECTED]
Sent
Yes, SuSE puts installed source RPM's in /usr/src/packages. The spec goes into SPECS,
all source elements, including tarballs and patches go into SOURCES.
If you run a build against a spec, the tarball is unpacked in BUILD, and if you build
an RPM, the actual rpm files go into RPMS/${ARCH}
For those of you with SuSE maintenance contracts, the SP3 ISO images are available
from their support site:
http://sdb.suse.de/en/psdb/html/ef83f958af36a92fda2298ec03e3c87b.html
And there was great rejoicing.
(Yaaayyy!)
Many congratulations!
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
David Boyes
Sent: Tuesday, November 18, 2003 2:33 PM
To: [EMAIL PROTECTED]
Subject: [LINUX-390] OT: New doctor in the house...8-)
(This
It's in the cpint package. I know there's one in SLES8, but I vaguely recall having
to hunt for it in SLES7.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Eric Sammons
Sent: Monday, November 17, 2003 1:35 PM
To: [EMAIL PROTECTED]
Subject:
, 2003 2:55 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] Error message using Hummingbird Exceed V9 to
ssh to SuSE SLES8 on zSeries. new install
On Thu, 2003-11-13 at 20:22, Hall, Ken (IDS ECCS) wrote:
That's the point: To get an xterm session. Hummingbird
uses ssh/rsh/telnet
using Hummingbird Exceed V9 to
ssh to SuSE SLES8 on zSeries. new install
On Thu, 2003-11-13 at 13:22, Hall, Ken (IDS ECCS) wrote:
I almost always use xterm instead of straight ssh. The
terminal emulation is better supported, so curses-driven
stuff works as it should. That isn't
I've already sent them a note asking about this. IBM couldn't find ISO's either.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Little, Chris
Sent: Wednesday, November 12, 2003 2:04 PM
To: [EMAIL PROTECTED]
Subject: [LINUX-390] sles8 sp3 iso's?
Try:
http://sdb.suse.de/download/s390/update/SuSE-SLES/8/sources/
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Daniel Jarboe
Sent: Wednesday, November 12, 2003 4:18 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] sles8 sp3 iso's?
does anyone
A number of years ago I worked on a project that involved donating computers and
software to police departments, so we had a lot of press coverage.
The computer was an old mini that was one of the first ones without a front panel.
Just a plain beige metal box with a couple of big clunky disk
Okay, now add a slave display from the Service Element to the front door, and put up a
cool screensaver, such as [EMAIL PROTECTED], and you've got something.
Besides, it would give the operator/technician something to look at when things go
wrong, so he doesn't have to open the back door.
Unfortunately, Bastille doesn't seem to work on SLES7 or SLES8. A couple of IBM Linux
specialists told me they were able to get some version of it working, but the RPM's
seem to be useless.
One product I've used successfully in the past is Portsentry from Psionic, which
monitors unused ports
Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Hall,
Ken (IDS ECCS)
Sent: Tuesday, October 28, 2003 3:06 PM
To: [EMAIL PROTECTED]
Subject: Re: Memory access faults.
Recovery is only as good as the language framework allows it to be.
Compilers insulate you from
I agree completely, but I come from an Assembler background where you HAD to sanity
check EVERYTHING. The volume of buffer overflow issues in C programs boggles my
mind. Even after I started
coding in C, I still maintained a similar level of paranoia regarding input
validation. It's not like
1 - 100 of 174 matches
Mail list logo
