Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Tollef Fog Heen
]] Russell Stuart > As for *.link files, syntactically they like all systemd stuff are a > huge improvement on what came before them. But the old ugly udev rules > have one thing over them - they provide hooks for scripts to cover > cases they haven't thought of. Scripts seem to be an anathema

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Anthony DeRobertis
On 07/14/2017 08:01 PM, Russell Stuart wrote: (b) Those who enter the debian device names manually into config files, and have machines that network device names even though no one armed with a screw driver has been near the thing. These people would very much care. I was asking w

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Anthony DeRobertis
On 07/11/2017 03:08 PM, Nikolaus Rath wrote: I wonder if anyone actually uses /dev/disk/by-path? It's useful for a quick "ls -l /dev/disk/by-path | grep 'sda$;" to figure out which port a disk is plugged into. I'm sure there are other ways, probably better ones... but that one is easy to rem

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Russell Stuart
On Fri, 2017-07-14 at 18:31 -0700, Russ Allbery wrote: > I didn't think anyone was claiming they would, so I'm not sure why > you felt like it was necessary to say this. It's the same reason you feel like it was necessary to say this, I guess: On Fri, 2017-07-14 at 09:11 -0700, Russ Allbery wrote

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Russ Allbery
Russell Stuart writes: > On Fri, 2017-07-14 at 09:11 -0700, Russ Allbery wrote: >> Right, I'm completely happy with the current behavior.  I have no >> objections to the change.  I just also don't particularly care; I've >> stopped using ifupdown and am using *.link units for network >> configura

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Russell Stuart
On Fri, 2017-07-14 at 09:11 -0700, Russ Allbery wrote: > Right, I'm completely happy with the current behavior.  I have no > objections to the change.  I just also don't particularly care; I've > stopped using ifupdown and am using *.link units for network > configuration, which makes all of this t

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Russell Stuart
On Fri, 2017-07-14 at 11:20 -0300, Henrique de Moraes Holschuh wrote: > MOST PCI/PCIe NICs indeed use "ethX", etc.  But the naming scheme > really is device driver-specific, and the "default" name used by a > driver is considered part of the kernel stable ABI, and cannot be > changed on the kernel

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Tom H
On Fri, Jul 14, 2017 at 10:20 AM, Henrique de Moraes Holschuh wrote: > On Fri, 14 Jul 2017, Tom H wrote: >> The classic naming scheme for network interfaces applied by the kernel >> is to simply assign names beginning with "eth0", "eth1", ... to all >> interfaces as they are probed by the driver

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Russ Allbery
Vincent Bernat writes: > ❦ 13 juillet 2017 13:55 -0700, Russ Allbery  : >> Yeah, we were using FAI, but I believe that's the basic mechanism we >> were using and then found a way to use it to generate the udev rule to >> do persistent naming. > This is a perfect use case for the new udev. It wo

Bug#868339: ITP: libtk-fontdialog-perl -- font dialog widget for perl/Tk

2017-07-14 Thread Dominique Dumont
Package: wnpp Owner: Dominique Dumont Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: libtk-fontdialog-perl Version : 0.18 Upstream Author : sla...@rezic.de * URL : https://metacpan.org/release/Tk-FontDialog

Bug#868330: ITP: libalgorithm-svm-perl -- bindings for the libsvm Support Vector Machine library

2017-07-14 Thread Carnë Draug
Package: wnpp Severity: wishlist Owner: =?utf-8?q?Carn=C3=AB_Draug?= * Package name: libalgorithm-svm-perl Version : 0.13 Upstream Author : Matthew Laird * URL : https://metacpan.org/release/Algorithm-SVM * License : Artistic or GPL-1+ Programming Lang: Perl

Re: IMPORTANT: Do live Debian images have a future?

2017-07-14 Thread Steve McIntyre
Russell Stuart wrote: >On Wed, 2017-07-12 at 21:00 +0530, shirish शिरीष wrote: >> >> In short, this alone use-case answers Steve's original question which >> was primarily are there any users who use or would use this tool or >> his time would be better spent somewhere else. I think just

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Henrique de Moraes Holschuh
On Fri, 14 Jul 2017, Tom H wrote: > > I've never seen the kernel vary the order it enumerates a PCI bus. It doesn't, the last time it changed was on 2.4->2.6. OTOH, *driver probe* ordering can and does change, especially when device probes are being done in parallel. It is best to not get bus en

Bug#868323: ITP: node-lazy-property -- Adds a lazily initialized property to the object.

2017-07-14 Thread Saravanan P
Package: wnpp Severity: wishlist Owner: saravanan30erd X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-lazy-property Version : 1.0.0 Upstream Author : Mikola Lysenko * URL : https://github.com/mikolalysenko/lazy-property * License : Expat Pro

Bug#868295: ITP: ros-image-pipeline -- Utilities to work from raw images to higher-level vision processing

2017-07-14 Thread Leopold Palomo-Avellaneda
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org We (Robotics section of Debian Science team) are packaging ROS (Robot OS: http://www.ros.org/) for Debian. ROS uses many packages already in Debian, but also has a set of core/toolchain/build-system packages which are not

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Vincent Bernat
❦ 13 juillet 2017 13:55 -0700, Russ Allbery  : >>> The workaround was a bunch of bullshit in our install process to try to >>> figure out which NIC got the DHCP response and then pin that one to >>> eth0 for subsequent boots. (Which is basically what udev persistent >>> naming did.) > >> At leas

Re: Naming of network devices - how to improve it in buster

2017-07-14 Thread Tom H
On Thu, Jul 13, 2017 at 6:14 AM, Russell Stuart wrote: > On Thu, 2017-07-13 at 05:20 -0400, Tom H wrote: >> >> Stateless "/etc". >> >> Systems with multiple NICs where the order in which they're >> recognized by the kernel can vary. > > I asked for a person. You raised more than one point. I was