Currently, we have two filesystems: one in the kernel (in RAM), which we load programs from, and one in userspace. Eventually, only the latter should remain (it should also stop sucking, but that's another task entirely). This is in small part infrastructure bitchwork (some function for getting the programs in the userspace fs), but you also have to deal with the problem of exec. The lazy approach would be to have the syscall exec a buffer or something. The more correct approach is some sort of exec in userspace.
Currently, we have two filesystems: one in the kernel (in RAM), which we load programs from, and one in userspace. Eventually, only the latter should remain (it should also stop sucking, but that's another task entirely). This is in small part infrastructure bitchwork (some function for getting the programs in the userspace fs), but you also have to deal with the problem of exec. The lazy approach would be to have the syscall exec a buffer or something. The more correct approach is some sort of exec in userspace.