2007/3/6, Lucas C. Villa Real <[EMAIL PROTECTED]>: > On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > > On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > > > > > It shouldn't make difference. Detsch tested the upgrade on a 2.3 > > > system moving to a 2.4. I have never tried myself to upgrade Glibc. > > > Can anyone take a look into this? Maybe by running gobo inside qemu or > > > other emulator.. I don't have the time to test that right now, > > > unfortunately. > > > > > > > I tested a Glibc upgrade in qemu. Fresh 013 install. InstallPackage > > Scripts and Compile. Compile DHCPCD (we need a new bin package). > > InstallPackage Glibc. D/L and sig check fine. During SyminkProgram, > > fine until ldconfig, then get "FATAL: kernel too old" error messages. > > Now nothing works. On reboot, init dies with "FATAL: kernel too old". > > I'll upgrade kernels and check again. > > I think this can have something to do with glibc's --with-kernel > parameter. We used a very recent release, so this can be a problem. > Should be the case of adding Linux 2.6.x to Glibc's dependencies and > then creating a Linux package that presents > /System/Kernel/{Boot,Modules} + /Files/Compile/Sources/linux-2.6.x > (sanitized) inside Unmanaged? Seems to be a better way to handle the > kernel package and fix the Glibc issue, right? > I have thought about this but I don't like the idea of having everything for the kernel doubled, once in /Programs/Linux and the other at the "correct" places. I'm still trying to find a good way for this.
And I still think that the image and the source should be in separate packages anyway. -- /Jonas _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel