On Thu, Jan 17, 2013 at 9:51 AM, Ian Stakenvicius wrote:
> On 16/01/13 09:55 PM, Rich Freeman wrote:
>> SUBSYSTEM=="tty", DRIVERS=="pl2303", KERNELS=="4-1:1.0",
>> KERNEL=="ttyUSB*", SYMLINK="mythser/rca1"
>>
>> I'm not sure if rules are additive - if these symlinks would show
>> up in addition to
2013/1/19 William Hubbs
> On Fri, Jan 18, 2013 at 10:07:42AM -0500, Ian Stakenvicius wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On 18/01/13 09:54 AM, William Hubbs wrote:
> > > On Fri, Jan 18, 2013 at 08:33:13AM -0500, Ian Stakenvicius wrote:
> > >> -BEGIN PGP SIGN
On Fri, Jan 18, 2013 at 10:07:42AM -0500, Ian Stakenvicius wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 18/01/13 09:54 AM, William Hubbs wrote:
> > On Fri, Jan 18, 2013 at 08:33:13AM -0500, Ian Stakenvicius wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
> >>
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/01/13 09:54 AM, William Hubbs wrote:
> On Fri, Jan 18, 2013 at 08:33:13AM -0500, Ian Stakenvicius wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 18/01/13 07:24 AM, viv...@gmail.com wrote:
>>> Since for servers predictable n
On Fri, Jan 18, 2013 at 08:33:13AM -0500, Ian Stakenvicius wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 18/01/13 07:24 AM, viv...@gmail.com wrote:
> > Since for servers predictable names are useful and for desktop
> > (which usually have only one ethernet that never change) Is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/01/13 07:24 AM, viv...@gmail.com wrote:
> Since for servers predictable names are useful and for desktop
> (which usually have only one ethernet that never change) Is it
> possible to set desktop profiles to still use ethX, and base
> profile
Il 09/01/2013 23:13, William Hubbs ha scritto:
All,
as you probably know by now, udev-197 has hit the tree.
This new version implements a new feature called predictable network
interface names [1], which I have currently turned off for live systems,
because it
will require migration on the par
On Thu, Jan 17, 2013 at 07:44:39PM +0100, Tobias Klausmann wrote:
> Hi!
>
> On Thu, 17 Jan 2013, Peter Stuge wrote:
> > Tobias Klausmann wrote:
> > > It has been rather nifty that if I walk up to a random machine
> > > with exactly one NIC (that I've been asked to examine/fix), I
> > > _know_ tha
Hi!
On Thu, 17 Jan 2013, Peter Stuge wrote:
> Tobias Klausmann wrote:
> > It has been rather nifty that if I walk up to a random machine
> > with exactly one NIC (that I've been asked to examine/fix), I
> > _know_ that there will be eth0 and only that.
>
> Only as long as that system hasn't seen
Tobias Klausmann wrote:
> It has been rather nifty that if I walk up to a random machine
> with exactly one NIC (that I've been asked to examine/fix), I
> _know_ that there will be eth0 and only that.
Only as long as that system hasn't seen *another* NIC first, if it
has persistent interface name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/01/13 09:55 PM, Rich Freeman wrote:
> SUBSYSTEM=="tty", DRIVERS=="pl2303", KERNELS=="4-1:1.0",
> KERNEL=="ttyUSB*", SYMLINK="mythser/rca1"
>
> I'm not sure if rules are additive - if these symlinks would show
> up in addition to whatever othe
On 17/01/13 04:49, Greg KH wrote:
On Wed, Jan 16, 2013 at 06:36:59AM -0500, Rich Freeman wrote:
On Tue, Jan 15, 2013 at 10:42 PM, Peter Stuge wrote:
Rich Freeman wrote:
Not that anybody is taking requests, but it would be really handy
if serial ports were deterministically labeled.
Does /de
On Wed, Jan 16, 2013 at 9:49 PM, Greg KH wrote:
> On Wed, Jan 16, 2013 at 06:36:59AM -0500, Rich Freeman wrote:
>> On Tue, Jan 15, 2013 at 10:42 PM, Peter Stuge wrote:
>> > Rich Freeman wrote:
>> >> Not that anybody is taking requests, but it would be really handy
>> >> if serial ports were deter
On Wed, Jan 16, 2013 at 06:36:59AM -0500, Rich Freeman wrote:
> On Tue, Jan 15, 2013 at 10:42 PM, Peter Stuge wrote:
> > Rich Freeman wrote:
> >> Not that anybody is taking requests, but it would be really handy
> >> if serial ports were deterministically labeled.
> >
> > Does /dev/serial/* solve
On 01/16/2013 05:25 PM, Mike Gilbert wrote:
>> It has been rather nifty that if I walk up to a random machine
>> with exactly one NIC (that I've been asked to examine/fix), I
>> _know_ that there will be eth0 and only that.
++
> I would actually like to see iproute2 added to the system set.
++
--
Il 16/01/2013 17:25, Mike Gilbert ha scritto:
On Wed, Jan 16, 2013 at 10:19 AM, Tobias Klausmann wrote:
Hi!
On Tue, 15 Jan 2013, Greg KH wrote:
So anyone who relies on network names right now to be deterministic, and
you have more than one network device in your system, should seriously
recon
On Wed, Jan 16, 2013 at 10:19 AM, Tobias Klausmann wrote:
> Hi!
>
> On Tue, 15 Jan 2013, Greg KH wrote:
>> So anyone who relies on network names right now to be deterministic, and
>> you have more than one network device in your system, should seriously
>> reconsider how they are naming their devi
Hi!
On Tue, 15 Jan 2013, Greg KH wrote:
> So anyone who relies on network names right now to be deterministic, and
> you have more than one network device in your system, should seriously
> reconsider how they are naming their devices, as it will not work if you
> only rely on the kernel.
>
> Yo
On Tue, Jan 15, 2013 at 10:42 PM, Peter Stuge wrote:
> Rich Freeman wrote:
>> Not that anybody is taking requests, but it would be really handy
>> if serial ports were deterministically labeled.
>
> Does /dev/serial/* solve the problem?
I don't see this directory at all on my system.
Rich
Rich Freeman wrote:
> Not that anybody is taking requests, but it would be really handy
> if serial ports were deterministically labeled.
Does /dev/serial/* solve the problem?
//Peter
On Tue, Jan 15, 2013 at 1:58 PM, Greg KH wrote:
> And it's not udev that could rename the interface (hint, it wouldn't),
> it's the kernel, it _never_ guarantees the same interface "name" every
> time you boot. You might just be getting lucky, but really, PCI busses
> can be enumerated in differe
On Tue, Jan 15, 2013 at 08:58:59AM -0500, Ian Stakenvicius wrote:
> On 15/01/13 04:16 AM, Michael Weber wrote:
> > Hi,
> >
> > "This can have serious security implications" [1]
> >
> > For whom?
>
> I think the idea there is that a user expects eth0 and eth1 to stay
> the same, writes iptables r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/01/13 03:42 AM, Michael Weber wrote:
>
> e) Some distro/driver constellations (archlinux?) tend to name
> their wireless lan eth*. [...] e) never happened to me.
It has for me, but not for a *LONG* time -- iirc it was prior to
2.6.16 and I th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/01/13 04:16 AM, Michael Weber wrote:
> Hi,
>
> "This can have serious security implications" [1]
>
> For whom?
I think the idea there is that a user expects eth0 and eth1 to stay
the same, writes iptables rules on a per-interface basis to co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
"This can have serious security implications" [1]
For whom?
The often cited end user not running any network service, not even sshd?
Without firewalls, routing or dhcp_d_?
Some avahi-discovery woodoo stuff unaware of network topology at all?
M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
I respect both sides of the discussion, because:
a) I once set up an old P3-700 with 5+1 eth cards in 6 different
networks as (bridging)router and truly benefited from the ability to
change a broken NIC - which happened quite often due scra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/01/13 11:21 PM, Daniel Campbell wrote:
>> [1]
>> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
>
>>
>
> So long as users retain the choice of keeping eth* or wlan*, no
> complaints from me. I (and others)
On Wed, Jan 09, 2013 at 11:33:42PM -0500, Rich Freeman wrote:
> On Wed, Jan 9, 2013 at 11:21 PM, Daniel Campbell wrote:
> > So long as users retain the choice of keeping eth* or wlan*, no
> > complaints from me. I (and others) came to Gentoo to get away from
> > systemd, and this smells of a syste
On 01/09/2013 10:33 PM, Rich Freeman wrote:
> On Wed, Jan 9, 2013 at 11:21 PM, Daniel Campbell wrote:
>> So long as users retain the choice of keeping eth* or wlan*, no
>> complaints from me. I (and others) came to Gentoo to get away from
>> systemd, and this smells of a systemd-ism. Will eudev be
On Wed, Jan 9, 2013 at 11:21 PM, Daniel Campbell wrote:
> So long as users retain the choice of keeping eth* or wlan*, no
> complaints from me. I (and others) came to Gentoo to get away from
> systemd, and this smells of a systemd-ism. Will eudev be pursuing this
> as well?
Keep in mind that this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2013 04:13 PM, William Hubbs wrote:
> All,
>
> as you probably know by now, udev-197 has hit the tree.
>
> This new version implements a new feature called predictable
> network interface names [1], which I have currently turned off for
> li
On Wed, 9 Jan 2013 18:13:21 -0600
William Hubbs wrote:
> There is a way for users to opt out if we default this to on, but I
> think the new naming scheme has advantages over the traditional eth*
> wlan* etc names.
I think it should be taken with a grain of salt. The page mentions how
it lets yo
On Wed, Jan 09, 2013 at 02:59:10PM -0800, Christopher Head wrote:
> On Wed, 9 Jan 2013 16:13:10 -0600
> William Hubbs wrote:
>
> > http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
>
> This seems like a good thing for some systems. Will there be a news
> item when
On Wed, 9 Jan 2013 16:13:10 -0600
William Hubbs wrote:
> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
This seems like a good thing for some systems. Will there be a news
item when 197 (or greater) goes stable informing people that the option
is available and
All,
as you probably know by now, udev-197 has hit the tree.
This new version implements a new feature called predictable network
interface names [1], which I have currently turned off for live systems,
because it
will require migration on the part of the user.
When you upgrade to this new vers
35 matches
Mail list logo
