Re: [CentOS] Two external interfaces, one with "default" route and ping problem
On Mon, Aug 19, 2013 at 10:41 PM, Jobst Schmalenbach wrote: > > Hi > > I have two different IP addresses (in a block of /29), one is on port 0 and > the other is on port 2 of a Ciso 888. > I am doing this so I can have two different certs with two different ip > addresses. > > I have tried: > > 1) one machine, two real interfaces, two cables (eth0 and eth2) > 2) one machine, one real interface eth0 and one virtual interface eth0:1, > one network cable > > > Using number 2) > I can ping the two different ip addresses, no problem. The only problem here > is that iptables does not work (I cannot create rules for eth0:1 - and yes I > know about the security implications). Why do you need different rules for eth0:1? Can't you specify the IP addresses? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] mail server: sendmail with integrated AD
I'm preparing my new Sendmail mail server with pop3s + smtps where user authentication occurs through Microsoft Active Directory by Winbind daemon. OS is Centos 6.4 and Sendmail is 8.14 Mailboxes will be in this server but how to create them !??! It's necessary to add user by 'useradd' command into /etc/passwd or It's only necessary add new entry in '/etc/aliases' file for every AD user like in following example ?! mark.landers:marklanders - 'marklander' is the user account in Microsoft AD - user mail is 'mark.land...@example.com' POP3s the account name (AD user), which I'll use to access my mailbox by pop3s, must have the same name of mailbox file ? According to previous example: if I wanted to download email of 'mark.land...@example.com', in my client I shall have to type 'marklanders' with its password, so my requirement is to have this mailbox file into my mail server: / for example: /var/spool/mail/marklanders I think pop3S WILL SEARCH mailbox with the same name of account name ! What do you think ? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Two external interfaces, one with "default" route and ping problem
Hi, Two IP addresses within the same subnet is generally something that should be avoided if at all possible. See http://serverfault.com/questions/336021/two-network-interfaces-and-two-ip-addresses-on-the-same-subnet-in-linuxfor some information that may help. On Tue, Aug 20, 2013 at 3:41 PM, Jobst Schmalenbach wrote: > > Hi > > I have two different IP addresses (in a block of /29), one is on port 0 > and the other is on port 2 of a Ciso 888. > I am doing this so I can have two different certs with two different ip > addresses. > > I have tried: > > 1) one machine, two real interfaces, two cables (eth0 and eth2) > 2) one machine, one real interface eth0 and one virtual interface eth0:1, > one network cable > > > Using number 2) > I can ping the two different ip addresses, no problem. The only problem > here is that iptables does not work (I cannot create rules for eth0:1 - and > yes I know about the security implications). > > > I have a problem with number number 1) > > I can ping the first ip address and I get a return, but I cannot get a > return when I ping the second ip address. > I can see traffic coming into the second interface but it does not return. > Now one of the interfaces needs the "default" route applied (is this > correct??), which is eth0. > > I assume this is a routing problem? > What do I need to do to get this to work? > > > > Jobst > > > > > > > > -- > Student to Teacher: Sir, what's an oxymoron? Teacher to Student: > "Microsoft Works". > > | |0| | Jobst Schmalenbach, jo...@barrett.com.au, General Manager > | | |0| Barrett Consulting Group P/L & The Meditation Room P/L > |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia > ___ > 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] Two external interfaces, one with "default" route and ping problem
Hi I have two different IP addresses (in a block of /29), one is on port 0 and the other is on port 2 of a Ciso 888. I am doing this so I can have two different certs with two different ip addresses. I have tried: 1) one machine, two real interfaces, two cables (eth0 and eth2) 2) one machine, one real interface eth0 and one virtual interface eth0:1, one network cable Using number 2) I can ping the two different ip addresses, no problem. The only problem here is that iptables does not work (I cannot create rules for eth0:1 - and yes I know about the security implications). I have a problem with number number 1) I can ping the first ip address and I get a return, but I cannot get a return when I ping the second ip address. I can see traffic coming into the second interface but it does not return. Now one of the interfaces needs the "default" route applied (is this correct??), which is eth0. I assume this is a routing problem? What do I need to do to get this to work? Jobst -- Student to Teacher: Sir, what's an oxymoron? Teacher to Student: "Microsoft Works". | |0| | Jobst Schmalenbach, jo...@barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Really Weird Question.....
On 08/19/2013 09:23 PM, John R Pierce wrote: > On 8/19/2013 5:20 PM, Eddie G. O'Connor Jr. wrote: >> So I just got ahold of an old e-Machine (Model EL1600) with 1GB of >> memory. I was going to install CEntOS on it and try to run VirtualBox >> for other OS'es. I am curious to know if I have to stick with the 2GB >> "max" the specs say the machine can take or if its possible to install a >> 4GB module that is designed the same? In other words I have seen 2GB DDR >> PC2700 memory that will fit the casing and work, but I have ALSO seen >> 4GB DDR PC6400 memory modules with the same number of pins (240) will >> this work? I would want to have as much memory in there that will allow >> the VirtualBox to run smoothly.any help would be appreciated! > > if you are running VMs, you pretty much have to have more real memory > than all your VM's plus your main system are using. I run virtualbox on > machines with 8gb and more ram. with only 1gb, if you run a single > 512MB VM, you'll only have 512MB left for your regular system too. > what are you going to install in a 512MB VM other than very stripped > systems? > > I see that Stephen was right, this box will only max out at 2GB,.so I guess I'll install something else on it and look to install CEntOS on the "uber-machine" that I have on standby (1TB HDD - 6GB RAM - AMDFX9370...etc.) I just wanted to see if there was any "hope" for this boxthanks everyone! EGO II ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Really Weird Question.....
On 8/19/2013 5:20 PM, Eddie G. O'Connor Jr. wrote: > So I just got ahold of an old e-Machine (Model EL1600) with 1GB of > memory. I was going to install CEntOS on it and try to run VirtualBox > for other OS'es. I am curious to know if I have to stick with the 2GB > "max" the specs say the machine can take or if its possible to install a > 4GB module that is designed the same? In other words I have seen 2GB DDR > PC2700 memory that will fit the casing and work, but I have ALSO seen > 4GB DDR PC6400 memory modules with the same number of pins (240) will > this work? I would want to have as much memory in there that will allow > the VirtualBox to run smoothly.any help would be appreciated! if you are running VMs, you pretty much have to have more real memory than all your VM's plus your main system are using. I run virtualbox on machines with 8gb and more ram. with only 1gb, if you run a single 512MB VM, you'll only have 512MB left for your regular system too. what are you going to install in a 512MB VM other than very stripped systems? -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Really Weird Question.....
On Mon, Aug 19, 2013 at 08:20:28PM -0400, Eddie G. O'Connor Jr. wrote: > So I just got ahold of an old e-Machine (Model EL1600) with 1GB of Umm, this machine? http://www.newegg.com/Product/Product.aspx?Item=N82E16883114074 > memory. I was going to install CEntOS on it and try to run VirtualBox This is an Atom 230 based machine http://ark.intel.com/products/35635/Intel-Atom-Processor-230-512K-Cache-1_60-GHz-533-MHz-FSB It doesn't do VT; I'm not sure it's a good base for VirtualBox... it's probably gonna be very slow. > for other OS'es. I am curious to know if I have to stick with the 2GB > "max" the specs say the machine can take or if its possible to install a Crucial don't believe it can handle anything except 2GB http://www.crucial.com/upgrade/eMachines-memory/E-Series/EL1600-01-upgrades.html -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Really Weird Question.....
So I just got ahold of an old e-Machine (Model EL1600) with 1GB of memory. I was going to install CEntOS on it and try to run VirtualBox for other OS'es. I am curious to know if I have to stick with the 2GB "max" the specs say the machine can take or if its possible to install a 4GB module that is designed the same? In other words I have seen 2GB DDR PC2700 memory that will fit the casing and work, but I have ALSO seen 4GB DDR PC6400 memory modules with the same number of pins (240) will this work? I would want to have as much memory in there that will allow the VirtualBox to run smoothly.any help would be appreciated! EGO II ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
On 2013-08-19, Joerg Schilling wrote: > If you know about problems, send evidence The problem seems to be that you would rather rant about distributions' licensing and packaging decisions than help the OP. It seems like he would be perfectly happy to use your version of cdrtools, yet you insist on not telling him how to get it! > There are more then 100 bug reports in the redhat bugtracking system (just > change your view to see all closed but unfixed bugs) that confirm problems > with > the binaries distributed by redhat and the users who reported the bugs > confirmed > that upgrading to recent original software fixed the problem. > > It is pretty obvious that redhat does not care about it's users... Still, none of this solves the OP's problem! You do yourself and your software a disservice by being deliberately unhelpful to score political points. (Perhaps that is why distros are reluctant to include your software, preferring a buggy version to one with a difficult author.) --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
On Mon, Aug 19, 2013 at 5:36 PM, Joerg Schilling wrote: > >> >> This isn't aimed at you personally, but the reason people like >> RHEL/CentOS is that the 'no known bugs' status of a developer's >> software release often turns pretty quickly into 'bugs with no known >> fix' when they hit a wider distribution. And developers like to >> change things in ways that break existing interfaces in what they >> think are improvements. > > The Linux kernel and Linux distros are known for breaking things by e.g. > changing interfaces. Yes, that is true in general. RHEL (and thus CentOS) are known for _not_ changing interfaces within the supported life of each major release version. It is extremely rare for any previously working program to be broken by an OS update over that many-year span. And that is a good thing - and why they are popular. > Cdrtools are known for stability and backwardscompatibility while at the same > time enhancing functionality. That stops a little short of saying they would be fully compatible with any previous invocation or library linkage. > I am talking about obvious bugs that apply to the redhat version but not to > the > original code. I am talking about closing unfixed bugs instead of upgrading to > newer versions. I am talking abut redhat that is not doing it's homeworks. Part of the story must be missing here - why does a broken version exist in the first place and why would RedHat have picked it? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
Keith Keller wrote: > On 2013-08-19, Joerg Schilling wrote: > > > > Redhat had more than 100 bugs filed against the "cdrtools" version they > > ship. > > All these bugs could be avoided by upgrading to a recent original version. > > Redhat closed these unfixed bugs instead of doing it's homework that would > > result in updated versions. > > > > So it seems that redhat doesn't care about bug reports. > > None of this is helpful to the OP. You should either point him to your > preferred location for acquiring your version of cdrtools, or provide a > yum repository for RHEL/CentOS users to download rpms. You should warn > him that either of these methods will "officially" break binary > compatibility with upstream (which users need to decide for themselves > if they wish to do that). Please do not write false claims! If you know about problems, send evidence There are more then 100 bug reports in the redhat bugtracking system (just change your view to see all closed but unfixed bugs) that confirm problems with the binaries distributed by redhat and the users who reported the bugs confirmed that upgrading to recent original software fixed the problem. It is pretty obvious that redhat does not care about it's users... Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
Les Mikesell wrote: > On Mon, Aug 19, 2013 at 4:32 PM, Reindl Harald wrote: > > > > maybe you do not know who Joerg Schilling is > > > > he is the one person claiming he is the only one writing a > > working cd-burning software on earth and his fights against > > GPL and Linux are legend over the years > > > > http://lwn.net/Articles/199061/ > > http://slashdot.org/story/06/09/04/1335226/debian-kicks-jrg-schilling > > http://lwn.net/Articles/198171/ Mr. Corbet is not interested on the truth but likes to play games against OSS. He publishes unproven claims and does not give a place to correct his fault. > All I have to say about that is that I wish the GPL were not so > restrictive that it prohibits many potential best-of-breed > combinations of components. But that was it's intent and it isn't > likely to ever change. I'm just glad that people like Larry Wall > understood that early-on and used dual-licensing to make at least some > software usable in more situations. . Don't believe the attacks against OSS from Debian, Mr. Corbet and similar. Sun legal, Oracle legal and even Eben Moglen confirmed that cdrtools is without legal problems. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
Les Mikesell wrote: > On Mon, Aug 19, 2013 at 3:54 PM, Joerg Schilling > wrote: > > >> >> > Would you like to run a Linux kernel from 2004 today? > >> > >> Has the CD format changed since 2004? > > > > This is why you are happy with buggy software from 2004 shipped by redhat > > when > > there is software with no known bugs? > > This isn't aimed at you personally, but the reason people like > RHEL/CentOS is that the 'no known bugs' status of a developer's > software release often turns pretty quickly into 'bugs with no known > fix' when they hit a wider distribution. And developers like to > change things in ways that break existing interfaces in what they > think are improvements. The Linux kernel and Linux distros are known for breaking things by e.g. changing interfaces. Cdrtools are known for stability and backwardscompatibility while at the same time enhancing functionality. > > Redhat had more than 100 bugs filed against the "cdrtools" version they > > ship. > > All these bugs could be avoided by upgrading to a recent original version. > > Redhat closed these unfixed bugs instead of doing it's homework that would > > result in updated versions. > > > > So it seems that redhat doesn't care about bug reports. > > You are in a better position to judge that than me, but the whole > point of RHEL is to never break exiting, previously working interfaces > (and thus their user's programs...) within the life cycle of the > distro. So if they would lose backwards compatibility anywhere by > updating - and perhaps even if it isn't clear that they wouldn't, they > they are correctly following the policy that the people on this list > typically want. Othewise we'd be off reinstalling todays new and > buggy version of some other disto instead of reading email while our > servers keep working. But, maybe it's not so great for desktop type > activity that wasn't feature-complete in 2004. And if you are > talking about bug reports that were made long enough before the 6.0 > release to have gotten the update in, then I'd say you are right > regardless of compatibility. I am talking about obvious bugs that apply to the redhat version but not to the original code. I am talking about closing unfixed bugs instead of upgrading to newer versions. I am talking abut redhat that is not doing it's homeworks. People complain about problems and redhat is ignoring them even though the bug reports contain comments that make it obvious that the right way to deal with the bug is to upgrade to a more recent version. Nothing happens and after a few years the bugs are closed even thoug the bug still exists on redhat. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
On 2013-08-19, Joerg Schilling wrote: > > Redhat had more than 100 bugs filed against the "cdrtools" version they ship. > All these bugs could be avoided by upgrading to a recent original version. > Redhat closed these unfixed bugs instead of doing it's homework that would > result in updated versions. > > So it seems that redhat doesn't care about bug reports. None of this is helpful to the OP. You should either point him to your preferred location for acquiring your version of cdrtools, or provide a yum repository for RHEL/CentOS users to download rpms. You should warn him that either of these methods will "officially" break binary compatibility with upstream (which users need to decide for themselves if they wish to do that). --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
On Mon, Aug 19, 2013 at 4:32 PM, Reindl Harald wrote: > > maybe you do not know who Joerg Schilling is > > he is the one person claiming he is the only one writing a > working cd-burning software on earth and his fights against > GPL and Linux are legend over the years > > http://lwn.net/Articles/199061/ > http://slashdot.org/story/06/09/04/1335226/debian-kicks-jrg-schilling > http://lwn.net/Articles/198171/ All I have to say about that is that I wish the GPL were not so restrictive that it prohibits many potential best-of-breed combinations of components. But that was it's intent and it isn't likely to ever change. I'm just glad that people like Larry Wall understood that early-on and used dual-licensing to make at least some software usable in more situations. . -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
On Mon, Aug 19, 2013 at 3:54 PM, Joerg Schilling wrote: >> >> > Would you like to run a Linux kernel from 2004 today? >> >> Has the CD format changed since 2004? > > This is why you are happy with buggy software from 2004 shipped by redhat when > there is software with no known bugs? This isn't aimed at you personally, but the reason people like RHEL/CentOS is that the 'no known bugs' status of a developer's software release often turns pretty quickly into 'bugs with no known fix' when they hit a wider distribution. And developers like to change things in ways that break existing interfaces in what they think are improvements. > Redhat had more than 100 bugs filed against the "cdrtools" version they ship. > All these bugs could be avoided by upgrading to a recent original version. > Redhat closed these unfixed bugs instead of doing it's homework that would > result in updated versions. > > So it seems that redhat doesn't care about bug reports. You are in a better position to judge that than me, but the whole point of RHEL is to never break exiting, previously working interfaces (and thus their user's programs...) within the life cycle of the distro. So if they would lose backwards compatibility anywhere by updating - and perhaps even if it isn't clear that they wouldn't, they they are correctly following the policy that the people on this list typically want. Othewise we'd be off reinstalling todays new and buggy version of some other disto instead of reading email while our servers keep working. But, maybe it's not so great for desktop type activity that wasn't feature-complete in 2004. And if you are talking about bug reports that were made long enough before the 6.0 release to have gotten the update in, then I'd say you are right regardless of compatibility. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
Les Mikesell wrote: > On Mon, Aug 19, 2013 at 3:23 PM, Joerg Schilling > wrote: > > > > >> > Would you like to run a Linux kernel from 2004 today? > > Has the CD format changed since 2004? This is why you are happy with buggy software from 2004 shipped by redhat when there is software with no known bugs? > > In other words, you either choose a distro that offers up to date packages > > or > > you need to compile yourself. > > I'm sure you realize that no one on this list wants 'up to date' > software as shipped by developers - and why. Is there some compromise > possible where a somewhat vetted, packaged release exists?Or > RedHat gets appropriate bug reports so they fix the broken parts? > Redhat had more than 100 bugs filed against the "cdrtools" version they ship. All these bugs could be avoided by upgrading to a recent original version. Redhat closed these unfixed bugs instead of doing it's homework that would result in updated versions. So it seems that redhat doesn't care about bug reports. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
On Mon, Aug 19, 2013 at 3:23 PM, Joerg Schilling wrote: > > >> > Would you like to run a Linux kernel from 2004 today? Has the CD format changed since 2004? > In other words, you either choose a distro that offers up to date packages or > you need to compile yourself. I'm sure you realize that no one on this list wants 'up to date' software as shipped by developers - and why. Is there some compromise possible where a somewhat vetted, packaged release exists?Or RedHat gets appropriate bug reports so they fix the broken parts? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] qemu-kvm package?
On Mon, Aug 19, 2013 at 1:22 PM, Gene Poole wrote: > Let me say that your question does not match your subject. > > I run a 32-bit CentOS with virt-manager installed to monitor the virtual > machines running on a 64-bit CentOS. That leaves the following: > > Is it because I'm running CentOS 5.9 in both cases? > Or is it because I performed a full install from a DVD in both cases? > > That being said, It's a fact that virt-manager will run on a 32-bit OS. No, I think the subject is right. You can install/run virt-manager and use it as a client to 64-bit systems (in 6.x also). But you can't connect to localhost even though there is a libvirtd because of the missing qemu-kvm package. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
ken wrote: > > There is nothing like: cdrtools-2.01-10.7.el5 > > [cdrtools-2.01-10.7.el5 ist einmalig???] > > You're saying this is the preferred package, yes? and it will have the > functionality needed? If yes and yes, where does one get that package? > > Note that my rpm command output above says: > Source RPM: cdrtools-2.01-10.7.el5.src.rpm A version cdrtools-2.01-10.7.el5 does not exist. > > > > If you like to know what you are using, I recommend to call: > > > > cdrecord -version > > cdda2wav -version > > readcd -version > > mkisofs -version > > So there should be something definitive to say about these: > > $ cdrecord -version > Cdrecord-Clone 2.01 (cpu-pc-linux-gnu) Copyright (C) 1995-2004 J???rg > Schilling > Note: This version is an unofficial (modified) version with DVD support > Note: and therefore may have bugs that are not present in the original. > Note: Please send bug reports or support requests to > http://bugzilla.redhat.com/bugzilla > Note: The author of cdrecord should not be bothered with problems in > this version. So this is a release where somebody did rip off the working original DVD support code and replaced it with half baken other code that is known not to work correctly. You still get a completely outdated software. > $ cdda2wav -version > cdda2wav version 2.01_linux_2.6.18-92.1.10.el5_x86_64_x86_64 > $ readcd -version > readcd 2.01 (cpu-pc-linux-gnu) Copyright (C) 1987, 1995-2003 J???rg Schilling > $ mkisofs -version > mkisofs 2.01 (cpu-pc-linux-gnu) Be careful, this mkisofs is full of bugs and creates ISO buggy images. > Without knowing what is *essential* in the "-version" output, it's hard If I have trouble with a piece of software, I call xxx -version and if that prints 2004 as the newest date, I know that something is wrong. > to say anything definitive. Jörg, I'm not a lawyer, but I know it's > possible to get a tradename which then others could use only with your > permission. So is you owned "Jörg's unmessed with software" or "Jörg's > truly functional code", you could put that in the "-version" output, but > no one else could unless they had your permission... iow, they couldn't > muck with your code and then confuse people by saying it's your code. > (I'm assuming that this is what you mean by "original".) This then > would constitute a definitive determination. > > There is no need to get a trademark as the name "cdrecord" is a trademark even wihtout registering it. > >>> Programs like grip and cdparanoia don't care about the usability of the > >>> extracted files for later burning tasks and they are not able to extract > >>> so > >>> called "un-CDs". > > What's an "un-CD"? Did you try google? Intentionally broken CD shaped media sold by the music industry. > What I hear is that you and Redhat/CentOS have different ideas as to > what "up-to-date" means. My system is completely up-to-date as defined > by the latter. Someone who did not do his homework for 9 years could be called dead. It seems that your distro missed 97 updated versions from cdrtools. If FORD did stop creating newer models with Model T, this was still "up to date", but would you like to use it today? > For a person of considerable talents as you, it shouldn't be a big deal > to put together an RPM package for currently supported RH/cOS (v. 5.9 > and 6.x) with the needed utilities and which wouldn't break dependent > apps such as k3b, grip, gnome-cd, etc. Then these two disparate worlds > would be united, at least as far as burning and ripping CDs and DVDs goes. > You miss the point: I write software that compiles/runs nearly everywhere from source. It is the duty of the distros to create packages. I cannot create packages for > 100 OS/cpu combinations. > > Would you like to run a Linux kernel from 2004 today? > > No. But I wouldn't either want to go back to the days before package > management. I am sure that if you go to your favorite PC shop and this shop has no model from after 2004, you would ask the dealer to get newer items or chose another dealer. In other words, you either choose a distro that offers up to date packages or you need to compile yourself. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
On 08/19/2013 09:58 AM Joerg Schilling wrote: > ken wrote: > >>> If you are using this bad fork that is from September 2004 - 9 years ago, >>> you >>> suffer from many problems, like incomplete documentation and many bugs that >>> cannot be found in the original software. >> >> cdrecord and readcd are both part of this package: >> >> $ rpm -qi cdrecord >> Name: cdrecord Relocations: (not relocatable) >> Version : 2.01 Vendor: CentOS >> Release : 10.7.el5 Build Date: Thu 26 Feb 2009 >> 06:30:50 PM EST >> Install Date: Mon 05 Sep 2011 03:03:56 PM EDT Build Host: >> chamkaur.karan.org >> Group : Applications/ArchivingSource RPM: >> cdrtools-2.01-10.7.el5.src.rpm >> Size: 1383954 License: GPL >> Signature : DSA/SHA1, Sun 08 Mar 2009 09:45:19 PM EDT, Key ID >> a8a447dce8562897 >> Packager: Karanbir Singh >> URL : http://cdrecord.berlios.de/old/private/cdrecord.html >> Summary : A command line CD/DVD recording program. >> Description : >> >> >> The "Description" states nothing about it being from a bad fork from >> 2004. :) So how would anyone know? > > You will not get useful version information from calling "rpm". > > There is nothing like: cdrtools-2.01-10.7.el5 [cdrtools-2.01-10.7.el5 ist einmalig???] You're saying this is the preferred package, yes? and it will have the functionality needed? If yes and yes, where does one get that package? Note that my rpm command output above says: Source RPM: cdrtools-2.01-10.7.el5.src.rpm > > If you like to know what you are using, I recommend to call: > > cdrecord -version > cdda2wav -version > readcd -version > mkisofs -version So there should be something definitive to say about these: $ cdrecord -version Cdrecord-Clone 2.01 (cpu-pc-linux-gnu) Copyright (C) 1995-2004 J�rg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. $ cdda2wav -version cdda2wav version 2.01_linux_2.6.18-92.1.10.el5_x86_64_x86_64 $ readcd -version readcd 2.01 (cpu-pc-linux-gnu) Copyright (C) 1987, 1995-2003 J�rg Schilling $ mkisofs -version mkisofs 2.01 (cpu-pc-linux-gnu) > > If you are using original software, you will see someting like: > > Cdrecord-ProDVD-ProBD-Clone 3.01a16 (i386-pc-solaris2.11) Copyright (C) > 1995-2013 Joerg Schilling > > If one of the commends does not print a message like this, you should be > careful. Well, I'm always careful (except that one time I backed my car into the garage door). Without knowing what is *essential* in the "-version" output, it's hard to say anything definitive. Jörg, I'm not a lawyer, but I know it's possible to get a tradename which then others could use only with your permission. So is you owned "Jörg's unmessed with software" or "Jörg's truly functional code", you could put that in the "-version" output, but no one else could unless they had your permission... iow, they couldn't muck with your code and then confuse people by saying it's your code. (I'm assuming that this is what you mean by "original".) This then would constitute a definitive determination. > > BTW: cdrtools-2.01 is from September 2004. > >>> Programs like grip and cdparanoia don't care about the usability of the >>> extracted files for later burning tasks and they are not able to extract so >>> called "un-CDs". What's an "un-CD"? >>> >>> cdda2wav knows about the writing process, feteches cddb data and includes a >>> bug-fixed libparanoia. >>> >>> Recent man pages also contain several related examples. Did you read a >>> recent >>> manpage and follow the EXAMPLE section? >> >> I don't know what is meant here by "recent". Which is the earliest >> version which contains the functionality required? > > The features in question are in since a longer time, but if you are on a Linux > distro that does not deliver up-to-date software, you should expect that there > are bugs in your version that never have been in the original software. What I hear is that you and Redhat/CentOS have different ideas as to what "up-to-date" means. My system is completely up-to-date as defined by the latter. For a person of considerable talents as you, it shouldn't be a big deal to put together an RPM package for currently supported RH/cOS (v. 5.9 and 6.x) with the needed utilities and which wouldn't break dependent apps such as k3b, grip, gnome-cd, etc. Then these two disparate worlds would be united, at least as far as burning and ripping CDs and DVDs goes. > > Since 2004, the man pages have been completely rewritten for better > readability, the features have been massively enhanced (they did more than > double > since
[CentOS] LVM RAID0 and SSD discards/TRIM
I'm trying to work out the kinks of a proprietary, old, and clunky application that runs on CentOS. One of its main problems is that it writes image sequences extremely non-linearly and in several passes, using many CPUs, so the sequences get very fragmented. The obvious solution to this seems to be to use SSDs for its output, and some scripts that will pick up and copy our the sequences in proper order once it's done. I have two 512GB SSDs, and I've used LVM to set up a RAID0 between them. I've got that part running, but since I'm on CentOS 5.8 (which is what this application officially supports), I don't have a kernel with SSD discard support, and after a few days (I told you, this application is write intensive), things get very slow. Using hdparm to secure erase the drives and recreating the LVM RAID0 gets things back to speed again, but that's obviously not ideal. So, from what I understand, if I can get this thing running on CentOS 6.4, I'll get kernel discard support, and discard support in LVM when running a RAID0. I'm using ext4. Is that correct? Will this solve my problem? I want to confirm that discard support works on a RAID0 of SSDs using LVM and ext4 before I start working on getting this legacy application to run on a newer CentOS. -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] qemu-kvm package?
Let me say that your question does not match your subject. I run a 32-bit CentOS with virt-manager installed to monitor the virtual machines running on a 64-bit CentOS. That leaves the following: Is it because I'm running CentOS 5.9 in both cases? Or is it because I performed a full install from a DVD in both cases? That being said, It's a fact that virt-manager will run on a 32-bit OS. Thanks, Gene Poole ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Xyratex disk units
On Aug 17, 2013, at 5:16 PM, John R Pierce wrote: > On 8/16/2013 10:51 AM, Tony Schreiner wrote: >> Some years ago I installed a NAS unit from Exanet which consists of 2 >> rebadged IBM x3650 head nodes and a couple of Xyratex disk shelves with a >> total of 96 TB of raw disk, connected by fibre channel. The operating system >> is based on CentOS 4.4, but is modified, and runs a proprietary file system. >> It has pretty good performance and I'm happy with it. > > I would consider dumping the head nodes, and connecting the FC arrays > directly to the host HBA, and running them as fiber JBOD to a dedicated > host, which could run whatever sort of mdraid, lvm, file system you > want. or something like FreeNAS with ZFS and FreeBSD, then share stuff > via SMB, NFS, etc. > It may come to that eventually. Though I don't know why use say dump the head nodes, they are adequate servers (unless you mean overwrite them). The main reason I'm not doing that now, is that the Exanet software provides coherent caching between the 2 nodes for enhanced redundancy and performance. Additionally, I am stuck with the LUNs provides by the Xyratex until I am able to find a way to manage them. Tony ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL Subscriptions
Joseph Spenner wrote: > On 08/18/2013 09:30 PM, Anthony K wrote: >> >> I was recently approached by Dell stating that I HAVE TO renew my Red >> Hat Subscriptions. I challenged this statement and was informed that >> this has always been the case and that all servers I have bought off of >> Dell over the years need to have current subscription! >> >> I've been searching the Red Hat website to find where this is stated but >> can't seem to locate this info. So, is Dell having me on? > > Does seem kinda harsh. Maybe it's the only way Dell can support you? > Without subscriptions/license, I don't think yum updates will work unless > you modify the repos manually. > > The only time anyone at my company ever contacted Red Hat for support was > to figure out how to use the license they bought! It didn't take long > before we dropped that nonsense and started using CentOS. > Several things: should we assume that you bought the servers with RHEL licenses? We have a lot of Dells, but we buy them without licenses, since we intend to install CentOS (though we do have one or two that we bought with the licenses, so that we can actually get upstream to fix bugs and add enhancements, such as native PIV/CAC card support...). However, I don't see how they can force you to maintain the license. You can also switch over to CentOS (he says, here on the CentOS mailing list), and I can't see that they'll say anything. I speak to them a fair bit, but that's about hardware, and they have zero problems when I tell them we run CentOS (given that their OMSA disks boot... CentOS ). mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL Subscriptions
On 08/18/2013 09:30 PM, Anthony K wrote: > Hello List Members. > > I was recently approached by Dell stating that I HAVE TO renew my Red > Hat Subscriptions. I challenged this statement and was informed that > this has always been the case and that all servers I have bought off of > Dell over the years need to have current subscription! > > I've been searching the Red Hat website to find where this is stated but > can't seem to locate this info. So, is Dell having me on? Does seem kinda harsh. Maybe it's the only way Dell can support you? Without subscriptions/license, I don't think yum updates will work unless you modify the repos manually. The only time anyone at my company ever contacted Red Hat for support was to figure out how to use the license they bought! It didn't take long before we dropped that nonsense and started using CentOS. __ If life gives you lemons, keep them-- because hey.. free lemons. "♥ Sticker" fixer: http://microflush.org/stuff/stickers/heartFix.htm ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
ken wrote: > > If you are using this bad fork that is from September 2004 - 9 years ago, > > you > > suffer from many problems, like incomplete documentation and many bugs that > > cannot be found in the original software. > > cdrecord and readcd are both part of this package: > > $ rpm -qi cdrecord > Name: cdrecord Relocations: (not relocatable) > Version : 2.01 Vendor: CentOS > Release : 10.7.el5 Build Date: Thu 26 Feb 2009 > 06:30:50 PM EST > Install Date: Mon 05 Sep 2011 03:03:56 PM EDT Build Host: > chamkaur.karan.org > Group : Applications/ArchivingSource RPM: > cdrtools-2.01-10.7.el5.src.rpm > Size: 1383954 License: GPL > Signature : DSA/SHA1, Sun 08 Mar 2009 09:45:19 PM EDT, Key ID > a8a447dce8562897 > Packager: Karanbir Singh > URL : http://cdrecord.berlios.de/old/private/cdrecord.html > Summary : A command line CD/DVD recording program. > Description : > > > The "Description" states nothing about it being from a bad fork from > 2004. :) So how would anyone know? You will not get useful version information from calling "rpm". There is nothing like: cdrtools-2.01-10.7.el5 If you like to know what you are using, I recommend to call: cdrecord -version cdda2wav -version readcd -version mkisofs -version If you are using original software, you will see someting like: Cdrecord-ProDVD-ProBD-Clone 3.01a16 (i386-pc-solaris2.11) Copyright (C) 1995-2013 Joerg Schilling If one of the commends does not print a message like this, you should be careful. BTW: cdrtools-2.01 is from September 2004. > > Programs like grip and cdparanoia don't care about the usability of the > > extracted files for later burning tasks and they are not able to extract so > > called "un-CDs". > > > > cdda2wav knows about the writing process, feteches cddb data and includes a > > bug-fixed libparanoia. > > > > Recent man pages also contain several related examples. Did you read a > > recent > > manpage and follow the EXAMPLE section? > > I don't know what is meant here by "recent". Which is the earliest > version which contains the functionality required? The features in question are in since a longer time, but if you are on a Linux distro that does not deliver up-to-date software, you should expect that there are bugs in your version that never have been in the original software. Since 2004, the man pages have been completely rewritten for better readability, the features have been massively enhanced (they did more than double since September 2004) and many bugs have been fixed. In January 2010, cdda2wav e.g. added support for hidden tracks. Mkisofs added support for libfind in 2006 and cdrecord added support for BluRay in 2007. Would you like to run a Linux kernel from 2004 today? Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL Subscriptions
On 08/18/2013 09:30 PM, Anthony K wrote: > Hello List Members. > > I was recently approached by Dell stating that I HAVE TO renew my Red > Hat Subscriptions. I challenged this statement and was informed that > this has always been the case and that all servers I have bought off of > Dell over the years need to have current subscription! > > I've been searching the Red Hat website to find where this is stated but > can't seem to locate this info. So, is Dell having me on? The only way Dell can FORCE you to update your license is if your original purchase SAID you would maintain the subscriptions for a period of time. You should be able to check that and see. Are the servers "bought" by you or "leased" by you? If leased, they might be able to dictate the OS as well. If neither of those are the case (you are leasing or you agreed to maintain the OS for a period of time) then you can do whatever you want with the OS and Dell will provide hardware and not software support. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] k3b -> cddb doesn't work
On 08/18/2013 04:13 PM Joerg Schilling wrote: > ken wrote: > >> Thanks for your reply. As late as November 2012 I always used the CLI >> for copying *data* CDs, using cdrecord and readcd. But though I read >> and studied manpages and scads of documentation, I never had any luck >> cloning a music CD using these commands. So I'd doubt I could figure >> out on my own, in addition to cloning a CD, adding in the song titles etc. > > Are you using recent original software or are you using an outdated, dead > and defective fork that is distributed by some non-OpenSource oriented > Linux sources? > > If you are using this bad fork that is from September 2004 - 9 years ago, you > suffer from many problems, like incomplete documentation and many bugs that > cannot be found in the original software. cdrecord and readcd are both part of this package: $ rpm -qi cdrecord Name: cdrecord Relocations: (not relocatable) Version : 2.01 Vendor: CentOS Release : 10.7.el5 Build Date: Thu 26 Feb 2009 06:30:50 PM EST Install Date: Mon 05 Sep 2011 03:03:56 PM EDT Build Host: chamkaur.karan.org Group : Applications/ArchivingSource RPM: cdrtools-2.01-10.7.el5.src.rpm Size: 1383954 License: GPL Signature : DSA/SHA1, Sun 08 Mar 2009 09:45:19 PM EDT, Key ID a8a447dce8562897 Packager: Karanbir Singh URL : http://cdrecord.berlios.de/old/private/cdrecord.html Summary : A command line CD/DVD recording program. Description : The "Description" states nothing about it being from a bad fork from 2004. :) So how would anyone know? > >> I guess I wasn't clear about ripping a CD. Grip, as I said handles this >> fine, including downloading the cddb data. So if I wanted to create wav >> (or ogg or other) files, I could use grip. But for some CDs, a series >> of wav files just doesn't play back well; I'm talking about music in >> which one track blends into the following track with no break in >> between. These don't play back well because audio players insert a >> break (perhaps because they need a second or so to load that second >> track) and, in addition, often this break isn't in a good moment. So >> I've decided to just burn the entire CD to avoid hearing the breaks. So >> is it even possible to save the cddb data to a copied CD? > > Programs like grip and cdparanoia don't care about the usability of the > extracted files for later burning tasks and they are not able to extract so > called "un-CDs". > > cdda2wav knows about the writing process, feteches cddb data and includes a > bug-fixed libparanoia. > > Recent man pages also contain several related examples. Did you read a recent > manpage and follow the EXAMPLE section? I don't know what is meant here by "recent". Which is the earliest version which contains the functionality required? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL Subscriptions
> How does Dell know what OS your are running? > Should they know what OS you are running? > Dell provides the hardware only? Dell sells OEM RHEL and standard (Red Hat) RHEL as a software reseller. In OEM RHEL, Dell provides all but the highest level (passing the highest level back to Red Hat ) support. In standard RHEL, they are just selling you the same thing you would buy from Red Hat. They would know when both are to expire, but ironically they are more in tune with when the standard RHEL that they sell you is set to expire. Barry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL Subscriptions
On 8/18/2013 7:30 PM, Anthony K wrote: > I was recently approached by Dell stating that I HAVE TO renew my Red > Hat Subscriptions. I challenged this statement and was informed that > this has always been the case and that all servers I have bought off of > Dell over the years need to have current subscription! Here's my take on that... If you don't keep your RHEL support contract active, you will no longer be able to use yum to do online installs or updates. And, Dell will be less able to support you in whatever support contract you have with them. Your mileage may vary. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL Subscriptions
On 19.Aug.2013, at 04:30, Anthony K wrote: > I was recently approached by Dell stating that I HAVE TO renew my Red > Hat Subscriptions. How does Dell know what OS your are running? Should they know what OS you are running? Dell provides the hardware only? I am confused about this. I do not have experiences with Dell, though. -- Markus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
