Re: [DNG] Wanting to set up an email system

2021-11-28 Thread d...@d404.nl

On 27-11-2021 16:17, o1bigtenor via Dng wrote:

Greetings

Started way back when when I got to the web full-time using webmail.
Haven't ever setup an email system and AIUI it is a system - - - there 
are a lot of parts that have to work together to have everything 
working well.


A mentor, now deceased, recommended using Claws but even that's not 
all that's needed for an email system. So - - - I'm looking for 
recommendations on what and how to setup an email system. The why 
you're using what you are is vitally important for me (as are my 
security and privacy).


Please

TIA

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


If you want a fast way to setup a mailserver including spam and 
viruscontrol, webmail and webadmin and much much more, I would take a 
look at https://hub.docker.com/r/mailserver2/mailserver


This is a all-round mailserver in a docker container(s) which is 
relative easy to setup. Far more easy then doing it by hand and I have 
done both so I can tell from experience.


Full source code is available at github.

Grtz

Nick


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Viewing file content (was Re: system administration of non-systemd distros and releases)

2021-11-28 Thread Hendrik Boom
On Fri, Nov 26, 2021 at 09:23:05PM -0500, Steve Litt wrote:
> Olaf Meeuwissen said on Fri, 26 Nov 2021 18:40:37 +0900
> 
> >Hi,
> >
> >Steve Litt writes:
> >
> >> What could possibly be easier than vim /var/log/messages, or
> >> vi /var/log/messages, or emacs /var/log/messages, or
> >> nano /var/log/messages? And notice with the old way, you have a
> >> choice, rather than having to look at log output with the vendor's
> >> proprietary tool.  
> >
> >Maybe I'm peculiar but I always find it absolutely, totally
> >jaw-dropping when people use text *editors* to *look* at file content.
> > Makes my toes curl up and blood curdle.
> 
> You're right. Use less or some other *viewer*.

For things like log output, which must be kept unchanged, a read-only 
viewer would suffice.  Or a read-only editor.  Editors sometimes have 
texual search mechanisms that are better than viewers.  And if you use 
one editor a *lot*, its commands are muscle memory.

For things tat you primarily want to read, but rarely fix a typo or 
such, you can open a text editor in read-only mode, protecting you from 
inadvertent edits.

-- hendrik

> 
> SteveT
> 
> Steve Litt 
> Spring 2021 featured book: Troubleshooting Techniques of the Successful
> Technologist http://www.troubleshooters.com/techniques
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] What not to back up

2021-11-28 Thread Steve Litt
Bob Proulx via Dng said on Sun, 28 Nov 2021 10:57:36 -0700

>Mike Tubby wrote:
>> ... but if you run a nameserver you may well need:
>> 
>> /var/cache/bind
>> 
>> as that's where your zonefiles are ;-)  
>
>Sorry.  No.  I am curious what led you to that conclusion?
>
>By default in the Debian packaged configuration only the cached zone
>files downloaded on secondaries are located there.  (The upstream BIND
>does not specify a default location.  This is a distro package default
>location.)  Since it is a package default the local admin may also
>change it to any other location they wish.  But /var/cache is as good
>of a location as any for cached files.
>
>And therefore by all means delete that directory any time you feel
>like doing so and recreate it empty. 

Now that I have this new information, I retract my particular insult
for BIND. I still don't like it for various reasons, but fair's fair;
at least they didn't put config in a cache directory.

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] lpr print pdf file landscape orientation

2021-11-28 Thread Haines Brown
I have bsd-lpr. I can print a text file with landscape orientation 
with  $ lpr -o landscape file.txt

My problem is that I cannot print pdf files in landscape 
orientation. $ lpr -o landscape file.pdf does nothing.

I don't want to make landscape the default CUPS orientation.

Atril rotates the display of the PDF, but not the content of the 
file in relation to the page when printed. 

The qpdfview utility also can rotate the display of text but 
when printed the effect is simply move  text up on the page.

I don't see how poppler-utils can be of help.

How does one print a PDF with landscape orientattion? 


-- 
Haines Brown  
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Wanting to set up an email system

