Network Stack Cloning / Virtualization Extensions
HellRazr writes "From the FreeBSD hackers mailing list:
'at http://www.tel.fer.hr/zec/vimage/ you can find a set of patches
against 4.8-RELEASE kernel that provide support for network stack
cloning. The patched kernel allows multiple fully independent network
stack instances to simultaneously coexist within a single OS kernel,
providing a foundation for supporting diverse new applications.' We can sure have fun with this..."
It's cloning itself.
Why not fork?
I've heard about the idea and development of the vimage patch and this is a great news, that it's finally done and fully functional. Some of those ideas are not really new, as anyone who knows OS/390 could tell you, but it's really great they can now be used in FreeBSD systems.
For those of you, who know that I'm involved in building honeynets, it won't be a surprise, that I am really (by which I mean really) looking forward to use those new features in my future honeypots, firewalls and other security-related projects.
Actually, those features seem to be created just exactly to be used for deploying virtual honeynets. Just imagine what you can do with VMware, vimage-FreeBSD and UML all running on the same machine!
Great work, Marko.
Karma: Positive (probably because of superiour intellect)
seems like plenty of ideas from plan 9 are backporting their way to the unix-likes.
:
People, if you want plan 9 you know where to find it
http://plan9.bell-labs.com/plan9
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
It is interesting to see monolithical kernel systems trying to implement features which are basic stuff in multiserver microkernel operating systems.
UNET ran almost entirely in user space. All that went into the kernel were device drivers for the network devices and a psuedo-device to allow interprocess communication to the network process. This made modification and debugging much easier. You could kill and restart the network process without rebooting the system.
Twenty years later, someone has reinvented this approach.
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.