similar to: SOLVED - Can't build CentOS 5.1 kernel from source

I pulled down the kernel-2.6.18-53.el5.src.rpm source to build my usual custom kernel (adds NTFS wwrite support) and it does not build. Whether I include the NTFS or just build from the source with no changes (other than make oldconfig and adding the # x86_64 line), I get this error every time: Building modules, stage 2. + mkdir -p /var/tmp/kernel-2.6.18-53.el5.nx-root/usr/lib/debug/boot +

On Mon, May 12, 2008 at 4:47 PM, MHR <mhullrich at gmail.com> wrote: > On Mon, May 12, 2008 at 4:35 PM, Scott Silva <ssilva at sgvwater.com> wrote: > > on 5-12-2008 10:17 AM MHR spake the following: > > > > > It might not have finished the install, and something made it reboot before > > it had written the grub records. > > > > I figure

Yesterday I found a need to have the NTFS module support in my CentOS 5.0 at home, so I happily installed the 8.1.4 source, prepped it (after deleting the rhel and olpc lines per Johnny's notice earlier in this list), made the config with a ".nx" version name using make menuconfig (copying the config from the SOURCES directory, editing it to include the # x86_64 line and copying it

I've posted this question to the Gnome users list, but so far no luck, so I thought I'd mention this here. A little while ago, I noticed that I was no longer able to log out from my GDM. I'm running the default GDM (2.16) that comes with CentOS, and this problem started up right about the same time that I updated to the 53.1.4 kernel (from the 8.1.15 version). As I've posted

On Mon, Aug 25, 2008 at 11:33 AM, MHR <mhullrich at gmail.com> wrote: > Is there a setting somewhere in the "global" arena of CentOS that > controls whether or not "hidden" (.prefixed) files are displayed in > file lists? > Never mind - apparently if you right-click in the file list and select "show hidden files", it sticks system-wide. mhr

On Mon, Nov 10, 2008 at 4:32 PM, MHR <mhullrich at gmail.com> wrote: > On Mon, Nov 10, 2008 at 12:58 PM, Lanny Marcus <lmmailinglists at gmail.com> wrote: <snip> >> Question: Is /hda3 mounted properly? I don't think so, because when I >> try to boot Linux from the Grub menu on the HD, it gives me "Error 17: >> Cannot mount selected partition"

On my x86_64, I pulled down the source for the 2.6.18-92.1.13 kernel and followed the wiki faithfully, but it will not build. I'm getting errors in the Buslogic driver: In file included from drivers/scsi/BusLogic.c:56: drivers/scsi/BusLogic.h:241: error: redeclaration of enumerator 'false' include/linux/stddef.h:16: error: previous definition of 'false' was here

I got half way through an installation of CentOS on a box that has Window$ 98 in the first partition and Window$ XP in the second, where CentOS was designated for partitions 3 (/boot - 128MB) and 4 (/) and had some strange results. During the install, I changed the default OS to boot to Window$ (because I rarely use this machine, but others who don't have a clue use Wxx), but then while the

According to the man pages for sem_wait, etc., POSIX semaphores are available in Linux 2.6 (with the right NTPL threading in glibc). However, I have a program that compiles just fine but won't link because it can't find the library for the semaphore operations. What am I missing? I ran a find and grep through all the libc's on the system and they turned up nothing: $ find /lib

On top of my previously (just now) difficulties with yum, now I find that the 53.1.6 kernel is not installing properly. When I run "yum update" to install it, the install hangs here: Dependencies Resolved ============================================================================= Package Arch Version Repository Size

I installed the kernel-2.6.18-8.el5.src.rpm today and went to build it, but it fails with this error: $ rpmbuild -bp --target=`uname -m` kernel-2.6.spec Building target platforms: x86_64 Building for target x86_64 error: Failed build dependencies: unifdef is needed by kernel-2.6.18-8.el5.x86_64 I double checked and this appears to be the latest kernel source rpm on centos/5.0/os/SRPMS.

What does this mean: WARNING: "autofs_kill_sb" [fs/autofs/autofs.ko] undefined! WARNING: /var/tmp/kernel-2.6.18-8.1.6.el5.nx-root/lib/modules/2.6.18-8.1.6.el5.nx/kernel/fs/autofs/autofs.ko needs unknown symbol autofs_kill_sb It causes a similar warning when I install the kernel. The only change I made when I built this kernel was to add NTFS support (need it for various reasons,

I just had a strange occurrence. I was printing out some PDFs and I pulled one down off the web (my wireless bill) and tried to print page 1. My browser properly fired up AR9, but nothing printed. I tried agian, still nothing. I saved the file, opened it with the Document Viewer and it can't print the file either. I tried opening it with GIMP, and it gets this error: Opening

>---------- Forwarded message ---------- >From: Nicola Buso <nicola.buso at gmail.com> >Date: Aug 29, 2007 3:26 PM >Subject: Re: Nautilus does not open files with the correct app >To: Mark Hull-Richter <mhullrich at gmail.com> > >I had similar problem with nautilus opening pdf documents from root and not from a normal >user (showing a message saying that for

Did something change since (at least) CentOS 5.1, kernel 2.6.18-53.1.4 that would affect the CUPS printing system? I am no longer able to connect to it and that seems to be impacting my ability to use the newest unreleased beta version of SeaMonkey. (My standard release SeaMonkey, 1.1.8, works just fine, but I think that using CUPS is new in the 2.0 beta.) Any constructive input appreciated.

This is probably a dumb question, but I'll ask anyway (I do that - you all know... :-). Due to a bug I found in OOo 2.0, I moved to using OOo 2.3, back when I was still running CentOS 5.0. Now that I have upgraded to 5.1, yum wants to update my OOo from 2.3 BACK to 2.0. Is it possible to get yum to recognize that 2.3 is newer than 2.0, or should I just exclude OOo from the updates? Thanks.

In-Reply-To: <f4e013870805211022r36194b29gb74ca4421dc2ee77 at mail.gmail.com> On: Wed, 21 May 2008 10:22:19 -0700, MHR <mhullrich at gmail.com> wrote: >> On Wed, May 21, 2008 at 8:37 AM, James B. Byrne <byrnejb at harte-lyne.ca> >> wrote: >> >> This indeed turned out to be an SELinux policy problem which I have since >> resolved. > > Whoa,

On Fri, Aug 22, 2008 at 8:00 PM, Lanny Marcus <lmmailinglists at gmail.com> wrote: > On Fri, Aug 22, 2008 at 6:49 PM, Lanny Marcus <lmmailinglists at gmail.com> wrote: >> On Fri, Aug 22, 2008 at 3:48 PM, MHR <mhullrich at gmail.com> wrote: >>> On Fri, Aug 22, 2008 at 11:22 AM, Lanny Marcus <lmmailinglists at gmail.com> wrote: >>>> The version

For some reason, when I try to print any graphic PDF (or a PS file made from said graphic), it kills my Minolta 1100 laser printer, and I have to cancel the job, disable the printer and turn the printer off and on as many times as it takes to clear its buffer of the trash. I'm running CentOS 5.0 and have tried Adobe Acrobat Reader 7.0 for Linux; I have also tried printing the pdf to a file

]# yum update Loading "priorities" plugin Loading "fastestmirror" plugin Loading mirror speeds from cached hostfile * base: mirror.hmc.edu * updates: mirrors.versaweb.com * kbs-CentOS-Extras: centos.karan.org * extras: centos-distro.cavecreek.net Excluding Packages in global exclude list Finished Excluding Packages from CentOS-5 - Base Finished Excluding Packages from