Mailinglist Archive: opensuse (856 mails)

< Previous Next >
Re: [opensuse] interesting reading about systemd
On 10/03/2016 10:00 AM, Carlos E. R. wrote:
On 2016-10-03 15:26, Anton Aylward wrote:
On 10/03/2016 08:58 AM, Per Jessen wrote:
I'm sure that is/was a genuine problem, but allow me to count it as an
exception to prove the rule. I think it is very far from your example
to your general suggestion that

"... that if there is a problem I can not edit an script and solve it.
I have to wait for the devs to solve and distribute it".


Indeed.
As I say in another posting, if you are relying on /etc/fstab and the
generator
that parses it, you end up with the systemd semantics that maintain the
system,
automatically restarting when something 'dies' so as to maintain a constant
picture.

If you want different, take the entry out of fstab and write your own mount
file
that does what you want.

That's not a solution.

The right solution would be a syntax in fstab telling systemd to leave
that line alone.

Something like 'noauto' ?



This is not a problem with systemd.

Yes, it is. It started with systemd. Thus per definition, it is a
systemd generated problem.

No, systemd is trying to keep the system stable.
Systemd also corrected many problems and deficiencies that previously existed.
Relying on erroneous, buggy or poor operational practices is not a good thing.
Fixing them, re-architecting for robustness and stability is only a 'problem' of
you relied on those bugs and errors in the first place.
--
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting frowned upon?

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups