On Do, 21.06.18 09:33, Hans de Goede (hdego...@redhat.com) wrote:
> > > Wants=system-update-pre.target
> > > After=system-update-pre.target
> > Yep, that sounds reasonable.
>
> So one more question about this, as discussed in the pull-req,
> updates services being linked from system-update.target
Hi,
On 13-06-18 17:05, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote:
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is supposed
Hi,
On 13-06-18 17:05, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote:
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is supposed
On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote:
> Hi,
>
> On 12-06-18 19:11, Lennart Poettering wrote:
> >On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
> >>AFAIK the service actually doing the updates is supposed to call
> >>systemctl reboot --force when it is do
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is supposed to call
systemctl reboot --force when it is done, so any targets after
system-update.target won't get started ?
True, the
Hi,
On 13-06-18 05:40, Alexander E. Patrakov wrote:
Hans de Goede :
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boot was successful and
cleanly shutdown the machine and show
Hans de Goede :
>
> Hi All,
>
> So as you may have heard, I'm working on hiding the grub-menu
> by default on single OS Fedora Workstation. Part of the plan
> here is to detect if a previous boot was successful and
> cleanly shutdown the machine and show the menu (not hide the
> menu) if the previ
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
> > I figure gdm could
> > try to expose that feature somewhere, maybe in the top-right menu or
> > so?
>
> Yes I need to talk to the GNOME designers about adding some advanced
> reboot options somewhere:
>
> 1) Reboot into firmwa
Hi,
On 12-06-18 10:24, Lennart Poettering wrote:
On Mo, 11.06.18 17:40, Hans de Goede (hdego...@redhat.com) wrote:
It am very sure it's not worth trying to maintain a shutdown_sucess
variable that is determined that early. That's a pointless excercise,
OB> > you won't catch 99% of relevant is
On Mo, 11.06.18 17:40, Hans de Goede (hdego...@redhat.com) wrote:
> > It am very sure it's not worth trying to maintain a shutdown_sucess
> > variable that is determined that early. That's a pointless excercise,
OB> > you won't catch 99% of relevant issues that way...
>
> Ok, I had a quick chat w
Hi,
On 11-06-18 17:48, Jérémy Rosen wrote:
We solve a problem which is kinda similar in the embedded world when we do A/B
update
I'll describe how we do it so you see if this can help
* Have a single "last boot went wrong" flag
When grub starts
* if the flag is set, show the boot menu (or a t
We solve a problem which is kinda similar in the embedded world when we
do A/B update
I'll describe how we do it so you see if this can help
* Have a single "last boot went wrong" flag
When grub starts
* if the flag is set, show the boot menu (or a timer)
* if the flag is not set
* skip the m
Hi,
On 11-06-18 16:37, Lennart Poettering wrote:
On Mo, 11.06.18 15:37, Hans de Goede (hdego...@redhat.com) wrote:
Uurks. Quite frankly, it appears strange to me to delay this for this
long. I mean we reworked most code that delayed worked to shutdown
like this these days to happen as early as
On Mo, 11.06.18 15:37, Hans de Goede (hdego...@redhat.com) wrote:
> > Uurks. Quite frankly, it appears strange to me to delay this for this
> > long. I mean we reworked most code that delayed worked to shutdown
> > like this these days to happen as early as possible to make sure we
> > don't lose
Hi,
On 11-06-18 13:31, Lennart Poettering wrote:
On Mo, 11.06.18 12:48, Hans de Goede (hdego...@redhat.com) wrote:
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boot was succe
On Mo, 11.06.18 12:48, Hans de Goede (hdego...@redhat.com) wrote:
> Hi All,
>
> So as you may have heard, I'm working on hiding the grub-menu
> by default on single OS Fedora Workstation. Part of the plan
> here is to detect if a previous boot was successful and
> cleanly shutdown the machine an
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boot was successful and
cleanly shutdown the machine and show the menu (not hide the
menu) if the previous boot has failed to set eit
17 matches
Mail list logo
