Dne 01. 07. 20 v 10:29 Zbigniew Jędrzejewski-Szmek napsal(a):
On Tue, Jun 30, 2020 at 11:04:26AM +0200, Zdenek Kabelac wrote:
Dne 30. 06. 20 v 10:57 Vitaly Zaitsev via devel napsal(a):
On 29.06.2020 22:04, Ben Cotton wrote:
Fedora only support these RAID sets when they are already configured
On Tue, Jun 30, 2020 at 11:04:26AM +0200, Zdenek Kabelac wrote:
> Dne 30. 06. 20 v 10:57 Vitaly Zaitsev via devel napsal(a):
> >On 29.06.2020 22:04, Ben Cotton wrote:
> >>Fedora only support these RAID sets when they are already configured in
> >>the BIOS at installation time. So we can solve the
On 30.06.2020 12:16, Zdenek Kabelac wrote:
> The right plan is to fix all packaged dependencies and allow
> installation of packages without lvm2.
+1. This will be the best solution, I think.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
Dne 30. 06. 20 v 11:53 Vitaly Zaitsev via devel napsal(a):
On 30.06.2020 11:42, Zdenek Kabelac wrote:
Default for unskilled users who may use lvm2 - should remain enabled.
If LVM was not used during installation => Anakonda can automatically
disable it.
Hmm - I don't think this is a good
On 30.06.2020 11:42, Zdenek Kabelac wrote:
> Default for unskilled users who may use lvm2 - should remain enabled.
If LVM was not used during installation => Anakonda can automatically
disable it.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
Dne 30. 06. 20 v 11:34 Vitaly Zaitsev via devel napsal(a):
On 30.06.2020 11:23, Igor Raits wrote:
Sadly you can't have lvm2 not installed:
Yes, but it can be disabled.
Of course, you can disable this yourself if you are skilled admin and you do
not need it or use it (you can mask it
On 30.06.2020 11:23, Igor Raits wrote:
> Sadly you can't have lvm2 not installed:
Yes, but it can be disabled.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, 2020-06-30 at 11:04 +0200, Zdenek Kabelac wrote:
> Dne 30. 06. 20 v 10:57 Vitaly Zaitsev via devel napsal(a):
> > On 29.06.2020 22:04, Ben Cotton wrote:
> > > Fedora only support these RAID sets when they are already
> > > configured in
> >
On 30.06.2020 11:04, Zdenek Kabelac wrote:
> If the user does not need lvm2, then the package should not be installed/
> However when lvm2 is installed - lvm2 monitoring service is supposed to
> be there and enabled - it should not impact load time all that much...
I use classic partitions, but
On Mo, 29.06.20 16:04, Ben Cotton (bcot...@redhat.com) wrote:
> https://fedoraproject.org/wiki/Changes/DisableDmraidOnFirstRun
>
> == Summary ==
> The Fedora workstation livecd is the default Fedora variant getfedora.org
> advices people to download.
> As such most Fedora workstation installs
On Tue, Jun 30, 2020 at 10:30 AM José Abílio Matos wrote:
>
> IIRC this is probably related with the dependencies of anaconda:
Is there an easy suggestion we can make to our users other than play
with "rpm -e" or nuking dnf's database? There's a bunch of threads
over at askfedora where people
Dne 30. 06. 20 v 10:57 Vitaly Zaitsev via devel napsal(a):
On 29.06.2020 22:04, Ben Cotton wrote:
Fedora only support these RAID sets when they are already configured in
the BIOS at installation time. So we can solve the problem of
dmraid.service still depending on the obsolete udev-settle
On 29.06.2020 22:04, Ben Cotton wrote:
> Fedora only support these RAID sets when they are already configured in
> the BIOS at installation time. So we can solve the problem of
> dmraid.service still depending on the obsolete udev-settle service by
> making dmraid.service disable itself if no
Hi,
On 6/30/20 12:59 AM, Michael Catanzaro wrote:
On Mon, Jun 29, 2020 at 3:37 pm, Samuel Sieb wrote:
But that should be running concurrently. Does the plot show anything
important waiting for it? Your desktop should be able to load before
that service is finished starting.
Well notably:
On Tuesday, 30 June 2020 00.56.23 WEST Alexander Ploumistos wrote:
> I just tested it on F32 Workstation and for me it does. Have you
> cleaned dnf's databases by any chance? I think either that or having
> the packages as dependencies of something that was installed by the
> user would prevent
On Tuesday, 30 June 2020 00.56.23 WEST Alexander Ploumistos wrote:
> I just tested it on F32 Workstation and for me it does. Have you
> cleaned dnf's databases by any chance? I think either that or having
> the packages as dependencies of something that was installed by the
> user would prevent
On Tue, Jun 30, 2020 at 1:35 AM José Abílio Matos wrote:
>
> On Monday, 29 June 2020 22.23.00 WEST Alexander Ploumistos wrote:
> > This tends to take with it many things that it shouldn't, like gdb,
> > dbus-x11, python3-pwquality, tigervnc-server-minimal and tmux - among
> > others.
>
> I
On Monday, 29 June 2020 22.23.00 WEST Alexander Ploumistos wrote:
> This tends to take with it many things that it shouldn't, like gdb,
> dbus-x11, python3-pwquality, tigervnc-server-minimal and tmux - among
> others.
I noticed that before but at least on F32 it does not do it anymore. I have
On 6/29/20 3:59 PM, Michael Catanzaro wrote:
On Mon, Jun 29, 2020 at 3:37 pm, Samuel Sieb wrote:
But that should be running concurrently. Does the plot show anything
important waiting for it? Your desktop should be able to load before
that service is finished starting.
Well notably:
On Monday, June 29, 2020 1:57:55 PM MST Michael Catanzaro wrote:
> On Mon, Jun 29, 2020 at 3:45 pm, Michael Catanzaro
> wrote:
>
> > We might need to explicitly disable systemd-udev-settle.service
> > during the system upgrade to turn it off?
>
>
> Doesn't work... I tried 'systemctl disable
On Mon, Jun 29, 2020 at 3:37 pm, Samuel Sieb wrote:
But that should be running concurrently. Does the plot show anything
important waiting for it? Your desktop should be able to load before
that service is finished starting.
Well notably: plymouth-quit-wait.service. Surely plymouth keeps
On 6/29/20 1:57 PM, Michael Catanzaro wrote:
On Mon, Jun 29, 2020 at 3:45 pm, Michael Catanzaro
wrote:
We might need to explicitly disable systemd-udev-settle.service during
the system upgrade to turn it off?
Doesn't work... I tried 'systemctl disable systemd-udev-settle.service'
and
On Mon, Jun 29, 2020 at 11:09 PM Hans de Goede wrote:
>
> I fix this on my
> own systems with "dnf remove dmraid"
This tends to take with it many things that it shouldn't, like gdb,
dbus-x11, python3-pwquality, tigervnc-server-minimal and tmux - among
others.
On Mon, Jun 29, 2020 at 11:09 pm, Hans de Goede
wrote:
I got the name of the unit wrong in the change proposal, sorry. I fix
this on my
own systems with "dnf remove dmraid", but unlike multipath some
desktop machines
may actually have a BIOS/firmware RAID set configured which needs
dmraid and
On Mon, Jun 29, 2020 at 2:58 PM Michael Catanzaro wrote:
>
> On Mon, Jun 29, 2020 at 3:45 pm, Michael Catanzaro
> wrote:
> > We might need to explicitly disable systemd-udev-settle.service
> > during the system upgrade to turn it off?
>
> Doesn't work... I tried 'systemctl disable
Hi,
On 6/29/20 10:57 PM, Michael Catanzaro wrote:
On Mon, Jun 29, 2020 at 3:45 pm, Michael Catanzaro wrote:
We might need to explicitly disable systemd-udev-settle.service during the
system upgrade to turn it off?
Doesn't work... I tried 'systemctl disable systemd-udev-settle.service' and
On Mon, Jun 29, 2020 at 3:45 pm, Michael Catanzaro
wrote:
We might need to explicitly disable systemd-udev-settle.service
during the system upgrade to turn it off?
Doesn't work... I tried 'systemctl disable systemd-udev-settle.service'
and rebooted again, and it's still running. I tried
So, in relation to the device-mapper-multipath change in the other
thread, I ran 'sudo dnf remove device-mapper-multipath'. Then I ran
'systemctl status dmraid.service' and saw "Unit dmraid.service could
not be found," so I must not have that installed at all. Then I
rebooted. When I run
On Mon, Jun 29, 2020 at 4:05 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/DisableDmraidOnFirstRun
>
> == Summary ==
> The Fedora workstation livecd is the default Fedora variant getfedora.org
> advices people to download.
> As such most Fedora workstation installs will be done
On Mon, Jun 29, 2020 at 2:06 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/DisableDmraidOnFirstRun
> Fedora only support these RAID sets when they are already configured in the
> BIOS at installation time. So we can solve the problem of dmraid.service
> still depending on the
30 matches
Mail list logo