From: Jurij Smakov <jurij@xxxxxxxxx> Date: Sun, 15 Jan 2012 14:09:39 +0000 > Another option would be to start linking against libc to work around > this problem, but I don't know why it was not done in the first > place, some size constraints perhaps? Not only size, but you then have to audit every symbol libext2fs uses in libc to make sure the code in libc doesn't directly or indirectly do system calls or other things we can't support in the context of SILO's execution environment. That's why I suggest we just keep adding whatever routines libext2fs wants into SILO. That way we can audit what it wants, explicitly, and know that our implementation won't have unwanted dependencies upon executing in a real userland environment. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
