Re: [CentOS] A question about why the function "recv" return 0
> after the ssl handshake, the client side reset the tcp connection. Client doesn’t like TLS cypher list. Client doesn’t have intermediate certificate. Server needs intermediate certificate configured. Client needs remote certificate “installed”. Many more TLS issues. > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about why the function "recv" return 0
I have used tcpdump to capture the data packets and found that after the ssl handshake, the client side reset the tcp connection. Is there any method to pinpoint the culprit who drops the tcp connection? At 2018-12-18 01:58:36, "Fred Smith" wrote: >On Mon, Dec 17, 2018 at 01:30:14PM +0800, yf chu wrote: >> I am a website developer. We deploy a Nginx server on centos to provide >> HTTP services. Recently, some customers of our website were complaining >> about that occasionally they could not open the webpage, the web browser >> show that the tcp connection was reset. I checked the Nginx logs and source >> code and found that the function "recv" return 0 when some customers made >> HTTP requests. Our customers have confirmed that their network was ok at >> that time. Now, I could not find any clue about this issue. Is there any >> solution to find the reason? Does it have something to do with firewall, or >> ISP? Can we find something from the system log? > >All my references say that recv() returns zero when the link has been >shut down cleanly by the other end. > >You say that the other end hasn't done so, but possibly there are one >or more proxies in the middle,... maybe one of them has dropped the >link for some reason. > >-- > Fred Smith -- fre...@fcshome.stoneham.ma.us - > "For the word of God is living and active. Sharper than any double-edged > sword, it penetrates even to dividing soul and spirit, joints and marrow; > it judges the thoughts and attitudes of the heart." > Hebrews 4:12 (niv) -- >___ >CentOS mailing list >CentOS@centos.org >https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about why the function "recv" return 0
On Mon, Dec 17, 2018 at 01:30:14PM +0800, yf chu wrote: > I am a website developer. We deploy a Nginx server on centos to provide HTTP > services. Recently, some customers of our website were complaining about that > occasionally they could not open the webpage, the web browser show that the > tcp connection was reset. I checked the Nginx logs and source code and found > that the function "recv" return 0 when some customers made HTTP requests. Our > customers have confirmed that their network was ok at that time. Now, I > could not find any clue about this issue. Is there any solution to find the > reason? Does it have something to do with firewall, or ISP? Can we find > something from the system log? All my references say that recv() returns zero when the link has been shut down cleanly by the other end. You say that the other end hasn't done so, but possibly there are one or more proxies in the middle,... maybe one of them has dropped the link for some reason. -- Fred Smith -- fre...@fcshome.stoneham.ma.us - "For the word of God is living and active. Sharper than any double-edged sword, it penetrates even to dividing soul and spirit, joints and marrow; it judges the thoughts and attitudes of the heart." Hebrews 4:12 (niv) -- ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] A question about why the function "recv" return 0
I am a website developer. We deploy a Nginx server on centos to provide HTTP services. Recently, some customers of our website were complaining about that occasionally they could not open the webpage, the web browser show that the tcp connection was reset. I checked the Nginx logs and source code and found that the function "recv" return 0 when some customers made HTTP requests. Our customers have confirmed that their network was ok at that time. Now, I could not find any clue about this issue. Is there any solution to find the reason? Does it have something to do with firewall, or ISP? Can we find something from the system log? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] A question about smb.conf between C6 and c7
Are there any? Will a C 6 conf work under C 7? A pointer to a README would be appreciated on configuration differences, if any. Thanks in advance. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about NBD kernel module...
On Mon, Feb 12, 2018 at 7:59 AM, Raghuram Devarakonda wrote: > Hi, > > I would like to mount a device using NBD protocol on CentOS 7 but it looks > like the module is not available by default in the kernel. Is there a way I > can install it (like from a rpm somewhere)? I found instructions to build > such a module but want to make sure that it is not already available in > some repo before I go ahead with building. > > Any help is greatly appreciated. You can do one (or both) of the following: (1) File a request on http://bugs.centos.org and ask that CONFIG_BLK_DEV_NBD be enabled in the centosplus kernel. (2) File a request on http://elrepo.org/bugs and ask for a driver (kmod package) for that. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] A question about NBD kernel module...
Hi, I would like to mount a device using NBD protocol on CentOS 7 but it looks like the module is not available by default in the kernel. Is there a way I can install it (like from a rpm somewhere)? I found instructions to build such a module but want to make sure that it is not already available in some repo before I go ahead with building. Any help is greatly appreciated. Thanks, Raghu ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question on networking (CentOS 6)
seems to be a driver issue or something, according to some co-workers. Thanks for the help, but I guess I need to upgrade the OS or use another card. ThxKM From: KM To: KM ; CentOS mailing list Sent: Monday, February 13, 2017 1:31 PM Subject: Re: [CentOS] A question on networking (CentOS 6) Like I said, wishful thinking. The light is still out, so it could be the HW. I ran those commands (ip addr show, ip route show) on the 2 servers. The output is identical except for the IP addresses and the MAC addresses, except on the server with the new card, it is missing the following IPV6 info for the interface name p2p1 which is the interface in question. inet6 fe80::6a05:caff:fe06:9122/64 scope link valid_lft forever preferred_lft forever Somehow I doubt we are using IPV6 but does it need to be there for some reason? and if so , what do I do about it. I apologize if these questions make no sense. Other than the original setup, and sometimes editing the ifcfg files I usually don't have to do much else to get my network connections going. KM From: KM To: CentOS mailing list Sent: Monday, February 13, 2017 12:49 PM Subject: Re: [CentOS] A question on networking (CentOS 6) I will get back to the mailing list. But to answer your questions, yes the IP addresses and interface names are as expected (as before) with the new MAC/HW addresses. I have someone else looking into it because when we plugged in the cable the light on the card did not light up. when we connect the pair server to another separate server it did. Once the server is back up I will try these things that you suggest, and compare them to the pair server we are trying to connect to. We are hoping that reseating the card will work. Probably wishful thinking. Thx.KM From: Gordon Messmer To: CentOS mailing list Sent: Monday, February 13, 2017 12:08 PM Subject: Re: [CentOS] A question on networking (CentOS 6) On 02/13/2017 06:55 AM, KM wrote: > The NIC went bad and it has been replaced. I knew enough to update the HW > address in the ifcfg-* files. The network service restarts successfully > without errors. However I cannot connect via ping or ssh with the pt2pt > network setup on 192.168.x.*. When I use our internal network ip addresses > it is fine. That's not much to go on. The output of "ip addr show" and "ip route show" might help you figure out what's going on. Do your interfaces have the expected names? Do they have the expected IP addresses? One thing that might be problematic is that there are multiple systems that attempt to maintain consistent interface names. If your interface names are not what you expect, you might need to look at /etc/udev/rules.d/70-persistent-net.rules where there may be additional rules mapping specific MAC addresses to an interface name. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question on networking (CentOS 6)
Like I said, wishful thinking. The light is still out, so it could be the HW. I ran those commands (ip addr show, ip route show) on the 2 servers. The output is identical except for the IP addresses and the MAC addresses, except on the server with the new card, it is missing the following IPV6 info for the interface name p2p1 which is the interface in question. inet6 fe80::6a05:caff:fe06:9122/64 scope link valid_lft forever preferred_lft forever Somehow I doubt we are using IPV6 but does it need to be there for some reason? and if so , what do I do about it. I apologize if these questions make no sense. Other than the original setup, and sometimes editing the ifcfg files I usually don't have to do much else to get my network connections going. KM From: KM To: CentOS mailing list Sent: Monday, February 13, 2017 12:49 PM Subject: Re: [CentOS] A question on networking (CentOS 6) I will get back to the mailing list. But to answer your questions, yes the IP addresses and interface names are as expected (as before) with the new MAC/HW addresses. I have someone else looking into it because when we plugged in the cable the light on the card did not light up. when we connect the pair server to another separate server it did. Once the server is back up I will try these things that you suggest, and compare them to the pair server we are trying to connect to. We are hoping that reseating the card will work. Probably wishful thinking. Thx.KM From: Gordon Messmer To: CentOS mailing list Sent: Monday, February 13, 2017 12:08 PM Subject: Re: [CentOS] A question on networking (CentOS 6) On 02/13/2017 06:55 AM, KM wrote: > The NIC went bad and it has been replaced. I knew enough to update the HW > address in the ifcfg-* files. The network service restarts successfully > without errors. However I cannot connect via ping or ssh with the pt2pt > network setup on 192.168.x.*. When I use our internal network ip addresses > it is fine. That's not much to go on. The output of "ip addr show" and "ip route show" might help you figure out what's going on. Do your interfaces have the expected names? Do they have the expected IP addresses? One thing that might be problematic is that there are multiple systems that attempt to maintain consistent interface names. If your interface names are not what you expect, you might need to look at /etc/udev/rules.d/70-persistent-net.rules where there may be additional rules mapping specific MAC addresses to an interface name. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question on networking (CentOS 6)
I will get back to the mailing list. But to answer your questions, yes the IP addresses and interface names are as expected (as before) with the new MAC/HW addresses. I have someone else looking into it because when we plugged in the cable the light on the card did not light up. when we connect the pair server to another separate server it did. Once the server is back up I will try these things that you suggest, and compare them to the pair server we are trying to connect to. We are hoping that reseating the card will work. Probably wishful thinking. Thx.KM From: Gordon Messmer To: CentOS mailing list Sent: Monday, February 13, 2017 12:08 PM Subject: Re: [CentOS] A question on networking (CentOS 6) On 02/13/2017 06:55 AM, KM wrote: > The NIC went bad and it has been replaced. I knew enough to update the HW > address in the ifcfg-* files. The network service restarts successfully > without errors. However I cannot connect via ping or ssh with the pt2pt > network setup on 192.168.x.*. When I use our internal network ip addresses > it is fine. That's not much to go on. The output of "ip addr show" and "ip route show" might help you figure out what's going on. Do your interfaces have the expected names? Do they have the expected IP addresses? One thing that might be problematic is that there are multiple systems that attempt to maintain consistent interface names. If your interface names are not what you expect, you might need to look at /etc/udev/rules.d/70-persistent-net.rules where there may be additional rules mapping specific MAC addresses to an interface name. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question on networking (CentOS 6)
On 02/13/2017 06:55 AM, KM wrote: The NIC went bad and it has been replaced. I knew enough to update the HW address in the ifcfg-* files. The network service restarts successfully without errors. However I cannot connect via ping or ssh with the pt2pt network setup on 192.168.x.*. When I use our internal network ip addresses it is fine. That's not much to go on. The output of "ip addr show" and "ip route show" might help you figure out what's going on. Do your interfaces have the expected names? Do they have the expected IP addresses? One thing that might be problematic is that there are multiple systems that attempt to maintain consistent interface names. If your interface names are not what you expect, you might need to look at /etc/udev/rules.d/70-persistent-net.rules where there may be additional rules mapping specific MAC addresses to an interface name. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] A question on networking (CentOS 6)
Hi AllThis is NOT specifically related to CentOS per se. I have 2 servers that are on two networks. I did NOT set this up. The NIC went bad and it has been replaced. I knew enough to update the HW address in the ifcfg-* files. The network service restarts successfully without errors. However I cannot connect via ping or ssh with the pt2pt network setup on 192.168.x.*. When I use our internal network ip addresses it is fine. I am not sure how to troubleshoot this separate connection. What can I provide here that will allow someone to help? Thanks in advance. I tried searching a bit but didn't find anything of use so far. KM ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/15/2014 05:41, mark wrote: > On 01/14/14 20:17, Warren Young wrote: >> Now I have to remember which *PCI slot* my Ethernet card is in when I >> run "ifconfig" unless I want to dig through the full listing. > > What do you mean, "slot"? All of my servers, and our systems at home, the > NIC's on the m/b. I know what you mean, but on those systems, the Ethernet MAC chip is still on the PCI[e] bus, so it still gets a slot number. If you say lspci, it's generally the second number, between the colon and dot. Fun fact: the MAC chip isn't always on a PCI[e] bus. On the Raspberry Pi, it's on the USB bus, despite the fact that it's soldered to the PCB! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Wed, Jan 15, 2014 at 12:47 PM, wrote: > > The problem is when you clone a disk and ship it to a location with > 'hands-on' support that doesn't know linux to install in a new chassis > that will arrive there at the same time. Somehow you have to get > someone to put the 4 network cables in the right NICs before anything > can connect. With things tied to MAC addresses that you don't know > ahead of time, nothing will work. > We have to go through contortions plugging on cable in at a time, doing an 'ifconfig up' and checking which interface shows link up. And the people doing that part wish we used more windows instead of Linux. >>> >>> ifconfig up? Not ethtool eth? >> >> You have to do both. Link won't come up until you ifconfig up the >> device - which of course is difficult when you don't know its name... > > I don't think so - pretty sure I was just using ethtool eth? the other > week, to try to figure out the name of the port that I'd plugged the patch > cord into. I *know* that the ones with nothing in them weren't up (and > yes, obviously, I was at the console). Maybe something else had already probed them. I'm pretty sure that if you bring up a system where all of the udev rules and ifcfg- files have the wrong MAC addresses, none of the links will come up.With CentOS5 you could use mii-tool to enumerate the interfaces and show link. I think the best I've found with 6 is to use 'ip link ls' to show the names, then one at a time 'ifconfig up' each name and then use ethtool to check for link. All very awkward to describe to a windows admin over the phone. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
Les Mikesell wrote: > On Wed, Jan 15, 2014 at 8:48 AM, wrote: >> The problem is when you clone a disk and ship it to a location with 'hands-on' support that doesn't know linux to install in a new chassis that will arrive there at the same time. Somehow you have to get someone to put the 4 network cables in the right NICs before anything can connect. With things tied to MAC addresses that you don't know ahead of time, nothing will work. >>> We have to go through contortions >>> plugging on cable in at a time, doing an 'ifconfig up' and checking >>> which interface shows link up. And the people doing that part wish >>> we used more windows instead of Linux. >> >> ifconfig up? Not ethtool eth? > > You have to do both. Link won't come up until you ifconfig up the > device - which of course is difficult when you don't know its name... I don't think so - pretty sure I was just using ethtool eth? the other week, to try to figure out the name of the port that I'd plugged the patch cord into. I *know* that the ones with nothing in them weren't up (and yes, obviously, I was at the console). mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Wed, Jan 15, 2014 at 8:48 AM, wrote: > >>> The problem is when you clone a disk and ship it to a location with >>> 'hands-on' support that doesn't know linux to install in a new chassis >>> that will arrive there at the same time. Somehow you have to get >>> someone to put the 4 network cables in the right NICs before anything >>> can connect. With things tied to MAC addresses that you don't know >>> ahead of time, nothing will work. > > When you clone a disk, you can't get the ifcfg-eth* and > 70-persistant-net-rules from the old machine, or you don't have that info > under version control, with all those systems? I don't have that information on the 1st install. Once it is up and running the ocsinventory-ng client will report the hardware to a central server. I suppose with a huge increase in human effort needed, the MAC addresses of the systems and cards could be databased as they are installed.. But, even knowing them doesn't help when you clone multiple identical disk images. And something would still have to map the MACs to the physical positions. >> We have to go through contortions >> plugging on cable in at a time, doing an 'ifconfig up' and checking >> which interface shows link up. And the people doing that part wish >> we used more windows instead of Linux. > > ifconfig up? Not ethtool eth? You have to do both. Link won't come up until you ifconfig up the device - which of course is difficult when you don't know its name... -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
Steve Thompson wrote: > On Wed, 15 Jan 2014, mark wrote: > >> What do you mean, "slot"? All of my servers, and our systems at home, >> the NIC's on the m/b. What "slot" is that? Is it labeled *anywhere*? No, of >> course not. > > Many servers have PCI cards for NICs in addition to those on the > motherboard (if any). For example, most of my file servers have eight > ethernet interfaces (six 1GBE, two 10GbE). On my Dell servers, the > built-in interfaces are labeled on the back panel. I can think of one server we've got, a Dell PER815, that's got a NIC (that we don't use, dunno why it was in there), and four onboard. > > However, at least in CentOS 6, you can call the interfaces anything you > want by suitably changing /etc/udev/rules.d/70-persistent-net.rules. The > names used have to be consistent with > /etc/sysconfig/network-scripts/ifcfg-* > of course. > > BTW, I have some workstations that have only a single interface, and that > comes up as p2p1. I actually like the new scheme better, but don't get me > started on the use of UUID in /etc/fstab... > I disliked it when the first time I started doing sysadmin, on a Sparcserver 20, back in the mid-nineties, and I don't like it any better now. Among other things, too easy to mistype one of the letters or numbers. About UUIDs, though, I think we can start on that in harmony. UUID is *so* much easier to remember, and shorter than, say, the serial number on the disk label... oh, right, it's twice as long mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
Am Wed, 15 Jan 2014 16:25:04 +0200 schrieb JC Putter : > How about using ethtool -p which causes the LED of the NIC to blink? > > Very useful, unless the datacenter isn't in the basement ;-) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
Les Mikesell wrote: > On Wed, Jan 15, 2014 at 6:05 AM, Steve Clark wrote: >> On 01/14/2014 08:34 PM, Les Mikesell wrote: >> >> On Tue, Jan 14, 2014 at 7:17 PM, Warren Young >> wrote: >> >> I don't know about "less consistent", but I always considered it a >> feature in Linux vs the BSDs or big iron Unix that I could always count >> on the first network interface being "eth0". >> >> What does 'first' mean? And the same one isn't consistently first. >> The problem is when you clone a disk and ship it to a location with >> 'hands-on' support that doesn't know linux to install in a new chassis >> that will arrive there at the same time. Somehow you have to get >> someone to put the 4 network cables in the right NICs before anything >> can connect. With things tied to MAC addresses that you don't know >> ahead of time, nothing will work. When you clone a disk, you can't get the ifcfg-eth* and 70-persistant-net-rules from the old machine, or you don't have that info under version control, with all those systems? > If you insert the card yourself, you obviously know the slot. And you > can tell the position from the back just by looking at it. But > Centos6 will detect in random order, so knowing the name on one box > doesn't help with another. We have to go through contortions > plugging on cable in at a time, doing an 'ifconfig up' and checking > which interface shows link up. And the people doing that part wish > we used more windows instead of Linux. ifconfig up? Not ethtool eth? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
How about using ethtool -p which causes the LED of the NIC to blink? On Wed, Jan 15, 2014 at 4:05 PM, Les Mikesell wrote: > On Wed, Jan 15, 2014 at 6:05 AM, Steve Clark wrote: >> On 01/14/2014 08:34 PM, Les Mikesell wrote: >> >> On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: >> >> I don't know about "less consistent", but I always considered it a >> feature in Linux vs the BSDs or big iron Unix that I could always count >> on the first network interface being "eth0". >> >> What does 'first' mean? And the same one isn't consistently first. >> >> I get that network interfaces can move around on you, but I thought that >> was why they started putting the MAC address in the ifcfg-eth? scripts. >> What problem did that not solve, that we had to switch to this new system? >> >> The problem is when you clone a disk and ship it to a location with >> 'hands-on' support that doesn't know linux to install in a new chassis >> that will arrive there at the same time. Somehow you have to get >> someone to put the 4 network cables in the right NICs before anything >> can connect. With things tied to MAC addresses that you don't know >> ahead of time, nothing will work. >> >> Now I have to remember which *PCI slot* my Ethernet card is in when I >> run "ifconfig" unless I want to dig through the full listing. >> >> Yes, but that's something you _can_ know. >> >> How can you know it? And if you know which port is which why isn't in the >> instruction >> with the drive so the people on site know which port is which? > > If you insert the card yourself, you obviously know the slot. And you > can tell the position from the back just by looking at it. But > Centos6 will detect in random order, so knowing the name on one box > doesn't help with another. We have to go through contortions > plugging on cable in at a time, doing an 'ifconfig up' and checking > which interface shows link up. And the people doing that part wish > we used more windows instead of Linux. > > -- > Les Mikesell > lesmikes...@gmail.com > ___ > 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] A question about 7
On Wed, Jan 15, 2014 at 6:05 AM, Steve Clark wrote: > On 01/14/2014 08:34 PM, Les Mikesell wrote: > > On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: > > I don't know about "less consistent", but I always considered it a > feature in Linux vs the BSDs or big iron Unix that I could always count > on the first network interface being "eth0". > > What does 'first' mean? And the same one isn't consistently first. > > I get that network interfaces can move around on you, but I thought that > was why they started putting the MAC address in the ifcfg-eth? scripts. > What problem did that not solve, that we had to switch to this new system? > > The problem is when you clone a disk and ship it to a location with > 'hands-on' support that doesn't know linux to install in a new chassis > that will arrive there at the same time. Somehow you have to get > someone to put the 4 network cables in the right NICs before anything > can connect. With things tied to MAC addresses that you don't know > ahead of time, nothing will work. > > Now I have to remember which *PCI slot* my Ethernet card is in when I > run "ifconfig" unless I want to dig through the full listing. > > Yes, but that's something you _can_ know. > > How can you know it? And if you know which port is which why isn't in the > instruction > with the drive so the people on site know which port is which? If you insert the card yourself, you obviously know the slot. And you can tell the position from the back just by looking at it. But Centos6 will detect in random order, so knowing the name on one box doesn't help with another. We have to go through contortions plugging on cable in at a time, doing an 'ifconfig up' and checking which interface shows link up. And the people doing that part wish we used more windows instead of Linux. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Wed, Jan 15, 2014 at 6:08 AM, Steve Clark wrote: > > On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: > Now I have to remember which *PCI slot* my Ethernet card is in when I > run "ifconfig" unless I want to dig through the full listing. > Yes, but that's something you _can_ know. > > So... which PCI/PCI-e slots are associated with the dual gigabit NICs > integrated in/on every ASUS board I've bought over the last 8 years? > > I wouldn't know on the first one, but the important thing is that if > you have 50 identical servers they would all be the same for the same > physical location. The way 6.x works, the motherboard set and the > pair on the card will randomly flip in the initial detection. With > 5.x having the MAC address in the ifcfg-ethx file was enough. With > 6.x you also need a udev rule to nail the name down. These get tied > to MAC addresses in the initial install, but that makes it painful to > clone systems or restore backups into a different box. > > Hmm... we have over a 1000 units in the field and CentOS always enumerates > the 6 ethx interfaces the > same - as they are labeled by the manufacturer of the hardware. This has > continued to be consistent even > when the manufacturer upgraded the MB. > Are these Dells using the bios name conventions? Or maybe it works better if all NICs are the same vendor/model. Ours mostly have onboard Broadcomms's and Intel cards, and they routinely flip pairs of interfaces - the sets on the motherboard and on any particular card will stay in the same order, but the order of the motherboard set and any card will be random during the install. Worse, when you move a drive to a different chassis, the old udev rules keep any of the new set from matching any old name. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Wed, 15 Jan 2014, mark wrote: > What do you mean, "slot"? All of my servers, and our systems at home, the > NIC's on the m/b. What "slot" is that? Is it labeled *anywhere*? No, of course > not. Many servers have PCI cards for NICs in addition to those on the motherboard (if any). For example, most of my file servers have eight ethernet interfaces (six 1GBE, two 10GbE). On my Dell servers, the built-in interfaces are labeled on the back panel. However, at least in CentOS 6, you can call the interfaces anything you want by suitably changing /etc/udev/rules.d/70-persistent-net.rules. The names used have to be consistent with /etc/sysconfig/network-scripts/ifcfg-* of course. BTW, I have some workstations that have only a single interface, and that comes up as p2p1. I actually like the new scheme better, but don't get me started on the use of UUID in /etc/fstab... Steve ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 01/14/14 20:17, Warren Young wrote: > On 1/14/2014 16:37, Scott Robbins wrote: >> On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote: >>> >>> Everyone, drop a tear for the dead "eth0".We will miss you, eth0! >> >> Haven't played much with it in CentOS. In Fedora, at present, it is a bit >> of pain as both biosdevname and systemd have something to do with it, >> making it less consistent than ever. > > I don't know about "less consistent", but I always considered it a > feature in Linux vs the BSDs or big iron Unix that I could always count > on the first network interface being "eth0". BSD and big iron Unix > named the interface after the Ethernet driver, as if that was what was > important. > > I get that network interfaces can move around on you, but I thought that > was why they started putting the MAC address in the ifcfg-eth? scripts. >What problem did that not solve, that we had to switch to this new system? > > Now I have to remember which *PCI slot* my Ethernet card is in when I > run "ifconfig" unless I want to dig through the full listing. > > Evil shades of PR#1, begone! > > (Apple DOS 3.3 reference, there.) What do you mean, "slot"? All of my servers, and our systems at home, the NIC's on the m/b. What "slot" is that? Is it labeled *anywhere*? No, of course not. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 01/14/2014 09:25 PM, Les Mikesell wrote: > On Tue, Jan 14, 2014 at 7:56 PM, Darr247 wrote: >> On 2014-01-14 8:34 PM, Les Mikesell wrote: >>> On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: >>> Now I have to remember which *PCI slot* my Ethernet card is in when I >>> run "ifconfig" unless I want to dig through the full listing. >>> Yes, but that's something you _can_ know. >>> >> So... which PCI/PCI-e slots are associated with the dual gigabit NICs >> integrated in/on every ASUS board I've bought over the last 8 years? > > I wouldn't know on the first one, but the important thing is that if > you have 50 identical servers they would all be the same for the same > physical location. The way 6.x works, the motherboard set and the > pair on the card will randomly flip in the initial detection. With > 5.x having the MAC address in the ifcfg-ethx file was enough. With > 6.x you also need a udev rule to nail the name down. These get tied > to MAC addresses in the initial install, but that makes it painful to > clone systems or restore backups into a different box. > Hmm... we have over a 1000 units in the field and CentOS always enumerates the 6 ethx interfaces the same - as they are labeled by the manufacturer of the hardware. This has continued to be consistent even when the manufacturer upgraded the MB. -- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.cl...@netwolves.com http://www.netwolves.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 01/14/2014 08:34 PM, Les Mikesell wrote: > On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: >> I don't know about "less consistent", but I always considered it a >> feature in Linux vs the BSDs or big iron Unix that I could always count >> on the first network interface being "eth0". > What does 'first' mean? And the same one isn't consistently first. > >> I get that network interfaces can move around on you, but I thought that >> was why they started putting the MAC address in the ifcfg-eth? scripts. >> What problem did that not solve, that we had to switch to this new system? > The problem is when you clone a disk and ship it to a location with > 'hands-on' support that doesn't know linux to install in a new chassis > that will arrive there at the same time. Somehow you have to get > someone to put the 4 network cables in the right NICs before anything > can connect. With things tied to MAC addresses that you don't know > ahead of time, nothing will work. > >> Now I have to remember which *PCI slot* my Ethernet card is in when I >> run "ifconfig" unless I want to dig through the full listing. > Yes, but that's something you _can_ know. > How can you know it? And if you know which port is which why isn't in the instruction with the drive so the people on site know which port is which? -- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.cl...@netwolves.com http://www.netwolves.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 01/14/2014 08:17 PM, Warren Young wrote: > On 1/14/2014 16:37, Scott Robbins wrote: >> On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote: >>> Everyone, drop a tear for the dead "eth0".We will miss you, eth0! >> Haven't played much with it in CentOS. In Fedora, at present, it is a bit >> of pain as both biosdevname and systemd have something to do with it, >> making it less consistent than ever. > I don't know about "less consistent", but I always considered it a > feature in Linux vs the BSDs or big iron Unix that I could always count > on the first network interface being "eth0". BSD and big iron Unix > named the interface after the Ethernet driver, as if that was what was > important. I agree - it was so much easier when we switched to CentOS from FreeBSD all the interfaces were ethx instead of vrx, rlx, edx, fxpx, emx, bge, etc - it made it so much easier when the hardware platform changed to move our software configs. > I get that network interfaces can move around on you, but I thought that > was why they started putting the MAC address in the ifcfg-eth? scripts. >What problem did that not solve, that we had to switch to this new system? > > Now I have to remember which *PCI slot* my Ethernet card is in when I > run "ifconfig" unless I want to dig through the full listing. > > Evil shades of PR#1, begone! > > (Apple DOS 3.3 reference, there.) > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.cl...@netwolves.com http://www.netwolves.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 01/15/2014 06:17 AM, Warren Young wrote: > On 1/14/2014 19:54, Les Mikesell wrote: >> On Tue, Jan 14, 2014 at 8:43 PM, Stephen Harris wrote: >> >> If you are old enough, you might remember unix versions that >> named disks by controller, bus, target numbers. > /dev/rdsk/c0t0n0q0w0e0p1k5n8 :) > > It's another reason I took to Linux quickly, right along with eth0. I'm old enough to remember another distribution where the trick was to symlink to /dev/cdrom. DO you? :-P ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 19:54, Les Mikesell wrote: > On Tue, Jan 14, 2014 at 8:43 PM, Stephen Harris wrote: > > If you are old enough, you might remember unix versions that > named disks by controller, bus, target numbers. /dev/rdsk/c0t0n0q0w0e0p1k5n8 :) It's another reason I took to Linux quickly, right along with eth0. >> The new process is new and therefor bad, wrong, disgusting, an abomination. >> >> But maybe... just maybe... it'll work. > > Maybe. If the names are relative to populated slots, maybe not. Ve shall see. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 08:54:33PM -0600, Les Mikesell wrote: > On Tue, Jan 14, 2014 at 8:43 PM, Stephen Harris wrote: > > Ultimately what we have is a situation similar to hard disks. We've got > > used to sd devices changing depending on the order disks are discovered > > in, which is why we use LABEL or UUID. > > But those don't work until something has already identified the > device. If you are old enough, you might remember unix versions that At install time "we have a disk; we designate it 'datadisk' we give it label DATA". That's what Anaconda does. The production kernel might find it as another disk, but because it has the label then all works. There's still a "boot" dependency, but there's not a lot we can do to work around the BIOS. > named disks by controller, bus, target numbers. Which worked, but > wasn't very human-friendly either. You mean the "modern" c0t0d0s0 type structures (eg Solaris SPARC) and similar (truncated) SVR4 Intel paths? Heh, I'm much older than that. That was actually not a bad scheme... but it required the bus to be detected in a consistent format. The problem with the Intel architecture is that this detection is _not_ consistent. It depends on module loading order, hotplug device issues etc etc. "c0" isn't necessarily "c0" on an Intel platform. That's where it all fell down. Back in the day (if you can remember back that far), Dell servers were a fun issue with RedHat; the install kernel would detect devices on the PCI bus in one order but the production install kernel would detect them in the _reverse_ order. So if you had two ethernet cards eth0 and eth1 would be reversed between install and boot kernels. Some HP servers also did this. Fun times! -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 8:43 PM, Stephen Harris wrote: >> > Ultimately what we have is a situation similar to hard disks. We've got > used to sd devices changing depending on the order disks are discovered > in, which is why we use LABEL or UUID. But those don't work until something has already identified the device. If you are old enough, you might remember unix versions that named disks by controller, bus, target numbers. Which worked, but wasn't very human-friendly either. > The new process is new and therefor bad, wrong, disgusting, an abomination. > > But maybe... just maybe... it'll work. Maybe. If the names are relative to populated slots, maybe not. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 08:35:06PM -0600, Les Mikesell wrote: > Let anaconda figure it out. I don't care what it is, just that it is > repeatable. Awooga! Awoooga! Awooga! Here's the fun part; devices discovered by Anaconda may not match the devices disovered during the production boot. Device driver order and bus discovery order wasn't necessarily consistent with the production kernel. This is why the HWADDR stuff was added; to work around (poorly) this issue. I say poorly becuase I've seen many cases of _net# devices where the ifcfg files conflict in same way with the actual device. Ultimately what we have is a situation similar to hard disks. We've got used to sd devices changing depending on the order disks are discovered in, which is why we use LABEL or UUID. HWADDR doesn't work consistently. The existing process is demonstrably broken. The new process is new and therefor bad, wrong, disgusting, an abomination. But maybe... just maybe... it'll work. -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 8:27 PM, Thomas Eriksson wrote: > >> Puzzle for ya: What "PCI slot" is the Intel e1000e MAC chip in on a >> Supermicro X9SCA-F motherboard? It isn't called out in the mobo manual. >> I just looked. (For that matter, the actual PCI slots don't have >> their numbers documented in the manual, either.) >> >> If you can't get lucky with Google, you're just going to have to install >> EL7 on it and find out. And if you can do that, why not just build it >> and ship it? >> > > On top of that, it seems to be only populated slots. > > I added a USB3 PCIe card to my Gigabyte MB and the previous 'enp2s0' > became 'enp3s0'! Oh great, another naming scheme invented by people that don't actually deal with hardware. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 8:21 PM, Warren Young wrote: > > >>> Now I have to remember which *PCI slot* my Ethernet card is in when I >>> run "ifconfig" unless I want to dig through the full listing. >> >> Yes, but that's something you _can_ know. > > How much time and resources do you need to learn the answer? You need a box in a lab setting where you do the build you want to clone. > Puzzle for ya: What "PCI slot" is the Intel e1000e MAC chip in on a > Supermicro X9SCA-F motherboard? It isn't called out in the mobo manual. > I just looked. (For that matter, the actual PCI slots don't have > their numbers documented in the manual, either.) Let anaconda figure it out. I don't care what it is, just that it is repeatable. > If you can't get lucky with Google, you're just going to have to install > EL7 on it and find out. And if you can do that, why not just build it > and ship it? Don't want to ship the chassis twice - and especially not for the 2nd/3rd installs on a remote box. I want to send a disk and have someone on-site plug it in and have the box come up working. For the 2nd/3rd installs, I can get the MAC addresses, but usually don't know them on the first round. >> Somehow you have to get >> someone to put the 4 network cables in the right NICs before anything >> can connect. > > Yes, I know that problem. > > We solved it here years ago by building the full system, testing it, > then labeling the ports with a Sharpie. Then, later, we got really > fancy and switched to a Brother label maker. > > Sure, it means we have to have the barebones chassis shipped here first, > but as you're doubtless aware, that shipping charge is cheap next to the > confusion that can happen in the field when Joe Wirepuller is asked to > plug it all in, if nothing is labeled. It gets old when you are doing several a day. Oh, and we've been waiting over a month for a resolution on a server that disappeared in transit, too... -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 18:34, Les Mikesell wrote: > > Puzzle for ya: What "PCI slot" is the Intel e1000e MAC chip in on a > Supermicro X9SCA-F motherboard? It isn't called out in the mobo manual. > I just looked. (For that matter, the actual PCI slots don't have > their numbers documented in the manual, either.) > > If you can't get lucky with Google, you're just going to have to install > EL7 on it and find out. And if you can do that, why not just build it > and ship it? > On top of that, it seems to be only populated slots. I added a USB3 PCIe card to my Gigabyte MB and the previous 'enp2s0' became 'enp3s0'! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 19:10, John R Pierce wrote: > On 1/14/2014 5:55 PM, Warren Young wrote: >> I know the problem you mean, but doesn't the HWADDR setting in the >> ifcfg-ethX file fix the problem? Doesn't that force "ifup eth0" to bind >> that file's settings to the right physical interface? >> >> In the old days, ifcfg-ethX didn't have HWADDR, so "first" was somewhat >> unpredictable, as you say. > > that forces it to bind to the same interface.but when you're doing a > virgin install, its fairly unlikely you'll know what the MAC's are or > which port it will pick to be eth0 and the setup will pick them fairly > arbitrarily (bus enumeration order, typically) Yes, we've had that problem, too. Motherboard model A from Most Favored Manufacturer will put eth0 on the left, then model B replaces it, and eth0 is now on the right. We figure this out during setup, then label the ports. If we decide we really want eth0 and eth1 swapped, we swap the HWADDR lines between the ifcfg files. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 7:56 PM, Darr247 wrote: > On 2014-01-14 8:34 PM, Les Mikesell wrote: >> On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: >> Now I have to remember which *PCI slot* my Ethernet card is in when I >> run "ifconfig" unless I want to dig through the full listing. >> Yes, but that's something you _can_ know. >> > > So... which PCI/PCI-e slots are associated with the dual gigabit NICs > integrated in/on every ASUS board I've bought over the last 8 years? I wouldn't know on the first one, but the important thing is that if you have 50 identical servers they would all be the same for the same physical location. The way 6.x works, the motherboard set and the pair on the card will randomly flip in the initial detection. With 5.x having the MAC address in the ifcfg-ethx file was enough. With 6.x you also need a udev rule to nail the name down. These get tied to MAC addresses in the initial install, but that makes it painful to clone systems or restore backups into a different box. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 18:34, Les Mikesell wrote: > On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: >> > >> Now I have to remember which *PCI slot* my Ethernet card is in when I >> run "ifconfig" unless I want to dig through the full listing. > > Yes, but that's something you _can_ know. How much time and resources do you need to learn the answer? Puzzle for ya: What "PCI slot" is the Intel e1000e MAC chip in on a Supermicro X9SCA-F motherboard? It isn't called out in the mobo manual. I just looked. (For that matter, the actual PCI slots don't have their numbers documented in the manual, either.) If you can't get lucky with Google, you're just going to have to install EL7 on it and find out. And if you can do that, why not just build it and ship it? > Somehow you have to get > someone to put the 4 network cables in the right NICs before anything > can connect. Yes, I know that problem. We solved it here years ago by building the full system, testing it, then labeling the ports with a Sharpie. Then, later, we got really fancy and switched to a Brother label maker. Sure, it means we have to have the barebones chassis shipped here first, but as you're doubtless aware, that shipping charge is cheap next to the confusion that can happen in the field when Joe Wirepuller is asked to plug it all in, if nothing is labeled. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 5:55 PM, Warren Young wrote: > I know the problem you mean, but doesn't the HWADDR setting in the > ifcfg-ethX file fix the problem? Doesn't that force "ifup eth0" to bind > that file's settings to the right physical interface? > > In the old days, ifcfg-ethX didn't have HWADDR, so "first" was somewhat > unpredictable, as you say. that forces it to bind to the same interface.but when you're doing a virgin install, its fairly unlikely you'll know what the MAC's are or which port it will pick to be eth0 and the setup will pick them fairly arbitrarily (bus enumeration order, typically) -- 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] A question about 7
On 2014-01-14 8:34 PM, Les Mikesell wrote: > On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: > Now I have to remember which *PCI slot* my Ethernet card is in when I > run "ifconfig" unless I want to dig through the full listing. > Yes, but that's something you _can_ know. > So... which PCI/PCI-e slots are associated with the dual gigabit NICs integrated in/on every ASUS board I've bought over the last 8 years? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 18:23, John R Pierce wrote: > On 1/14/2014 5:17 PM, Warren Young wrote: >> I don't know about "less consistent", but I always considered it a >> feature in Linux vs the BSDs or big iron Unix that I could always count >> on the first network interface being "eth0". BSD and big iron Unix >> named the interface after the Ethernet driver, as if that was what was >> important. > > conversely, it wasn't always consistent WHICH NIC would be eth0. Had > several x86 servers with dual integral nic's where eth0/eth1 were > swapped relative to what RHEL/CentOS thought they were. I know the problem you mean, but doesn't the HWADDR setting in the ifcfg-ethX file fix the problem? Doesn't that force "ifup eth0" to bind that file's settings to the right physical interface? In the old days, ifcfg-ethX didn't have HWADDR, so "first" was somewhat unpredictable, as you say. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 01/15/2014 02:17 PM, Warren Young wrote: > > I don't know about "less consistent", but I always considered it a > feature in Linux vs the BSDs or big iron Unix that I could always count > on the first network interface being "eth0". BSD and big iron Unix > named the interface after the Ethernet driver, as if that was what was > important. Admittedly I like the ethX naming scheme as well, but it did have issues. > I get that network interfaces can move around on you, but I thought that > was why they started putting the MAC address in the ifcfg-eth? scripts. > What problem did that not solve, that we had to switch to this new system? There are situations where the nic needs to be used or at least initialized before networking is brought up, pxe boot comes to mind as just one example. With the new naming convention the nic will have a consistent name everywhere barring any hardware changes (like moving it to a different slot). > Now I have to remember which *PCI slot* my Ethernet card is in when I > run "ifconfig" unless I want to dig through the full listing. > > Evil shades of PR#1, begone! You can still use the old naming convention. There's a setting somewhere for it and it's easy to change, I can't recall off the top of my head where it is, though. Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 01/15/2014 10:57 AM, Warren Young wrote: > On 1/14/2014 14:32, m.r...@5-cent.us wrote: > > Everyone, drop a tear for the dead "eth0".We will miss you, eth0! Not as dead as you may think, there are still situations where eth0 will be used, even by default: [root@el7-test ~]# ip a ... 2: eth0: ... Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 7:17 PM, Warren Young wrote: > > I don't know about "less consistent", but I always considered it a > feature in Linux vs the BSDs or big iron Unix that I could always count > on the first network interface being "eth0". What does 'first' mean? And the same one isn't consistently first. > I get that network interfaces can move around on you, but I thought that > was why they started putting the MAC address in the ifcfg-eth? scripts. > What problem did that not solve, that we had to switch to this new system? The problem is when you clone a disk and ship it to a location with 'hands-on' support that doesn't know linux to install in a new chassis that will arrive there at the same time. Somehow you have to get someone to put the 4 network cables in the right NICs before anything can connect. With things tied to MAC addresses that you don't know ahead of time, nothing will work. > Now I have to remember which *PCI slot* my Ethernet card is in when I > run "ifconfig" unless I want to dig through the full listing. Yes, but that's something you _can_ know. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 5:17 PM, Warren Young wrote: > I don't know about "less consistent", but I always considered it a > feature in Linux vs the BSDs or big iron Unix that I could always count > on the first network interface being "eth0". BSD and big iron Unix > named the interface after the Ethernet driver, as if that was what was > important. conversely, it wasn't always consistent WHICH NIC would be eth0. Had several x86 servers with dual integral nic's where eth0/eth1 were swapped relative to what RHEL/CentOS thought they were. while you COULD force it via mucking about in some kernel file or another, it was rarely worth the hassle. -- 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] A question about 7
On 1/14/2014 17:33, Ljubomir Ljubojevic wrote: > " If the system's BIOS does not have SMBIOS version 2.6 or higher and > this data, the new naming convention will not be used. Apparently VirtualBox emulates SMBIOS, since my RHEL 7 VM uses this new scheme. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 16:37, Scott Robbins wrote: > On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote: >> >> Everyone, drop a tear for the dead "eth0".We will miss you, eth0! > > Haven't played much with it in CentOS. In Fedora, at present, it is a bit > of pain as both biosdevname and systemd have something to do with it, > making it less consistent than ever. I don't know about "less consistent", but I always considered it a feature in Linux vs the BSDs or big iron Unix that I could always count on the first network interface being "eth0". BSD and big iron Unix named the interface after the Ethernet driver, as if that was what was important. I get that network interfaces can move around on you, but I thought that was why they started putting the MAC address in the ifcfg-eth? scripts. What problem did that not solve, that we had to switch to this new system? Now I have to remember which *PCI slot* my Ethernet card is in when I run "ifconfig" unless I want to dig through the full listing. Evil shades of PR#1, begone! (Apple DOS 3.3 reference, there.) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 01/15/2014 12:37 AM, Scott Robbins wrote: > On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote: >> On 1/14/2014 14:32, m.r...@5-cent.us wrote: >>> >>> configure can't >>> find the interface, >> >> Were you aware that RHEL 7 now uses "Consistent Network Device Naming" >> (http://goo.gl/Z0ydDF) in more situations? It was optional in RHEL 6 >> (http://goo.gl/TiuTP9) but is all but enforced in RHEL 7. >> >> Everyone, drop a tear for the dead "eth0".We will miss you, eth0! > > Haven't played much with it in CentOS. In Fedora, at present, it is a bit > of pain as both biosdevname and systemd have something to do with it, > making it less consistent than ever. > > So, to remove it, one has to both run rpm -e biosdevname and add to > /etc/deafaults/grub kernel line net.ifnames=0. > > Fpr 7: " If the system's BIOS does not have SMBIOS version 2.6 or higher and this data, the new naming convention will not be used. Most older hardware does not support this feature because of a lack of BIOSes with the correct SMBIOS version and field information. For BIOS or SMBIOS version information, contact your hardware vendor." -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 02:57:20PM -0700, Warren Young wrote: > On 1/14/2014 14:32, m.r...@5-cent.us wrote: > > > > configure can't > > find the interface, > > Were you aware that RHEL 7 now uses "Consistent Network Device Naming" > (http://goo.gl/Z0ydDF) in more situations? It was optional in RHEL 6 > (http://goo.gl/TiuTP9) but is all but enforced in RHEL 7. > > Everyone, drop a tear for the dead "eth0".We will miss you, eth0! Haven't played much with it in CentOS. In Fedora, at present, it is a bit of pain as both biosdevname and systemd have something to do with it, making it less consistent than ever. So, to remove it, one has to both run rpm -e biosdevname and add to /etc/deafaults/grub kernel line net.ifnames=0. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 14 January 2014 20:41, Les Mikesell wrote:
>
> Is there anything to simplify the process of duplicating the set of
> installed packages when you didn't pay that much attention the first
> time around? It seems like taking the list from 'rpm -qa' on a
> running machine and feeding it to 'yum install ' on a new minimal
> install should get pretty close, but then you need to find all of your
> locally modified config files. Most of that should be under
> /etc/sysconfig for an easy diff, but not everything.
>
>
Well one bit is /root/anaconda-ks.cfg to see what the kickstart to
duplicate the install of the system would look like ...
As for config files well behaved RPMs should mark their config files in the
manifest so a rpm -Va and parsing the output to look for config files
changed from install should help ...
In addition you could do something like find /etc -type f -exec rpm -qf {}
\; | grep -i 'not owned by' to find any config files in /etc that are
properly marked in the spec files for a package...
There are probably a few special cases like postgresql having the
postgres,conf file in the data directory for the service but you should be
able to catch most config files to back up by combining the two tricks...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 14:32, m.r...@5-cent.us wrote: > > configure can't > find the interface, Were you aware that RHEL 7 now uses "Consistent Network Device Naming" (http://goo.gl/Z0ydDF) in more situations? It was optional in RHEL 6 (http://goo.gl/TiuTP9) but is all but enforced in RHEL 7. Everyone, drop a tear for the dead "eth0".We will miss you, eth0! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/14/2014 13:41, Les Mikesell wrote:
>
> It seems like taking the list from 'rpm -qa' on a
> running machine and feeding it to 'yum install '
I suspect it's not actually that simple. I think you'd need to do a
fair bit of processing on the rpm -qa list to be able to build a yum
command that will succeed. Consider the RPM "provides" mechanism, which
allows two different RPMs to provide the same capability under different
names. {redhat,centos}-release is this way, for example.
One of the reasons I'm playing with RHEL 7 right now is that my end
purpose is to be able to modify the documentation and scripts our system
installers will use to build new CentOS 7 systems. So, I'm already
recording all of the changes needed, partly on paper, partly in a
Subversion repository. My RHEL 7 VM is disposable.
> then you need to find all of your
> locally modified config files.
Whenever I'm faced with a system with unknown changes which has to be
nuked and rebuilt, I tar up /etc, /home, and *maybe* /var and/or
/usr/local.
I usually don't bother with /var, since the irreplaceable things under
/var get backed up separately: DB tables, the web tree, etc.
There are exceptions. The Bind zone files on the primary DNS server are
essentially unique, for example. (The cached version on the secondary
DNS server(s) isn't identical to the primary copy. It's stripped of
comments, the formatting is a bit different, etc.)
I scp the backup tarball off to a file server somewhere, then replace
the hard drive and start fresh. The extra HDD and disk space for the
backups are cheap insurance.
The replaced HDD can be given another mission once you're satisfied that
everything's migrated. Put it in an external USB case and use it for
the new system's off-site backup, for example.
> Most of that should be under
> /etc/sysconfig for an easy diff, but not everything.
Not a lot of things. I regularly modify things under
/etc/ssh/
/etc/httpd/
/etc/pki/
/etc/{init.d, rc.d}/ (via chkconfig and yum)
/etc/yum.repos.d/
/etc/samba/
Plus there's plenty at the top level that changes occasionally:
/etc/{hosts,services}
/etc/{group,passwd,shadow}
/etc/sudoers
No, I'll stand by my current practice: tar up all of /etc and /home, at
minimum.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
Les Mikesell wrote: > On Tue, Jan 14, 2014 at 2:27 PM, Warren Young wrote: >> >> How bad is the worst case -- reinstall the OS and rebuild the software -- anyway? By doing your initial work on the RHEL 7 beta, you learn what you need to know to quickly redo the work on CentOS 7. > > Is there anything to simplify the process of duplicating the set of installed packages when you didn't pay that much attention the first time around? It seems like taking the list from 'rpm -qa' on a running machine and feeding it to 'yum install ' on a new minimal install should get pretty close, but then you need to find all of your locally modified config files. Most of that should be under > /etc/sysconfig for an easy diff, but not everything. Interesting note: I just started looking at the docs for 7. and two things: one, of course, preupgrade is in, and second, something that, if I read it correctly, called zstream, which will give you a report of what preupgrade would do, and list things that would have to be done my hand, so you can judge the difficulty of upgrading in place. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
Warren Young wrote: > On 1/13/2014 07:33, m.r...@5-cent.us wrote: >> Reason for this: at one of my local sf clubs, I've been trying to install Evergreen, F/OSS library software, on a system, and it's a nightmare. >> They seem to have been building it for Ubuntu whateverthelatestanimalis. The >> biggest problem is, IIRC, eventhandler and memchached; oh, and it uses postgresql 9, and nothing else. PGSQL 9 was not a big deal to install, but the other stuff Even trying to build it in /usr/local is a royal mess:though I've got the dbi installed, ./configure can't find it. > > Post an actual error message, and someone may be able to help. That's not a problem, well, the issue, as I said, is that configure can't find the interface, even when I've given it the correct paths. Can't really just give it to you, since a) I'm at work, in the DC 'burbs, and b) the clubhouse is up in Baltimore. Not building it at home - I've got other things to build (like xtrackcad) Thanks for the offer, though. I'm sure there's either some environment variable it isn't happy with, or is missing, or an option isn't right to tell it what path to use. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7 - arm distro?
Since RH7 is built on Fedora 19 and f19 is available for arm boards, will we see a RH7 for arm boards? I would spend time on the beta if I could get an arm build for a reasonable arm board. Target application is a PBX. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On Tue, Jan 14, 2014 at 2:27 PM, Warren Young wrote: > > How bad is the worst case -- reinstall the OS and rebuild the software > -- anyway? By doing your initial work on the RHEL 7 beta, you learn > what you need to know to quickly redo the work on CentOS 7. Is there anything to simplify the process of duplicating the set of installed packages when you didn't pay that much attention the first time around? It seems like taking the list from 'rpm -qa' on a running machine and feeding it to 'yum install ' on a new minimal install should get pretty close, but then you need to find all of your locally modified config files. Most of that should be under /etc/sysconfig for an easy diff, but not everything. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 1/13/2014 07:33, m.r...@5-cent.us wrote: > is there a CentOS > version of that beta? Not yet publicly available. I've heard they have something running in the development environment, but that they're still working on getting some of the RPMs to build. That's a prerequisite for generating ISOs. > If not, is it likely to be a real pain, once CentOS > 7 is released, to upgrade from RHEL 7 beta to CentOS 7? Anything that makes a RHEL7 -> C7 transition more difficult also makes the reverse transition more difficult. In this new world of Red Hat / CentOS collaboration, that would be a Bad Thing. I'd be surprised if the transition was more difficult than just a forced upgrade of the centos-release RPM. How bad is the worst case -- reinstall the OS and rebuild the software -- anyway? By doing your initial work on the RHEL 7 beta, you learn what you need to know to quickly redo the work on CentOS 7. > Reason for this: at one of my local sf clubs, I've been trying to install > Evergreen, F/OSS library software, on a system, and it's a nightmare. They > seem to have been building it for Ubuntu whateverthelatestanimalis. The > biggest problem is, IIRC, eventhandler and memchached; oh, and it uses > postgresql 9, and nothing else. PGSQL 9 was not a big deal to install, but > the other stuff Even trying to build it in /usr/local is a royal mess: > though I've got the dbi installed, ./configure can't find it. Post an actual error message, and someone may be able to help. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about 7
On 13 January 2014 14:33, wrote: > I've seen that RHEL 7 beta is out for some time now: is there a CentOS > version of that beta? If not, is it likely to be a real pain, once CentOS > 7 is released, to upgrade from RHEL 7 beta to CentOS 7? > > Check the progress on http://seven.centos.org/ As for the latter question - too early to tell. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] A question about 7
I've seen that RHEL 7 beta is out for some time now: is there a CentOS version of that beta? If not, is it likely to be a real pain, once CentOS 7 is released, to upgrade from RHEL 7 beta to CentOS 7? Reason for this: at one of my local sf clubs, I've been trying to install Evergreen, F/OSS library software, on a system, and it's a nightmare. They seem to have been building it for Ubuntu whateverthelatestanimalis. The biggest problem is, IIRC, eventhandler and memchached; oh, and it uses postgresql 9, and nothing else. PGSQL 9 was not a big deal to install, but the other stuff Even trying to build it in /usr/local is a royal mess: though I've got the dbi installed, ./configure can't find it. I do see, with a little googling, that everything I need for an older release of Evergreen should be installable without all this mess. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
Les Mikesell wrote: > On Thu, Feb 14, 2013 at 10:49 AM, wrote: >>> Reminds me of the *only* O'Reilly book I didn't like: I think it was Larry's original book on Perl - the index was *dreadful*, couldn't find anything. >>> >>> On the other hand, if you wrote a perl program following those >>> examples, it would almost certainly still run today, with the only >>> change it might need being to escape @ symbols that you had in >>> double-quoted strings. That's pretty rare. >> >> Well, yes. And I can do the same with my favorite language of all, ANSI >> C. > > Umm, yeah - now. In 1987 when perl was released you'd have been using > K&R C which needed some changes when compilers started demanding the > syntax from the ANSI changes. Or worse, some compiler with it's own > unique syntax. True... but in '87, I was still on mainframes, and using *GAG* DOS/VSE/SP (and whatever letters have been added since). I didn't get to use C until '89, and perl... no one had heard of it were I was working in TX until about '92 or '93. Yes, I did start with K&R, and have my copy of the Bible (K&R, ANSI version). Syntax on languages shouldn't change, anyway mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
On Thu, Feb 14, 2013 at 11:00 AM, Les Mikesell wrote: Reminds me of the *only* O'Reilly book I didn't like: I think it was Larry's original book on Perl - the index was *dreadful*, couldn't find anything. >>> >>> On the other hand, if you wrote a perl program following those >>> examples, it would almost certainly still run today, with the only >>> change it might need being to escape @ symbols that you had in >>> double-quoted strings. That's pretty rare. >> >> Well, yes. And I can do the same with my favorite language of all, ANSI C. > > Umm, yeah - now. In 1987 when perl was released you'd have been using > K&R C which needed some changes when compilers started demanding the > syntax from the ANSI changes. Or worse, some compiler with it's own > unique syntax. And I forgot my favorite issue with 'C': a failing 'include' is fatal. So, even though the language is mostly portable you can't, within the language, write code that will compile across systems that provide different include files. So you have to use some other less portable preprocessing toolset to get your code to a point where the compiler has a chance of accepting it - something that has turned into one of the most arcane arts you are likely to ever see. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
On Thu, Feb 14, 2013 at 10:49 AM, wrote: >> >>> Reminds me of the *only* O'Reilly book I didn't like: I think it was >>> Larry's original book on Perl - the index was *dreadful*, couldn't find >>> anything. >> >> On the other hand, if you wrote a perl program following those >> examples, it would almost certainly still run today, with the only >> change it might need being to escape @ symbols that you had in >> double-quoted strings. That's pretty rare. > > Well, yes. And I can do the same with my favorite language of all, ANSI C. Umm, yeah - now. In 1987 when perl was released you'd have been using K&R C which needed some changes when compilers started demanding the syntax from the ANSI changes. Or worse, some compiler with it's own unique syntax. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
Les Mikesell wrote: > On Thu, Feb 14, 2013 at 10:15 AM, wrote: >> But real books don't have that 'search' box up at the top... >>> >>> Agree with one of the other responders about that's what the index is >>> for. One of my "tests" for a book on the subject is to go to the index and >>> see how easy it is to find the answers to some of the questions I have >>> that have moved me to buy a book on the subject. > > If you know the right question ahead of time you probably really don't > need the book. Not necessarily. Sometimes, you know *something* the book covers, but not all, or not nearly all. You can look for answers to stuff you've had trouble solving. > >> Reminds me of the *only* O'Reilly book I didn't like: I think it was >> Larry's original book on Perl - the index was *dreadful*, couldn't find >> anything. > > On the other hand, if you wrote a perl program following those > examples, it would almost certainly still run today, with the only > change it might need being to escape @ symbols that you had in > double-quoted strings. That's pretty rare. Well, yes. And I can do the same with my favorite language of all, ANSI C. Breaking a language, unless there's no other answer, is NOT something I have any sympathy with, he says, remembering how ever sub-release of python 10-12 years ago would break previous system scripts, or then there's ruby now mark "the fault, dear Brutus, is not in our language, but in our code" ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
On Thu, Feb 14, 2013 at 10:15 AM, wrote: > >>> But real books don't have that 'search' box up at the top... >> >> Agree with one of the other responders about that's what the index is for. >> One of my "tests" for a book on the subject is to go to the index and >> see how easy it is to find the answers to some of the questions I have >> that have moved me to buy a book on the subject. If you know the right question ahead of time you probably really don't need the book. > Reminds me of the *only* O'Reilly book I didn't like: I think it was > Larry's original book on Perl - the index was *dreadful*, couldn't find > anything. On the other hand, if you wrote a perl program following those examples, it would almost certainly still run today, with the only change it might need being to escape @ symbols that you had in double-quoted strings. That's pretty rare. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
David G. Miller wrote: > Les Mikesell writes: >> On Wed, Feb 13, 2013 at 9:13 AM, David G. Miller wrote: >> > >> >> Red Hat Linux is ancient. >> > >> > I started with Red Hat Linux 5 in 1998. Mind your manners when >> > calling RHL 9 ancient or I'll come over and hit you with my walker. >> >> In computer years, that's like a century ago. >> > > I guess that means the IBM and CDC mainframes I started out on in the '70s > and '80s were prehistoric. Funny thing is that an application I helped write > in the early 1980s was still being used by the customer in the mid-1990s (long > story how I found out). It had been ported from the original platform (IBM Yep. 370, timeshare, 4300's > S/370) to a SUN workstation and the customer still loved it. Wouldn't > surprise me if they aren't still using it. After all, they still fly > B-52s that are even older. >> But real books don't have that 'search' box up at the top... > > Agree with one of the other responders about that's what the index is for. > One of my "tests" for a book on the subject is to go to the index and > see how easy it is to find the answers to some of the questions I have > that have moved me to buy a book on the subject. Reminds me of the *only* O'Reilly book I didn't like: I think it was Larry's original book on Perl - the index was *dreadful*, couldn't find anything. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
Les Mikesell writes: > > On Wed, Feb 13, 2013 at 9:13 AM, David G. Miller wrote: > > > >> Red Hat Linux is ancient. > > > > I started with Red Hat Linux 5 in 1998. Mind your manners when calling RHL > > 9 > > ancient or I'll come over and hit you with my walker. > > In computer years, that's like a century ago. > I guess that means the IBM and CDC mainframes I started out on in the '70s and '80s were prehistoric. Funny thing is that an application I helped write in the early 1980s was still being used by the customer in the mid-1990s (long story how I found out). It had been ported from the original platform (IBM S/370) to a SUN workstation and the customer still loved it. Wouldn't surprise me if they aren't still using it. After all, they still fly B-52s that are even older. > But real books don't have that 'search' box up at the top... Agree with one of the other responders about that's what the index is for. One of my "tests" for a book on the subject is to go to the index and see how easy it is to find the answers to some of the questions I have that have moved me to buy a book on the subject. Cheers, Dave ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
On 02/13/13 17:53, John R Pierce wrote: > On 2/13/2013 7:46 AM, m.r...@5-cent.us wrote: >> That's "tease me about my age, and I'll beat you with my cane". And >> RH9 was fine - that's what I ran on my firewall/router box for*years*, >> with few updates. > > my home firewall/router box is STILL running something that started life > as RHL6 but is heavily hacked up. hasn't ever been broken into, so > I've not had a lot of incentive to rip it apart and redo it. > I started, I think, with either 5 or 5.2 for a firewall router, and ran Bastille Linux on it. Never got invaded, as far as I could tell. mark -- This email transmission contains information. If it was confidential, I'dbe telling you it on the phone. It's intended for the addresses. The FBI, CIA, NSA, and Homeland Security Theater (and anyone else) can keep their mitts off it unless they have a warrant; they may *not* kiss my ass, because I don't want their lips anywhere near me. If you're going to disseminate it, check with me first, unless I ask dissemination. Anything else is artificial dissemination, and you're fucked. If you are not the intended recipient(s), delete before reading; in fact, delete it before you receive it. Only dead critters from the Cretaceous and before were harmed by the creation of this message, and they haven't cared since the comet hit. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
On 2/13/2013 7:46 AM, m.r...@5-cent.us wrote: > That's "tease me about my age, and I'll beat you with my cane". And > RH9 was fine - that's what I ran on my firewall/router box for*years*, > with few updates. my home firewall/router box is STILL running something that started life as RHL6 but is heavily hacked up. hasn't ever been broken into, so I've not had a lot of incentive to rip it apart and redo it. $ uname -a Linux $DOMAIN.com 2.2.24-6.2.3-jrp7 #1 Wed Jan 14 03:17:05 PST 2004 i686 unknown -- 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] A question
On Wed, Feb 13, 2013 at 10:09 AM, wrote: >> >> But real books don't have that 'search' box up at the top... > > Les, that's what the index is for. Never works. Where do you file the bug report? >> It is really unfortunate that neither paper books nor pdf's have >> developed the technology to easily show you 'just' those changes so >> you end up starting from scratch every time a developer decides to >> make some small change. I've always wished for something where you >> could input the version you know and get a description of the changes >> between that and some current version. > > The good ones *do* tell you that, in examples, in appendices, on the CD > they give you Maybe, if you only need to bump one version at a time. I tend to remember things from 10 versions back better than last week's. And I get grumpy when I still have instances of those that have been running perfectly well for years, mostly with no attention, yet someone thinks they have to change it in incompatible ways. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
Les Mikesell wrote: > On Wed, Feb 13, 2013 at 9:13 AM, David G. Miller > wrote: >> >>> Red Hat Linux is ancient. >> > >> Advice to OP: Don't spend much money on treeware books about Linux in >> general or CentOS in particular. The technology moves fast enough that the book >> will be obsolete in six months to a year. I work best with real books because I >> can easily dog-ear, underline, highlight, mark, etc. so I understand liking >> a real book. > > But real books don't have that 'search' box up at the top... Les, that's what the index is for. > It is really unfortunate that neither paper books nor pdf's have > developed the technology to easily show you 'just' those changes so > you end up starting from scratch every time a developer decides to > make some small change. I've always wished for something where you > could input the version you know and get a description of the changes > between that and some current version. The good ones *do* tell you that, in examples, in appendices, on the CD they give you mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
On Wed, Feb 13, 2013 at 9:13 AM, David G. Miller wrote: > >> Red Hat Linux is ancient. > > I started with Red Hat Linux 5 in 1998. Mind your manners when calling RHL 9 > ancient or I'll come over and hit you with my walker. In computer years, that's like a century ago. > Advice to OP: Don't spend much money on treeware books about Linux in general > or > CentOS in particular. The technology moves fast enough that the book will be > obsolete in six months to a year. I work best with real books because I can > easily dog-ear, underline, highlight, mark, etc. so I understand liking a real > book. But real books don't have that 'search' box up at the top... > If you really want to have a real book, take the time to visit a local book > store that has a decent selection of technical books and page through some of > the books there to see which author's style fits you. If you can afford it, > spend the money and support your local book store. If you can't afford it, > see > what you can find on-line, at a garage or yard sale, etc. Either way, get > used > to using Google to get answers to your questions. The answer will change over > time. It is really unfortunate that neither paper books nor pdf's have developed the technology to easily show you 'just' those changes so you end up starting from scratch every time a developer decides to make some small change. I've always wished for something where you could input the version you know and get a description of the changes between that and some current version. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
David G. Miller wrote: > John R Pierce writes: >> On 2/12/2013 4:51 PM, Bassem Sossan wrote: >> > I'm beginner with Linux... >> > I have found a good resource, it's a book called "Beginning Red Hat >> > Linux 9"... the centos's version that I've installed "centos 6"... >> > Is this book may be compatible with Centos 6 ? >> >> not really. >> >> Red Hat Linux is ancient. > > I started with Red Hat Linux 5 in 1998. Mind your manners when calling > RHL 9 ancient or I'll come over and hit you with my walker. That's "tease me about my age, and I'll beat you with my cane". And RH9 was fine - that's what I ran on my firewall/router box for *years*, with few updates. > > Advice to OP: Don't spend much money on treeware books about Linux in > general or CentOS in particular. The technology moves fast enough that > the book will be obsolete in six months to a year. Yup, it's a problem. However, most stuff really doesn't change, if you're looking at administering it, or working on it (except for N33t k3wl GUIs). > I work best with real books because I can easily dog-ear, underline, > highlight, mark, etc. so I understand liking a real book. Book molester! > > If you really want to have a real book, take the time to visit a local > book store that has a decent selection of technical books and page > through some of the books there to see which author's style fits you. > If you can afford it, spend the money and support your local book store. And, of course, almost anything published by O'Reilly is going to be somewhere between good and really good: well-written, knowledgeable, and reliable. mark "not getting a kickback from them, really!" ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
John R Pierce writes: > > On 2/12/2013 4:51 PM, Bassem Sossan wrote: > > I'm beginner with Linux... > > I have found a good resource, it's a book called "Beginning Red Hat Linux > > 9"... > > the centos's version that I've installed "centos 6"... > > Is this book may be compatible with Centos 6 ? > > not really. > > Red Hat Linux is ancient. I started with Red Hat Linux 5 in 1998. Mind your manners when calling RHL 9 ancient or I'll come over and hit you with my walker. Advice to OP: Don't spend much money on treeware books about Linux in general or CentOS in particular. The technology moves fast enough that the book will be obsolete in six months to a year. I work best with real books because I can easily dog-ear, underline, highlight, mark, etc. so I understand liking a real book. If you really want to have a real book, take the time to visit a local book store that has a decent selection of technical books and page through some of the books there to see which author's style fits you. If you can afford it, spend the money and support your local book store. If you can't afford it, see what you can find on-line, at a garage or yard sale, etc. Either way, get used to using Google to get answers to your questions. The answer will change over time. Cheers, Dave ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
Am 13.02.2013 um 01:59 schrieb Stephen Harris : > On Tue, Feb 12, 2013 at 04:51:54PM -0800, Bassem Sossan wrote: >> I have found a good resource, it's a book called "Beginning Red Hat Linux >> 9"... >> the centos's version that I've installed "centos 6"... >> Is this book may be compatible with Centos 6 ? > > Define "compatible". RH9 is very very *very* old. It's from 2003. > It got replace with Fedora. To confuse you, "RedHat Enterprise Linux" > (RHEL) is a not the same as "RedHat Linux" (RH). CentOS follows RHEL. > RHEL 2.1 was approximately RH7. RHEL3 ~= RH9. RHEL6 ~= Fedora 12. http://fedoraproject.org/wiki/Red_Hat_Enterprise_Linux#History -- LF ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
On 2/12/2013 4:51 PM, Bassem Sossan wrote: > I'm beginner with Linux... > I have found a good resource, it's a book called "Beginning Red Hat Linux > 9"... > the centos's version that I've installed "centos 6"... > Is this book may be compatible with Centos 6 ? not really. Red Hat Linux is ancient. 9 was the short lived final version, in 2003. after RHL 9 came RH Enterprise Linux 2.1, then RHEL 3, then 4, 5, and now RHEL 6, which is rebuilt as CentOS 6. so that book is describing a version of linux that is from 10 years ago, an eternity in computer software evolution. the most basic usermode shell commands will be somewhat the same. -- 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] A question
On 2/12/2013 7:51 PM, Bassem Sossan wrote: > I'm beginner with Linux... > I have found a good resource, it's a book called "Beginning Red Hat Linux > 9"... > the centos's version that I've installed "centos 6"... > Is this book may be compatible with Centos 6 ? > > Ahhh easy confusion. Red Hat Linux was a bit less Enterprise oriented. If I recall, Red Hat 9 was out about the same time the Red Hat Enterprise Linux 2.x was out. That became known as RHEL for short. CentOS is a clone of RHEL. So, CentOS 6 is the latest from Redhat other than the Fedora project. In summary, most of that book will have good information, in particular the basics, but it is very old at this point. I suppose around 10 years old now. That book will not cover a number of things that have been added into CentOS 6. -- John Hinton 877-777-1407 ext 502 http://www.ew3d.com Comprehensive Online Solutions ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question
On Tue, Feb 12, 2013 at 04:51:54PM -0800, Bassem Sossan wrote: > I have found a good resource, it's a book called "Beginning Red Hat Linux > 9"... > the centos's version that I've installed "centos 6"... > Is this book may be compatible with Centos 6 ? Define "compatible". RH9 is very very *very* old. It's from 2003. It got replace with Fedora. To confuse you, "RedHat Enterprise Linux" (RHEL) is a not the same as "RedHat Linux" (RH). CentOS follows RHEL. RHEL 2.1 was approximately RH7. RHEL3 ~= RH9. RHEL6 ~= Fedora 12. So some of the ideas (eg "rpm") are the same, but because it's old many of the details will be wrong. -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] A question
I'm beginner with Linux... I have found a good resource, it's a book called "Beginning Red Hat Linux 9"... the centos's version that I've installed "centos 6"... Is this book may be compatible with Centos 6 ? Best regards... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about DRBD and nfs
>I been working on for about a month and half on setup drbd and nfs. I keep >running >into issue with the way heartbeat/pacemaker handles nfs. Does anyone know a >good >way to set up a HA NFS server with DRBD and Heartbeat and NFS. I am willing >to share >my pain in setting it up. It involves a bit of manual work which all depends on how seamless you want failover. Which I assume is your problem so far. Client mount options play a more significant role in this setup. The drbd part is trivially provided by the included scripts. It will promote/demote from sec to pri as needed. The NFS part involves some work. http://sources.redhat.com/cluster/doc/nfscookbook.pdf If I can offer a small suggestion, if you're on CentOS, use the boxed RHCS, its very good to understate it. Drop pacemaker, but that's my $0.02 CAN:) It's as simple as yum install with some cluster.conf tweaking and voila to setup a cluster. If you don't care about the locks/states being available on the secondary when it gets promoted (I assume you're not using a cluster FS and running pri/pri) then it's easy. When I was learning RHCS I recall symlinking the appropriate dirs on the replicated block device. HTH, jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] A question about DRBD and nfs
Hi, I been working on for about a month and half on setup drbd and nfs. I keep running into issue with the way heartbeat/pacemaker handles nfs. Does anyone know a good way to set up a HA NFS server with DRBD and Heartbeat and NFS. I am willing to share my pain in setting it up. Chuck Payne NEO Linux System Engineer chuck.pa...@vocolacity.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
