Re: [gentoo-user] Re: Network config problem
* Nuno Silva: > Which version of netifrc do you have? Could this be bug 642774[1]? Possibly. Similar issues have been reported for a while, see for example https://bugs.gentoo.org/609682 . Since I only stop network interfaces manually once in a blue moon, I have shrugged it off so far. -Ralph
[gentoo-user] Re: Network config problem
On 2019-11-30 14:34, Peter Humphrey wrote: > I want to start playing with IPv6 (thanks, Ralph S.) but first I need > to clean up something wrong with my existing IPv4. > * Bringing down interface eth0 > RTNETLINK answers: No such file or directory > Error talking to the kernel Do you mean the bit above? I get that too, and I have been seeing it for as long as I remember - maybe always. I ignore it and nothing bad happens. I have totally different hardware (r8169), and I have the "stable" names on (ahem), so I think neither of those are relevant. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.
Re: [gentoo-user] per package parallel build
On Sat, 30 Nov 2019 16:47:35 +, Wols Lists wrote: > > There's no need to mess around adding and removing masks, just use > > the - > > - exclude option. > > > > Yep! For some reason, that option doesn’t always occur to me, but > > that’s clearly a simpler way to do it. Thanks for reminding me! > > > Couldn't you just have a script that "emerge --update"s each package in > sequence? If the package isn't due for update nothing will happen. And > then you could follow that with an "emerge world" knowing that your hogs > are already done. Sometimes the packages are rebuilt without an update, especially if you use --changed-use or --changed-deps, so it's not quite that simple. -- Neil Bothwick I am Flatulus of Borg. You will be asphixiated. pgpVAqzy6WIHV.pgp Description: OpenPGP digital signature
[gentoo-user] Re: Network config problem
On 2019-11-30, Peter Humphrey wrote: > I want to start playing with IPv6 (thanks, Ralph S.) but first I need > to clean up something wrong with my existing IPv4. > > # /etc/init.d/net.eth0 restart [...] > * Bringing down interface eth0 > RTNETLINK answers: No such file or directory > Error talking to the kernel > * Bringing up interface eth0 [...] Which version of netifrc do you have? Could this be bug 642774[1]? It depends on the request to stabilize netifrc-0.6.1, so if you have an older version, you could try that one. >From the commit itself[2], it looks like netifrc is checking for L2TP in a way which produces this output when L2TP isn't supported. [1] https://bugs.gentoo.org/show_bug.cgi?id=642774 [2] https://gitweb.gentoo.org/proj/netifrc.git/commit/?id=1e14262524d65918ed6d1d13f2abd87b2f11425b -- Nuno Silva
Re: [gentoo-user] Network config problem
On sam. 30 nov. 16:36:33 2019, Peter Humphrey wrote: > It doesn't raise an error on starting, only on stopping. Yeah, you already posted it. -- Alarig
Re: [gentoo-user] per package parallel build
On 26/10/19 14:32, John Blinka wrote: > There's no need to mess around adding and removing masks, just use the - > - exclude option. > > Yep! For some reason, that option doesn’t always occur to me, but > that’s clearly a simpler way to do it. Thanks for reminding me! > Couldn't you just have a script that "emerge --update"s each package in sequence? If the package isn't due for update nothing will happen. And then you could follow that with an "emerge world" knowing that your hogs are already done. Cheers, Wol
Re: [gentoo-user] Network config problem
On Saturday, 30 November 2019 16:28:38 GMT Alarig Le Lay wrote: > On sam. 30 nov. 16:19:42 2019, Peter Humphrey wrote: > > I don't know what to make of that systemd-udevd failure: this is an openrc > > box. > > If you don’t have eudev, /dev is still managed by systemd. > > > My ISP has set me up with IPv6, and my Billion Bipac vDSL modem-router > > evidently passes me an IPv6 address when I '/etc/init.d/net.eth0 start'. > > Perhaps, try to disable eth0 from default, do ip link up eth0; ip a & > stuff by hand, and try to see what’s happening and at witch step netlink > raises the error. It doesn't raise an error on starting, only on stopping. -- Regards, Peter.
Re: [gentoo-user] Network config problem
On sam. 30 nov. 16:19:42 2019, Peter Humphrey wrote: > I don't know what to make of that systemd-udevd failure: this is an openrc > box. If you don’t have eudev, /dev is still managed by systemd. > My ISP has set me up with IPv6, and my Billion Bipac vDSL modem-router > evidently passes me an IPv6 address when I '/etc/init.d/net.eth0 start'. Perhaps, try to disable eth0 from default, do ip link up eth0; ip a & stuff by hand, and try to see what’s happening and at witch step netlink raises the error. Regards, -- Alarig
Re: [gentoo-user] Network config problem
On Saturday, 30 November 2019 14:44:15 GMT Alarig Le Lay wrote: > Isn’t your NIC called eno1 or enp1s0 or enp1s0f0? Nope: # dmesg | grep eth0 [6.510595] e1000e :00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 9c:5c: 8e:d1:17:f7 [6.510596] e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection [6.510620] e1000e :00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FF-0FF [8.948273] systemd-udevd[823]: eth0: Process 'net.sh eth0 start' failed with exit code 1. [ 11.674656] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 14.580833] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 14.580865] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready I don't know what to make of that systemd-udevd failure: this is an openrc box. My ISP has set me up with IPv6, and my Billion Bipac vDSL modem-router evidently passes me an IPv6 address when I '/etc/init.d/net.eth0 start'. Eno and enp don't appear in dmesg; I have net.ifnames=0 as a kernel parameter at boot time. -- Regards, Peter.
Re: [gentoo-user] Network config problem
Hi, On sam. 30 nov. 14:34:00 2019, Peter Humphrey wrote: > Hello list, > > I want to start playing with IPv6 (thanks, Ralph S.) but first I need to > clean > up something wrong with my existing IPv4. > > # /etc/init.d/net.eth0 restart > * Unmounting network filesystems ... [ ok ] > * Stopping gkrellmd ...[ ok ] > * Bringing down interface eth0 > RTNETLINK answers: No such file or directory > Error talking to the kernel > * Bringing up interface eth0 > * 192.168.1.5/24 ... [ ok ] > * Adding routes > * default via 192.168.1.254 ...[ ok ] > * default via fe80::1 ... [ ok ] > * Starting gkrellmd ...[ ok ] > * Mounting network filesystems ... [ ok ] > > How should I debug this? > > # cat etc/conf.d/net > dns_domain_lo="prhnet.local" > > config_eth0="192.168.1.5/24" > routes_eth0="default via 192.168.1.254" > dns_servers_eth0="192.168.1.2 192.168.1.254" > > The NIC is an e1000e. Isn’t your NIC called eno1 or enp1s0 or enp1s0f0? Regards, -- Alarig
[gentoo-user] Network config problem
Hello list, I want to start playing with IPv6 (thanks, Ralph S.) but first I need to clean up something wrong with my existing IPv4. # /etc/init.d/net.eth0 restart * Unmounting network filesystems ... [ ok ] * Stopping gkrellmd ...[ ok ] * Bringing down interface eth0 RTNETLINK answers: No such file or directory Error talking to the kernel * Bringing up interface eth0 * 192.168.1.5/24 ... [ ok ] * Adding routes * default via 192.168.1.254 ...[ ok ] * default via fe80::1 ... [ ok ] * Starting gkrellmd ...[ ok ] * Mounting network filesystems ... [ ok ] How should I debug this? # cat etc/conf.d/net dns_domain_lo="prhnet.local" config_eth0="192.168.1.5/24" routes_eth0="default via 192.168.1.254" dns_servers_eth0="192.168.1.2 192.168.1.254" The NIC is an e1000e. -- Regards, Peter.
Re: [gentoo-user] Conflicting version...but the version scheme is confusing...
Am Sa., 30. Nov. 2019 um 11:34 Uhr schrieb Mick : > On Saturday, 30 November 2019 07:17:01 GMT Franz Fellner wrote: > > inkscape-0.92.4 has the same issue. > > The problem is that the API (Programming interface, not Binary interface) > > between imagemagick-6 and imagemagick-7 isn't compatible. > > And inkscape never was updated to use the API from imagemagick-7. > > Yes, that's exactly the problem. > > media-gfx/inkscape-0.92.4 which is presently the stable version is quite > happy > with media-gfx/imagemagick-7.0.9.5. > Ah. It's 7.0.8.5, not 7.0.9.5: https://bugs.gentoo.org/663468#c5 Some deprecated features of the API were removed. Unfortunately also the pkgconfig file was renamed to Magick++ which made inkscape silently disable imagemagick support and the compilation failure/incompatibility wasn't noticed for a long time. > However, the unstable version of inkscape-1.0_beta1 requires imagemagick > versions prior to 7.0.9.5, with the currently available version of > imagemagick-6.9.10.74 fulfilling the requirement. > imakemagick-7.0.8.5, again. Not that nobody will stay confused. > > 1) entirely disable imagemagick for inkscape, e.g. with > "media-gfx/inkscape > > -imagemagick" in package.use > > If you do this, you'll find that conversions and imports/exports from one > graphics file format to another would be somewhat limited. Imagemagick > relies > on inkscape for this functionality. > The other way around, inkscape needs imagemagick for such conversions. I don't know how limiting it will be. If all you want to do is create pure vector graphics you are good to go. > 2) Use inkscape-1.0.0_beta1 and enable both USE-Flags "imagemagick > > graphicsmagick". > > That way you will get the imagemagick features through > graphicsmagick, > > which means imagemagick is not a dependency of inkscape anymore. > > Right, but graphicsmagick is more limited in its functionality than > imagemagick. For a poweruser of imagemagick this may present a problem - > but > I don't know how big a problem it might be. You aren't forced to build graphicsmagick as a complete replacement for imagemagick. You only need the C++-API for inkscape and not the commandline tools. Put "media-gfx/graphicsmagick cxx -imagemagick" in your package.use and imagemagick and graphicsmagick can be installed at the same time.
Re: [gentoo-user] Conflicting version...but the version scheme is confusing...
On Saturday, 30 November 2019 07:17:01 GMT Franz Fellner wrote: > inkscape-0.92.4 has the same issue. > The problem is that the API (Programming interface, not Binary interface) > between imagemagick-6 and imagemagick-7 isn't compatible. > And inkscape never was updated to use the API from imagemagick-7. Yes, that's exactly the problem. media-gfx/inkscape-0.92.4 which is presently the stable version is quite happy with media-gfx/imagemagick-7.0.9.5. However, the unstable version of inkscape-1.0_beta1 requires imagemagick versions prior to 7.0.9.5, with the currently available version of imagemagick-6.9.10.74 fulfilling the requirement. The inkscape package is the dog and imagemagick (a dependency) is the tail. Usually the dog wags the tail and not the other way around. However, portage is asking for inkscape to be keyworded to a testing beta version for what appears to me to be no good reason. Portage should keep inkscape at the stable 0.92.4 version, with imagemagick at 6.9.10.74, on a system which is running stable packages. > That's why you are forced to downgrade imagemagick to a version lower than > 7 when you want to use imagemagick in inkscape. > If you want to stay with imagemagick >=7 you have two options: > 1) entirely disable imagemagick for inkscape, e.g. with "media-gfx/inkscape > -imagemagick" in package.use If you do this, you'll find that conversions and imports/exports from one graphics file format to another would be somewhat limited. Imagemagick relies on inkscape for this functionality. > 2) Use inkscape-1.0.0_beta1 and enable both USE-Flags "imagemagick > graphicsmagick". > That way you will get the imagemagick features through graphicsmagick, > which means imagemagick is not a dependency of inkscape anymore. Right, but graphicsmagick is more limited in its functionality than imagemagick. For a poweruser of imagemagick this may present a problem - but I don't know how big a problem it might be. While I was chasing my tail around this clash hoping portage would eventually get it right, I seem to recall a more recent combo. When inkscape-1.0_beta1 is keyworded, portage is asking to also keyword imagemagick-*. I assume the trunk has a version which works with inkscape-1.0_beta1, but I'm not sure. For now I just exclude inkscape from upgrades until the dust on this settles. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
