Re: [DNG] ASCII - clearlooks-Phenix-Purpy style issues

Adwaita and Clearlooks seems to be ok in ascii. I'm running openbox, tint2, thunar, geany, and I think xfce4-terminal. ozi On Tue, Aug 22, 2017 at 12:38 PM, Tom Cassidy wrote: > I had filed bug #107 against xfce4-terminal in ascii for this issue but I > guess I can

Re: [DNG] ASCII - clearlooks-Phenix-Purpy style issues

I had filed bug #107 against xfce4-terminal in ascii for this issue but I guess I can close that now if it's caused by the theme. I have also solved my issue by switching to another theme. --Tomas > I never expected Clearlooks Phenix Purpy to work in ascii. Both Xfce and > (I'm pretty sure)

Re: [DNG] ASCII - clearlooks-Phenix-Purpy style issues

On 2017-08-21 21:02, Gary Olzeke wrote: *There was a (closed) bug #50 that may be relevant.* Hadn't been using ascii for a week or so - did the update & upgrade it loaded 49 packages -- will append at the end. with the Settings/Appearance/Style set to *clearlooks-phenix-purpy* (this reverted

[DNG] FWIW fixed :: network down after ASCII upgrades

Haven't been on my ascii setup for a week or so. so I did the 'update & 'upgrade routine installed these upgrades:: [see below] ' did a reboot and lost my network connection. ifconfig isn't available anymore (am I getting old?!) ip was too confusing to me ' ended up doing this: sudo bash

[DNG] ASCII - clearlooks-Phenix-Purpy style issues

*There was a (closed) bug #50 that may be relevant.* Hadn't been using ascii for a week or so - did the update & upgrade it loaded 49 packages -- will append at the end. with the Settings/Appearance/Style set to *clearlooks-phenix-purpy* (this reverted back to this after the upgrade/reboot) '

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

On Mon, Aug 21, 2017 at 05:01:13PM -0700, Rick Moen wrote: > Quoting Adam Borowski (kilob...@angband.pl): > > > Manually creating the configuration -- or even manually triggering its > > creation -- is a pretty bad idea. It just guarantees you won't have > > working X when you make any change to

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

On Sun, 20 Aug 2017 at 22:24:58 -0400 Steve Litt wrote: > As a wee lad, my mentors told me never to put two of the same model > NICs in a computer, because which one became eth0 and which became eth1 > would be indeterminate from boot to boot. What about the

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

On Mon, 21 Aug 2017 at 12:56:24 +0200 Didier Kryn wrote: > In any case the admin must either hack /etc/network/interfaces or > the udev rules. But I think this little inconveniency is better than the > meaningless device names promoted by Systemd people. And the other

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

On Mon, 21 Aug 2017 at 10:32:43 +0200 Narcis Garcia wrote: [...] > This logic does not guarantee 100% predictable naming (think about > removable NICs), but gives enough confort to a sysadmin deals any with > situation. If it's not 100% predictable and configurable by

Re: [DNG] auto.mirror.devuan.org or us.mirror.devuan.org

On Mon, Aug 21, 2017 at 09:17:58AM +0200, Evilham wrote: > IIRC, when the package mirror network is setup (plans are for it to > start soon), auto.mirror would send you to the closest mirror, so if you > move around, that'd be best for you; if you'd rather use a specific > country mirror, you

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

On Mon, 21 Aug 2017 at 09:22:22 +0100 Simon Hobson wrote: [...] > I suppose that one REALLY good way to fix the problem (at least in the > server & desktop areas) is actually to undo a lot of "progress" and make > all driver and service initiation strictly linear. Ie, do

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

Quoting Adam Borowski (kilob...@angband.pl): > Manually creating the configuration -- or even manually triggering its > creation -- is a pretty bad idea. It just guarantees you won't have > working X when you make any change to your hardware -- and sometimes > software as well. Gosh, what you

[DNG] new behaviour of /dev

Hi! Do you remember when for decades we had to populate /dev using mknod (using makedev or something) -- both on Linux and on Unices that predated it? Then when udev came to make device creation dynamic. I just installed a new server, not using d-i but manual debootstrap. Not even regular

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

On Mon, Aug 21, 2017 at 02:30:00PM -0700, Rick Moen wrote: > My guess is that the udev developers thought 'It'd be excellent to > automatically supply to the starting Xorg binary the output of "Xorg > -configure" when /etc/X11/Xorg.conf doesn't exist, thereby making Xorg > automagically able to

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

Quoting Didier Kryn (k...@in2p3.fr): > Sorry, Rick, but I don't understand how it is possible that, on > one hand, it needs libudev to configure itself, and, on the other > hand, it is able to generate its config file without it. Can you > explain this paradox? Not really, no. My guess is that

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

Le 21/08/2017 à 16:48, Rick Moen a écrit : Quoting Didier Kryn (k...@in2p3.fr): [mdev:] Sure it would be helpful :-) AFAIK X11 is able to configure itself automatically without a config file when libudev provides it with an interface to query device properties, and without this library it is

Re: [DNG] openbox-themes in ASCII?

On 08/21/2017 08:59 AM, Michael Siegel wrote: > Am 18.08.2017 um 16:04 schrieb fsmithred: > >> Some themes work, some don't, and they seem to work better if I use >> lxappearance-obconf instead of just obconf. > > What exactly do you mean by "some themes don't work"? I use obconf for > setting

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

On Sun, Aug 20, 2017 at 09:30:00PM -0700, Rick Moen wrote: > Let me try to draw a distinction with some nuance, here: To the best of > my knowledge -- and my knowledge might be incomplete or unaware of some > new developments -- 'spontaneous' network device renaming, just like > spontaneous mass

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

