similar to: Server Crashing

> src: > devhelp-0.9.2-2.4.6.src.rpm > mozilla-1.7.10-1.4.1.centos4.src.rpm The mozilla src.rpm is there, but the devhelp one seems to be missing from the mirrors.... -- Matthew Miller mattdm at mattdm.org <http://www.mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/> Current office temperature: 76 degrees

Question about differences in RHEL 4.1 and CentOS 4.1 organization. Does CentOS follows same organization as RHEL? I don't see separate directory for 4.1 on Red Hat's ftp server (well, the public part of it, with SRPM packages), seems like all the updates were simply dumped into the 4.0 updates area, so basically doing normal system upgrade will bump all RHEL 4.0 systems to 4.1. On the

In short, the reason considering (and still only considering) turning it off is to make tripwire usable again (security vs. performance, I guess). Is it possible to completely turn it off system-wide? Any additional steps needed on the existing system (that already have half of the binaries prelinked)? What order of performance degradation to expect? If it is minor, nobody is going to cry

Does anyone know of any programs capable of fine tuning my screen display settings? I'm using the NVIDIA drivers, and everything is slightly blurry - regardless of how much (or little) I set anti-aliasing to.

Hi, I'm working on a RHSA tracking tool, named Sarah. It allows you to build a local RHSA database of different RHEL releases and then allows you to verify systems for compliance (and lists applicable RHSA and required packages). But before releasing my prototype, I would like to know what requirements people have. How they would be using such a tool and what for reports they need to

There seems to be some confusion over the way we release CentOS, and the release cycle. First, let's define what the upstream provider does. They released RHEL-2.1 (originally RHAS-2.1), RHEL-3 and RHEL-4. Those are specific and unique releases. They have the following Maintenance Phases: Phase 1: Full Support Start Date: General Availability End Date: 2.5 Years from General

- This avoids problematic "reloc'ed while mapped" messages and some associated corruption as well. Signed-off-by: Maarten Maathuis <madman2003 at gmail.com> --- src/gallium/drivers/nouveau/nouveau_screen.c | 21 +++++++++++++++++++++ src/gallium/drivers/nouveau/nouveau_screen.h | 3 +++ src/gallium/drivers/nouveau/nouveau_stateobj.h | 13 +++++++++++++

From: Greg Knaddison <greg.knaddison at gmail.com> > Look - brevity is the soul of wit. It also keeps other folks on lists > from calling you a troll. The problem is that then the same people then start complaining about my "oversimplification." In fact, that's part of the problem here. I really _tried_ to make a recommendation without breaking down into the

I am running Centos 4.2 x86_64. When I do "yum update", it shows these packages: ============================================================================ = Package Arch Version Repository Size ============================================================================ = Updating: compat-openldap i386 2.1.30-4 update

Has anyone else noticed that firefox is less stable after the recent security update? I'm getting several occurrences per day of "just goes poof," i.e. probably seg fault. -- Collins When I saw the Iraqi people voting three weeks ago, 8 million of them, it was the start of a new Arab world.... The Berlin Wall has fallen. - Lebanese Druze leader Walid

I've just spent at least half an hour swapping files, downloading things and stuffing around with memtest86 and memtest86+. I can't get either to start from pxelinux. Currently I have "memtest86" as the filename, and i'm trying to load it direct (not trying to use memdisk or anything). This just results in a near instant reboot. Am I doing something wrong? I can't

Dear Colleagues, memtest86 does not work any more after upgrading PXELINUX to 6.01. When trying to boot, I get the following message: PXELINUX 6.01 2013-07-04 Copyright (C) 1994-2013 H. Peter Anvin et al Loading memtest86... ok Booting kernel failed: invalid argument boot: The config is simple: DEFAULT memtest label memtest kernel memtest86 Any ideas? What additional information can I

Hello list, any try the new memtest86 v3.2 with isolinux 3.11 cd and pxeboot? How is the proper way to chainload memtest86 I was tried: label memtest kernel memtest.bin but, nothing happens just a weird hang (my older versions of memtest hangs too). Anyway chainloading in a floppy image with memdisk on CD or pxeboot was fine but if I use memory to emulate a floppy I was not using this memory

Hi! At first thanks for your great work! I started to make multiboot CDs 1,5 years ago, with Bart Lagerweij 's utils. I have a problem with the memtest86 floppy image, made by the authors in the .zip file, downloadable from it's homepage, when I use diskemu. Some days ago I found on Bart's page a new method to select boot images on CD with syslinux/isolinux/memdisk. I thought this is

Does anyone use tcp wrappers (hosts.allow/hosts.deny) anymore? And, would you care strongly if it went away (or would you just migrate to something else)? I bring this up because we are discussing dropping it from Fedora. This would be far enough in the future that it wouldn't impact RHEL 7, and therefore won't affect anyone here for Quite Some Time*, but here in the new world order of

Hello Matthew, On Thu, 27 Jul 2017 14:27:47 -0400 Matthew Miller <mattdm at mattdm.org> wrote: > On Thu, Jul 27, 2017 at 07:25:25PM +0200, wwp wrote: > > I've just got a Dell XPS 15 (9590) at work and need to set up a stable > > GNU/Linux system on it. I thought of CentOS7, but.. obviously its > > kernel can't run on this hardware. > > What sense of

i'm experimenting with some basic removable media mounting exercises for an upcoming class, and i read that, while you can use gconf-editor to change some of the mount options in cases like that, there is no way to override the mount options of nodev, noexec and nosuid. for example, that claim is made here (admittedly for fedora, but it appears to be true for centos as well):

Hi guys! I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 works fine both memtest 4.1 and 4.2. With version 6.00 no error message caught, only writes out dots. Any keypress does a reboot.With version 5.01 the error message is the follow:Loading images/memtest/memtest86... okBooting kernel failed: Bad file

Did you already try current Centos? If yes what was the problem? Why it did not work? On Thu, Jul 27, 2017 at 9:59 PM, Matthew Miller <mattdm at mattdm.org> wrote: > On Thu, Jul 27, 2017 at 08:38:14PM +0200, wwp wrote: > > Say, instead of stable, something not rawhide. But I'll examine all > > options that do work, so let's forget about "stable". > >

Hi! I am currently trying upgrade my bios pxe server with additional uefi support. My current using memtest86+ doesn't seem to support uefi, so I would have to use memtest86, as it supports this. But the memtest86 file itself is an *.efi file. When booting this one directly without syslinux, its working. But I want to launch it later from the syslinux menu. Can I chainload somehow another