[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 2.6.14 status summary, and upcoming 2.6.15 ...



On Monday 28 November 2005 12:45, Jonas Smedegaard wrote:
> The following problems are known for yaird currently in sid:

Add:
* Does not work for drivers that don't have sysfs support, like BusLogic

> We do not have _automated_ workarounds, which it seems you imply and I
> clearly didn't above.

Manual workarounds are not always possible. In a lot of cases manual 
workarounds are fine for upgrades, but they are impractical to say the 
least for new installations.
Every case where a manual workaround is needed is one that makes yaird 
less attractive for use in Debian Installer.

> Only yaird problem I know of leading to problems booting (and brick'ing
> if using bootloaders with no alternative) is with drivers that does not
> support sysfs. We do not have an overview of the size of that problem.

Correct. It would be very nice if that could be investigated.
IMHO it should not be too hard to write a yaird module that checks if 
modules that don't support sysfs are loaded on the running system and, if 
that is the case, adds them to the initrd.

> > If there is a workaround, we could put out a errata list of the
> > problems and possible workarounds and stuff.
>
> ...that's what Erik wants to do as well for the non-sysfs supported
> hardware. I am not ahead of him, and I don't think such list exist yet.

Again, this is not really a solution for new installations.

Attachment: pgpQ7qxxn3TU3.pgp
Description: PGP signature


Reply to: