On 5 December 2016 at 08:50, Joel Roth wrote:
> Nate Bargmann wrote:
> > If there is no technical reason for it, is it spite?
>
> The natural tendency to grasp for a piece of technical
> candy, trying to play nicely with others who are all
> using it, to name two other
> possible reasons.
>
>
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mo den 5. Dez 2016 um 9:01 schrieb Aldemir Akpinar:
> Seems like it's been infected about 1.5 years ago.
>
> https://anonscm.debian.org/cgit/collab-maint/procps.git/commit/?id=e24f0f994ad3279eb387bea8cda907d4e6f61926
Might be. I just seen
Where should we be commending the storage of iptables rules in Devuan
Jessie?
I notice that iptables-apply looks for rules in
/etc/network/iptables.up.rules while iptables-persist looks for rules in
/etc/iptables/rules.v4 instead. The former utility is installed by
default as part of the iptables
On 12/04/2016 10:26 PM, Robert Storey wrote:
> I wrote:
>
>> Refracta saved the day! Thank goodness it exists, or else I would
>> not be able to install Devuan on any of my machines. Please note
>> that with Refracta, I did not need to set up networking at all
>> during the installation, but Wicd
On 12/03/2016 06:21 PM, goli...@dyne.org wrote:
> On 2016-12-03 16:32, fsmithred wrote:
>> ...and here is the entire link:
>>
>> https://sourceforge.net/projects/refracta/files/unofficial_devuan_live/
>>
>> Sorry about that!
>>
>> -fsr
>>
>> ___
> Actuall
As preparation for the coming Beta2 and RC I did a dry run on a virtual
machine from Debian Wheezy to Devuan Jessie (beta) with the instructions
from dev1fanboy. It worked flawlessy with one minor point: apt-get purge
systemd-shim libsystemd0 gave an error message from dpkg for systemd.
But aft
On Mon, 5 Dec 2016 09:05:11 +0800
Robert Storey wrote:
> It pains me to say this, but the installation program for Devuan
> Beta2 is seriously broken. And I say this not as some kind of troll,
> but rather as a Devuan enthusiast who has already been running Devuan
> as my main system for six mont
On Mon, Dec 05, 2016 at 06:50:15PM +0200, Lars Noodén wrote:
> Where should we be commending the storage of iptables rules in Devuan
> Jessie?
While this doesn't exactly answer your question, I simply have a
script in /usr/local/etc called firewall.sh which runs all the
iptables rules that I want
On 12/05/2016 10:50 AM, Lars Noodén wrote:
Because iptables-apply is there by default, I'm leaning a bit towards
recommending /etc/network/iptables.up.rules as the location over
/etc/iptables/rules.v4
Do you still need to consider some users may need ip6tables rules also?
Perhaps /etc/ipta
On 12/05/2016 09:59 PM, dev wrote:
>
>
> On 12/05/2016 10:50 AM, Lars Noodén wrote:
>> Because iptables-apply is there by default, I'm leaning a bit
>> towards recommending /etc/network/iptables.up.rules as the
>> location over /etc/iptables/rules.v4
>
>
> Do you still need to consider some us
On Mon, Dec 05, 2016 at 10:09:38PM +0200, Lars Noodén wrote:
[cut]
>
> What do you see as the advantage? I'm interested in hearing the
> rational for either /etc/iptables/ or /etc/network/ since iptables-apply
> and iptables-persistent are conflicting and unlikely to be resolved
> upstream in t
On 06/12/16 05:50, Lars Noodén wrote:
> Where should we be commending the storage of iptables rules in Devuan
> Jessie?
There should not be a default location. It should be left to each
firewall application to define. This is particularly important as
iptables has a competitor in nftables and li
On 12/03/2016 05:32 PM, fsmithred wrote:
> ...and here is the entire link:
>
> https://sourceforge.net/projects/refracta/files/unofficial_devuan_live/
>
> Sorry about that!
>
> -fsr
>
I had to replace the amd64 iso. If you downloaded the one dated
20161203_0200 (in the file name) throw it away
13 matches
Mail list logo