2021-11-28 Thread marc
> Greetings
> 
> Started way back when when I got to the web full-time using webmail.
> Haven't ever setup an email system and AIUI it is a system - - - there are
> a lot of parts that have to work together to have everything working well.
> 
> A mentor, now deceased, recommended using Claws but even that's not all
> that's needed for an email system. So - - - I'm looking for recommendations
> on what and how to setup an email system. The why you're using what you are
> is vitally important for me (as are my security and privacy).

Hi

I am assuming you are asking how to set up your own complete
mail infrastructure.

If so: Congratulations - I think you are doing the *right* thing.
Not only for yourself, but for the internet as a whole. The
concentration of email servers under the control of a
few big corporations is a singularly bad thing.

The core of internet email is the SMTP server or MTA.
There are a number of implementations including postfix,
sendmail, exim and qmail - amongst others. I think the
most important step in hosting your own email infrastructure
is to start understanding one of them - installing one of
them on a spare computer (or container, or hosted system) would
be a good start. If you don't know which MTA to pick, I'd
say try postfix or exim (whatever your distribution defaults
to). And if you want to get going quickly, enable local delivery with 
a mail client you can run via ssh such as alpine, mutt or one
of several emacs extensions (the latter only if you use emacs). 

There are other parts to hosting your own email (DNS,
spam mitigation, getting mail to your remote email client, dealing
with difficult remote servers). Each of these is its own topic.
These topics can be large, but they can be understood - do
not believe the naysayers who claim it is all too complex.
They might value convenience over liberty, but not everybody
has to be that shortsighted.

regards

marc
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] What not to back up

2021-11-28 Thread Bob Proulx via Dng
Mike Tubby wrote:
> ... but if you run a nameserver you may well need:
> 
> /var/cache/bind
> 
> as that's where your zonefiles are ;-)

Sorry.  No.  I am curious what led you to that conclusion?

By default in the Debian packaged configuration only the cached zone
files downloaded on secondaries are located there.  (The upstream BIND
does not specify a default location.  This is a distro package default
location.)  Since it is a package default the local admin may also
change it to any other location they wish.  But /var/cache is as good
of a location as any for cached files.

And therefore by all means delete that directory any time you feel
like doing so and recreate it empty.  It's not important and does not
require being backed up.  It only needs to exist so the named has a
location to store and cache files (that have a TTL too) downloaded
from the primary.

If that directory is empty then upon start the BIND named will request
a fresh download of all of the zones it is configured for as a
secondary nameserver and will cache them in that directory again.  If
the named is not configured as a secondary then that directory will be
empty of zone files.

For DNS primaries one specifies the source zone file using the
named.conf "file" directive.  Put that file anywhere you wish to put
it.  But putting that in /var/cache/bind would be a very poor choice
in my opinion.

Example of actually doing this.

file "/etc/bind/db.proulx.com";

Since this is an option that must be configured when setting up a
primary zone then you can put those source zone files anywhere you
decide is the place to keep the source of them.  I highly recommend
etckeeper for all of /etc and therefore I prefer to keep source there
where etckeeper can track them.

Bob


signature.asc
Description: PGP signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] networking thinking

2021-11-28 Thread d...@d404.nl

On 28-11-2021 15:36, wirelessduck--- via Dng wrote:




On 29 Nov 2021, at 01:07, tito via Dng  wrote:

On Sun, 28 Nov 2021 07:20:14 -0600
o1bigtenor via Dng  wrote:


Greetings

In anticipation of a fiber optical connection (moving from a wireless) I
have been planning out and purchasing some bits of hardware. Am finding
that networking is, at least sure seems to be, another black hole 
for time

and effort.

TL;DR (skip to last paragraphs for the question(s))

At present this is a soho office kind of installation but that will 
slowly

be morphing into something that is at least somewhat larger. There are a
number of input sensor locations being worked on some of which would be
generating, initially at least, up to 15 data streams sampled possibly
every second (some maybe more often - - - decisions aren't all done 
as yet)
so there will be a fair amount of data running around on my network 
which

I'm trying to keep largely a wired affair.

At this point I'm working on the three entry bits of hardware (and their
software) - - - the router, hardware firewall, and the managed 
switch. The

initial hockup on the fiber system is going to be at 250 Mbps sysmetric.

For the router I'm planning on using OpenWRT running on a Nanopi r4s 
which
according to the folks over on openwrt capable of even very close to 
full
Gbps speeds (IIRC tested to some 918 Mbps) which would give some 
headroom

