On Thu, Oct 17, 2019 at 05:06:32PM -0700, Ross Vandegrift wrote:
> On Fri, Oct 18, 2019 at 01:04:56AM +0200, Dick Visser wrote:
> > On Fri, 18 Oct 2019 at 00:53, Noah Meyerhans wrote:
> > > Can you explain why this causes problems for you? We want to keep device
> > > renaming enabled for
On Fri, Oct 18, 2019 at 01:04:56AM +0200, Dick Visser wrote:
> On Fri, 18 Oct 2019 at 00:53, Noah Meyerhans wrote:
> > Can you explain why this causes problems for you? We want to keep device
> > renaming enabled for consistency with standard Debian installations, and
> > we aren't aware of
On Fri, 18 Oct 2019 at 00:53, Noah Meyerhans wrote:
> Can you explain why this causes problems for you? We want to keep device
> renaming enabled for consistency with standard Debian installations, and
> we aren't aware of specific problems with it that necessitate it being
> disabled.
I'm
Hello.
On Fri, Oct 18, 2019 at 12:39:15AM +0200, Dick Visser wrote:
> I'm happily using the new Buster AMI, but I noticed that the image has
> consistent device naming enabled, so my instances have their single
> interface called "ens5".
Can you explain why this causes problems for you? We want
Hi
I'm happily using the new Buster AMI, but I noticed that the image has
consistent device naming enabled, so my instances have their single
interface called "ens5".
The Stretch AMIs have that disabled (net.ifnames=0) so there it's just "eth0".
The Stretch AMI has this in /etc/default/grub:
