On Tue, 11 Jul 2017 15:20:41 +0200
Michael Biebl wrote:
> Am 11.07.2017 um 12:14 schrieb Guus Sliepen:
> > Ok, it should be clear now that the new way of naming interfaces is not
> > ideal, but the older ways weren't either. Let's have a look at what we
> > want:
> >
> > - A simple name for syst
Then what next? I want to use gui version
(I had sent an email about the same problem, before this one )
On Wed, Jul 12, 2017 at 2:36 AM, Jose M Calhariz wrote:
> Anyone have recently done a Crossgrading in stretch?
I have not, but I think it would be interesting to have automated
testing of individual packages via piuparts.d.o and various default
configurations via jenkins.d.n.
--
bye,
pabs
http
On Jul 11 2017, Simon McVittie wrote:
> On Tue, 11 Jul 2017 at 13:45:25 +0200, Bjørn Mork wrote:
>> I got to ask: Why? We do not have stable names for e.g. disks. Why do
>> we need it for network devices?
>
> We do have stable names for disks: look in /dev/disk/by-* and you'll see
> a bewilderin
Processing commands for cont...@bugs.debian.org:
> tags 868061 + moreinfo
Bug #868061 [general] general: Sleep not reliable
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
868061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868061
Debi
tags 868061 + moreinfo
thanks
Hi Oliver,
> sleep mode is not reliable. My Notebook wakes up in my bag and heats up
> to insane temperature. This could destroy my notebook, the life time is
> definitely shortend.
I'm sorry to hear the potential damage to your laptop. I think you need to
provide a
Anyone have recently done a Crossgrading in stretch? Do you want to
share your experience?
I have followed the instructions https://wiki.debian.org/CrossGrading,
more or less, and done the crossgrade from 32bits to 64bits. I
managed to successfully crossgrade X11 and Mate desktop to 64bits.
Som
Package: general
Severity: important
Dear Maintainer,
sleep mode is not reliable. My Notebook wakes up in my bag and heats up
to insane temperature. This could destroy my notebook, the life time is
definitely shortend.
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy:
On Tue, Jul 11, 2017 at 01:45:25PM +0200, Bjørn Mork wrote:
> The remaining problem is to make ifupdown do device matching on other
> (and hopefully more stable) attributes than the device name.
This is not impossible to do. I actually have some code to make ifupdown
use interface matching, I'm a
On Tue, 11 Jul 2017, Bjørn Mork wrote:
> Previously I could ask a user to do e.g. 'ifconfig wwan0'. Now?
sudo ip link; sudo ip addr;
and probably also:
sudo iw dev|awk '/^phy/'|xargs -IIFACE sudo iw IFACE info
--
Don Armstrong https://www.donarmstrong.com
What I can't sta
On Tue, Jul 11, 2017 at 10:12 AM, Samuel Thibault
wrote:
> Matt Zagrabelny, on mar. 11 juil. 2017 09:53:58 -0500, wrote:
> > Relatedly, network device name lengths are limited to the length of
> some
> > arbitrarily-sized struct field in the kernel ABI,
> >
> > Feature request to bump the
Matt Zagrabelny, on mar. 11 juil. 2017 09:53:58 -0500, wrote:
> Relatedly, network device name lengths are limited to the length of some
> arbitrarily-sized struct field in the kernel ABI,
>
> Feature request to bump the size of of interface names struct? Any reason to
> not do so?
One re
Simon McVittie, on mar. 11 juil. 2017 15:18:26 +0100, wrote:
> Network devices are (as far as I know) the only class of device managed by
> udev that is not backed by a device node, which means udev cannot provide
> multiple equivalent names for the same device,
Couldn't that be what should be fix
On Jul 11 2017, Michael Biebl wrote:
> Am 11.07.2017 um 12:14 schrieb Guus Sliepen:
>> Ok, it should be clear now that the new way of naming interfaces is not
>> ideal, but the older ways weren't either. Let's have a look at what we
>> want:
>>
>> - A simple name for systems with a single Etherne
On Tue, Jul 11, 2017 at 9:18 AM, Simon McVittie wrote:
> On Tue, 11 Jul 2017 at 13:45:25 +0200, Bjørn Mork wrote:
> > I got to ask: Why? We do not have stable names for e.g. disks. Why do
> > we need it for network devices?
>
> We do have stable names for disks: look in /dev/disk/by-* and you'l
* Vincent Bernat [170710 16:25]:
> ❦ 10 juillet 2017 15:53 -0400, Marvin Renich :
>
> >> > With the new scheme, if I want to rename the interface to something more
> >> > meaningful, ..., and type all of
> >> > that information by hand, hoping I type everything correctly.
> >>
> >> Have a look
Package: wnpp
Severity: wishlist
Owner: Diego M. Rodriguez
* Package name: golang-github-shibukawa-configdir
Version : 0.0~git20170330.0.e180dbd-1
Upstream Author : Yoshiki Shibukawa
* URL : https://github.com/shibukawa/configdir
* License : Expat
Programming
On Tue, 11 Jul 2017 at 13:45:25 +0200, Bjørn Mork wrote:
> I got to ask: Why? We do not have stable names for e.g. disks. Why do
> we need it for network devices?
We do have stable names for disks: look in /dev/disk/by-* and you'll see
a bewildering variety of ways to refer to the same disk or p
Package: wnpp
Severity: wishlist
Owner: Jonathan Carter
* Package name: vim-airline-themes
Version : git-master
Upstream Author : Bailey Ling
* URL : https://github.com/vim-airline/vim-airline-themes
* License : expat
Programming Lang: vim-config
Descripti
Package: wnpp
Severity: wishlist
Owner: Jonathan Carter
* Package name: vim-airline
Version : 0.8-1
Upstream Author : Bailey Ling
* URL : https://github.com/vim-airline/vim-airline
* License : expat
Programming Lang: vimconfig
Description : Lean & mean
Am 11.07.2017 um 12:14 schrieb Guus Sliepen:
> Ok, it should be clear now that the new way of naming interfaces is not
> ideal, but the older ways weren't either. Let's have a look at what we
> want:
>
> - A simple name for systems with a single Ethernet and/or Wireless
> interface (the simple d
On Tue, 11 Jul 2017 12:14:59 +0200
Guus Sliepen wrote:
>
> So, what can we do to improve the situation and get the best of both
> worlds?
>
systemd.link(5) describes a NamePolicy option for interface names.
I would suggest to introduce a new policy "keep" to stick with
the native interface n
Guus Sliepen writes:
> Ok, it should be clear now that the new way of naming interfaces is not
> ideal, but the older ways weren't either. Let's have a look at what we
> want:
>
> - A simple name for systems with a single Ethernet and/or Wireless
> interface (the simple desktop/laptop scenario)
Ok, it should be clear now that the new way of naming interfaces is not
ideal, but the older ways weren't either. Let's have a look at what we
want:
- A simple name for systems with a single Ethernet and/or Wireless
interface (the simple desktop/laptop scenario).
- A consistent naming scheme for
Samuel Thibault writes:
> Vincent Bernat, on lun. 10 juil. 2017 20:55:29 +0200, wrote:
>
>> Other major distributions are using this new scheme (notably Ubuntu
>> which has no reason to have users smarter than ours)
>
> The reasoning is the converse: non-techy users will just not be exposed
> to i
Package: wnpp
Severity: wishlist
Owner: Alastair McKinstry
* Package name: dh-fortran-mod
Version : 1.0
Upstream Author : Sebastien Villemont
* URL :
http://anonscm.debian.org/gitweb/?p=debian-science/packages/dh-fortran-mod.git
* License : GPL3
Programming
26 matches
Mail list logo
