|
From: Matt Z. <md...@de...> - 2003-12-21 00:47:56
|
On Sat, Dec 20, 2003 at 12:14:50PM -0500, Jeff Dike wrote: > On Fri, Dec 19, 2003 at 05:13:23PM -0800, Matt Zimmerman wrote: > > There definitely seems to be something awry here, even in skas mode. I am > > getting a lot of ENOSYS errors inside UML: > > > > /usr/lib/apt/methods/http: error while loading shared libraries: libc.so.6: cannot map zero-fill pages: Error 38 > > > > dpkg: error processing /var/cache/apt/archives/debhelper_4.0.2_all.deb (--unpack): > > failed to rmdir/unlink `/usr/share/man/man1/dh_compress.1.gz.dpkg-tmp': Function not implemented > > > > basename: write error: Function not implemented > > > > etc. > > > > Downgrading to user-mode-linux 2.4.22-6um-1 still has the problem, > > downgrading further to 2.4.22-5um-1 (the old binary) fixes it. The > > following things changed from 2.4.22-5um-1 to 2.4.22-6um-1, most of which > > were outside of UML itself: > > These changes look OK. I looked through the -5 to -6 diffs and saw nothing > that would cause stuff to start returning -ENOSYS. The only thing that > seemed remotely relevant is the unistd.h change, which fixes a bug in the > case of an error in an internally called system call. You can try reverting > that and see what happens. > > Beyond that, if you can find a system call that reproducably fails, then > just step through it, and see where the -ENOSYS comes from. This shouldn't > be too difficult. Thanks for looking at it. It's sounding more and more like the new glibc/linux-kernel-headers packages have broken UML. Maybe something is getting the host's kernel headers when it needs the ones from the UML build tree? -- - mdz |