for future increases although I don't see a need for the foreseeable
future.

For the switch I have found myself a XyZel 1900-48 that I'm working on
getting OpenWRT on. This ability to run a managed switch on OpenWRT is
somewhat new but its open source and I'm not tied (I don't think) to
OpenWRT - - - - except I don't know any other real alternative - - - so
that's not a difficult solution either. I don't 'need' 48 ports but 
I have
16 at present on a hub and its almost full and that's for stuff only 
here

in the orifice (sic!). I also want the capabilities of forcing streaming
services and wireless communications to not collect any more data 
from any

other part of the network (using VLANs) as is possible.

Then lastly to the hardware firewall.
I've been looking at pfsense and opnsense. Both are ipv6 possible 
although
both are mostly focused on ipv4 at the present. IPfire seems to have 
gotten

itself into a holding pattern and is not continuing work toward ipv6
functionality. Any one of these options are producing headaches when I'm
trying to figure out how to configure them - - - nothing installed at
present, just researching so far.

So - - - - questions - - - -
1. is my splitting the network system into the three parts a good 
idea or
should I truncate parts 1 and 2 into the router? If you would please 
give

reasons - - - please?


Hi,

If you want to have reliability splitting is good, if the router breaks
you still have a working firewall and switch and so on.
If you want also some redundancy you should think of buying
two of everything:

2 routers
2 firewalls
2 switches (2 x24 rather than 1x48 ports)

I personally prefer x86 hardware for this kind of things
when I see that little boxes like the Nanopi R4S they make me
think about toys. In my case sadly I'm tied to adsl over pots
so for the modem I still need to use this little plastic blackboxes.
In your case I would swap the nanopi for a nice mini-itx board
with intel nics, a sfx/flex psu (or pico psu), 4-8 gb of ram and a well
ventilated case (with low noise Noctua fans).


2. are there any good sources for information on and about networking?
debian has moved to nftables from iptables  - - - is devuan doing
similar?


I think so.


Where does one find information to enable a firewall that works yet
isn't stupid?


I use arno-iptables-firewall It is easy to create a basic setup for 
your network,
reliable, comes with good defaults and can easily be tweaked (for 
port-forwarding,
vpns, geoip filtering and so on, don't know about vlans as don't use 
them yet).


(I've wondered about having some kind of easy 'switch' that when 
users left
their systems that the system wouldn't be calling home in the 
overnight at

least a la ms googly. Dunno if that's 'simple' or not - - - so much to
learn and so little time to do it all in!)

TIA


Ciao,
Tito


I’ve just finished setting up a new router using PCEngines APU2 
(apu4d4 model) with OpenWRT. Uses x64 AMD Embedded G series GX-412TC 
and has 4x Intel i211AT Ethernet ports. It also runs a Coreboot bios 
and I can see regular bios updates approximately monthly. The coreboot 
bios and AMD CPU were the main reasons I picked this over a Qotom box. 
It’s also fanless which is good for a quiet environment.


The only downside is having only serial console output so you need a 
serial cable or serial-usb cable for the initial setup or bios 
configuration changes. Thankfully subsequent bios updates can be done 
with OpenWRT via flashrom.


https://pcengines.ch/apu2.htm 

Re: [DNG] networking thinking

2021-11-28 Thread wirelessduck--- via Dng


