Very sorry. I told you guys some horrible lies yesterday about Buster.
ifupdown is there.
route is back.
ifconfig is back.
Thanks much, Fungi4All, for the name fix, I haven't implemented it
yet, and I'm not sure I will because who knows what'll happen in the
next release. I'm going to try to
Fungi4All composed on 2017-09-04 07:16 (UTC-0400):
>> From: mrma...@earthlink.net To: debian-user@lists.debian.org
>> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):
>>> But Fungi4All"s solution is so easy to use that I"m won over, and have
>>> implemented it here.
>> I think I
> From: mrma...@earthlink.net
> To: debian-user@lists.debian.org
>
> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):
>
>> But Fungi4All"s solution is so easy to use that I"m won over, and
>> have implemented it here.
>
> I think I started putting net.ifnames=0 on the kernel command line
On 04.09.17 04:42, Felix Miata wrote:
> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):
>
> > But Fungi4All's solution is so easy to use that I'm won over, and
> > have implemented it here.
>
> I think I started putting net.ifnames=0 on the kernel command line close to 3
> years ago.
Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):
> But Fungi4All's solution is so easy to use that I'm won over, and
> have implemented it here.
I think I started putting net.ifnames=0 on the kernel command line close to 3
years ago. :-)
More than that it's been around:
On 03.09.17 20:09, Glenn English wrote:
> I looked on the 'Net, asking why the interface names were changed. I
> found a good reason: sometimes the ethn names aren't reliably
> consistent. Fine, I say, you've figured how to make them consistent.
> That's no reason to change the names from a
On 04/09/17 10:27, Fungi4All wrote:
Before you get a long lecture on the merits of long unique names try this:
Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :
GRUB_CMDLINE_LINUX="net.ifnames=0" If the biosdevname is installed you need to
add :
GRUB_CMDLINE_LINUX="net.ifnames=0
On Sun, Sep 03, 2017 at 06:27:12PM -0400, Fungi4All wrote:
> > From: ghe2...@gmail.com
> > The WiFi works, but the Ethernet doesn"t, and I can"t figure out why.
> > ip addr:
...
> Before you get a long lecture on the merits of long unique names try this:
>
> Edit your /etc/default/grub change
On 9/3/17, Glenn English wrote:
> Working on a Dell 5414 laptop, Stretch.
>
> The WiFi works, but the Ethernet doesn't, and I can't figure out why.
>
> ip addr:
>
> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
> link/loopback
> From: ghe2...@gmail.com
> To: debianUsers
>
> Working on a Dell 5414 laptop, Stretch.
>
> The WiFi works, but the Ethernet doesn"t, and I can"t figure out why.
>
> ip addr:
>
> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen
Working on a Dell 5414 laptop, Stretch.
The WiFi works, but the Ethernet doesn't, and I can't figure out why.
ip addr:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope
11 matches
Mail list logo