On Fri, Apr 16, 2004 at 11:19:53PM +0200, Pip Oomen wrote: > Sven Luther wrote: > > >>2. Config network (DHCP) succeeds, but fails to create proper > >>/etc/resolv.conf. > >This is fixed now. > > Which package did this bug originate from? Bug#? Since I am now building > my own installer it would be nice to double-check wether I am using the > fixed version and if the fix actually works ;)
I suppose the version in unstable solves this problem. > >>3. Partition for yaboot was created manually. After that, partioning of > >>disk (singe filesystem) works fine. This requires a recent build since > >>the IDE driver is not compiled into the kernel for beta3. > >Yep. daily builds fixed that. > > As we discussed earlier. Thanks for fixing that one. No problem > >>4. For base system install it is necessary to choose 'unstable' since > >>the necessary kernel is not available in testing (yet). Also running > >>discover from testing makes the machine hang while discover v2 > >>(unstable) seems to work fine. > >Mmm, maybe we should fast track 2.4.25-8 into testing. It contains both > >d-i fixes and security fixes, so this would be a good idea. > > That does not solve the problem with discover vs. discover2, but I guess > I can override just that one (post-install) now that i know about it. ok. > >>5. Automatic installation of yaboot is reported to fail. However, > >>manually running yabootconfig from a chroot does install the bootloader > >>succesfully: > >Yep, this is being worked on. > > That is the partman-newworld stuff? No, probably a broken yuaboot-installer, not sure though. > >>Generally, the first stage installation looks very promising, but seems > >>to lack robustness when things don't go as planned. The second stage > >>installation looks very nice. > >Yep, in general d-i is not very robust, but once everything is fixed, it > >should not fail. > > I am counting on that. Very aware that this is a work-in-progress. Hehe. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
