when startup delays become bugs

Adam Williamson awilliam at redhat.com
Fri May 17 19:27:43 UTC 2013


On Fri, 2013-05-17 at 10:18 -0500, David Lehman wrote:
> On Fri, 2013-05-17 at 09:07 +0200, Hans de Goede wrote:
> > Hi,
> > 
> > On 05/17/2013 01:31 AM, Lennart Poettering wrote:
> > > On Thu, 16.05.13 16:17, Bill Nottingham (notting at redhat.com) wrote:
> > >
> > >> Lennart Poettering (mzerqung at 0pointer.de) said:
> > >>>> RequiredBy=
> > >>>> WantedBy=dmraid-activation.service
> > >>>>
> > >>>> I'm not using dmraid, or md raid, or any kind of raid at the moment. I also have this entry, previously explained in this thread as probably not being needed unless dmraid is being used, so is the likely offender for udev-settle.
> > >>>>
> > >>>>            2.823s dmraid-activation.service
> > >>>
> > >>> Given that this is really only needed for exotic stuff I do wonder why
> > >>> we need to install this by default even.
> > >>
> > >> We *could* drop all the assorted local storage tools from @standard and just leave
> > >> them to be installed by anaconda if they're being used to create such
> > >> storage. They'd have to remain on the live image, though, and so this would
> > >> not help installs done from the live images.
> > >
> > > Does anaconda have infrastructure for this?
> > 
> > Yes, it already drags in for example iscsi-initiator-utils automatically when
> > iscsi disks are used during install. IIRC doing the same for dmraid should
> > not be hard.
> 
> This has been in place since somewhere around F11 or F12. You just can't
> tell since dmraid is in base. There is still the anaconda-tools group,
> which I forget the purpose of (live media?).

Isn't anaconda-tools the group used to ensure that things anaconda may
need to install for particular hardware are present on images?
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net



More information about the devel mailing list