lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Tue, 29 Aug 2006 02:26:35 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	miles.lane@...il.com
Cc:	akpm@...l.org, dcbw@...hat.com, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, jeremy@...p.org, rml@...ell.com
Subject: Re: 2.6.18-rc4-mm[1,2,3] -- Network card not getting assigned an
 "eth" device name

From: "Miles Lane" <miles.lane@...il.com>
Date: Tue, 29 Aug 2006 01:43:48 -0700

> Then, when I testing running NetworkManager.bak, I got:
> 
> [NetworkManager.:6078]: Changing netdevice name from [eth1] to [`.$,3u=.(B..$,3u=.(B]
> [NetworkManager.:6078]: Changing netdevice name from [eth0] to [`.$,3u=.(B..$,3u=.(B]

Someone who can debug NetworkManager with gdb or similar needs
to step through it and figure out why it wants to use this
crazy garbage string as the name.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