On Thu, 28 Apr 2022 at 19:39, Dave Ihnat wrote:
> On 28 Apr at 17:27, Tom Horsley wrote:
> > But systemd-timedated tries to supplant them all :-). This is where
> > my "computer fungus" description comes from. Every systemd release
> > seems to take over something else that worked fine without s
On 4/28/22 15:38, Dave Ihnat wrote:
On 28 Apr at 17:27, Tom Horsley wrote:
But systemd-timedated tries to supplant them all :-). This is where
my "computer fungus" description comes from. Every systemd release
seems to take over something else that worked fine without systemd
engulfing it.
Th
On 28 Apr at 17:27, Tom Horsley wrote:
> But systemd-timedated tries to supplant them all :-). This is where
> my "computer fungus" description comes from. Every systemd release
> seems to take over something else that worked fine without systemd
> engulfing it.
I've been working in Unix since ab
On Thu, 28 Apr 2022 18:15:16 -0400
Sam Varshavchik wrote:
> History is full of similar examples, of an established component getting
> replaced by a lighter replacement: chrony supplanting ntp; cronie
> supplanting vixie-cron. This certainly can happen again.
But systemd-timedated tries to su
Justin Moore writes:
And, not to be too flip, I think that's part of the problem.
Only the slow march of time will fix this problem.
The core features of systemd – the dependency-based replacement for init
that uses containers – the initial feature set that was was used as its
advocacy: i
On Wed, Apr 27, 2022 at 08:05:56AM -0400, Sam Varshavchik wrote:
>
> And in the instant case, we had:
>
> 1) A broken systemd-resolved scriptlet that ended up overwriting the
> /etc/resolv.conf symlink. This was fixed in the -2 update, but the initial
> reports were ignored, because we were told
On Wed, 2022-04-27 at 08:05 -0400, Sam Varshavchik wrote:
> The only reason systemd-resolved exists is because glibc caches
> /etc/resolv.conf when a process performs its first DNS lookup. Having
> the means to have an existing process become aware that its been
> changed, and it should reread it
> On 27 Apr 2022, at 13:05, Sam Varshavchik wrote:
>
> The only reason systemd-resolved exists is because glibc caches
> /etc/resolv.conf when a process performs its first DNS lookup. Having the
> means to have an existing process become aware that its been changed, and it
> should reread it
Justin Moore writes:
This kind of blanket dismissal of user feedback and refusal to believe *even
the possibility* that systemd could be broken in obvious ways contributes to
the sense from the community that negative feedback about systemd has been
and will be ignored.
Had the response
Tom Horsley writes:
> if you want it to, it will terminate all user processes *for that session*
when it logs out
This only recently started working moderately well. If I ever ssh'ed into
my desktop for a separate login session, systemd would create some sort
of systemd user daemon that would
Todd Zullinger writes:
The relevant parts of the diff from -1 to -2 are:
%posttrans resolved
+[ $1 -eq 1 ] || exit 0
+# Initial installation
+
And that's why an update to 11-1.fc35 ran the rest of the script.
- if ! test -e /etc/resolv.conf && ! test -L /etc/resolv.co
Sam Varshavchik wrote:
> Kevin Fenzi writes:
>
>>> That's the first ln -s call in the scriptlet.
>>>
>>> Now, look at the second one, the one with the -f flag.
>>
>> Which systemd version are you looking at?
>
> systemd-249.11-1.fc35.src.rpm
>
>> bug #2074122 was just recently fixed in
>> https
Kevin Fenzi writes:
> That's the first ln -s call in the scriptlet.
>
> Now, look at the second one, the one with the -f flag.
Which systemd version are you looking at?
systemd-249.11-1.fc35.src.rpm
bug #2074122 was just recently fixed in
https://bodhi.fedoraproject.org/updates/FEDORA-2022-
On Sun, Apr 24, 2022 at 02:12:50PM -0400, Sam Varshavchik wrote:
> Kevin Fenzi writes:
>
> > I suggest the OP misunderstood the setup or intended setup.
> >
> > The scriptlets will set /etc/resolv.conf to point to the
> > systemd-resolved resolver if:
> >
> > * The /etc/resolv.conf file doesn't
Kevin Fenzi writes:
I suggest the OP misunderstood the setup or intended setup.
The scriptlets will set /etc/resolv.conf to point to the
systemd-resolved resolver if:
* The /etc/resolv.conf file doesn't exist yet
AND
* systemd is being used to boot (so, it's not a container, etc)
AND
* systemd
Michael Hennebry writes:
On Sat, 23 Apr 2022, Samuel Sieb wrote:
The benefits have been well explained. The problem is that some people
really don't like change even if it's for the better. And sometimes things
do break when changed and instead of finding out why it breaks and how to
fi
Michael Hennebry writes:
TH was making fun of code, not the person who is
just trying to figure out how to live with it.
No, the allegation was that disparaging comments directed at the code are
perceived as impuning the character of the code's source, and not the
character who's using the
systemd-resolved can also be just uninstalled. Provides at least very
basic symlink removal.
On 4/19/22 14:27, Tom Horsley wrote:
> On Mon, 18 Apr 2022 23:43:36 -0400
> Sam Varshavchik wrote:
>
>> Help me out here: wasn't there a point of order made, way back when: hey, if
>>
>> you want to dis
On Mon, 18 Apr 2022 23:43:36 -0400
Sam Varshavchik wrote:
> Help me out here: wasn't there a point of order made, way back when: hey, if
> you want to disable systemd-resolved, just manually replace the
> /etc/resolv.conf symlink?
You also need to systemctl disable systemd-resolved (and proba
On Mon, Apr 18, 2022 at 11:43 PM Sam Varshavchik wrote:
> Help me out here: wasn't there a point of order made, way back when: hey, if
> you want to disable systemd-resolved, just manually replace the
> /etc/resolv.conf symlink?
*and* disable the systemd unit, I believe. At least that is what I
Tim via users writes:
On Mon, 2022-04-18 at 20:57 -0400, Matthew Miller wrote:
> This is quite missing my point. I'm not interested in _arguing_ at
> all. The point is: your hyperbole about "hijacking" and etc. is not
> appropriate. This is an intentional, discussed, and approved change
> that w
21 matches
Mail list logo
