As one who put himself into the shoes of a vagabond, because I was commanded to, I doubt I'll ever enjoy travelling with company: each town we pass, someone is sure to say, 'wouldn't it be nice if we lived here?'
A vagabond learns what towns and cities are about: the difficulty is to get inside. We need a reliable go-between.
Trusty Kernel has trusty between-goers.
Thus we may also see processes as vagabonds: vagabonds who would be happy for there to be one world bank; people who buy property not to make money of them, nor to make them homes.
Naturally this sets them apart from regular home-owners. It's always better to take an existing system and do your work within it, than to try to get everyone together to explain why they need to change their ways. Thus regular home-owners will see vagabonds who buy property as up to no good. Thus we see the importance of freedom.
A vagabond knows not to go into a town himself, for he might get lost and then find himself being herded into close quarters with those who want to stop people from doing things which make them uncomfortable. People who don't know how to mind their own business, in other words.
Our vagabonds simply need to say a word to a stranger, in passing, and a go-between appears. These between-goers arrange for any property that the vagabond requires. It does make sense to require that a vagabond only makes one request to a between-goer at once; this way such requests may be called syscalls, with the slight difference that the process may continue execution so long as it does not make a second syscall until the signal for the first is received.
Finally, while a vagabond may choose to sell all its property before exiting--which may be done in a number of ways, obviously--it does seem that this is a matter of preference, for a bank's responsibility is to keep track of a man's estate.
In other words, what is a memory leak?