Re: [systemd-devel] Network Interface Names: solution for a desktop OS

On Wed, Apr 13, 2016 at 02:42:29AM +0200, Xen wrote: > When you say that probing on the PCI bus never ends, and if we are > talking not about some form of hotplugging, then I really wonder what > you're on about ;-) because I do think the kernel has a limited set of > probes that it can perform,

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

13.04.2016 02:24, Jordan Hargrave пишет: > > I am the primary developer of biosdevname. I've been wanting this > naming functionality built into systemd or even the OS itself. > Primarily I am interested in servers with multiple physical and > virtual NICs but getting it working on desktops

Re: [systemd-devel] Configuring ethernet link fails with No such device

[added Tom Gundersen as he seemed to have worked on udev's net link built-in] On 2016-04-12 08:44, David Miller wrote: > From: Bob Ham > Date: Tue, 12 Apr 2016 09:58:12 +0100 > >> On Mon, 2016-04-11 at 15:46 -0700, Stefan Agner wrote: >> >>> Or in other words: Is this a

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Reindl Harald schreef op 13-04-16 02:06: > > > Am 13.04.2016 um 01:20 schrieb Xen: >> Greg KH schreef op 13-04-16 01:16: >>> On Wed, Apr 13, 2016 at 12:39:37AM +0200, Xen wrote: All you need to do is wait a few seconds before you start renaming >>> >>> Most machines boot to login faster

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Reindl Harald schreef op 13-04-16 02:04: > > > Am 13.04.2016 um 00:03 schrieb Xen: >> Reindl Harald schreef op 12-04-16 21:35: >>> >>> Am 12.04.2016 um 21:24 schrieb Xen: However currently for me, biosdev renumbers these, while my scheme wouldn't >>> >>> wow - you even don't realise

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Greg KH schreef op 13-04-16 01:29: > On Wed, Apr 13, 2016 at 01:20:05AM +0200, Xen wrote: > All execpt for 4-socket and larger servers. They take tens of minutes > in the BIOS and then less than a minute in the kernel/userspace, > depending on the amount of memory. > > Doesn't your

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Jordan Hargrave schreef op 13-04-16 01:24: > I am the primary developer of biosdevname. I've been wanting this > naming functionality built into systemd or even the OS itself. > Primarily I am interested in servers with multiple physical and > virtual NICs but getting it working on desktops

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

> On Tue, Apr 12, 2016 at 5:06 PM, Reindl Harald wrote: Is there a ML anywhere on which you don't sputter, fume, rant and insult? If you don't like what you're reading -- walk away and don't participate. Adding yet another rule to the 'Raindl-Filter(tm)'. The

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 13.04.2016 um 01:20 schrieb Xen: Greg KH schreef op 13-04-16 01:16: On Wed, Apr 13, 2016 at 12:39:37AM +0200, Xen wrote: All you need to do is wait a few seconds before you start renaming Most machines boot to login faster than a "few seconds", so: Most machines boot to login faster

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 13.04.2016 um 00:03 schrieb Xen: Reindl Harald schreef op 12-04-16 21:35: Am 12.04.2016 um 21:24 schrieb Xen: However currently for me, biosdev renumbers these, while my scheme wouldn't wow - you even don't realise that "biosdevname" and

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

On Wed, Apr 13, 2016 at 01:20:05AM +0200, Xen wrote: > Greg KH schreef op 13-04-16 01:16: > > On Wed, Apr 13, 2016 at 12:39:37AM +0200, Xen wrote: > >> All you need to do is wait a few seconds before you start renaming > > > > Most machines boot to login faster than a "few seconds", so: > > Most

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

On Tue, Apr 12, 2016 at 5:39 PM, Xen wrote: > Just want to summarize here very shortly. > > > If you turn the hotplug naming scheme into something more attractive. > > If you turn the USB naming scheme into something more attractive. > > If you accept like a 99.9% confidence

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Greg KH schreef op 13-04-16 01:16: > On Wed, Apr 13, 2016 at 12:39:37AM +0200, Xen wrote: >> All you need to do is wait a few seconds before you start renaming > > Most machines boot to login faster than a "few seconds", so: Most machines boot to login faster than a few seconds? What machines

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

On Wed, Apr 13, 2016 at 12:39:37AM +0200, Xen wrote: > All you need to do is wait a few seconds before you start renaming Most machines boot to login faster than a "few seconds", so: > or wait on some defined trigger. Exactly what type of "defined trigger" would work for busses that you never

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Just want to summarize here very shortly. If you turn the hotplug naming scheme into something more attractive. If you turn the USB naming scheme into something more attractive. If you accept like a 99.9% confidence interval for waiting until hardware has shown itself, then taking the

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Reindl Harald schreef op 12-04-16 21:35: > > > Am 12.04.2016 um 21:24 schrieb Xen: >> However currently for me, biosdev renumbers these, while my scheme >> wouldn't > > wow - you even don't realise that "biosdevname" and >

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Reindl Harald schreef op 12-04-16 20:54: >> Then do it yourself. > > what? Design or propose something better. Maybe you thought the original system was better, I guess you mentioned something like that. > i am just a user like you but with technical understanding, the point is > that you

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 12.04.2016 um 21:24 schrieb Xen: However currently for me, biosdev renumbers these, while my scheme wouldn't wow - you even don't realise that "biosdevname" and https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ are two completly different things

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Manuel Amador (Rudd-O) schreef op 12-04-16 12:46: > On 04/12/2016 02:26 AM, Xen wrote: >> That is completely nonsensical because it would imply that some network >> device could be initialized 2 hours after the system had booted. > > Greg KH is completely correct -- that can totally happen. If

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 12.04.2016 um 20:37 schrieb Xen: Reindl Harald schreef op 12-04-16 11:24: Regular hardware should not suddenly appear out of nowhere, but I do not know about that Thunderbolt thing you mentioned that is nonsense * USB hardware is often *onboard* like SD-card slots on ProLiant

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Reindl Harald schreef op 12-04-16 11:24: >> Regular hardware should not suddenly appear out of nowhere, but I do not >> know about that Thunderbolt thing you mentioned > > that is nonsense > > * USB hardware is often *onboard* like SD-card slots on ProLiant > machines down to the HP

Re: [systemd-devel] centos-ci

On Tue, 12.04.16 14:57, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > >Right now the CI systems we use are all based on Ubuntu, which is > >kinda weird, as most of the systemd core developers actually work for > >RH and run Fedora locally... ;-) > > I see but It's should not matter which

