Discuss

discuss@lists.centos.org

34753 discussions

CentOS 5 on an MSI Wind U100 Netbook && RTL8187 wireless card configuration
by Niki Kovacs 12 Sep '08

12 Sep '08

Hi, I recently purchased an MSI Wind Netbook, just slightly bigger than an EeePC, and IMHO just one step above the mere toy category. It's got a 10" monitor, 80 GB SATA HD, and the keyboard is just big enough so I can type with ten fingers (with a little exercise). The thing came preinstalled with Windows XP, and I've spent the last two days figuring out how I could possibly install my favourite OS on it. Among the many hairy details: 1) there's no CDROM nor floppy, only USB, and 2) the NIC is an RTL8101, not handled by the install kernel (nor the normal CentOS kernel). There were several Catch22's, but here's how I went about it. I published my detailed install notes (in French, but the Linux bits are universal :oD), since it seems to be a quite popular bit of hardware: http://www.microlinux.fr/article.php3?id_article=47 There's one exception though: the wireless card is a Realtek RTL8187 (which lspci lists as RTL8199 Unknown device). I must have tried about ten different drivers out there, none of them worked (MSI only published precompiled kernel modules for SuSE Linux Enterprise 10, go figure). The ndiswrapper solution didn't work either: the Windows driver loaded OK, but no signal. I tried the dkms-rtl818x driver from RPMForge, but to no avail. Any suggestions on this piece of hardware? Cheers, Niki

1 0

cfengine and crontab
by Ric Moore 12 Sep '08

12 Sep '08

The docs to installing cfengine refers to /var/spool/cron/crontabs/root That doesn't exist. Nor does /etc/crontab. Heck I remember that from the "old days", now there are lots of cron entries, in /etc but no crontab. Not installed by default. So, I'm hunting that one down. Nate, what did you wind up doing?? Ric -- ---------------------------------------------------- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. Linux user# 44256 Sign up at: http://counter.li.org/ https://nuoar.dev.java.net/ Verizon Cell # 336-254-1339

5 10

My turn at building a custom kernel for IPsec BEET mode
by Robert Moskowitz 12 Sep '08

12 Sep '08

Well I am working on building a kernel that will have the IPsec BEET mode patch available from infrahip.hiit.fi. I have some decent help, but really no one there is a seasoned Centos kernel builder (though they work with different FC kernels), and now they are mostly done for the day. I have been following the wiki on building a custom kernel, got my patch in ~/rpmbuild/SOURCES and away with the rpmbuild. That failed on line 69: Unknown tag: % define buildid .hipl0809111 But the comments say to set the define to something like ".local" or ".bz123456" So why the failure? Too long our are the quotes required? If this works, I would like to see this patch 'mainstreamed' as it is in the 2.6.27 kernel....

4 5

Alarming (?) smartd reports
by MHR 11 Sep '08

11 Sep '08

