89 4288363 8251 267872 1146073
22996 140662 0 18601904
proc4 2 0 0
proc4ops 59 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Thanks for your time,
-Wayne Betts
STAR Computing Support at BNL
Physics Dept., Bldg. 510
P
STAR's RACF nodes use the SL-built packages of TUV's preview release of
gcc-4.3, not a locally built version.
If you have an account on the farm and can get on an ATLAS interactive
node, it should be easy enough to check: "rpm -qi gcc43" should reveal
the answer, right?
-Wayne Betts
STAR Computing Support at BNL
use and kernel modules
for the various kernel errata levels above 2.16.18-128-*?
-Wayne Betts
STAR Computing Support at BNL
A colleague here is trying to build a 64-bit network boot image, but he
is creating it on a 32-bit host. We can't figure out how to make yum
grab the 64-bit packages in this case.
Any idea what we can do to force yum to grab 64-bit packages while
running on a 32-bit host? We tried specifying the
Troy,
Thank you for looking into this. I noticed this while upgrading
somebody else's desktop - it had SL4.4 with both k3b and k3b-mp3
installed, and the update to 4.8 went fine except for this small bump,
which I got over by uninstalling k3b-mp3. Afterwards I tried to
re-install k3b-mp3, naivel
Jon Peatfield wrote:
On Fri, 22 Aug 2008, Wayne Betts wrote:
Hi Wayne,
This is not an oops, it is on purpose.
From the README in that directory
"These versions of openssh have been patched to be able to use
both the old and the new versions of gssapi. This allows them
to do ker
Troy Dawson wrote:
Wayne Betts wrote:
I inadvertently had sl-contrib enabled on an SL4.6 system and this
morning it updated openssh,
openssh-server, etc, getting them from sl-contrib. For instance:
openssh-server-3.9p1-22.SL.4.22.i386
According to the changelog, the changes appear to only
I inadvertently had sl-contrib enabled on an SL4.6 system and this morning it updated openssh,
openssh-server, etc, getting them from sl-contrib. For instance:
openssh-server-3.9p1-22.SL.4.22.i386
According to the changelog, the changes appear to only include some bug fixes compared to the
"s
In the distant past, I used to add several ACCEPT rules for afs in
ipchains or iptables when using openafs clients. But somewhere in time
I stopped doing this (not conciously -- it just slipped my mind when
making my checklist at some point), yet I've never noticed a problem
while using the de
-- selinux seems to add unintuitive complexity for all but the die hard
admins that will likely cause much grief in exchange for few if any
"saves", but over time the balance will shift in its favor as more
people become comfortable with it. If someone has an anecdote of how
selinux saved the day at some point, please share it!
-Wayne Betts
It strikes me as highly unlikely that I'm the only one to encounter
this... Or has everyone else decided that SELinux just isn't worth the
effort and disabled it? :-(
Fwiw, I have initscripts-7.93.25.EL-1 (i386) on both systems.
-Wayne Betts
Brookhaven National Lab
Wayne Betts w
this one system.
SELinux, syslogd and utmp are all pretty much core pieces of the Linux
puzzle, so I'd hope they would get along naturally without any
intervention from me...
-Wayne Betts
Brookhaven National Lab
12 matches
Mail list logo
