search for: duhh

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.

...ried to simply turn off the has_journal bit using tune2fs: didn't help. (I'm willing to lose the info in the journal, as long as I can get the rest of my large f/s.) But tune2fs and friends gave me a chicken-and-egg error about the invalid arg wrt the journal, while trying to turn it off (duhh). At this point I've begun to suspect that there's something awfully wrong with the journal inode, and maybe, just maybe, my superblocks and group descriptors might be intact. Next, I tried to reinitialize the superblocks and group descriptors WITHOUT a journal (tell mke2fs to make a plai...

After hearing all the rave about Half-Life/Counter-Strike on Wine I decided to take the plunge myself... after rpm -e the default OLD wine packages from my RH7.2 install I installed wine20011004 graciously provided by http://www.linux-easy.com/daily/ ... setup my ~/.wine/config and got VERY UPSET when Half-Life install would even work... barfing the folloowing message! :( [msowka@mainframe

Hey Y'all, I just set up a new old machine on my network. I did a net install of CentOS 6.7 on it replacing an outdated copy of Win XP. Of course I'm now in the throws of configuring the machine to be a useful member of society. [mlapier at peach ~]$ nmap -sn 192.168.15.0/24 Starting Nmap 5.51 ( http://nmap.org ) at 2015-08-23 20:12 EDT Nmap scan report for 192.168.15.1 Host is up

This is mildly off topic since it has more to do with TCP/IP networking than with CentOS per se. However, at the risk of ruffling a few feathers I would like some advice on how to resolve the following routing problem: Given: dual homed host running CentOS-5.2 with eth0 = 2xx.yyy.zzz.23 eth1 = 192.168.219.1 and a Cisco gateway at 2xx.1xx.y7y.1 with the following networks: interface

I might add that there seems to be a subtle difference between using `...elt()` and `match.call()`, which is that the former causes `a` itself to be evaluated while the latter doesn't: ``` # Some approaches that have been suggested: # 1. Using `list()` (Bert Gunter) f1 <- function(...) list(...)[["a"]] # 2. Using `...elt()` (Bert Gunter) f2 <- function(...)