I decided, after the last discussion of smartd and S.M.A.R.T. disks, to take a look in my /var/log/messages, and I'm seeing fair bit of this: Sep 10 20:11:23 mhrichter smartd[3361]: Device: /dev/sda, 4294967295 Offline uncorrectable sectors Sep 10 20:41:23 mhrichter smartd[3361]: Device: /dev/hdb, 21 Currently unreadable (pending) sectors Sep 10 20:41:24 mhrichter smartd[3361]: Device: /dev/sda, 4294967295 Currently unreadable (pending) sectors Sep 10 20:41:24 mhrichter smartd[3361]: Device: /dev/sda, 4294967295 Offline uncorrectable sectors Sep 10 21:11:23 mhrichter smartd[3361]: Device: /dev/hdb, 21 Currently unreadable (pending) sectors Sep 10 21:11:23 mhrichter smartd[3361]: Device: /dev/sda, 4294967295 Currently unreadable (pending) sectors Sep 10 21:11:23 mhrichter smartd[3361]: Device: /dev/sda, 4294967295 Offline uncorrectable sectors Clearly there is a minor problem on /dev/hdb, which doesn't really surprise me, nor is it particularly worrisome (because I don't use that drive much). However, the other one I find more than a little curious. /dev/sda is a Seagate 300GB SATA drive that's coming up on two years old next month, but the number of "Currently unreadable (pending) sectors" or "Offline uncorrectable sectors," depending on which one you believe, is interesting - 4294967295 is FFFFFFFF in hex, and I'm running a 64-bit machine. Google is not particularly informative on this subject - anyone know more than general suggestions about dd, badblocks, etc.? This is my boot and primary system disk (has been for some time), but the error message is essentially meaningless (to me, right now). Thanks. mhr PS: In the last couple of months there was a discussion of how to make the disk less active, starting with someone reporting that their disk drive activity light blinked every 30 seconds or something like that. I tried to find it again, but I couldn't pin down what to search for - what was the solution?

10 16

Thin client
by lingu 11 Sep '08

11 Sep '08

Dear all, I am very much new to Linux Thin Client Concept. But know i am very much interested to create Centos 5 based thin client of 512MB on flash rom. Can any one guide me to how to start and if you provide any suitable links that will be very much great full. Regards. Lingu

4 3

Logwatch / spamassassin
by Bob Hoffman 11 Sep '08

11 Sep '08

Hi all, Well it took a while for me to figure it out, but apparently my logwatch no longer can be mailed locally on my computer as I believe spamassassin is eating it. I can send it out to an email address outside my server though. So spamassassin is only checking incoming I guess. My question is....how do I...or should I.... Make all local mail go straight to the boxes and skip spamasassin entirely.. Or.. Whitelist logwatch. Apparently, I am guessing, all those nifty log reports are so full of blacklisted urls and ips...well, you get the picure. Best ways to make this work so I can get it delivered to root again? Thanks

4 4

RE: Logwatch / spamassassin
by Bob Hoffman 11 Sep '08

11 Sep '08

So.. To answer my own question... so I edited the file /etc/mail/spamassassin/local.cf whitelist_from logwatch(a)localhost.localdomain Where localhost.localdomain is your hostname.servername And it worked. However, I am concerned about spoofing. I would think that mail agent and spamassassin would have an 'okay, it's a local user' thing going on. They do not. On the internet there are 1000s of posts like mine, asking questions about this and getting no answers. I hope this helps. Centos 5.2... -----Original Message----- From: Bob Hoffman [mailto:bob@bobhoffman.com] Sent: Thursday, September 11, 2008 4:54 AM To: 'centos(a)centos.org' Subject: Logwatch / spamassassin Hi all, Well it took a while for me to figure it out, but apparently my logwatch no longer can be mailed locally on my computer as I believe spamassassin is eating it. I can send it out to an email address outside my server though. So spamassassin is only checking incoming I guess. My question is....how do I...or should I.... Make all local mail go straight to the boxes and skip spamasassin entirely.. Or.. Whitelist logwatch. Apparently, I am guessing, all those nifty log reports are so full of blacklisted urls and ips...well, you get the picure. Best ways to make this work so I can get it delivered to root again? Thanks

3 2

RE: Logwatch / spamassassin
by Bob Hoffman 11 Sep '08

11 Sep '08

Ned, Thanks for the letters. Yes, I added the whitelist, but think that is not right either. No matter what I add in there, it will allow someone to use it and come in. The postmaster not getting tagged is just as scary actually. The weird part is the mail will go to another server via smtp and not be tagged as SPAM. How strange is that. I can only assume I should be changing something in the logwatch file to make it not be from 'logwatch' but to instead be 'root' or some other local user. Since logwatch has no local user in my mail setups...maybe that is the problem. So it might be that matter that makes it get killed by procmail or by spamassassin. Strange. But a very obvious problem across the net. I will work on this more tonight and see if I can get it to run better without whitelisting.

1 0

RE: [CentOS] /etc/rc5.d
by Bowie Bailey 11 Sep '08

11 Sep '08

tony.chamberlain(a)lemko.com wrote: > > start() { > date >> /root/joe.log > /usr/bin/joevpn start & > RES=$? > return $RES > } > > This all works and everything. I am just curious as to why when I do > a ps I get this: > /bin/bash /etc/rc5.d/S99runjoevpn > > Shouldn't that init script terminate since I have an "&" when I do the > start() function above? No other rc5 stuff (i.e. tomcat for instance) > shows up in the ps, though tomcat is running, it started up and > returned. Is this OK or am I missing something? The "&" doesn't terminate anything. It simply moves the process to the background and leaves it attached to the parent process. The parent process cannot exit until all of its child processes exit. What you are looking for is this: start() { date >> /root/joe.log nohup /usr/bin/joevpn start & RES=$? return $RES } The "nohup" command will detach the joevpn process from the parent and allow the parent process to exit. -- Bowie

1 0

RE: [CentOS] RE: Logwatch / spamassassin
by Bowie Bailey 11 Sep '08

11 Sep '08

Bob Hoffman wrote: > So.. > > To answer my own question... > > so I edited the file /etc/mail/spamassassin/local.cf > > whitelist_from logwatch(a)localhost.localdomain > > Where localhost.localdomain is your hostname.servername > > And it worked. > > However, I am concerned about spoofing. I would think that mail agent > and spamassassin would have an 'okay, it's a local user' thing going > on. Generally, using 'whitelist_from' is a bad idea due to spoofing. The address you are using will probably not cause too many problems, but you should still fix it if possible. Use 'whitelist_from_rcvd' instead. This will whitelist the address only if the mail comes from a specified domain. Try this (untested): whitelist_from_rcvd logwatch(a)localhost.localdomain localhost.localdomain Note that this will require your DNS server to resolve localhost.localdomain (forward and reverse). Another option is to configure your mail server to bypass SA entirely for local mail. -- Bowie

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss