Re: [systemd-devel] How to log to journald using fifo?

On Sun, 10.04.16 22:57, Samuel Williams (space.ship.travel...@gmail.com) wrote: > Hello, > > > I've been trying to figure out the best way to support legacy applications > that don't support syslog for logging. The best we can do, I think, is to > use fifo and have another process read the fifo

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

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 almost always have the entire chip in powerdown state

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

On Mon, Apr 11, 2016 at 11:13:25PM +0200, Xen wrote: > >> You can put usb devices at the end of the list. > > > > Why last? How do you know they go last when scanning? How do you know > > when / if they will show up? What about 2 USB devices? 3? > > To me it seems obvious that you initialize

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

Xen schreef op 11-04-16 23:13: > No. You are causing pain and suffering to millions of people. > > You (...) have not inquired with anyone whether they really wanted this. > > So you push something and then you say "oh, but you can opt out". > > So you place the burden on the user. It doesn't

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

Xen schreef op 12-04-16 04:26: > I didn't even know it was that bad, jeez. > > My apologies. My sound stopped working as well because it was now a new device ;-) (different PCI bus number). The system sees it now as two devices, one of which is not present. They are the same device of course.

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

Greg KH schreef op 12-04-16 00:14: > On Mon, Apr 11, 2016 at 11:13:25PM +0200, Xen wrote: You can put usb devices at the end of the list. >>> >>> Why last? How do you know they go last when scanning? How do you know >>> when / if they will show up? What about 2 USB devices? 3? >> >> To me

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

On Mon, Apr 11, 2016 at 11:56:00AM +0200, Xen wrote: > The predictability issue seems to be due to using a MAC address. > > AFAIK a reinstall will not change PCI bus devices etc. No, PCI device numbers change all the time, they are not guaranteed to be stable at all. Yes, lots of machines do

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

Reindl Harald [2016-04-10 17:44 +0200]: > >Because we had a mechanism for stable (but not predictable) interfaces > >names, the 75-persistent-net-generator.rules thingy. Without either, > >the first time you plugged in a second card/USB dongle/add an ibmveth > >etc., chaos would start. > > that

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

Am 11.04.2016 um 10:40 schrieb Martin Pitt: Reindl Harald [2016-04-10 17:44 +0200]: Because we had a mechanism for stable (but not predictable) interfaces names, the 75-persistent-net-generator.rules thingy. Without either, the first time you plugged in a second card/USB dongle/add an ibmveth

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

Martin Pitt schreef op 11-04-16 10:40: > Reindl Harald [2016-04-10 17:44 +0200]: >>> Because we had a mechanism for stable (but not predictable) interfaces >>> names, the 75-persistent-net-generator.rules thingy. Without either, >>> the first time you plugged in a second card/USB dongle/add an

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

Greg KH schreef op 11-04-16 01:05: > On Mon, Apr 11, 2016 at 12:27:24AM +0200, Xen wrote: >> Michael Biebl schreef op 11-04-16 00:22: >>> So why don't you implement such a scheme? Talk is cheap >> >> Criticising an idea by saying "do it yourself" is even cheaper. >> >> MUCH MUCH cheaper. >> >>

[systemd-devel] ReadOnlyDirectories and new mounts

I have long-running service with tight restrictions: ReadOnlyDirectories=/ ReadWriteDirectories=-/proc ReadWriteDirectories=-/var/lib/foobar ReadWriteDirectories=-/var/log/foobar ReadWriteDirectories=-/var/run I mounted some new directory on main system, and noticed that

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

Greg KH schreef op 11-04-16 15:42: > On Mon, Apr 11, 2016 at 11:56:00AM +0200, Xen wrote: >> The predictability issue seems to be due to using a MAC address. >> >> AFAIK a reinstall will not change PCI bus devices etc. > > No, PCI device numbers change all the time, they are not guaranteed to >

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

On Mon, Apr 11, 2016 at 07:59:30PM +0200, Xen wrote: > Greg KH schreef op 11-04-16 15:42: > > On Mon, Apr 11, 2016 at 11:56:00AM +0200, Xen wrote: > >> The predictability issue seems to be due to using a MAC address. > >> > >> AFAIK a reinstall will not change PCI bus devices etc. > > > > No, PCI

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

On Mon, Apr 11, 2016 at 08:49:48PM +0200, Xen wrote: > It will just not be "predictable" when you remove or add hardware, > because that reorders the resulting lists. > > Ie, if you have: > > ethernet0 > ethernet1 > ethernet2 > > And you add a new device, it might become: > > ethernet0 >

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

Greg KH schreef op 11-04-16 22:19: >> My device is enp3s0, which implies 3rd bus number, which it indeed is: >> >> E: ID_PATH=pci-:03:00.0 >> >> Are you telling me there are systems where this is not guaranteed to be >> stable? > > Yes, including your own. So biosdev is not guaranteed to be

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

On Mon, Apr 11, 2016 at 08:49:48PM +0200, Xen wrote: > It will just not be "predictable" when you remove or add hardware, > because that reorders the resulting lists. > > Ie, if you have: > > ethernet0 > ethernet1 > ethernet2 > > And you add a new device, it might become: > > ethernet0 >

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

Hi All, I traced an issue in which we tried configuring duplex mode and speed in a systemd-udevd .link file failed with the following error: "Could not set speed or duplex of eth0 to 0 Mbps (half): No such device" The FEC driver (fec_main.c) does not initialize phy_dev until the device has been

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

Greg KH schreef op 11-04-16 22:21: > On Mon, Apr 11, 2016 at 08:49:48PM +0200, Xen wrote: >> It will just not be "predictable" when you remove or add hardware, >> because that reorders the resulting lists. >> >> Ie, if you have: >> >> ethernet0 >> ethernet1 >> ethernet2 >> >> And you add a new

Re: [systemd-devel] ReadOnlyDirectories and new mounts

Am 11.04.2016 um 21:22 schrieb Yuriy M. Kaminskiy: I have long-running service with tight restrictions: ReadOnlyDirectories=/ ReadWriteDirectories=-/proc ReadWriteDirectories=-/var/lib/foobar ReadWriteDirectories=-/var/log/foobar ReadWriteDirectories=-/var/run I mounted