Re: [systemd-devel] Configuring ethernet link fails with No such device

From: Bob Ham Date: Tue, 12 Apr 2016 09:58:12 +0100 > On Mon, 2016-04-11 at 15:46 -0700, Stefan Agner wrote: > >> Or in other words: Is this a Kernel or systemd issue? > > From what I recall, both; an issue with the FEC driver, and issues in > systemd/udevd's handling of

Re: [systemd-devel] centos-ci

On 04/12/2016 02:43 PM, Lennart Poettering wrote: On Tue, 12.04.16 11:52, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: Anyone know that centos is not running the latest version(s) of systemd required for the upstream bug tracker so one has to ask what notification spam is this "Can one

Re: [systemd-devel] centos-ci

On Tue, 12.04.16 11:52, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > Anyone know that centos is not running the latest version(s) of systemd > required for the upstream bug tracker so one has to ask what notification > spam is this > "Can one of the admins verify this patch?" Daniel is

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Reindl Harald schreef op 12-04-16 14:02: > Am 12.04.2016 um 14:00 schrieb Xen: >> Martin Pitt schreef op 12-04-16 12:57: >>> Xen [2016-04-12 3:37 +0200]: The trick to turn it off on the website doesn't work: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules >>> >>> It

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 12.04.2016 um 14:00 schrieb Xen: Martin Pitt schreef op 12-04-16 12:57: Xen [2016-04-12 3:37 +0200]: The trick to turn it off on the website doesn't work: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules It does (at least on Debian, Ubuntu, and Fedora), but you need to

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Martin Pitt schreef op 12-04-16 12:57: > Xen [2016-04-12 3:37 +0200]: >> The trick to turn it off on the website doesn't work: >> >> ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules > > It does (at least on Debian, Ubuntu, and Fedora), but you need to > rebuild your initrd after doing

[systemd-devel] centos-ci

Anyone know that centos is not running the latest version(s) of systemd required for the upstream bug tracker so one has to ask what notification spam is this "Can one of the admins verify this patch?" JBG ___ systemd-devel mailing list

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Xen [2016-04-12 3:37 +0200]: > The trick to turn it off on the website doesn't work: > > ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules It does (at least on Debian, Ubuntu, and Fedora), but you need to rebuild your initrd after doing this. Martin -- Martin Pitt

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

On 04/12/2016 02:26 AM, Xen wrote: > Greg KH schreef op 12-04-16 00:14: >>> Also, since the current scheme puts usb devices in a slightly different >>> format you can identify them from the name. >>> >>> You are right in saying that that would cause a list that changes as it >>> is getting

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 12.04.2016 um 04:26 schrieb Xen: Greg KH schreef op 12-04-16 00:14 How you determine if a device is "onboard" or "offboard"? Are you going to know when all "onboard" devices are found before you do anything else? How? I don't know, do you know? I am just a nitwit right. The

Re: [systemd-devel] Configuring ethernet link fails with No such device

On Mon, 2016-04-11 at 15:46 -0700, Stefan Agner wrote: > The FEC driver (fec_main.c) does not initialize phy_dev until the > device > has been opened, and therefor the callback > fec_enet_(get|set)_settings > returns -19. I saw the same problem with the FEC driver. From what I recall, it became

Re: [systemd-devel] Configuring ethernet link fails with No such device

On 2016-04-11 18:29, David Miller wrote: > From: Stefan Agner > Date: Mon, 11 Apr 2016 15:46:08 -0700 > >> What is the expectation/definition when link configuration should be >> possible? Only after the network device got opened or before? > > Only after it is open. Drivers

Re: [systemd-devel] Callback or Event Notification from journald in case of crash

On Wed, Apr 6, 2016 at 7:04 AM, P.R.Dinesh wrote: > I am using systemd, journald and systemd-coredump in my system. When a > process crashes the systemd-coredump util handles the core dump and logs a > message in the journal with MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1