On Tue Nov 23 2010 at 18:41:21 +0000, David Laight wrote: > On Tue, Nov 23, 2010 at 12:19:36AM +0200, Antti Kantee wrote: > > > > > > Surely it would be more appropriate to make thye rump kernel directly > > > forward some paths to the real kernel? > > > > Can you explain how that could work? > > First thoughts are something like the way /../ is used to 'escape' > from the emulation root. > But maybe just mount the real filesystem within the rump kernel?
The client may be on a different machine, so you'd have to, if not invent a completely new protocol, at least include server side functionality on the client and add some weird pingpong/adjust logic into the server. > Making something work well enough to copy files is probably not that hard! Adding a ton of special case code to copy files is extremely poor design! Doubly so since the only reason is because you don't happen to like some flags which bring 0 cost when not used. If you don't like them, don't use them. Unless someone can actually name a *problem*, move along.