On 21-08-17 06:30, Rick Moen wrote: Quoting Steve Litt (sl...@troubleshooters.com): As a wee lad, my mentors told me never to put two of the same model NICs in a computer, because which one became eth0 and which became eth1 would be indeterminate from boot to boot. It's funny you'll say that,

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

On Mon, 21 Aug 2017 07:26:04 -0700 Rick Moen wrote: > > On Sun, 20 Aug 2017 21:30:00 -0700 Rick Moen > > wrote: > > > > > However_, even given that, in my experience any reshuffle USB would > > > add to the _existing_ devices' node assignments would

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

Quoting Didier Kryn (k...@in2p3.fr): [mdev:] > Sure it would be helpful :-) AFAIK X11 is able to configure > itself automatically without a config file when libudev provides it > with an interface to query device properties, and without this > library it is necessary to provide a config file.

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

Quoting Renaud OLGIATI (ren...@olgiati-in-paraguay.org): > On Sun, 20 Aug 2017 21:30:00 -0700 Rick Moen > wrote: > > > However_, even given that, in my experience any reshuffle USB would > > add to the _existing_ devices' node assignments would occur only at > > reboot time

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

El 21/08/17 a les 15:52, Didier Kryn ha escrit: > Note that a similar problem with disks has been solved elegantly by > referencing disks by their uuid or label in /etc/fstab. Maybe > /etc/network/interface could specify the MAC address as a hook. This > would only suppose that the hotplugger

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

Le 21/08/2017 à 16:04, k...@aspodata.se a écrit : Didier Kryn: Le 21/08/2017 à 14:41, Arnt Karlsen a écrit : ..we need to sell either vdev or eudev or some such non-systemd udev upstream to Linus and the kernel guys and get them happy about kicking out systemd-udev from the kernel code base.

Re: [DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

Didier Kryn: > Le 21/08/2017 à 14:41, Arnt Karlsen a écrit : > > ..we need to sell either vdev or eudev or some such non-systemd > > udev upstream to Linus and the kernel guys and get them happy > > about kicking out systemd-udev from the kernel code base. > > [OT]I would prefer Mdev if the

[DNG] An alternative to renaming [was Re: Proposed change in behaviour for ascii: eudev net.ifnames]

Le 21/08/2017 à 14:41, Arnt Karlsen a écrit : ..we need to sell either vdev or eudev or some such non-systemd udev upstream to Linus and the kernel guys and get them happy about kicking out systemd-udev from the kernel code base. [OT]I would prefer Mdev if the issue with X11 could be

Re: [DNG] openbox-themes in ASCII?

Am 18.08.2017 um 16:04 schrieb fsmithred: > I downloaded the wheezy source and built a package on ascii pretty > easily last night. Didn't change anything. Nice. But the package meta data would have to be revised for an official Devuan package, I guess. > Some themes work, some don't, and they

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

Le 21/08/2017 à 12:56, Didier Kryn a écrit : Le 20/08/2017 à 18:57, Renaud (Ron) OLGIATI a écrit : On Sun, 20 Aug 2017 16:38:18 +0100 Rowland Penny wrote: As far as I am aware, each network device should have a different MAC, couldn't this be used to identify which device

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

Le 20/08/2017 à 18:57, Renaud (Ron) OLGIATI a écrit : On Sun, 20 Aug 2017 16:38:18 +0100 Rowland Penny wrote: As far as I am aware, each network device should have a different MAC, couldn't this be used to identify which device is which ? Could, but whenever you have to

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

On Sun, 20 Aug 2017 21:30:00 -0700 Rick Moen wrote: > However_, even given that, in my experience any reshuffle > USB would add to the _existing_ devices' node assignments would occur > only at reboot time _if_ you left the USB device plugged in. Personal experience: I run

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

Quoting marc (marc...@welz.org.za): > Like Rick I haven't encountered a spontaneous device name > re-order in the wild. Just to be skeptical for a moment of my own wording, I probably _slightly_ overstated (at least by implication) what I've observed over the decades, here: I understood

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

Edward Bartolo wrote: > Therefore, if I were in a position to take decisions I would > not expect a computer to know what I need. However, a computer should > have no difficulty processing data. A decent OS should save a map of > how hardware is connected, somewhat like a

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

El 20/08/17 a les 21:53, fsmithred ha escrit: > On 08/20/2017 10:27 AM, Adam Borowski wrote: >> >> * systemd-udev's promise of providing _stable_ names didn't deliver. They >> still change on major kernel upgrades, and sometimes on every boot. >> And their chosen naming is utterly insane

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

Steve Litt wrote: > As a wee lad, my mentors told me never to put two of the same model > NICs in a computer, because which one became eth0 and which became eth1 > would be indeterminate from boot to boot. That's horrible, and that *is* > solved by the systemd naming

[DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

If Devuan decides to use a different device name naming scheme apart from the one discussed several months ago (a year ago?), it will result in breaking simple-netaid-backend and simple-netaid-gui. I used the naming scheme en* for ethN and wl* for wlanN. Regarding this discussion what I have to

Re: [DNG] auto.mirror.devuan.org or us.mirror.devuan.org

Am 20/08/2017 um 12:50 schrieb tirveni yadav: > Currently, Both the hostnames us.mirror.devuan.org and > auto.mirror.devuan.org are pointing to packages.devuan.org. > > And packages.devuan.org is pointing to an IP in pool of ovh, France. > > So, there's no difference. Pretty sure that's

Re: [DNG] Proposed change in behaviour for ascii: eudev net.ifnames logic reversing proposal

So another vote for keeping the eth0/wlan0 scheme and not renaming devices in userspace. Like Rick I haven't encountered a spontaneous device name re-order in the wild. However, some time ago the authors of the reverse engineered nvidia ethernet driver (was it forcedeth?) noticed they had