Re: [systemd-devel] systemd network interface names - new twist
On 6/2/2016 11:28 AM, Reindl Harald wrote: Am 02.06.2016 um 19:24 schrieb JB: On 6/2/2016 11:01 AM, Reindl Harald wrote: Am 02.06.2016 um 18:50 schrieb Greg KH: On Thu, Jun 02, 2016 at 06:29:50PM +0200, Reindl Harald wrote: Am 02.06.2016 um 18:20 schrieb Greg KH: Ok, but please ask on a fedora list as this is a fedora specific issue, as it is running a very old version of systemd as well as the kernel, so there's not much we can do here either you must confuse Fedora with other distributions in context of "as well as the kernel" because of 4.5.6-200.fc23.x86_64 #1 SMP Wed Jun 1 21:28:20 UTC 2016 OP stated they were using Fedora 21 and the 3.18 kernel, what does that have to do with Fedora 23 and the 4.5.6 kernel? well, i overlooked that someone posts problems with a long ago EOL distribution which should not have contact to any network at all hence the proper response would have not been "fedora specific issue" but "you don't run any usable system at all" That is pretty damn presumptuous really? only when you are not aware that i run our complete infsrastructure and dozens of servers for 8 years on Fedora and *never* had a EOL machine running if you can't manage dist-upgrades in that frequency just don#t install a operating systems which requires you to do so - that's it Yes, really. It's really damn presumptuous to assume that whatever few dozen servers you manage can and should represent every single other scenario, use case, application, and environment all over the rest of the world and "that's it." You can yell, scream, insult my intelligence, and all the other manner of bullying I've seen come out of the people behind this project which, IMHO is the primary contributor to all the divisiveness experienced in the open source community over systemd. I don't expect you to believe me or listen, or frankly even care about other users out there but I do hope you will at least consider that there is reality beyond your world. I fully expect some insulting arrogant dismissive or insulting blow off so you can have the last word or whatever, but I will no longer feed this thread as it is not productive. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
Am 02.06.2016 um 19:24 schrieb JB: On 6/2/2016 11:01 AM, Reindl Harald wrote: Am 02.06.2016 um 18:50 schrieb Greg KH: On Thu, Jun 02, 2016 at 06:29:50PM +0200, Reindl Harald wrote: Am 02.06.2016 um 18:20 schrieb Greg KH: Ok, but please ask on a fedora list as this is a fedora specific issue, as it is running a very old version of systemd as well as the kernel, so there's not much we can do here either you must confuse Fedora with other distributions in context of "as well as the kernel" because of 4.5.6-200.fc23.x86_64 #1 SMP Wed Jun 1 21:28:20 UTC 2016 OP stated they were using Fedora 21 and the 3.18 kernel, what does that have to do with Fedora 23 and the 4.5.6 kernel? well, i overlooked that someone posts problems with a long ago EOL distribution which should not have contact to any network at all hence the proper response would have not been "fedora specific issue" but "you don't run any usable system at all" That is pretty damn presumptuous really? only when you are not aware that i run our complete infsrastructure and dozens of servers for 8 years on Fedora and *never* had a EOL machine running if you can't manage dist-upgrades in that frequency just don#t install a operating systems which requires you to do so - that's it signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
Am 02.06.2016 um 18:50 schrieb Greg KH: On Thu, Jun 02, 2016 at 06:29:50PM +0200, Reindl Harald wrote: Am 02.06.2016 um 18:20 schrieb Greg KH: Ok, but please ask on a fedora list as this is a fedora specific issue, as it is running a very old version of systemd as well as the kernel, so there's not much we can do here either you must confuse Fedora with other distributions in context of "as well as the kernel" because of 4.5.6-200.fc23.x86_64 #1 SMP Wed Jun 1 21:28:20 UTC 2016 OP stated they were using Fedora 21 and the 3.18 kernel, what does that have to do with Fedora 23 and the 4.5.6 kernel? well, i overlooked that someone posts problems with a long ago EOL distribution which should not have contact to any network at all hence the proper response would have not been "fedora specific issue" but "you don't run any usable system at all" signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
On Thu, Jun 02, 2016 at 06:29:50PM +0200, Reindl Harald wrote: > > > Am 02.06.2016 um 18:20 schrieb Greg KH: > > Ok, but please ask on a fedora list as this is a fedora specific issue, > > as it is running a very old version of systemd as well as the kernel, so > > there's not much we can do here either > > you must confuse Fedora with other distributions in context of "as well as > the kernel" because of 4.5.6-200.fc23.x86_64 #1 SMP Wed Jun 1 21:28:20 UTC > 2016 OP stated they were using Fedora 21 and the 3.18 kernel, what does that have to do with Fedora 23 and the 4.5.6 kernel? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
On 06/02/2016 04:33 PM, JB wrote: Thanks, that's the plan but in order to buy myself that time, I'd need to get this resolved first. I'm afraid you wont buy yourself anything since your only option is to start immediately to look into applying real-time kernel patches or find another distro since F21 is EOL and the only response you get from everybody is "upgrade" or "try with latest release" F22 is on 4.4x kernels F23/F24 is on 4.5.x ( soon to be on 4.6.x ) and rawhide on 4.7.x so you need to apply patches to those release or use for example CentOS 7.x which comes with the 3.10 kernel JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
On 6/2/2016 10:20 AM, Greg KH wrote: On Thu, Jun 02, 2016 at 10:14:22AM -0600, JB wrote: Hi Greg, Thank you very much for responding! On 6/2/2016 9:46 AM, Greg KH wrote: On Thu, Jun 02, 2016 at 06:24:39AM -0600, JB wrote: I'm running kernel 3.18.22. I'm seeing some odd behavior from systemd. The motherboard is an intel board with dual onboard NIC. I installed FC21 initially with secondary ethernet interface disabled in the BIOS. Then after install, I enabled it. However, while the first NIC name comes up as expected getting renamed from eth0 to eno#. The second NIC never gets renamed and instead is brought up as eth1. What's up with that? I thought they were all supposed to get en* names. I mean after all, I've already retooled all our software to accommodate the new scheme. This sounds like a Fedora bug, in noticing your "new" NIC that showed up after the system was installed. I suggest you file a bug with their reporting system. Sorry, I probably should have been more clear. I disabled the secondary NIC in the BIOS intentionally prior to OS installation. Then I did the FC21 minimal installation which excludes most of Fedora's network management stuff. I also disabled NetworkManager and ripped out any other fedora specific stuff. In looking at dmesg and journalctl I'm seeing where systemd renames eth0 to it's new name, but leaves eth1 untouched which is the part that is confusing me. The new NIC showed up, as expected, after I enabled it in the BIOS. I think I could more easily see your point if NIC naming was determined at OS installation time but my experience has been that systemd does it as part of it's initialization regardless of what was there when the OS was installed. Ok, but please ask on a fedora list as this is a fedora specific issue, as it is running a very old version of systemd as well as the kernel, so there's not much we can do here either. I doubt that it's fedora only, it looks deeper than that to me, but I will check and if not, perhaps prove the issue out on either another distro or a custom build. Also, please note that the 3.18 kernel is very old and unsupported, you might want to update to a modern kernel release :) Yeah, I'm aware of that. Sadly, the application I'm dealing with has strong dependencies on RTAI and the most recent kernel supported by even the most recent beta of RTAI is 3.18.22 :( This is particularly challenging since most of the driver support we need is all in the newer kernels. I've been looking at some of the more recent RT processing capabilities slowly making their way into the stock kernel but for now, it's a circumstance I must contend with! You might try the real-time kernel patches, they seem to perform just as well, if not better, than RTAI, and you are not stuck with obsolete and unsuportable kernel versions. Thanks, that's the plan but in order to buy myself that time, I'd need to get this resolved first. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
Am 02.06.2016 um 18:20 schrieb Greg KH: Ok, but please ask on a fedora list as this is a fedora specific issue, as it is running a very old version of systemd as well as the kernel, so there's not much we can do here either you must confuse Fedora with other distributions in context of "as well as the kernel" because of 4.5.6-200.fc23.x86_64 #1 SMP Wed Jun 1 21:28:20 UTC 2016 signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
On Thu, Jun 02, 2016 at 10:14:22AM -0600, JB wrote: > Hi Greg, > Thank you very much for responding! > > On 6/2/2016 9:46 AM, Greg KH wrote: > > On Thu, Jun 02, 2016 at 06:24:39AM -0600, JB wrote: > > > I'm running kernel 3.18.22. I'm seeing some odd behavior from systemd. The > > > motherboard is an intel board with dual onboard NIC. I installed FC21 > > > initially with secondary ethernet interface disabled in the BIOS. Then > > > after > > > install, I enabled it. However, while the first NIC name comes up as > > > expected getting renamed from eth0 to eno#. The second NIC never gets > > > renamed and instead is brought up as eth1. > > > > > > What's up with that? I thought they were all supposed to get en* names. I > > > mean after all, I've already retooled all our software to accommodate the > > > new scheme. > > This sounds like a Fedora bug, in noticing your "new" NIC that showed up > > after the system was installed. I suggest you file a bug with their > > reporting system. > Sorry, I probably should have been more clear. I disabled the secondary NIC > in the BIOS intentionally prior to OS installation. Then I did the FC21 > minimal installation which excludes most of Fedora's network management > stuff. I also disabled NetworkManager and ripped out any other fedora > specific stuff. In looking at dmesg and journalctl I'm seeing where systemd > renames eth0 to it's new name, but leaves eth1 untouched which is the part > that is confusing me. > > The new NIC showed up, as expected, after I enabled it in the BIOS. I think > I could more easily see your point if NIC naming was determined at OS > installation time but my experience has been that systemd does it as part of > it's initialization regardless of what was there when the OS was installed. Ok, but please ask on a fedora list as this is a fedora specific issue, as it is running a very old version of systemd as well as the kernel, so there's not much we can do here either. > > Also, please note that the 3.18 kernel is very old and unsupported, you > > might want to update to a modern kernel release :) > > Yeah, I'm aware of that. Sadly, the application I'm dealing with has strong > dependencies on RTAI and the most recent kernel supported by even the most > recent beta of RTAI is 3.18.22 :( This is particularly challenging since > most of the driver support we need is all in the newer kernels. I've been > looking at some of the more recent RT processing capabilities slowly making > their way into the stock kernel but for now, it's a circumstance I must > contend with! You might try the real-time kernel patches, they seem to perform just as well, if not better, than RTAI, and you are not stuck with obsolete and unsuportable kernel versions. Best of luck! greg k-h ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
Hi Greg, Thank you very much for responding! On 6/2/2016 9:46 AM, Greg KH wrote: On Thu, Jun 02, 2016 at 06:24:39AM -0600, JB wrote: I'm running kernel 3.18.22. I'm seeing some odd behavior from systemd. The motherboard is an intel board with dual onboard NIC. I installed FC21 initially with secondary ethernet interface disabled in the BIOS. Then after install, I enabled it. However, while the first NIC name comes up as expected getting renamed from eth0 to eno#. The second NIC never gets renamed and instead is brought up as eth1. What's up with that? I thought they were all supposed to get en* names. I mean after all, I've already retooled all our software to accommodate the new scheme. This sounds like a Fedora bug, in noticing your "new" NIC that showed up after the system was installed. I suggest you file a bug with their reporting system. Sorry, I probably should have been more clear. I disabled the secondary NIC in the BIOS intentionally prior to OS installation. Then I did the FC21 minimal installation which excludes most of Fedora's network management stuff. I also disabled NetworkManager and ripped out any other fedora specific stuff. In looking at dmesg and journalctl I'm seeing where systemd renames eth0 to it's new name, but leaves eth1 untouched which is the part that is confusing me. The new NIC showed up, as expected, after I enabled it in the BIOS. I think I could more easily see your point if NIC naming was determined at OS installation time but my experience has been that systemd does it as part of it's initialization regardless of what was there when the OS was installed. Also, please note that the 3.18 kernel is very old and unsupported, you might want to update to a modern kernel release :) Yeah, I'm aware of that. Sadly, the application I'm dealing with has strong dependencies on RTAI and the most recent kernel supported by even the most recent beta of RTAI is 3.18.22 :( This is particularly challenging since most of the driver support we need is all in the newer kernels. I've been looking at some of the more recent RT processing capabilities slowly making their way into the stock kernel but for now, it's a circumstance I must contend with! Thanks, JB ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd network interface names - new twist
On Thu, Jun 02, 2016 at 06:24:39AM -0600, JB wrote: > I'm running kernel 3.18.22. I'm seeing some odd behavior from systemd. The > motherboard is an intel board with dual onboard NIC. I installed FC21 > initially with secondary ethernet interface disabled in the BIOS. Then after > install, I enabled it. However, while the first NIC name comes up as > expected getting renamed from eth0 to eno#. The second NIC never gets > renamed and instead is brought up as eth1. > > What's up with that? I thought they were all supposed to get en* names. I > mean after all, I've already retooled all our software to accommodate the > new scheme. This sounds like a Fedora bug, in noticing your "new" NIC that showed up after the system was installed. I suggest you file a bug with their reporting system. Also, please note that the 3.18 kernel is very old and unsupported, you might want to update to a modern kernel release :) hope this helps, greg k-h ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd network interface names - new twist
I'm running kernel 3.18.22. I'm seeing some odd behavior from systemd. The motherboard is an intel board with dual onboard NIC. I installed FC21 initially with secondary ethernet interface disabled in the BIOS. Then after install, I enabled it. However, while the first NIC name comes up as expected getting renamed from eth0 to eno#. The second NIC never gets renamed and instead is brought up as eth1. What's up with that? I thought they were all supposed to get en* names. I mean after all, I've already retooled all our software to accommodate the new scheme. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
