Samuel Sieb writes:
On 3/22/21 6:00 PM, Sam Varshavchik wrote:
Yup. This is an obvious vendor lock-in play. Replace widely-known
technologies with new, arcane stuff whose full documentation is kept
internal, and is leveraged as a value-added product.
We all understand by now that you
On 3/22/21 6:00 PM, Sam Varshavchik wrote:
Tom Horsley writes:
On Mon, 22 Mar 2021 18:07:12 -0400
Sam Varshavchik wrote:
> It seems to be trying to derive epoch time for
> the next start time, something along those lines.
More obviously it seems to be systemd re-implementing
cron from
Tom Horsley writes:
On Mon, 22 Mar 2021 18:07:12 -0400
Sam Varshavchik wrote:
> It seems to be trying to derive epoch time for
> the next start time, something along those lines.
More obviously it seems to be systemd re-implementing
cron from scratch instead of just using the already
working
On Mon, 22 Mar 2021 18:07:12 -0400
Sam Varshavchik wrote:
> It seems to be trying to derive epoch time for
> the next start time, something along those lines.
More obviously it seems to be systemd re-implementing
cron from scratch instead of just using the already
working after decades of use
Tom Horsley writes:
On Mon, 22 Mar 2021 08:22:46 -0400
Sam Varshavchik wrote:
> This is complexity purely for the sake of having complexity, and
introducing
> more unneeded dependencies on the systemd monstrosity.
Didn't this thread start with a warning about raid systems
hanging at boot?
The bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1941335
Fix is nearly ready:
https://github.com/systemd/systemd/pull/19075
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
On Mon, 2021-03-22 at 10:06 -0400, Ben Cotton wrote:
> On Mon, Mar 22, 2021 at 9:52 AM Tom Horsley
> wrote:
> >
> > Didn't this thread start with a warning about raid systems
> > hanging at boot? What on earth does raid care what the
> > timezone is?
>
> From the thread on the devel list[1], it
On Mon, 22 Mar 2021 at 10:45, Tom Horsley wrote:
> On Mon, 22 Mar 2021 08:22:46 -0400
> Sam Varshavchik wrote:
>
> > This is complexity purely for the sake of having complexity, and
> introducing
> > more unneeded dependencies on the systemd monstrosity.
>
> Didn't this thread start with a
On Mon, Mar 22, 2021 at 9:52 AM Tom Horsley wrote:
>
> Didn't this thread start with a warning about raid systems
> hanging at boot? What on earth does raid care what the
> timezone is?
From the thread on the devel list[1], it seems that the issue may be
that Ireland switched to summer time at
On Mon, 22 Mar 2021 08:22:46 -0400
Sam Varshavchik wrote:
> This is complexity purely for the sake of having complexity, and introducing
> more unneeded dependencies on the systemd monstrosity.
Didn't this thread start with a warning about raid systems
hanging at boot? What on earth does raid
Ed Greshko writes:
On 22/03/2021 19:26, Patrick O'Callaghan wrote:
On Sun, 2021-03-21 at 19:48 -0400, Sam Varshavchik wrote:
But, it seems that this was too simple. Things cannot be this simple
anymore. We must have daemons involved in this process, for some
unclear
reason. The more, the
On 22/03/2021 20:07, Patrick O'Callaghan wrote:
On Mon, 2021-03-22 at 19:43 +0800, Ed Greshko wrote:
When it comes to time zones, it can help clear up some ambiguities
for people that don't live in
the US. Like, did you know that Taiwan the abbreviation for our time
zone is CST? Setting the
On Mon, 2021-03-22 at 19:43 +0800, Ed Greshko wrote:
> When it comes to time zones, it can help clear up some ambiguities
> for people that don't live in
> the US. Like, did you know that Taiwan the abbreviation for our time
> zone is CST? Setting the
> time zone from the list provided by
On 22/03/2021 19:26, Patrick O'Callaghan wrote:
On Sun, 2021-03-21 at 19:48 -0400, Sam Varshavchik wrote:
But, it seems that this was too simple. Things cannot be this simple
anymore. We must have daemons involved in this process, for some
unclear
reason. The more, the merrier.
Pandemonium.
On Sun, 2021-03-21 at 19:48 -0400, Sam Varshavchik wrote:
> But, it seems that this was too simple. Things cannot be this simple
> anymore. We must have daemons involved in this process, for some
> unclear
> reason. The more, the merrier.
Pandemonium.
poc
On Sun, Mar 21, 2021 at 4:37 PM Patrick O'Callaghan
wrote:
>
> On Mon, 2021-03-22 at 06:12 +0800, Ed Greshko wrote:
> > On 22/03/2021 02:27, Chris Murphy wrote:
> > > Some folks are reporting a hang when booting Fedora 33 this morning
> > > (or also possibly wake from sleep). We're still digging
Ed Greshko writes:
Another interesting factoid.
[egreshko@f33g ~]$ sudo timedatectl set-timezone Europe/Dublin
[egreshko@f33g ~]$ date
Sun Mar 21 22:49:06 GMT 2021
[egreshko@f33g ~]$ sudo timedatectl set-timezone Asia/Taipei
And the command is "hung"
Until
Failed to set time zone:
On 22/03/2021 07:07, Patrick O'Callaghan wrote:
Clearly BZ-worthy I'd say.
Oh, there is one. https://bugzilla.redhat.com/show_bug.cgi?id=1941335
--
People who believe they don't make mistakes have already made one.
___
users mailing list --
On Mon, 2021-03-22 at 06:54 +0800, Ed Greshko wrote:
> On 22/03/2021 06:36, Patrick O'Callaghan wrote:
> > On Mon, 2021-03-22 at 06:12 +0800, Ed Greshko wrote:
> > > On 22/03/2021 02:27, Chris Murphy wrote:
> > > > Some folks are reporting a hang when booting Fedora 33 this
> > > > morning
> > > >
On 22/03/2021 06:36, Patrick O'Callaghan wrote:
On Mon, 2021-03-22 at 06:12 +0800, Ed Greshko wrote:
On 22/03/2021 02:27, Chris Murphy wrote:
Some folks are reporting a hang when booting Fedora 33 this morning
(or also possibly wake from sleep). We're still digging into it but
looks like a
On Mon, 2021-03-22 at 06:12 +0800, Ed Greshko wrote:
> On 22/03/2021 02:27, Chris Murphy wrote:
> > Some folks are reporting a hang when booting Fedora 33 this morning
> > (or also possibly wake from sleep). We're still digging into it but
> > looks like a work around right now is to boot with
On 22/03/2021 02:27, Chris Murphy wrote:
Some folks are reporting a hang when booting Fedora 33 this morning
(or also possibly wake from sleep). We're still digging into it but
looks like a work around right now is to boot with parameter:
systemd.mask=raid-check.timer
You can subsequently
Some folks are reporting a hang when booting Fedora 33 this morning
(or also possibly wake from sleep). We're still digging into it but
looks like a work around right now is to boot with parameter:
systemd.mask=raid-check.timer
You can subsequently 'systemctl disable raid-check.timer'. Folks with
23 matches
Mail list logo
