This is what good old systemd has done to me...
 

No longer can get email and after 3 days of digging, haven't been
able to find out what is wrong. And people have accused me of simply
hating systemd for no reason.

'DNS query for me.com returned an error from the server: ServerFailure'

This is what good old systemd has done to me...
 

On 2019-01-13, Ike wrote:

No longer can get email and after 3 days of digging, haven't been
able to find out what is wrong. And people have accused me of simply
hating systemd for no reason.

'DNS query for me.com returned an error from the server: ServerFailure'

Of course it must be systemd's fault, rather than you own. Everything is
someone else's fault for you.

This is what good old systemd has done to me...
 

Ike writes:

No longer can get email and after 3 days of digging, haven't been
able to find out what is wrong. And people have accused me of simply
hating systemd for no reason.

What makes you think systemd has anything to with your ability to read
mail?

'DNS query for me.com returned an error from the server: ServerFailure'

I doubt that the message "ServerFailure" came from the remote mail
server.

For what it's worth, the message I get is:

homepc nslookup me.com
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: me.com
Address: 17.142.160.83
Name: me.com
Address: 17.172.224.103
Name: me.com
Address: 17.178.96.97

You need to actually present your problem with real error messages
and an actual description of what the problem is.
Assuming you actually want something to work instead of picking
your favorite scab.

--
Dan Espen

This is what good old systemd has done to me...
 

On 13/01/2019 22.23, Ike wrote:

*No longer can get email and after 3 days of digging, haven't been able
to find out what is wrong.* And people have accused me of simply hating
systemd for no reason.

And why would that be a systemd problem?

And why are you posting to a Windows group? Are you trolling?


'DNS query for me.com returned an error from the server: ServerFailure'

It works here, and I'm using systemd.

--
Cheers, Carlos.

This is what good old systemd has done to me...
 

On 2019-01-13, Ike wrote:

No longer can get email and after 3 days of digging, haven't been
able to find out what is wrong. And people have accused me of
simply hating systemd for no reason.

'DNS query for me.com returned an error from the server:
ServerFailure'

Of course it must be systemd's fault, rather than you own. Everything
is someone else's fault for you.

Didn't touch the machine for months. Had systemd do something like
this before. So no, it wasn't me. It is the ill-conceived, written
systemd.

This is what good old systemd has done to me...
 

Ike writes:

No longer can get email and after 3 days of digging, haven't been
able to find out what is wrong. And people have accused me of
simply hating systemd for no reason.

What makes you think systemd has anything to with your ability to
read mail?

'DNS query for me.com returned an error from the server:
ServerFailure'

I doubt that the message "ServerFailure" came from the remote mail
server.

For what it's worth, the message I get is:

homepc nslookup me.com
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: me.com
Address: 17.142.160.83
Name: me.com
Address: 17.172.224.103
Name: me.com
Address: 17.178.96.97

You need to actually present your problem with real error messages
and an actual description of what the problem is.
Assuming you actually want something to work instead of picking
your favorite scab.

systemd lovers will never omit they are wrong. I never had this
happen before with non-systemd debian.

This is what good old systemd has done to me...
 

On Sun, 13 Jan 2019 15:23:24 -0600, Ike wrote:

And people have accused me of simply
hating systemd for no reason.


For a personal workstation systemd is a TOTALLY UNNECESSARY and
massive layer of pure junk. Anyone stupid enough to accept it
will reject all counterarguments for its usefulness.

Systemd is RedHat's attempt to foist a universal API, under its
total control and for its own profit, onto the Linux ecosystem.
This fact may not be that surprising, but what is surprising,
if not shocking, is the rapid acquiescence demonstrated by all
major distros to RedHat's wishes.

Distro maintainers are now the slaves and lackeys of RedHat.

Although unlikely, the only salvation for free software will
be the GNU HURD OS under strict control by GNU and the FSF.

This is what good old systemd has done to me...
 

On 14/01/2019 01.28, Ike wrote:
On 2019-01-13, Ike wrote:

* No longer can get email and after 3 days of digging, haven't been
able to find out what is wrong.* And people have accused me of
simply* hating systemd for no reason.

'DNS query for me.com returned an error from the server: ServerFailure'

Of course it must be systemd's fault, rather than you own. Everything
is someone else's fault for you.

