Re: [CentOS] Sun Microsystems Quad gigabit ethernet nic compatibility
On Thu, 2015-01-01 at 22:01 -0800, John R Pierce wrote: > On 1/1/2015 9:41 PM, mechy2k2000 wrote: > > Hello I am thinking of buying this card to and wanted to know if this NIC > > is supported. The card is a Sun Microsystems PCI-X Quad-Port Gigabit > > Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on how well the > > card plays with centos and also proxmox ve (if any of you use that distro ) > > I've not tried that card on anything other than Sun UltraSparc running > Solaris 9 and 10, but rumor has it Linux has a 'cassini' driver that > supports the Sun GigaSwift NIC on those. > > > > > I see. My gut is starting to tell me its not worth the time to replace it, if this Sun NIC doesnt play nice with Linux. I also intend to use the card with Proxmox VE which is debian based. ~ Rafeal Stewart ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Sun Microsystems Quad gigabit ethernet nic compatibility
On 1/1/2015 9:41 PM, mechy2k2000 wrote: Hello I am thinking of buying this card to and wanted to know if this NIC is supported. The card is a Sun Microsystems PCI-X Quad-Port Gigabit Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on how well the card plays with centos and also proxmox ve (if any of you use that distro ) I've not tried that card on anything other than Sun UltraSparc running Solaris 9 and 10, but rumor has it Linux has a 'cassini' driver that supports the Sun GigaSwift NIC on those. -- 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
[CentOS] Sun Microsystems Quad gigabit ethernet nic compatibility
Hello I am thinking of buying this card to and wanted to know if this NIC is supported. The card is a Sun Microsystems PCI-X Quad-Port Gigabit Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on how well the card plays with centos and also proxmox ve (if any of you use that distro ) If things don't seem to work I may bite the bullet and buy an Intel card thanks Rafeal Stewart ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Secret incantations for virt-viewer?
On Tue, Dec 30, 2014 at 4:08 PM, Bill Gee wrote: > > Thanks! I changed the qemu.conf file to listen on 0.0.0.0. That works - > I can > connect to the virtual machines using a VNC client. > Listening on 0.0.0.0 listens on all network interfaces. Mark's comment is not a major concern unless your KVM host is directly connected to the Internet (no firewall). * You should consider adding firewall rules on your KVM host none the less. > > The problem with VNC is that the port number assigned to a particular VM > depends on the order in which it is started. There is no command-line > option > for VNC that will attach to a VM by name ... only by display number or > port > number. > You can specify the VNC port when creating a host. But as far as connecting via VNC to a host VM by name without also having to add a port # suffix, that is more difficult. Easiest way for you to do so is to create shell aliases for each one. For my own deployments, I have a wiki page which documents what VNC ports are used. There's also virsh commands to extract info. virsh dominfo virsh vncdisplay > > With virt-viewer I can name the domain on the command line. It is > unambiguous > - There is no doubt about which VM it will connect to. > > I found where the VNC port can be fixed in the XML file that defines each > VM. > However, it is a manual process. I have not found a way to set it using > virsh. > Yes, a manual process. One would think there's a way to change it via virsh, but that could/would be a problem for a running VM. virt-install has options for specifying VNC ports. > > I found where virsh can report the VNC port number used by a domain. > However, > the computers from where I am running VNC client do not have virsh > installed. > They do not need virsh. SSH to the KVM host and run the virsh commands from there. > > Somewhere in all this experimenting I have managed to break virt-viewer > again. > It was working, but no more. Argh! Good thing this is all happening on > test > computers! > > Bill Gee -- ---~~.~~--- Mike // SilverTip257 // ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Design changes are done in Fedora
On Thu, January 1, 2015 3:15 pm, James B. Byrne wrote: > > On Wed, December 31, 2014 12:03, Warren Young wrote: >> >> So, cope with change. >> > > Is one to infer from your mantra 'cope with change' that one is not > supposed > to express any opinion whatsoever, ever, on any forum; on the externalised > cost of changes made to software with no evident technical justification? > And > that to do so is evidence of some moral or intellectual defect in oneself? > > We all cope with change until we die. That is not a philosophy or > program. It > is an observation on the state of existence; and is no more useful than > the > observation that, eventually, we all die. > First of all, I must say that I agree with you, James, on almost all of your points. Or disagree with your opponents on majority of their points. Moreover, I do suffer myself from "unnecessary change", thus for some tasks I even switched to different system (if the stuff that affects you is already in the kernel, you can not just switch from one Linux distro to another ;-( I have been suggested to shut up when I was too loud/persistent saying about that (luckily I do not remember by whom and do not care to remember ;-) Nonetheless, even though I try to speak up when I'm unhappy thus hopefully I'm providing feedback for developers and architects, I came to realizing that [open source] software developers most likely will not listen to me, even though I do represent certain number of their end customers. Take as example my last worst displeasure. I upgraded my FreeBSD workstation from 10.0 to 10.1 which made me step up from Gnome 2 to Gnome 3. And I can not bear the change. So, after a couple of weeks of frustration of just trying to do what I usually do on workstation I came to decision to abandon Gnome altogether. Whoever did that transition knows what I'm talking about. It is pretty much as switching from CentOS 6 to CentOS 7. What I told myself (not that I'm suggesting others they should...) is this. Developers often work without monetary reward and their only reward is seeing the result of their programming. What they get best reward is from seeing new, fancy... Which kind of contradicts utilitarian programming (to achieve particular goal your program is for). In last case we always were following the principle (yes, I was programmer too): do not make any changes unless they are absolutely necessary. Which appears to contradict goals many developers have (KDE, GNOME, Firefox, Windows 8,... you continue the list). All seem to abandon structured logical tree-like arrangements of your tools, and switch you to stupid search for what you need. Welcome to ipad generation, folks! Thus, I decided for myself to tolerate the change as long as I can and keep being grateful to developers whose products I use, but switch to something more suitable for my way of working with things as soon as I can not stand the change. I hope, this helps someone ;-) Happy New Year everybody! (and welcome to ipad generation! ;-) Valeri Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] how to delete a trashed kernel
I have a screwed up disk arrangement, but I have had no trouble because of it after using it over a year. Recently I did a yum update. After starting the update, which included a new kernel, it seemed to either freeze or loop. It was a long time at the prompt and I got impatient and did a Ctrl C. I then tried to re-boot. The result was a kernel panic. I am keeping 5 kernels and when I select the second kernel it boots OK. Now I would like to remove the bad kernel. One other thing that I don't understand and may be relevant, the name of the bad package is kernel-2.6.32-504.3.3.el6.centos-plus.i386 I have never noticed a "centos-plus" in a kernel name before. Does the centos-plus repo deal out kernels?I have tried yum remove and "gpk application" (add and remove software) with no luck.I have tried google, but all the solutions for kernel deletions were to delete old kernels. I don't want to do that because I would be deleting my backups. I am in no hurry because I can still boot and it is possible that if I can wait through several kernel updates yum might delete the bad one after an update. I should have mentioned that I am using grub2 to boot, although I don't think that has anything to do with deleting the kernel package.I would appreciate any advice (except "go back to windows") ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Design changes are done in Fedora
On Wed, December 31, 2014 12:03, Warren Young wrote: > > So, cope with change. > Is one to infer from your mantra 'cope with change' that one is not supposed to express any opinion whatsoever, ever, on any forum; on the externalised cost of changes made to software with no evident technical justification? And that to do so is evidence of some moral or intellectual defect in oneself? We all cope with change until we die. That is not a philosophy or program. It is an observation on the state of existence; and is no more useful than the observation that, eventually, we all die. -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Happy New Year!
Happy new year, kids! http://img.nux.ro/mL4-hnypicard.jpg -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Jake Shipton" > To: "CentOS mailing list" > Sent: Thursday, 1 January, 2015 16:38:39 > Subject: Re: [CentOS] Happy New Year! > On 31/12/14 22:12, Ljubomir Ljubojevic wrote: >> On behalf of the CentOS project I wish you Happy New Year! >> >> Happy New Year! >> > > Happy New Year all! I hope you all have a great new year! > > (I know I'm a little late to the party... but hey, better late than > never!) > > Kind Regards, > Jake Shipton (JakeMS) > GPG Key: 0xE3C31D8F > GPG Fingerprint: 7515 CC63 19BD 06F9 400A DE8A 1D0B A5CF E3C3 1D8F > ___ > 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] Design changes are done in Fedora
On 12/29/2014 09:04 PM, Warren Young wrote: On Dec 29, 2014, at 4:03 PM, Les Mikesell wrote: On Mon, Dec 29, 2014 at 3:03 PM, Warren Young wrote: the world where you design, build, and deploy The System is disappearing fast. Sure, if you don't care if you lose data, you can skip those steps. How did you jump from incremental feature roll-outs to data loss? There is no necessary connection there. In fact, I’d say you have a bigger risk of data loss when moving between two systems released years apart than two systems released a month apart. That’s a huge software market in its own right: legacy data conversion. If your software is DBMS-backed and a new feature changes the schema, you can use one of the many available systems for managing schema versions. Or, roll your own; it isn’t hard. You test before rolling something to production, and you run backups so that if all else fails, you can roll back to the prior version. None of this is revolutionary. It’s just what you do, every day. when it breaks it's not the developer answering the phones if anyone answers at all. Tech support calls shouldn’t go straight to the developers under any development model, short of sole proprietorship, and not even then, if you can get away with it. There needs to be at least one layer of buffering in there: train up the secretary to some basic level of cluefulness, do everything via email, or even hire some dedicated support staff. It simply costs too much to break a developer out of flow to allow a customer to ring a bell on a developer’s desk at will. The world is moving toward incrementalism, where the first version of The System is the smallest thing that can possibly do anyone any good. That is deployed ASAP, and is then built up incrementally over years. That works if it was designed for rolling updates. Most stuff isn’t, Since we’re contrasting with waterfall development processes that may last many years, but not decades, I’d say the error has already been made if you’re still working with a waterfall-based methodology today. The first strong cases for agile development processes were first made about 15 years ago, so anything started 7 years ago (to use the OP’s example) was already disregarding a shift a full software generation old. some stuff can't be. Very little software must be developed in waterfall fashion. Avionics systems and nuclear power plant control systems, for example. Such systems make up a tiny fraction of all software produced. A lot of commercial direct-to-consumer software also cannot be delivered incrementally, but only because the alternative messes with the upgrade treadmill business model. Last time I checked, this sort of software only accounted for about ~5% of all software produced, and that fraction is likely dropping, with the moves toward cloud services, open source software, subscription software, and subsidized software. The vast majority of software developed is in-house stuff, where the developers and the users *can* enter into an agile delivery cycle. Where did you get the 5% from according to google there are "over 200 billion lines of existing COBOL code, much of it running mission-critical 24/7 applications, it is simply too costly (in the short run) for many organizations to convert." And what about Fortran, RPG etc. Also how big is the outfit you work for? Sounds like you have no shortage of help, a lot of place don't have unlimited resources like you seem to have. Instead of trying to go from 0 to 100 over the course of ~7 years, you deliver new functionality to production every 1-4 weeks, achieving 100% of the desired feature set over the course of years. If you are, say, adding up dollars, how many times do you want that functionality to change? I’m not sure what you’re asking. If you’re talking about a custom accounting system, the GAAP rules change several times a year in the US: http://www.fasb.org/jsp/FASB/Page/SectionPage&cid=1176156316498 The last formal standard put out by FASB was 2009, and they’re working on another version all the time. Chances are good that if you start a new 7-year project, a new standard will be out before you finish. If instead you’re talking about the cumulative cost of incremental change, it shouldn’t be much different than the cost of a single big-bang change covering the same period. In fact, I’d bet the incremental changes are easier to adopt, since each change can be learned piecemeal. A lot of what people are crying about with EL7 comes down to the fact that Red Hat is basically doing waterfall development: many years of cumulative change gets dumped on our HDDs in one big lump. Compare a rolling release model like that of Cygwin or Ubuntu (not LTS). Something might break every few months, which sounds bad until you consider that the alternative is for *everything* to break at the same time, every 3-7 years. I’m not arguing for CentOS/RHE
Re: [CentOS] Happy New Year!
On 31/12/14 22:12, Ljubomir Ljubojevic wrote: > On behalf of the CentOS project I wish you Happy New Year! > > Happy New Year! > Happy New Year all! I hope you all have a great new year! (I know I'm a little late to the party... but hey, better late than never!) Kind Regards, Jake Shipton (JakeMS) GPG Key: 0xE3C31D8F GPG Fingerprint: 7515 CC63 19BD 06F9 400A DE8A 1D0B A5CF E3C3 1D8F ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