> On 29 Nov 2021, at 01:07, tito via Dng  wrote:
> 
> On Sun, 28 Nov 2021 07:20:14 -0600
> o1bigtenor via Dng  wrote:
> 
>> Greetings
>> 
>> In anticipation of a fiber optical connection (moving from a wireless) I
>> have been planning out and purchasing some bits of hardware. Am finding
>> that networking is, at least sure seems to be, another black hole for time
>> and effort.
>> 
>> TL;DR (skip to last paragraphs for the question(s))
>> 
>> At present this is a soho office kind of installation but that will slowly
>> be morphing into something that is at least somewhat larger. There are a
>> number of input sensor locations being worked on some of which would be
>> generating, initially at least, up to 15 data streams sampled possibly
>> every second (some maybe more often - - - decisions aren't all done as yet)
>> so there will be a fair amount of data running around on my network which
>> I'm trying to keep largely a wired affair.
>> 
>> At this point I'm working on the three entry bits of hardware (and their
>> software) - - - the router, hardware firewall, and the managed switch. The
>> initial hockup on the fiber system is going to be at 250 Mbps sysmetric.
>> 
>> For the router I'm planning on using OpenWRT running on a Nanopi r4s which
>> according to the folks over on openwrt capable of even very close to full
>> Gbps speeds (IIRC tested to some 918 Mbps) which would give some headroom
>> for future increases although I don't see a need for the foreseeable
>> future.
>> 
>> For the switch I have found myself a XyZel 1900-48 that I'm working on
>> getting OpenWRT on. This ability to run a managed switch on OpenWRT is
>> somewhat new but its open source and I'm not tied (I don't think) to
>> OpenWRT - - - - except I don't know any other real alternative - - - so
>> that's not a difficult solution either. I don't 'need' 48 ports but I have
>> 16 at present on a hub and its almost full and that's for stuff only here
>> in the orifice (sic!). I also want the capabilities of forcing streaming
>> services and wireless communications to not collect any more data from any
>> other part of the network (using VLANs) as is possible.
>> 
>> Then lastly to the hardware firewall.
>> I've been looking at pfsense and opnsense. Both are ipv6 possible although
>> both are mostly focused on ipv4 at the present. IPfire seems to have gotten
>> itself into a holding pattern and is not continuing work toward ipv6
>> functionality. Any one of these options are producing headaches when I'm
>> trying to figure out how to configure them - - - nothing installed at
>> present, just researching so far.
>> 
>> So - - - - questions - - - -
>> 1. is my splitting the network system into the three parts a good idea or
>> should I truncate parts 1 and 2 into the router? If you would please give
>> reasons - - - please?
> 
> Hi,
> 
> If you want to have reliability splitting is good, if the router breaks
> you still have a working firewall and switch and so on.
> If you want also some redundancy you should think of buying 
> two of everything:
> 
> 2 routers 
> 2 firewalls
> 2 switches (2 x24 rather than 1x48 ports)
> 
> I personally prefer x86 hardware for this kind of things
> when I see that little boxes like the Nanopi R4S they make me
> think about toys. In my case sadly I'm tied to adsl over pots
> so for the modem I still need to use this little plastic blackboxes.
> In your case I would swap the nanopi for a nice mini-itx board
> with intel nics, a sfx/flex psu (or pico psu), 4-8 gb of ram and a well
> ventilated case (with low noise Noctua fans).
> 
>> 2. are there any good sources for information on and about networking?
>> debian has moved to nftables from iptables  - - - is devuan doing
>> similar?
> 
> I think so.
> 
>> Where does one find information to enable a firewall that works yet
>> isn't stupid?
> 
> I use arno-iptables-firewall It is easy to create a basic setup for your 
> network,
> reliable, comes with good defaults and can easily be tweaked (for 
> port-forwarding, 
> vpns, geoip filtering and so on, don't know about vlans as don't use them 
> yet).
> 
>> (I've wondered about having some kind of easy 'switch' that when users left
>> their systems that the system wouldn't be calling home in the overnight at
>> least a la ms googly. Dunno if that's 'simple' or not - - - so much to
>> learn and so little time to do it all in!)
>> 
>> TIA
> 
> Ciao,
> Tito

I’ve just finished setting up a new router using PCEngines APU2 (apu4d4 model) 
with OpenWRT. Uses x64 AMD Embedded G series GX-412TC and has 4x Intel i211AT 
Ethernet ports. It also runs a Coreboot bios and I can see regular bios updates 
approximately monthly. The coreboot bios and AMD CPU were the main reasons I 
picked this over a Qotom box. It’s also fanless which is good for a quiet 
environment.

The only downside is having only serial console output so you need a serial 
cable or serial-usb cable for the initial setup or bios 

Re: [DNG] networking thinking

2021-11-28 Thread tito via Dng
On Sun, 28 Nov 2021 07:20:14 -0600
o1bigtenor via Dng  wrote:

> Greetings
> 
> In anticipation of a fiber optical connection (moving from a wireless) I
> have been planning out and purchasing some bits of hardware. Am finding
> that networking is, at least sure seems to be, another black hole for time
> and effort.
> 
> TL;DR (skip to last paragraphs for the question(s))
> 
> At present this is a soho office kind of installation but that will slowly
> be morphing into something that is at least somewhat larger. There are a
> number of input sensor locations being worked on some of which would be
> generating, initially at least, up to 15 data streams sampled possibly
> every second (some maybe more often - - - decisions aren't all done as yet)
> so there will be a fair amount of data running around on my network which
> I'm trying to keep largely a wired affair.
> 
> At this point I'm working on the three entry bits of hardware (and their
> software) - - - the router, hardware firewall, and the managed switch. The
> initial hockup on the fiber system is going to be at 250 Mbps sysmetric.
> 
> For the router I'm planning on using OpenWRT running on a Nanopi r4s which
> according to the folks over on openwrt capable of even very close to full
> Gbps speeds (IIRC tested to some 918 Mbps) which would give some headroom
> for future increases although I don't see a need for the foreseeable
> future.
> 
> For the switch I have found myself a XyZel 1900-48 that I'm working on
> getting OpenWRT on. This ability to run a managed switch on OpenWRT is
> somewhat new but its open source and I'm not tied (I don't think) to
> OpenWRT - - - - except I don't know any other real alternative - - - so
> that's not a difficult solution either. I don't 'need' 48 ports but I have
> 16 at present on a hub and its almost full and that's for stuff only here
> in the orifice (sic!). I also want the capabilities of forcing streaming
> services and wireless communications to not collect any more data from any
> other part of the network (using VLANs) as is possible.
> 
> Then lastly to the hardware firewall.
> I've been looking at pfsense and opnsense. Both are ipv6 possible although
> both are mostly focused on ipv4 at the present. IPfire seems to have gotten
> itself into a holding pattern and is not continuing work toward ipv6
> functionality. Any one of these options are producing headaches when I'm
> trying to figure out how to configure them - - - nothing installed at
> present, just researching so far.
> 
> So - - - - questions - - - -
> 1. is my splitting the network system into the three parts a good idea or
> should I truncate parts 1 and 2 into the router? If you would please give
> reasons - - - please?

Hi,

If you want to have reliability splitting is good, if the router breaks
you still have a working firewall and switch and so on.
If you want also some redundancy you should think of buying 
two of everything:

2 routers 
2 firewalls
2 switches (2 x24 rather than 1x48 ports)

I personally prefer x86 hardware for this kind of things
when I see that little boxes like the Nanopi R4S they make me
think about toys. In my case sadly I'm tied to adsl over pots
so for the modem I still need to use this little plastic blackboxes.
In your case I would swap the nanopi for a nice mini-itx board
with intel nics, a sfx/flex psu (or pico psu), 4-8 gb of ram and a well
ventilated case (with low noise Noctua fans).

> 2. are there any good sources for information on and about networking?
>  debian has moved to nftables from iptables  - - - is devuan doing
> similar?

I think so.

>  Where does one find information to enable a firewall that works yet
> isn't stupid?

I use arno-iptables-firewall It is easy to create a basic setup for your 
network,
reliable, comes with good defaults and can easily be tweaked (for 
port-forwarding, 
vpns, geoip filtering and so on, don't know about vlans as don't use them yet).
 
> (I've wondered about having some kind of easy 'switch' that when users left
> their systems that the system wouldn't be calling home in the overnight at
> least a la ms googly. Dunno if that's 'simple' or not - - - so much to
> learn and so little time to do it all in!)
> 
> TIA

Ciao,
Tito
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] networking thinking

2021-11-28 Thread o1bigtenor via Dng
Greetings

In anticipation of a fiber optical connection (moving from a wireless) I
have been planning out and purchasing some bits of hardware. Am finding
that networking is, at least sure seems to be, another black hole for time
and effort.

TL;DR (skip to last paragraphs for the question(s))

At present this is a soho office kind of installation but that will slowly
be morphing into something that is at least somewhat larger. There are a
number of input sensor locations being worked on some of which would be
generating, initially at least, up to 15 data streams sampled possibly
every second (some maybe more often - - - decisions aren't all done as yet)
so there will be a fair amount of data running around on my network which
I'm trying to keep largely a wired affair.

At this point I'm working on the three entry bits of hardware (and their
software) - - - the router, hardware firewall, and the managed switch. The
initial hockup on the fiber system is going to be at 250 Mbps sysmetric.