*Didn't touch the machine for months.* Had systemd do something like
this before.* So no, it wasn't me.* It is the ill-conceived, written
systemd.

Yeah sure.

Oh, wait! You forgot to go round your computer seven times singing and
praying.

--
Cheers, Carlos.

This is what good old systemd has done to me...
 

On 2019-01-14, F. Russell wrote:
Although unlikely, the only salvation for free software will
be the GNU HURD OS under strict control by GNU and the FSF.

There are always the BSDs.

--
-----------------------------------------------------------------------------
Roger Blake (Posts from Google Groups killfiled due to excess spam.)

NSA sedition and treason -- http://www.DeathToNSAthugs.com
Don't talk to cops! -- http://www.DontTalkToCops.com
Badges don't grant extra rights -- http://www.CopBlock.org
-----------------------------------------------------------------------------

This is what good old systemd has done to me...
 

On 14/01/2019 01.28, Ike wrote:
On 2019-01-13, Ike wrote:

* No longer can get email and after 3 days of digging, haven't
been able to find out what is wrong.* And people have accused me
of simply* hating systemd for no reason.

'DNS query for me.com returned an error from the server:
ServerFailure'

Of course it must be systemd's fault, rather than you own.
Everything is someone else's fault for you.

*Didn't touch the machine for months.* Had systemd do something like
this before.* So no, it wasn't me.* It is the ill-conceived, written
systemd.

Yeah sure.

Oh, wait! You forgot to go round your computer seven times singing
and praying.

Calling this guy a liar is not a valid defense.

This is what good old systemd has done to me...
 

On 14/01/2019 13.52, Tech Systems wrote:
On 14/01/2019 01.28, Ike wrote:
On 2019-01-13, Ike wrote:

* No longer can get email and after 3 days of digging, haven't been
able to find out what is wrong.* And people have accused me of
simply* hating systemd for no reason.

'DNS query for me.com returned an error from the server:
ServerFailure'

Of course it must be systemd's fault, rather than you own.
Everything is someone else's fault for you.

*Didn't touch the machine for months.* Had systemd do something like
this before.* So no, it wasn't me.* It is the ill-conceived, written
systemd.

Yeah sure.

Oh, wait! You forgot to go round your computer seven times singing and
praying.

*Calling this guy a liar is not a valid defense.

I'm not exactly calling him a liar... Just baseless.

Claiming that systemd is the culprit of his problems is the same as
claiming that chanting around with candles have anything to do.

--
Cheers, Carlos.

This is what good old systemd has done to me...
 

Ike wrote:

Ike writes:

No longer can get email and after 3 days of digging, haven't been
able to find out what is wrong. And people have accused me of
simply hating systemd for no reason.

What makes you think systemd has anything to with your ability to
read mail?

'DNS query for me.com returned an error from the server:
ServerFailure'

I doubt that the message "ServerFailure" came from the remote mail
server.

For what it's worth, the message I get is:

homepc nslookup me.com
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: me.com
Address: 17.142.160.83
Name: me.com
Address: 17.172.224.103
Name: me.com
Address: 17.178.96.97

You need to actually present your problem with real error messages
and an actual description of what the problem is.
Assuming you actually want something to work instead of picking
your favorite scab.

systemd lovers will never omit they are wrong. I never had this
happen before with non-systemd debian.

Actually, it never happened to you at all. You are trolling, and badly at
that. I would believe that you can't read mail from your wintendo system,
given that you post with a windows-only newsreader. But that would be your
problem and a windows problem. Which is also your problem

This is what good old systemd has done to me...
 

Tech Systems wrote:

On 14/01/2019 01.28, Ike wrote:
On 2019-01-13, Ike wrote:

No longer can get email and after 3 days of digging, haven't
been able to find out what is wrong. And people have accused me
of simply hating systemd for no reason.

'DNS query for me.com returned an error from the server:
ServerFailure'

Of course it must be systemd's fault, rather than you own.
Everything is someone else's fault for you.

Didn't touch the machine for months. Had systemd do something like
this before. So no, it wasn't me. It is the ill-conceived, written
systemd.

Yeah sure.

Oh, wait! You forgot to go round your computer seven times singing
and praying.

Calling this guy a liar is not a valid defense.

Well, it is what he is. He is spouting pure, unadultered bull****