hello,

while waiting rc1 to be mirrored out, i've set up a WIP repo at

http://ftp.frugalware.org/pub/other/people/vmiklos/kernel2624

it contains kernel-2.6.24 and i'm about to fix up other packages which
are now broken by this update.

non-kernel-module pkgs:
- kbd pkg. it now handles that the terminals are by default utf8, so it
  disabled unicode if utf8 is not in $LANG

external modules:
- acerhk: fixed up FB, built
- kqemu: rebuilt
- ipw3945: patched, built and blacklisted by default. the in-kernel
  iwl3945 driver is more stable, but i haven't removed ipw3945 as for
  example it's needed for wpa2 support (hopefully the in-kernel driver
  will support it as well.
- rt2400: removed, use the new in-kernel driver
- rt2500: same
- gspcav1: rebuilt
- truecrypt: patched, built
- nvidia: rebuilt
- redirfs: new package, required by dazuko, see below
- dazuko: patched, now using redirfs as lsm support has been removed in
  2.6.24
- ndiswrapper: rebuilt
- adm8211: removed, use the new in-kernel driver
- nvidia-96xx: rebuilt
- lirc: patched, built
- madwifi: rebuilt
- virtualbox: rebuilt
- qc-usb: patched, built
- wlan-ng: patched, built
- acx100: patched, built

still broken:
- fglrx: FTBFS, should we switch to the catalyst driver? (it builds with
  2.6.24) - voroskoi?
- rlocate: FTBFS, because of lsm removal. crazy suggested to make this
  nobuild if other modules are already ok, we'll see what can we do.
- r8169: FTBFS. is it still needed - voroskoi?

i'm running this repo for 2 days and it seems i have no stability
problems so far. if we can resolve these 3 issues, i think we could
merge, and let 0.8 go with 2.6.24. opinions?

(as a side note, no rush. we can wait with that merge if we want, rc2 is
not near.)

references:
- lsm removal:
  
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=20510f2f4e2dabb0ff6c13901807627ec9452f98;hp=5c3b447457789374cdb7b03afe2540d48c649a36

thanks,
- VMiklos

Attachment: pgpR3zox0EEVT.pgp
Description: PGP signature

_______________________________________________
Frugalware-devel mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-devel

Reply via email to