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

On Wed, 2017-07-12 at 17:35 +0200, Marc Haber wrote: > I'd rather have breakage in this case than having to look for the > interface every fscking time I need to run tcpdump, or having to > adapt to an entirely new name schema like lanc0 and lanw0 to not > stomp in the kernel's name space when usin

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

On Wed, 2017-07-12 at 21:00 +0530, shirish शिरीष wrote: > On 12/07/2017, Fernando Toledo wrote: > > Our Use-case: > > > > We develop a derivated distro from Debian called Huayra GNU/Linux, > > this is for educational program of government in Argentina. This > > big program ship around 5 millons o

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

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. I guess I really asking for a use case. "Stateless /etc" isn't either. I've never seen the kernel vary

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

On Thu, 2017-07-13 at 11:21 +, Clinton Roy wrote: > Unfortunately, others have (well, not the kernel, but PCI): > > https://lists.freedesktop.org/archives/systemd-devel/2017-May/038924. > html If you plug new hardware devices in then of course things are going to change. The claim really is

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

On Thu, 2017-07-13 at 09:07 -0700, Russ Allbery wrote: > Er, I saw this all the time without udev persistent naming.  Every > time we rebooted one of our servers, the four onboard NICs (of which > we were only using one -- long story, but basically that's just what > the systems came with out of th

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

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

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

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

On Sat, 2017-07-15 at 07:46 +0200, Tollef Fog Heen wrote: > Doesn't something like: > > [Unit] > Description=My hook for foo.link > After=foo.link > BindsTo=foo.link > > [Service] > Type=oneshot > ExecStart=/usr/local/sbin/whatever > RemainAfterExit=yes > > [Install] > WantedBy=multi-user.target

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

On Thu, 2017-07-27 at 10:05 +, Sam Morris wrote: > You'd have to use BindsTo=sys-subsystem-net-devices-blah.device. But  > BindsTo= and device units are a bit fiddly, see systemd/systemd/issues/4413>. I had a systemd enthusiast sitting beside me who recommended that. I

Re: Debian Stretch new user report (vs Linux Mint)

On Mon, 2017-12-04 at 21:01 +, Ben Hutchings wrote: > I end up needing non-free firmware on most bare metal systems, but > nothing else from non-free.  I never remember how to include it at > installation time.  And I don't want us to gloss over the fact that > it is non-free and therefore not

Re: An abrupt End to Debian Live

On Mon, 2015-11-09 at 17:47 +0100, Daniel Baumann wrote: > An abrupt End to Debian Live As a person who recently used Debian Live to set up a PXE boot image after trying several different alternatives including debian-cd, I am sorry to hear this and sad to see debian-live go. It will be missed, b

Re: trying to use wireless not from gnome... what's the incantation?

On Mon, 2016-05-23 at 08:28 +0200, Adam Borowski wrote: > Using low-level tools can indeed be tricky, so while they're more > powerful than anything NM or wicd can do, they're an overkill and a > waste of learning time if what you want is regular use of a single > interface. I have a new laptop on

Re: trying to use wireless not from gnome... what's the incantation?

On Thu, 2016-05-26 at 10:24 +0200, Michael Biebl wrote: > It's hard to say though. For this we'd need proper debug logs to > further investigate this. You shamed me into doing something about it.  But now I test it, network-manager works.  It's been 3 months and a similar number of kernels, so who

Re: trying to use wireless not from gnome... what's the incantation?

On Thu, 2016-05-26 at 12:15 -0800, Britton Kerin wrote: > On Thu, May 26, 2016 at 4:35 AM, Andrew Shadura > wrote: > > There's no need in any of this, ifupdown already supports this mode > > without anything apart from wpa-conf. > > > > See /usr/share/doc/wpasupplicant/README.Debian.gz for more d

Re: Thinking about a "jessie and a half" release

On Tue, 2016-07-05 at 00:38 +0200, Ben Hutchings wrote: > As I understand it, xserver-xorg-video-modesetting should be used > instead of xserver-xorg-video-intel, for chips supported by the i915 > kernel driver.  So the latter should be changed to limit the device > IDs it claims, then both of them

Re: Thinking about a "jessie and a half" release

On Tue, 2016-07-05 at 08:25 +0100, Rebecca N. Palmer wrote: > Have you reported this bug (with the full warnings)?  If not, please > do so. I haven't.  If I got a response at all to "My monitor doesn't work" it looks to me it would be: compile latest source with instrumentation turned on and send

<    1   2