On Fri, Jun 11, 2004 at 01:05:21AM -0400, Kyle McMartin wrote: > Everything went swimmingly. When I rebooted to finish the install, I had > to manually set the kernfile variable to /vmlinuz-2.4.25-netwinder. A > better solution would be for the installer to detect that it's installing > to a seperate /boot partition and to add a /boot/vmlinuz symlink instead of > an /vmlinuz one.
If this applies to arm in general, then we could do this: Index: rootskel/debian/templates-arch =================================================================== --- rootskel/debian/templates-arch (revision 16700) +++ rootskel/debian/templates-arch (working copy) @@ -63,6 +63,7 @@ Default[sparc]: true Default[hppa]: true Default[powerpc]: true +Default[arm]: true Description: kernel needs a link in /boot/ (linux only) Setting this to true makes base-installer include 'link_in_boot=yes' in /etc/kernel-img.conf. If not, it'll be more complicated. > As well, when I finished the base install (opting out of using tasksel or > dselect), I was unable to install ssh. It installed to the point where it > tried to generate keys, and then died with Illegal instruction. I suspect > this is a hardware problem with my netwinder, however. No, this has been reported elsewhere; I believe it's currently considered to be either a toolchain bug or a bug with libssl using incorrect optimizations, but I don't know the details. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
