On Thu, Dec 22, 2016 at 10:40 AM, Daniel Frey wrote:
> On 12/21/2016 10:53 PM, Tom H wrote:
>> On Tue, Dec 20, 2016 at 3:35 PM, Daniel Frey wrote:
>>>
>>> It could be I found a bug. After a reboot it went from the normal
>>> enp0s1 (or whatever) to eno1677789 or something ridiculous. I had
>>> th
On Thu, Dec 22, 2016 at 7:38 AM, Neil Bothwick wrote:
>
> I don't use grub on UEFI systems, but I use the systemd bootloader, so I
> thought I'd keep quiet about that ;-)
I'm also a heretic who uses the systemd bootloader no matter what pid1
is in charge.
It's the best thing that the systemd dev
It took me all of my skills ;-) . But I installed Pale Moon, using my
local overlay made from the official
https://github.com/deuiore/palemoon-overlay
which installed, via my Cgit bare git repo served by my (local only yet)
Apache, and so from my local mirror, in arcane ways (which I do not
underst
On 12/21/2016 10:53 PM, Tom H wrote:
> On Tue, Dec 20, 2016 at 3:35 PM, Daniel Frey wrote:
>> On 12/19/2016 01:09 PM, Andrej Rode wrote:
>>>
>>> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
>>
>> It could be I found a bug. After a reboot it went from the norm
On Thu, 22 Dec 2016 05:27:03 -0500, Tom H wrote:
> > You forgot /etc/default/grub ;-)
>
> Indeed :)
>
> But I was going with the idea of using udev to rename NICs rather than
> reverting to kernel names.
>
> I hope that you're ready to duck because someone might say "Linux is
> about choice"
On Thu, Dec 22, 2016 at 5:14 AM, Neil Bothwick wrote:
> On Thu, 22 Dec 2016 04:52:41 -0500, Tom H wrote:
>
>> All of this whining about predictable NIC names would be more or less
>> OK if there wasn't an easy way to override them in
>> "/{lib,etc}/systemd/network/" (even on a non-systemd system,
On Thu, 22 Dec 2016 04:52:41 -0500, Tom H wrote:
> All of this whining about predictable NIC names would be more or less
> OK if there wasn't an easy way to override them in
> "/{lib,etc}/systemd/network/" (even on a non-systemd system, see [1])
> or in "/etc/udev/rules.d/"!
You forgot /etc/defau
On Thu, Dec 22, 2016 at 3:56 AM, Neil Bothwick wrote:
> On Thu, 22 Dec 2016 04:15:50 +0100, lee wrote:
>>
>> The perceived advantage lies in being able to refer to network ports
>> in a more reliable way, and I don't see how using unrecognisable
>> names instead of recognisable ones would make any
On Wed, Dec 21, 2016 at 05:19:35PM -0800, Daniel Campbell wrote
> On Wed, Dec 21, 2016 at 07:53:51AM -0500, Rich Freeman wrote:
>
> > How do you think we ended up with eudev?
>
> I assume we ended up with eudev because upstream decided that
> they were going back on their promise that udev would
On Thu, 22 Dec 2016 04:15:50 +0100, lee wrote:
> > There are no config files to edit with the predictable names, the
> > names are created from the physical location of the port. That's why
> > they are called predictable,
>
> I only know what the names are when I can look them up when the com
10 matches
Mail list logo
