[CentOS] Mail delivery failing with 450
I'm not sure why this started, but apparently I'm having a DNS problem. Yesterday mail started bouncing with this error: 450 Unable to find obrien-pifer.com I think the messages eventually get delivered, but not sure. I guess I'll see if this one makes the list. I checked my domain using http://www.checkdns.net/ and it gives me a couple warnings. One is that there's no MX record, but there is. I use a smarthost for sending mail. My DNS records are: http://www.obrien-pifer.com/mydns.txt Anyone see any problems in my DNS records? Thanks, James ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail delivery failing with 450
James Pifer wrote: ... > Anyone see any problems in my DNS records? Doesn't look right to me: $ nslookup > set type=mx > obrien-pifer.com Server: 127.0.0.1 Address:127.0.0.1#53 Non-authoritative answer: *** Can't find obrien-pifer.com: No answer Authoritative answers can be found from: > $ nslookup > www.obrien-pifer.com Server: 127.0.0.1 Address:127.0.0.1#53 Non-authoritative answer: www.obrien-pifer.comcanonical name = obrien-pifer.com. Name: obrien-pifer.com Address: 70.62.90.185 Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: m...@crc.dk Homepage: http://www.crc.dk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail delivery failing with 450
hi James there is a MX recond for mail.obrien-pifer.com, not for obrien-pifer.com: bash-3.2$ dig obrien-pifer.com any ; <<>> DiG 9.5.1-P1-RedHat-9.5.1-1.P1.fc10 <<>> obrien-pifer.com any ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10894 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;obrien-pifer.com. IN ANY ;; ANSWER SECTION: obrien-pifer.com. 36647 IN A 70.62.90.185 obrien-pifer.com. 36647 IN NS porky.obrien-pifer.com. obrien-pifer.com. 36647 IN NS sammy.obrien-pifer.com. obrien-pifer.com. 36647 IN NS ns1.obrien-pifer.com. obrien-pifer.com. 36647 IN NS ns2.obrien-pifer.com. ;; AUTHORITY SECTION: obrien-pifer.com. 36647 IN NS ns2.obrien-pifer.com. obrien-pifer.com. 36647 IN NS porky.obrien-pifer.com. obrien-pifer.com. 36647 IN NS sammy.obrien-pifer.com. obrien-pifer.com. 36647 IN NS ns1.obrien-pifer.com. ;; ADDITIONAL SECTION: ns1.obrien-pifer.com. 36647 IN A 70.62.90.185 ns2.obrien-pifer.com. 36647 IN A 70.62.90.185 porky.obrien-pifer.com. 36647 IN A 70.62.90.185 sammy.obrien-pifer.com. 36647 IN A 70.62.90.185 ;; Query time: 3 msec ;; SERVER: 192.168.159.1#53(192.168.159.1) ;; WHEN: Sat Mar 7 13:53:39 2009 ;; MSG SIZE rcvd: 246 bash-3.2$ dig mail.obrien-pifer.com any ; <<>> DiG 9.5.1-P1-RedHat-9.5.1-1.P1.fc10 <<>> mail.obrien-pifer.com any ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31815 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;mail.obrien-pifer.com. IN ANY ;; ANSWER SECTION: mail.obrien-pifer.com. 38400 IN MX 1 70.62.90.185.obrien-pifer.com. ;; AUTHORITY SECTION: obrien-pifer.com. 36592 IN NS ns1.obrien-pifer.com. obrien-pifer.com. 36592 IN NS ns2.obrien-pifer.com. obrien-pifer.com. 36592 IN NS porky.obrien-pifer.com. obrien-pifer.com. 36592 IN NS sammy.obrien-pifer.com. ;; ADDITIONAL SECTION: ns1.obrien-pifer.com. 36592 IN A 70.62.90.185 ns2.obrien-pifer.com. 36592 IN A 70.62.90.185 porky.obrien-pifer.com. 36592 IN A 70.62.90.185 sammy.obrien-pifer.com. 36592 IN A 70.62.90.185 ;; Query time: 140 msec ;; SERVER: 192.168.159.1#53(192.168.159.1) ;; WHEN: Sat Mar 7 13:54:34 2009 ;; MSG SIZE rcvd: 208 bash-3.2$ Br, Louis On Sat, 2009-03-07 at 08:18 -0500, James Pifer wrote: > I'm not sure why this started, but apparently I'm having a DNS problem. > Yesterday mail started bouncing with this error: > 450 Unable to find obrien-pifer.com > > I think the messages eventually get delivered, but not sure. I guess > I'll see if this one makes the list. > > I checked my domain using http://www.checkdns.net/ and it gives me a > couple warnings. One is that there's no MX record, but there is. > > I use a smarthost for sending mail. > > My DNS records are: http://www.obrien-pifer.com/mydns.txt > > Anyone see any problems in my DNS records? > > Thanks, > James > > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail delivery failing with 450
Hi James, MX-records must point to A-records and not to IP adresses. A "dig -t AXFR obrien-pifer.com @ns1.obrien-pifer.com | grep MX" returns: mail.obrien-pifer.com. 38400 IN MX 1 70.62.90.185.obrien-pifer.com. Whereas you list "mail.obrien-pifer.com.INMX1 70.62.90.185" in your config. So your setup is invalid because: - you're pointing your one and only MX record directly to an IP - since it is interpreted as host and missing a "." at the end it's expanded to "70.62.90.185.obrien-pifer.com." which doesnt exist - it's a MX record for mail.obrien-pifer.com and not obrien-pifer.com Your whole definition of the MX record looks goofy to me, dont want to sound like an a.. but you better (re)read some tutorials on setting up DNS. I really wonder if you receive the reply at all. Regards, Thomas ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
At Fri, 06 Mar 2009 23:31:08 +0100 CentOS mailing list wrote: > > Robert Heller napsal(a): > > I need to be able to install CentOS 5.2 on a machine with software RAID > > (and LVM) setup. I discovered (the hard way!) that there is a bug in > > the mkinitrd package that causes it to enter an endless loop when there > > are /dev/mapper/ devices present during the install process. There is a > > patch to mkinitrd, which I applied and created a new rpm for mkinitrd > > with this patch applied. I'd like to now create a alternitive install > > CD, but I am not sure of the exact mkisofs command line to properly > > create a bootable CD. > > > > I am also not sure if I need to update any of the files the installer > > uses to install the system -- is it enough to just drop the alternitive > > mkinitrd rpm? Do I need to rebuild any of the other files on the CD? > > > > Robert, > go with Revisor > http://fs12.vsb.cz/hrb33/el5/hrb/stable/i386/repodata/repoview/revisor-0-2.0.5.2-2.el5.hrb.html > http://fs12.vsb.cz/hrb33/el5/hrb/stable/x86_64/repodata/repoview/revisor-0-2.0.5.2-2.el5.hrb.html > David HrbÃ¡Ä This seems overly complex for my needs. I don't want (or need) to rebuild all 6 of the install CDs. I just want to *replace* one RPM on the first CD. I have copied the CD's directory tree to a writable file system and replaced the rpm in question. I now need to just make a new ISO file and all I need is the proper command line arguments to mkisofs to do this. I am *NOT* creating a new distribution. And I really don't want to mess with a complex GUI program or edit many configuration files. I would also rather do this on my CentOS 4.7 system (revisor does not seem to be available for CentOS 4 / RHEL 4). Running it on a diskless workstation with a read-only root file system is a total pain. And will become even more painful when I then have to mount a large file system with NFS. > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > > > -- Robert Heller -- 978-544-6933 Deepwoods Software-- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows hel...@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail delivery failing with 450
On Sat, 2009-03-07 at 14:01 +0100, Joebstl Thomas wrote: > Hi James, > > MX-records must point to A-records and not to IP adresses. > A "dig -t AXFR obrien-pifer.com @ns1.obrien-pifer.com | grep MX" returns: > mail.obrien-pifer.com. 38400 IN MX 1 > 70.62.90.185.obrien-pifer.com. > > Whereas you list "mail.obrien-pifer.com.INMX1 70.62.90.185" > in your config. > > So your setup is invalid because: > - you're pointing your one and only MX record directly to an IP > - since it is interpreted as host and missing a "." at the end it's > expanded to "70.62.90.185.obrien-pifer.com." which doesnt exist > - it's a MX record for mail.obrien-pifer.com and not obrien-pifer.com > > Your whole definition of the MX record looks goofy to me, dont want to > sound like an a.. but you better (re)read some tutorials on setting up DNS. > I really wonder if you receive the reply at all. > > Regards, > Thomas Thomas, Can you tell me if it looks better now? Thanks, James ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
On Sat, 7 Mar 2009, Robert Heller wrote: > At Fri, 06 Mar 2009 23:31:08 +0100 CentOS mailing list > wrote: >>> I am also not sure if I need to update any of the files the installer >>> uses to install the system -- is it enough to just drop the alternitive >>> mkinitrd rpm? Do I need to rebuild any of the other files on the CD? > This seems overly complex for my needs. I don't want (or need) to > rebuild all 6 of the install CDs. I just want to *replace* one RPM on > the first CD. This is the problem with people thinking a respin is just shuttling files in and out, or adding a driver to a mkinitrd. In a post process, you can easily enough 'update' the one RPM in question with a bit of care in choosing the EVR information. Anaconda has provided for this in every CentOS release, and it usually suffices (adding install time drivers are the major exception). One can drop in anything that may be scripted -- the environment can be made Turing complete. But then, _who_ is on the hook for maintaining and supporting such a respin? No intention for providing a yum archive for updates is stated; no attention is paid to ensure that 'authentic' SIGNED rpms would be retrieved. Who gets splashed with mud when things go wrong? Assume there turns out to be a security hole in that package and it needs to be updated, or even worse worse if the re-spinner adds a package to drop in a "no key required" 'just a couple of files add-on' updates yum archive. For the sake of analysis assume that the archive added then gets compromised. Or the re-spinner loses interest, and lets the domain lapse, and it gets picked up by a 'blackhat'. Or a DNS poisoning attack subverts resolution of the domain -- no signed package protection can raise the alarm. It was bypassed. As I say, the customary bypass I have seen by minimal interest 'just change a couple of things' packagers and archives, is to wholly disable key checking for the archive they add. People regularly offer content from their personal archives. [I invite a self-audit, and would welcome a report of the last ten mentioned, to see if they are still viable (churning out updates), offering ONLY signed content with a well published signing key fingerprint, and issuing a yum.repo.d file requiring the packages used to be signed.] So continuing the thought experiment, when so altered to trust an additional archive, the remote machines doing update through cron, or yum-updatesd will trust ANYTHING, including malicious content, placed in that compromised archive. Game over. Here is the fallout: The poor end user 'knows' it was CentOS, because she was told by the respinner that it is 'CentOS with just one package replaced'. Who gets the black eye here? Who bears the support load of sorting out what happened when the poor hurt user shows up in what she thinks is the correct support venue, barely able to describe her VOIP turnkey box's operation? The answer is, of course, the main mother-ship CentOS project folks. And it is not right that people do this to us, but it is also hard to stop. Probably the only real solution is to enforce the CentOS trademark on the art and brand packages, and prohibit respins containing such (just as the upstream does). Sad, but true. There is a reason the core CentOS group are skittish about respins. We'll have to discuss this seriously. -- Russ herrold ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
On Sat, Mar 7, 2009 at 10:08 AM, Robert Heller wrote > > This seems overly complex for my needs. I don't want (or need) to > rebuild all 6 of the install CDs. I just want to *replace* one RPM on > the first CD. I have copied the CD's directory tree to a writable file > system and replaced the rpm in question. I now need to just make a new > ISO file and all I need is the proper command line arguments to mkisofs > to do this. I am *NOT* creating a new distribution. And I really don't > want to mess with a complex GUI program or edit many configuration > files. > > I would also rather do this on my CentOS 4.7 system (revisor does not > seem to be available for CentOS 4 / RHEL 4). Running it on a diskless > workstation with a read-only root file system is a total pain. And will > become even more painful when I then have to mount a large file system > with NFS. > First of all, if you replace an RPM, you'll need to do createrepro. disc_info=`head -1 $BASE/$ARCH/.discinfo` createrepo -v --baseurl="$disc_info" -g repodata/comps.xml $ARCH If the RPM is a "system RPM", then you probably want to do a buildinstall first to get it into the anaconda system (and get a new disc_info), a la: $BASE/buildinstall --debug \ --version 5 --product 'CentOS' --release "CentOS 5" \ --prodpath CentOS $BASE/$ARCH 2>&1 If all you want is a mkisofs, what's wrong with the "man" command?? Maybe something like: mkisofs -q -r -R -J -T -no-emul-boot -boot-load-size 4 -pad \ -b isolinux/isolinux.bin -c isolinux/boot.cat -boot-info-table \ -V "$VER ($date)" \ -A "$REL - $VER - $firmware" \ -publisher "$PUB" -p "$PUB" -x lost+found \ -o "CentOS-$VER-$date.iso" $ARCH2>&1 ... reboot, lather, rinse and repeat :-) :=) You may find "re-generating" the CentOS CDs/DVD quite easy at times and very frustrating and complex at others .. HTH -rak- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 49, Issue 3
-- Pasi Pirhonen - u...@iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.centos.org/pipermail/centos-announce/attachments/20090307/3768431a/attachment-0001.bin -- Message: 8 Date: Sat, 7 Mar 2009 15:25:15 +0200 From: Pasi Pirhonen Subject: [CentOS-announce] CESA-2009:0325 Critical CentOS 4 ia64 seamonkey - security update To: centos-annou...@centos.org Message-ID: <20090307132515.gj23...@centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2009:0315 https://rhn.redhat.com/errata/RHSA-2009-0325.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/seamonkey-1.0.9-38.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-chat-1.0.9-38.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-devel-1.0.9-38.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-dom-inspector-1.0.9-38.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-js-debugger-1.0.9-38.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-mail-1.0.9-38.el4.centos.ia64.rpm -- Pasi Pirhonen - u...@iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.centos.org/pipermail/centos-announce/attachments/20090307/4cce14ec/attachment-0001.bin -- ___ CentOS-announce mailing list centos-annou...@centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 49, Issue 3 ** ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I have a test system that hangs hard...
Robert Moskowitz wrote: > I have a test system: Centos 5.2 on an OQO, that has been hanging > hard. I have to unplug it and pull the battery so I can then cold start it. > > This last time all I did was open a terminal window and SU to root, then > start the lastest build of SIP Communicator (which uses JRE 1.6.0_10). > I was not even making a test phone call at the time. Oh, and the system > only runs IPv6, no v4 addressing. > > So how do I find out what is causing the hard lockups? if the problem is triggered reproducibly by building SIP C, then just don't use X when starting the build; change to a console (Ctrl-Alt-F1) and watch out for kernel messages indicating a software (kernel) problem. If the problem is due to hardware, there is a chance that memtest86+ will find bad memory. If it's a bad disk, you can check with smartctl. There's are burn-in programs available; I use burnCPU to put load on multi-core systems. Compiling the Linux kernel a hundred times in a row is also a good test; not a single build should fail. HTH, Kay ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I have a test system that hangs hard...
Robert Moskowitz wrote: See embedded comments. I'm not familiar with the specific package mentioned but these are just a few standard debugging ideas. > I have a test system: Centos 5.2 on an OQO, that has been hanging > hard. I have to unplug it and pull the battery so I can then cold start it. > I assume this also means that the system runs as expected if you don't take any of the actions described below. > This last time all I did was open a terminal window and SU to root, then > start the lastest build of SIP Communicator (which uses JRE 1.6.0_10). > I was not even making a test phone call at the time. Any chance of trying an earlier version? Especially one that uses an earlier JRE? > Oh, and the system > only runs IPv6, no v4 addressing. > And what happens if you enable IPV4? If possible, can SIP Communicator be configured to use IPV4 instead of V6? If so, does the problem persist? > So how do I find out what is causing the hard lockups? > I'd start with enabling IPV4 addressing since it's fairly trivial to do and then work back toward running an earlier version of the program. You may find something like the JRE wants an IPV4 connection (just wildly speculating here). Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail delivery failing with 450
James Pifer wrote on Sat, 07 Mar 2009 11:07:00 -0500: > Can you tell me if it looks better now? It's better, but still: - as the MX is the same as your domain name you do not need an MX - as all your hosts point to the same IP you can just use a wildcard - as I'm sure you don't change your hosts several times a day you can up the TTL to a more reasonable time like 86400 (=a day) - having four ns records all point to the same IP is just, uhm, pointless Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
R P Herrold wrote: >> > Here is the fallout: The poor end user 'knows' it was CentOS, > because she was told by the respinner that it is 'CentOS with > just one package replaced'. Who gets the black eye here? > Who bears the support load of sorting out what happened when > the poor hurt user shows up in what she thinks is the correct > support venue, barely able to describe her VOIP turnkey box's > operation? > > The answer is, of course, the main mother-ship CentOS project > folks. > > And it is not right that people do this to us, but it is also > hard to stop. Probably the only real solution is to enforce > the CentOS trademark on the art and brand packages, and > prohibit respins containing such (just as the upstream does). > > Sad, but true. > > There is a reason the core CentOS group are skittish about > respins. We'll have to discuss this seriously. I can see your point about the brand value you have embedded into the packages, but it also seems wrong to make everyone who wants to improve it or adapt to some additional purpose repeat all the rebranding work from scratch. How hard would it be to generate an 'unbranded' drop in replacement package for everything specifically Centos - or a framework so others could share the work? That way everyone who needed to replace a driver wouldn't have to repeat all this work unless they wanted to create their own unique brand identity. If you think respins containing Centos branding are wrong, make it easy to to the right thing. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
> -Original Message- > From: centos-boun...@centos.org > [mailto:centos-boun...@centos.org] On Behalf Of Les Mikesell > Sent: Saturday, March 07, 2009 17:59 > To: CentOS mailing list > Subject: Re: [CentOS] Creating an alternitive install CD for > CentOS 5.2 (w/ patched mkinitrd) > > R P Herrold wrote: > >> > > Here is the fallout: The poor end user 'knows' it was > CentOS, because > > she was told by the respinner that it is 'CentOS with just > one package > > replaced'. Who gets the black eye here? > > Who bears the support load of sorting out what happened > when the poor > > hurt user shows up in what she thinks is the correct support venue, > > barely able to describe her VOIP turnkey box's operation? > > > > The answer is, of course, the main mother-ship CentOS project folks. > > > > And it is not right that people do this to us, but it is > also hard to > > stop. Probably the only real solution is to enforce the CentOS > > trademark on the art and brand packages, and prohibit respins > > containing such (just as the upstream does). > > > > Sad, but true. > > > > There is a reason the core CentOS group are skittish about > respins. > > We'll have to discuss this seriously. > > I can see your point about the brand value you have embedded > into the packages, but it also seems wrong to make everyone > who wants to improve it or adapt to some additional purpose > repeat all the rebranding work from scratch. > > How hard would it be to generate an 'unbranded' drop in > replacement package for everything specifically Centos - or a > framework so others could share the work? That way everyone > who needed to replace a driver wouldn't have to repeat all > this work unless they wanted to create their own unique brand > identity. Kinky idea, I like it. > > If you think respins containing Centos branding are wrong, > make it easy to to the right thing. > > -- >Les Mikesell > lesmikes...@gmail.com > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail delivery failing with 450
Kai Schaetzl wrote: > - as the MX is the same as your domain name you do not need an MX It is good to always have an MX. > - having four ns records all point to the same IP is just, uhm, pointless Can make it easier to separate workloads and move them to different servers later. //Morten ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail delivery failing with 450
Kai Schaetzl wrote: > It's better, but still: > > - as the MX is the same as your domain name you do not need an MX > - as all your hosts point to the same IP you can just use a wildcard > - as I'm sure you don't change your hosts several times a day you can up > the TTL to a more reasonable time like 86400 (=a day) > - having four ns records all point to the same IP is just, uhm, pointless > worse than pointless, its ugly. in the event your server is down and not responding, a lookup server will try it 4 times as many times as it otherwise would. the only NS records that should be in your zone are exactly the same as the ones in the registrar for the domain. $ whois obrien-pifer.com ... Domain Name: OBRIEN-PIFER.COM Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com Name Server: NS1.OBRIEN-PIFER.COM Name Server: NS2.OBRIEN-PIFER.COM Server Name: NS1.OBRIEN-PIFER.COM IP Address: 70.62.90.185 Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com Server Name: NS2.OBRIEN-PIFER.COM IP Address: 70.62.90.185 Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com I'm surprised the registrar let you register two HOST names for the same IP, they aren't supposed to do that. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
At Sat, 7 Mar 2009 10:45:19 -0500 (EST) CentOS mailing list wrote: > > On Sat, 7 Mar 2009, Robert Heller wrote: > > > At Fri, 06 Mar 2009 23:31:08 +0100 CentOS mailing list > > wrote: > > >>> I am also not sure if I need to update any of the files the installer > >>> uses to install the system -- is it enough to just drop the alternitive > >>> mkinitrd rpm? Do I need to rebuild any of the other files on the CD? > > > This seems overly complex for my needs. I don't want (or need) to > > rebuild all 6 of the install CDs. I just want to *replace* one RPM on > > the first CD. > > This is the problem with people thinking a respin is just > shuttling files in and out, or adding a driver to a mkinitrd. > > In a post process, you can easily enough 'update' the one RPM > in question with a bit of care in choosing the EVR > information. Anaconda has provided for this in every CentOS > release, and it usually suffices (adding install time drivers > are the major exception). One can drop in anything that may > be scripted -- the environment can be made Turing complete. The problem is that the mkinitrd rpm that is shipped with CentOS 5.2 *go into an infinite loop* if one is installing a kernel on a system with software raid disks. This means that the base install process *hangs*. I suspect that killing the looping mkinitrd process kills (crashes) the install. This means it is impossible to do a base install this way. *This is a known problem* (check the bug database for both RHEL5 and CentOS5 for details). The only other option is to patch the mkinitrd script *while* the install is in progress. I ended up doing this when I originally installed CentOS 5.2, but mis-typed the patch command and ended up with a zero length file in /sbin/mkinitrd -- this did not cause the installer to crash, it just failed to make the initrd file -- not really a problem -- I just booted with a rescue disk and manually re-made the initrd (and it was only a secondard O/S on my system and I had told the installer to not install any boot loader). > > > But then, _who_ is on the hook for maintaining and supporting > such a respin? No intention for providing a yum archive for > updates is stated; no attention is paid to ensure that > 'authentic' SIGNED rpms would be retrieved. Who gets splashed > with mud when things go wrong? > > > Assume there turns out to be a security hole in that package > and it needs to be updated, or even worse worse if the > re-spinner adds a package to drop in a "no key required" > 'just a couple of files add-on' updates yum archive. > > For the sake of analysis assume that the archive added then > gets compromised. Or the re-spinner loses interest, and lets > the domain lapse, and it gets picked up by a 'blackhat'. Or a > DNS poisoning attack subverts resolution of the domain -- no > signed package protection can raise the alarm. It was > bypassed. > > As I say, the customary bypass I have seen by minimal interest > 'just change a couple of things' packagers and archives, is to > wholly disable key checking for the archive they add. People > regularly offer content from their personal archives. [I > invite a self-audit, and would welcome a report of the last > ten mentioned, to see if they are still viable (churning out > updates), offering ONLY signed content with a well published > signing key fingerprint, and issuing a yum.repo.d file > requiring the packages used to be signed.] > > So continuing the thought experiment, when so altered to > trust an additional archive, the remote machines doing update > through cron, or yum-updatesd will trust ANYTHING, including > malicious content, placed in that compromised archive. > > Game over. > > Here is the fallout: The poor end user 'knows' it was CentOS, > because she was told by the respinner that it is 'CentOS with > just one package replaced'. Who gets the black eye here? > Who bears the support load of sorting out what happened when > the poor hurt user shows up in what she thinks is the correct > support venue, barely able to describe her VOIP turnkey box's > operation? > > The answer is, of course, the main mother-ship CentOS project > folks. > > And it is not right that people do this to us, but it is also > hard to stop. Probably the only real solution is to enforce > the CentOS trademark on the art and brand packages, and > prohibit respins containing such (just as the upstream does). > > Sad, but true. > > There is a reason the core CentOS group are skittish about > respins. We'll have to discuss this seriously. > > -- Russ herrold > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > -- Robert Heller -- 978-544-6933 Deepwoods Software-- Download the Model Railroad System http://www.deepsoft
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
At Sat, 7 Mar 2009 10:48:29 -0500 CentOS mailing list wrote: > > On Sat, Mar 7, 2009 at 10:08 AM, Robert Heller wrote > > > > This seems overly complex for my needs. Â I don't want (or need) to > > rebuild all 6 of the install CDs. Â I just want to *replace* one RPM on > > the first CD. Â I have copied the CD's directory tree to a writable file > > system and replaced the rpm in question. Â I now need to just make a new > > ISO file and all I need is the proper command line arguments to mkisofs > > to do this. Â I am *NOT* creating a new distribution. Â And I really don't > > want to mess with a complex GUI program or edit many configuration > > files. > > > > I would also rather do this on my CentOS 4.7 system (revisor does not > > seem to be available for CentOS 4 / RHEL 4). Â Running it on a diskless > > workstation with a read-only root file system is a total pain. Â And will > > become even more painful when I then have to mount a large file system > > with NFS. > > > > First of all, if you replace an RPM, you'll need to do createrepro. > > disc_info=`head -1 $BASE/$ARCH/.discinfo` > createrepo -v --baseurl="$disc_info" -g repodata/comps.xml $ARCH > OK, it looks like I need to do this (see below). > If the RPM is a "system RPM", then you probably want to do a > buildinstall first to get it into the anaconda system (and get a new > disc_info), > a la: > >$BASE/buildinstall --debug \ > --version 5 --product 'CentOS' --release "CentOS 5" \ > --prodpath CentOS $BASE/$ARCH 2>&1 > > If all you want is a mkisofs, what's wrong with the "man" command?? > > Maybe something like: > > mkisofs -q -r -R -J -T -no-emul-boot -boot-load-size 4 -pad \ > -b isolinux/isolinux.bin -c isolinux/boot.cat -boot-info-table \ > -V "$VER ($date)" \ > -A "$REL - $VER - $firmware" \ > -publisher "$PUB" -p "$PUB" -x lost+found \ > -o "CentOS-$VER-$date.iso" $ARCH 2>&1 I was unsure of the specific options above -- After installing revisor and poked around in the source code and found what I needed, but my test install failed -- it complained that there was a problem with mkinitrd -- could not open it or find it -- guessing I need to rebuild the repro database. > > ... reboot, lather, rinse and repeat :-) :=) > > You may find "re-generating" the CentOS CDs/DVD quite easy at > times and very frustrating and complex at others .. Yeah, it appears so. I just hope I don't have to rebuild all 6 CDs, since I don't have the DVD nor do I have a DVD-R drive either, so doing things with a single DVD is not an option. > > HTH > >-rak- > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > > -- Robert Heller -- 978-544-6933 Deepwoods Software-- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows hel...@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
At Sat, 07 Mar 2009 11:59:02 -0600 CentOS mailing list wrote: > > R P Herrold wrote: > >> > > Here is the fallout: The poor end user 'knows' it was CentOS, > > because she was told by the respinner that it is 'CentOS with > > just one package replaced'. Who gets the black eye here? > > Who bears the support load of sorting out what happened when > > the poor hurt user shows up in what she thinks is the correct > > support venue, barely able to describe her VOIP turnkey box's > > operation? > > > > The answer is, of course, the main mother-ship CentOS project > > folks. > > > > And it is not right that people do this to us, but it is also > > hard to stop. Probably the only real solution is to enforce > > the CentOS trademark on the art and brand packages, and > > prohibit respins containing such (just as the upstream does). > > > > Sad, but true. > > > > There is a reason the core CentOS group are skittish about > > respins. We'll have to discuss this seriously. > > I can see your point about the brand value you have embedded into the > packages, but it also seems wrong to make everyone who wants to improve > it or adapt to some additional purpose repeat all the rebranding work > from scratch. Or deal with a 'show stopping bug', like the known problem with mkinitrd. I have no interest in rebranding anything or even redistributing my 'replacement' CD (I'll probably toss the replacement CD once I get the install done). I just want to install CentOS on a system with pre-existing software RAID disks -- I am migrating a server from Ubuntu to CentOS 5 and I don't want to lose prexisting data, so simply wiping the disks and installing on bare partitions is not an option (and even then I'd want to use LVM for some things, and even without RAID, LVM will also send mkinitrd off into never, never land -- basically anything the fires up /dev/mapper/... will do it: RAID, LVM, cryptfs, all seem to do this). > > How hard would it be to generate an 'unbranded' drop in replacement > package for everything specifically Centos - or a framework so others > could share the work? That way everyone who needed to replace a driver > wouldn't have to repeat all this work unless they wanted to create their > own unique brand identity. > > If you think respins containing Centos branding are wrong, make it easy > to to the right thing. > -- Robert Heller -- 978-544-6933 Deepwoods Software-- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows hel...@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail delivery failing with 450
> $ whois obrien-pifer.com > ... >Domain Name: OBRIEN-PIFER.COM >Registrar: WILD WEST DOMAINS, INC. >Whois Server: whois.wildwestdomains.com >Referral URL: http://www.wildwestdomains.com >Name Server: NS1.OBRIEN-PIFER.COM >Name Server: NS2.OBRIEN-PIFER.COM > >Server Name: NS1.OBRIEN-PIFER.COM >IP Address: 70.62.90.185 >Registrar: WILD WEST DOMAINS, INC. >Whois Server: whois.wildwestdomains.com >Referral URL: http://www.wildwestdomains.com > > >Server Name: NS2.OBRIEN-PIFER.COM >IP Address: 70.62.90.185 >Registrar: WILD WEST DOMAINS, INC. >Whois Server: whois.wildwestdomains.com >Referral URL: http://www.wildwestdomains.com > > > > I'm surprised the registrar let you register two HOST names for the same > IP, they aren't supposed to do that. I removed the other two NS records. I also raised the TTL as suggested. Thanks for all the help. James ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
Robert Heller wrote: > I don't want (or need) to > rebuild all 6 of the install CDs. I just want to *replace* one RPM on > the first CD. the installer supports external repo's - at install time. All you then need is to provide a new repo, with a higher EVR for mkinitrd. -- Karanbir Singh : http://www.karan.org/ : 2522...@icq ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
At Sat, 07 Mar 2009 19:39:00 + CentOS mailing list wrote: > > Robert Heller wrote: > > I don't want (or need) to > > rebuild all 6 of the install CDs. I just want to *replace* one RPM on > > the first CD. > > the installer supports external repo's - at install time. All you then > need is to provide a new repo, with a higher EVR for mkinitrd. I am not sure how to do this and did not know it was possible -- there is nothing obvious in the install menus that suggest this. I do prefer the 'text' based install. Also, in the case of my home system, the external repo would *have* be on the local disk somewhere, since I don't have any other machines available on my LAN and the the only external Internet option is dialup. > -- Robert Heller -- 978-544-6933 Deepwoods Software-- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows hel...@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
Robert Heller wrote: At Sat, 07 Mar 2009 11:59:02 -0600 CentOS mailing list wrote: R P Herrold wrote: Here is the fallout: The poor end user 'knows' it was CentOS, because she was told by the respinner that it is 'CentOS with just one package replaced'. Who gets the black eye here? Who bears the support load of sorting out what happened when the poor hurt user shows up in what she thinks is the correct support venue, barely able to describe her VOIP turnkey box's operation? The answer is, of course, the main mother-ship CentOS project folks. And it is not right that people do this to us, but it is also hard to stop. Probably the only real solution is to enforce the CentOS trademark on the art and brand packages, and prohibit respins containing such (just as the upstream does). Sad, but true. There is a reason the core CentOS group are skittish about respins. We'll have to discuss this seriously. I can see your point about the brand value you have embedded into the packages, but it also seems wrong to make everyone who wants to improve it or adapt to some additional purpose repeat all the rebranding work from scratch. Or deal with a 'show stopping bug', like the known problem with mkinitrd. I have no interest in rebranding anything or even redistributing my 'replacement' CD (I'll probably toss the replacement CD once I get the install done). I just want to install CentOS on a system with pre-existing software RAID disks -- I am migrating a server from Ubuntu to CentOS 5 and I don't want to lose prexisting data, so simply wiping the disks and installing on bare partitions is not an option (and even then I'd want to use LVM for some things, and even without RAID, LVM will also send mkinitrd off into never, never land -- basically anything the fires up /dev/mapper/... will do it: RAID, LVM, cryptfs, all seem to do this). How hard would it be to generate an 'unbranded' drop in replacement package for everything specifically Centos - or a framework so others could share the work? That way everyone who needed to replace a driver wouldn't have to repeat all this work unless they wanted to create their own unique brand identity. If you think respins containing Centos branding are wrong, make it easy to to the right thing. tried nodmraid on the kernel boot line? begin:vcard fn:Rob Kampen n:Kampen;Rob email;internet:rkam...@kampensonline.com x-mozilla-html:TRUE version:2.1 end:vcard ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] topbanel and bottompanel on gnome
On Fri, Mar 6, 2009 at 6:01 AM, Jerry Geis wrote: > > Or better yet how do I completely disable the top and bottom panels > using gconftool-2? > Not sure about gconftool-2, but you can delete one panels by right clicking on the panel and selecting the delete panel option. I'm not sure you can remove both of them altogether, and you may be stuck with the 1 pixel line for at least one of them. You might try asking in the gnome email list HTH mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
At Sat, 07 Mar 2009 18:44:46 -0500 CentOS mailing list wrote: > > > Robert Heller wrote: > > At Sat, 07 Mar 2009 11:59:02 -0600 CentOS mailing list > > wrote: > > > > > >> R P Herrold wrote: > >> > >>> Here is the fallout: The poor end user 'knows' it was CentOS, > >>> because she was told by the respinner that it is 'CentOS with > >>> just one package replaced'. Who gets the black eye here? > >>> Who bears the support load of sorting out what happened when > >>> the poor hurt user shows up in what she thinks is the correct > >>> support venue, barely able to describe her VOIP turnkey box's > >>> operation? > >>> > >>> The answer is, of course, the main mother-ship CentOS project > >>> folks. > >>> > >>> And it is not right that people do this to us, but it is also > >>> hard to stop. Probably the only real solution is to enforce > >>> the CentOS trademark on the art and brand packages, and > >>> prohibit respins containing such (just as the upstream does). > >>> > >>> Sad, but true. > >>> > >>> There is a reason the core CentOS group are skittish about > >>> respins. We'll have to discuss this seriously. > >>> > >> I can see your point about the brand value you have embedded into the > >> packages, but it also seems wrong to make everyone who wants to improve > >> it or adapt to some additional purpose repeat all the rebranding work > >> from scratch. > >> > > > > Or deal with a 'show stopping bug', like the known problem with > > mkinitrd. I have no interest in rebranding anything or even > > redistributing my 'replacement' CD (I'll probably toss the replacement > > CD once I get the install done). I just want to install CentOS on a > > system with pre-existing software RAID disks -- I am migrating a server > > from Ubuntu to CentOS 5 and I don't want to lose prexisting data, so > > simply wiping the disks and installing on bare partitions is not an > > option (and even then I'd want to use LVM for some things, and even > > without RAID, LVM will also send mkinitrd off into never, never land -- > > basically anything the fires up /dev/mapper/... will do it: RAID, LVM, > > cryptfs, all seem to do this). > > > > > >> How hard would it be to generate an 'unbranded' drop in replacement > >> package for everything specifically Centos - or a framework so others > >> could share the work? That way everyone who needed to replace a driver > >> wouldn't have to repeat all this work unless they wanted to create their > >> own unique brand identity. > >> > >> If you think respins containing Centos branding are wrong, make it easy > >> to to the right thing. > >> > >> > > > > > tried nodmraid on the kernel boot line? The problem is that I need to actually install on the raid arrays, so this isn't an option either. > > > begin:vcard > fn:Rob Kampen > n:Kampen;Rob > email;internet:rkam...@kampensonline.com > x-mozilla-html:TRUE > version:2.1 > end:vcard > > > MIME-Version: 1.0 > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > > -- Robert Heller -- 978-544-6933 Deepwoods Software-- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows hel...@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Please test kmod packages for CentOS-4
Hello, There are currently 3 kmod packages in CentOS-4 that require re-installation upon each kernel update: kmod-drbd kmod-drbd82 kmod-xfs CentOS is going to offer a kernel-independent version of these kmod packages. With this version, you install once, and they should survive kernel updates. They are in the testing repository at the moment and need to be tested before they can be made available from the regular place (extras repo). Getting enough testing is important because CentOS may not be providing kernel-specific kmod-packages any longer. If you have never used the testing repository, please refer to the Wiki article: http://wiki.centos.org/AdditionalResources/Repositories Happy testing! Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Memory vs. Display Card
Since memory has become quite cheap lately I decided to move from 2 GB to 6. When I installed the memory every thing was fine until I went to run level 5. At that point the screen turned to garbage and the system froze. Is there a way to fix this so I can use the memory I bought? Do I need a new display card? Current hardware: Intel D975XBX2 Motherboard VGA compatible controller: ATI Technologies Inc RV505 [Radeon X1550 64-bit] -- http://www.spinics.net/lists/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Memory vs. Display Card
On Sun, Mar 08, 2009 at 03:00:59AM +, Rick wrote: > Since memory has become quite cheap lately I decided to move from 2 GB > to 6. When I installed the memory every thing was fine until I went to > run level 5. At that point the screen turned to garbage and the system > froze. Is there a way to fix this so I can use the memory I bought? Do > I need a new display card? > > Current hardware: > > Intel D975XBX2 Motherboard > VGA compatible controller: ATI Technologies Inc RV505 [Radeon X1550 64-bit] That sounds pretty strange. Have you confirmed that removing the "new" memory allows you to run in runlevel 5 again? If so, maybe you need to adjust some memory timing settings in BIOS. Ray ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Memory vs. Display Card
Rick writes: > Since memory has become quite cheap lately I decided to move from 2 GB > to 6. When I installed the memory every thing was fine until I went to > run level 5. At that point the screen turned to garbage and the system > froze. Is there a way to fix this so I can use the memory I bought? Do > I need a new display card? Have you tried memtest86? without a serial console, it'd be hard to see if that's the problem, but it is a good place to start. Often if you have bad memory the problem doesn't show until you use something that actually uses more of your memory (like starting the GUI) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hardware compatibility IM-945GC Intel Atom Mini-ITX]
Le Lun 2 mars 2009 23:39, Jason Pyeron a écrit : > Can this MB be used with Centos 4 (or 5)? > > For reference: > http://www.logicsupply.com/products/ms_9832 > > > I don't think we can use this new MB since the Realtek 8111C does not seem > to be > supported (well) > > http://forums.tweaktown.com/f69/8111c-nic-revision-ep45-27089- > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I'm using Cents 5 on an Intel atom D945GCLF MB which has the same network card and it's working fine : - with Centos 5.0, 5.1, 5.2 : you've to erase the R8169 kernel module and manually install realtek drivers ( http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=7&Level=5&Conn=4&DownTypeID=3&GetDown=false#2 ) - with upcoming Centos 5.3 : nothing to do, the driver is included in the kernel ( 2.6.18-128.1.1.el5 ) David Amiel - > - Jason Pyeron PD Inc. http://www.pdinc.us - > - Principal Consultant 10 West 24th Street #100- > - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - > - - > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > This message is copyright PD Inc, subject to license 20080407P00. > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] samsung sata disk pb
Hi there, I'm running a centos 5.2 (with a centos 5.3 kernel) on a box with a samsung 1To green edition, and this disk looks a bit slow to me and it's not recognized by hdparm : # hdparm -iI /dev/sda /dev/sda: HDIO_GET_IDENTITY failed: Invalid argument HDIO_DRIVE_CMD(identify) failed: Invalid argument # hdparm -tT /dev/sda /dev/sda: Timing cached reads: 2252 MB in 2.00 seconds = 1125.57 MB/sec Timing buffered disk reads: 94 MB in 3.05 seconds = 30.81 MB/sec I've got a samsung 640go on my desktop running ubuntu (kernel 2.6.27-11), hdparm -iI is working and benchmark is a lot better : $ sudo hdparm -tT /dev/sda /dev/sda: Timing cached reads: 2392 MB in 2.00 seconds = 1196.00 MB/sec Timing buffered disk reads: 226 MB in 3.02 seconds = 74.81 MB/sec the green HD is a 5400rpm, though the other one is 7400rpm, but a factor 2 in performance between them looks very strange to me. As the green 1 To disk is not identified by hdparm I think it's not configured properly. Any hint to make my 1To disk flying like the other one ? :) cheers, David ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] samsung sata disk pb
David Amiel wrote: > Hi there, > > I'm running a centos 5.2 (with a centos 5.3 kernel) on a box with a > samsung 1To green edition, and this disk looks a bit slow to me and it's > not recognized by hdparm > more likely to be a problem with support for the specific SATA controller than the drive itself. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
