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

[systemd-devel] Adding dbus interface to networkd for dhcp leases

I'd like to add a dbus interface to networkd to be able to query information about the current dhcpcd leases. I've seen some talk [0][1] before saying the dbus interface is being worked on/planned. What is its current status and what plans are already in place, if any? If there aren't already

Re: [systemd-devel] Stretch systemd_230-1_amd64.deb systemctl set-default segfaults

Lennart Poettering composed on 2016-06-02 13:21 (UTC+0200): Felix Miata wrote: Anyone else notice this happening? Known problem? [ 848.647555] systemctl[666]: segfault at 0 ip 561573dc3c03 sp 7ffeddbff490 error 4 in systemctl[561573d51000+a3000] Please provide a proper

[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

Re: [systemd-devel] why does bootctl default to /boot and not to /boot/efi?

On Thu, Jun 2, 2016 at 1:34 PM, Lennart Poettering wrote: > > sd-boot certainly requires none of that. > 640K is more memory than anyone will ever need. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] why does bootctl default to /boot and not to /boot/efi?

On Wed, 01.06.16 19:53, Chris Murphy (li...@colorremedies.com) wrote: > On Wed, Jun 1, 2016 at 2:46 AM, Colin Guthrie wrote: > > Lennart Poettering wrote on 30/05/16 17:47: > >> hence an acceptable alternatively might be to > >> introduce /efi and mount the esp there, and

Re: [systemd-devel] Stretch systemd_230-1_amd64.deb systemctl set-default segfaults

On Thu, 02.06.16 00:57, Felix Miata (mrma...@earthlink.net) wrote: > Anyone else notice this happening? Known problem? > > [ 848.647555] systemctl[666]: segfault at 0 ip 561573dc3c03 sp > 7ffeddbff490 error 4 in systemctl[561573d51000+a3000] Please provide a proper backtrace.

Re: [systemd-devel] why does bootctl default to /boot and not to /boot/efi?

On Wed, Jun 1, 2016 at 10:13 PM, Mantas Mikulėnas wrote: > Hmm, I thought Windows creates a 512 MB ESP by default (as per MS's own > recommendations)? It depends on the OEM. Few installations are done by users/admins, Windows is pre-installed and the restore software is OEM

Re: [systemd-devel] why does bootctl default to /boot and not to /boot/efi?

On Thu, Jun 2, 2016 at 4:34 AM, Lennart Poettering wrote: > On Wed, 01.06.16 19:53, Chris Murphy (li...@colorremedies.com) wrote: >> Well it's a non-starter for dual boot because the existing Windows and >> OS X ESP's are too small to host kernels, and I'm not aware of

[systemd-devel] Unit that depends on A or B

Hi all, On my system, I can setup 2 VPN connections, which are mutually exclusive as they reach the same subnet for the most part. Let's call these A and B. A is faster than B, but B gives access to some extra subnets. Now, I have a unit(some-dht.service) that needs a VPN connection but

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

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

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

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

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

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

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

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

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