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

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. > > Idiot. No he isn't. The developers here

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

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. Idiot. ___ systemd-devel mailing list

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

So why don't you implement such a scheme? Talk is cheap 2016-04-10 18:22 GMT+02:00 Xen : > I just want to present my conclusion here succintly. > > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ > > Was introduced to safeguard against a

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

I just want to present my conclusion here succintly. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Was introduced to safeguard against a rare occasion where an important network computer in a critical environment would suffer from the kernel anomaly that

Re: [systemd-devel] Fwd: Random X crash on nvidia card on Gnome 3.20

Thanks guys, I'm just a noob and don't know where to go, just followed system log suggested links to here. On Sun, Apr 10, 2016 at 11:49 PM, Tomasz Torcz wrote: > > Bob, > > There is so much wrong with this email, I'll be brief: > – this is gnome-shell crashing, nothing

Re: [systemd-devel] Fwd: Random X crash on nvidia card on Gnome 3.20

On Sun, Apr 10, 2016 at 11:12:00PM +0800, Bob Peng wrote: > Today I upgraded to 3.20 and it begins random crash, log is attached. > and dmesg log too. This isn't a systemd issue, it's a nvidia issue, please contact them for support as they are the only ones that can do so because of their closed

Re: [systemd-devel] Fwd: Random X crash on nvidia card on Gnome 3.20

Bob, There is so much wrong with this email, I'll be brief: – this is gnome-shell crashing, nothing related to systemd (and this is systemd-devel) - you are using binary nvidia drivers, which is nothing community can help you with - you are using this driver in unsupported configuration,

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

Am 10.04.2016 um 16:57 schrieb Martin Pitt: Andrei Borzenkov [2016-04-10 11:31 +0300]: It had been working out of the box for quite a lot of users actually. Because we had a mechanism for stable (but not predictable) interfaces names, the 75-persistent-net-generator.rules thingy. Without

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

Thank you Andrei and Reindl for your answers. Let's stick to the facts for the moment or as much of it as we can. Martin Pitt schreef op 10-04-16 10:17: > There are very good reasons for having a mechanism for stable names by > default. Most importantly, to keep your machine actually >

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

I would like to write to /dev/stderr and tried that but it didn’t work. I think it’s something to do with the way it works internally (nginx + phusion passenger). > On 11/04/2016, at 12:43 AM, Mantas Mikulėnas wrote: > > On Sun, Apr 10, 2016 at 1:57 PM, Samuel Williams >

[systemd-devel] Fwd: Random X crash on nvidia card on Gnome 3.20

Today I upgraded to 3.20 and it begins random crash, log is attached. and dmesg log too. Cheers 1] % dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.5-1-ARCH

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

Andrei Borzenkov [2016-04-10 11:31 +0300]: > It had been working out of the box for quite a lot of users actually. 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

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

On Sun, Apr 10, 2016 at 1:57 PM, 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

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

Am 10.04.2016 um 10:17 schrieb Martin Pitt: Any user running a system with multiple NICs should be willing and capable of choosing and assigning these names. To be frank, this is the attitude of the 90's when you had to sit down with a thick book and spend a week until your Linux system was

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

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 to journald. I made the following unit journald-fifo@.service [Unit] Description=A fifo

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

10.04.2016 11:17, Martin Pitt пишет: > Hello, > > Xen [2016-04-09 20:29 +0200]: >> 1. I believe most users do not like the "enp5s0" scheme >> 2. I do not think there are any good reasons for making it the default. > > There are very good reasons for having a mechanism for stable names by >

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

Hello, Xen [2016-04-09 20:29 +0200]: > 1. I believe most users do not like the "enp5s0" scheme > 2. I do not think there are any good reasons for making it the default. There are very good reasons for having a mechanism for stable names by default. Most importantly, to keep your machine actually