For the router I'm planning on using OpenWRT running on a Nanopi r4s which
according to the folks over on openwrt capable of even very close to full
Gbps speeds (IIRC tested to some 918 Mbps) which would give some headroom
for future increases although I don't see a need for the foreseeable
future.

For the switch I have found myself a XyZel 1900-48 that I'm working on
getting OpenWRT on. This ability to run a managed switch on OpenWRT is
somewhat new but its open source and I'm not tied (I don't think) to
OpenWRT - - - - except I don't know any other real alternative - - - so
that's not a difficult solution either. I don't 'need' 48 ports but I have
16 at present on a hub and its almost full and that's for stuff only here
in the orifice (sic!). I also want the capabilities of forcing streaming
services and wireless communications to not collect any more data from any
other part of the network (using VLANs) as is possible.

Then lastly to the hardware firewall.
I've been looking at pfsense and opnsense. Both are ipv6 possible although
both are mostly focused on ipv4 at the present. IPfire seems to have gotten
itself into a holding pattern and is not continuing work toward ipv6
functionality. Any one of these options are producing headaches when I'm
trying to figure out how to configure them - - - nothing installed at
present, just researching so far.

So - - - - questions - - - -
1. is my splitting the network system into the three parts a good idea or
should I truncate parts 1 and 2 into the router? If you would please give
reasons - - - please?
2. are there any good sources for information on and about networking?
 debian has moved to nftables from iptables  - - - is devuan doing
similar?
 Where does one find information to enable a firewall that works yet
isn't stupid?

(I've wondered about having some kind of easy 'switch' that when users left
their systems that the system wouldn't be calling home in the overnight at
least a la ms googly. Dunno if that's 'simple' or not - - - so much to
learn and so little time to do it all in!)

TIA
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] system administration of non-systemd distros and releases

2021-11-28 Thread Peter Duffy
Thanks for posting that. I confess that I'd not seen it before. It does
indeed hit all the nails squarely on the heads.

On Sat, 2021-11-27 at 15:39 -0600, goli...@devuan.org wrote:
> On 2021-11-27 15:00, Mark Rousell wrote:
> > On 25/11/2021 22:57, Steve Litt wrote:
> >> Like I said in 2014,
> >> they won't quit until the cat command requires systemd.
> > 
> > They won't stop until SystemD is in the kernel, such that Linux
> > unavoidably is SystemD.
> > 
> 
> Just have to repost this prescient rant about systemd from 2014.  My all 
> time fav!
> 
> Open letter to the Linux World
>  From: Christopher Barry
> Date: Tue Aug 12 2014 - 15:35:49 EST
> 
> http://lkml.iu.edu//hypermail/linux/kernel/1408.1/02496.html
> 
> golinux
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] system administration of non-systemd distros and releases

2021-11-28 Thread tito via Dng
On Sat, 27 Nov 2021 20:09:33 -0600
goli...@devuan.org wrote:

> On 2021-11-27 18:27, tito via Dng wrote:
> > On Sat, 27 Nov 2021 15:39:53 -0600
> > goli...@devuan.org wrote:
> > 
> >> On 2021-11-27 15:00, Mark Rousell wrote:
> >> > On 25/11/2021 22:57, Steve Litt wrote:
> >> >> Like I said in 2014,
> >> >> they won't quit until the cat command requires systemd.
> >> >
> >> > They won't stop until SystemD is in the kernel, such that Linux
> >> > unavoidably is SystemD.
> >> >
> >> 
> >> Just have to repost this prescient rant about systemd from 2014.  My 
> >> all
> >> time fav!
> >> 
> >> Open letter to the Linux World
> >>  From: Christopher Barry
> >> Date: Tue Aug 12 2014 - 15:35:49 EST
> >> 
> >> http://lkml.iu.edu//hypermail/linux/kernel/1408.1/02496.html
> >> 
> >> golinux
> > 
> > Quod rectum erat, id solum bonum hominibus exstimabat Socrates.
> > 
> > Tito
> > 
> 
> Tito ...
> None of the translations I found made any sense. Please enlighten me/us.
Hi,

:-) maybe due to a little late night typo that slipped through... exstimabat => 
existimabat
translation of translation is roughly:

"The things that were right (honest), only that things Socrates thought were 
good 
for the mankind."

...  in 399 b.C. he was sentenced to death by poisoning.

Ciao,
Tito
  

> Thanks,
> golinux
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng