Joey Hess wrote: > Thiemo Seufer wrote: > > > - mips Installs on r4k-ip22 with 32 MB fails, it needs 36 MB until > > > swap is available, lowmem assumes 25 MB > > > > With SVN as of a few days ago, it needs ~28 MB, I haven't figured out > > the reason (nearly all of it due to increased memory usage, which was > > only partially reflected in the ps output). > > With what from svn, exactly? With the initrd from SVN (as far as the packages are there), installing unstable. tc1 needs about 17 MB Memory before swap can be activated, normal are ~10. > > > or we can make some > > > more (but still very controlled and focused) changes to fix some of the > > > other problems listed above too, which would mean starting over with a > > > tc2. > > > > I prefer this option, as it allows to sync the 2.2/2.4 kernel versions > > to 2.2.25 and 2.4.26 (except apus, ia64, powerpc for 2.4, which have > > only 2.4.25), which is basically a requirement for release. > > That is the kind of thing that can easily expose problems, and take > about a month to settle down. I used the 2.4.26 Kernel for several test installs, it is in unstable and testing for a while now, and I haven't heard of any problems which could be installer-related. The installer-visible change is that the swarm kernel has its socket module now built in. > By which time there will be a new upstream kernel.. For a release, we _have_ to sync the kernel versions, otherwise the security team will collectively get nuts. If we want to settle with an older version than newest upstream for release, we have to make sure the new kernel won't propagate to testing. Thiemo
Attachment:
signature.asc
Description: Digital signature