Just FYI:
I just tried to install ascii (PXE) and the installer fails when it
wants to remove systemd I suppose:
Jan 10 08:30:24 in-target: WARNING: The following essential packages will be
removed.
Jan 10 08:30:24 in-target: This should NOT be done unless you know exactly what
you are doing!
J
On Sun, 10 Jan 2016 09:36:26 +0100
richard lucassen wrote:
Jessie no prob
--
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Hi,
To display eye-pleasing Truetype fonts in Xorg, /etc/fonts/local.conf
needs to set few options:
- Anti-aliasing
- Hinting
- RGB type of LCD monitor
- LCD filter
The link (http://www.lagom.nl/lcd-test/subpixel.php) explains how to
identify RGB type of your LCD monitor.
Here is my /etc/fo
"Enrico Weigelt, metux IT consult" writes:
> On 05.02.2015 11:42, Gravis wrote:
>> please, let's not include terrorists or their ideologies in our
>> conversations.
>
> terrorist or freedoms fighter ?
"Fighting freedom" is surely on the agenda of these people
[SCNR]
___
Anto writes:
[...]
> It turned out that the eth0 interface was changed to ens3, due to the
> implementation of Predictable Network Interface Names
> (http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames).
> I
> can change everything which contain eth0 into ens3, but
Jude Nelson writes:
>> Isn't the initial identification of network adapters and assignment
> originally handled by the Kernel or is this another urban myth that I have
> mistakenly hung on to?
>
> Yes--network interfaces are given a monotonically-increasing sequence
> number as they are enumerated
Rainer Weikusat writes:
[ethX reordering]
> in the relative rare case that more than one network driver actually
> has to be loaded, if the order in which the drivers call their init
> routines changes. There's nothing which would stop "driver loading
> support software" from ensuring that this
Hi,
As I am reading this discussion a temptative thought is coming to my
mind which is: what can Devuan do to avoid this new device naming
scheme breaking breaking software that rely on the old naming
convention?
As I wrote in my earlier reply, I am ready to offer my help in this,
provided the co
El 2015-12-21 10:58, Simon Hobson escribió:
Linux O'Beardly wrote:
While many here would probably say it's not a good idea to run servers
on Devuan until a production release, I am already running it on a
number of servers.
That's good to know - I need to find time to do some testing myself
El 2016-01-05 14:50, Joel Roth escribió:
Rainer Weikusat wrote:
Clarke Sideroad writes:
> So I've been thinking more about this as to why?
>
> It is quite obvious that it is driven by Redhat to be the same as Oracle
> Solaris, they say as much.
That's "quite obviously" an after-the-fact justif
Le 10/01/2016 20:30, Ángel Ramírez Isea a écrit :
IMHO, at some point we will have to start ignoring whatever they do.
This looks extremely desirable. Unfortunately we are not yet at the
point where there are two parallel threads of Gnu/Linux (since they
persist to use that name) development.
Slackware is hard work when you have been used to the ease of debian for
so many years...
Eventually it all worked OK until one particular bit of music
composition software I like to use could only be found in Slackbuilds,
and it would not install even after I did some editing of the scripts.
I
Stephanie Daugherty writes:
> Having dealt with systems with half a dozen interfaces in the past there's
> a very small number of cases where it even matters, but when it does, it
> can be a huge inconvenience either way.
Namely, "it matters" because Dell boxes with more than one interface
usuall
Steve Litt writes:
[...]
> Second, once you really know the new ip command (and forget the old
> ifconfig stuff),
JFTR: I've adopted 'the new IP command' with a sigh of relief by the
time it was actually new. That was when Linux 2.2 was released in 1998.
___
On Sun, 10 Jan 2016 21:55:48 +
Dave Turner wrote:
> Slackware is hard work when you have been used to the ease of debian
> for so many years...
> Eventually it all worked OK until one particular bit of music
> composition software I like to use could only be found in
> Slackbuilds, and it wo
Hi,
I'm making progress in netman-gtk3:
http://s15.postimg.org/5zzjn2k0b/Screenshot_01112016_12_37_27_AM.png
Piano, piano :)
Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
OpenBSD's overall stance on virtualization makes it a poor choice for a
desktop OS unfortunately. I partially understand the reasoning, however,
given the limits of software support on the *BSDs in general, and OpenBSD
in particular, the lack of virtualization options effectively makes it
unusable
This looks extremely desirable. Unfortunately we are not yet at the
point where there are two parallel threads of Gnu/Linux (since they
persist to use that name) development. RedHat and Debian are still the
major driving force, due to their large number of developpers. And
Devuan is still derived
All the BSDs have the packages I want and need, except working WiFi for
laptops!
My main desktop is an old Intel iMac. FreeBSD and PC-BSD would not install.
I could not get sound to work on NetBSD and OpenBSD.
So the old iMac runs debian jessie systemd and all.
My old laptop is now running devua
Yes, I agree completely.
Getting all the anti-systemd distros working together would be a very
good thing.
DaveT
On 11/01/16 01:05, da...@olansa.co.uk wrote:
This looks extremely desirable. Unfortunately we are not yet at the
point where there are two parallel threads of Gnu/Linux (since they
20 matches
Mail list logo
