On Thu, Dec 10, 2020, at 5:56 PM, Chris Murphy wrote:
> I personally am gravitating toward the idea of not updating the
> currently running OS (sometimes called transactional system updates)
> where if we had a way to test the out-of-band updated OS, like in a
> container or VM,
We've been
Am 10.12.20 um 23:56 schrieb Chris Murphy:
There is also the sysroot fails to mount problem. That leaves us in
the initramfs which is an even more limited environment. For sure
falling over at boot or during startup is rare, but no matter why it
often induces panic in even experienced users, in
On Thu, Dec 10, 2020 at 1:07 PM Benjamin Berg wrote:
>
> Hi,
>
> On Thu, 2020-12-10 at 12:20 -0700, Chris Murphy wrote:
> > On Thu, Dec 10, 2020 at 5:40 AM Benjamin Berg
> > wrote:
> > > Hi,
> > >
> > > so, the other day we had a major regression in the PAM stack[1]
> > > that,
> > >
Hi,
On Thu, 2020-12-10 at 12:20 -0700, Chris Murphy wrote:
> On Thu, Dec 10, 2020 at 5:40 AM Benjamin Berg
> wrote:
> > Hi,
> >
> > so, the other day we had a major regression in the PAM stack[1]
> > that,
> > unfortunately, ended up hitting rawhide and the Fedora 33 testing
> > (not
> >
On Thu, Dec 10, 2020 at 5:40 AM Benjamin Berg wrote:
>
> Hi,
>
> so, the other day we had a major regression in the PAM stack[1] that,
> unfortunately, ended up hitting rawhide and the Fedora 33 testing (not
> stable) repository before being unpushed.
>
> In this case it was easy to work around
On Thu, Dec 10, 2020 at 1:39 pm, Benjamin Berg wrote:
I suppose to improve this, we would need a kind of "sudologin" that
accepts any user in the "wheel" group. Or maybe some other more rigid
requirement like configuring the first admin user that was created.
I'd say ideally any user in wheel
Hi,
so, the other day we had a major regression in the PAM stack[1] that,
unfortunately, ended up hitting rawhide and the Fedora 33 testing (not
stable) repository before being unpushed.
In this case it was easy to work around as SSH was still working fine.
But, it seems that rescue mode
