LWN: Comments on "Namespace file descriptors" https://lwn.net/Articles/407495/ This is a special feed containing comments posted to the individual LWN article titled "Namespace file descriptors". en-us Thu, 16 Oct 2025 19:23:10 +0000 Thu, 16 Oct 2025 19:23:10 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Namespace file descriptors https://lwn.net/Articles/461347/ https://lwn.net/Articles/461347/ uriel <div class="FormattedComment"> Plan 9 always used a file system interface to its network stack, and you could mount multiple ip stacks, and remote network stacks, and 'virtual network stacks' (eg., providing tunneling to a remote non-plan9 system using sshnet).<br> <p> See:<br> <p> <a rel="nofollow" href="http://doc.cat-v.org/plan_9/4th_edition/papers/net/">http://doc.cat-v.org/plan_9/4th_edition/papers/net/</a><br> <a rel="nofollow" href="http://man.cat-v.org/plan_9/3/ip">http://man.cat-v.org/plan_9/3/ip</a><br> </div> Sun, 02 Oct 2011 16:20:46 +0000 Namespace file descriptors https://lwn.net/Articles/453132/ https://lwn.net/Articles/453132/ chloe_zen <div class="FormattedComment"> How can it be race-free?<br> </div> Wed, 27 Jul 2011 19:15:34 +0000 Namespace file descriptors https://lwn.net/Articles/453094/ https://lwn.net/Articles/453094/ renzo <div class="FormattedComment"> I think it would be simpler for programmers to have network stacks on the file system as special files.<br> <p> I proposed this approach two years ago at FOSDEM. msocket is similar<br> to socketat but it has a pathname instead of a file descriptor as its<br> first argument.<br> If the network stacks were special files, sysadm may provide more than one<br> stack to the users, each application can decide which stack to use.<br> A "default" stack can be defined for backwards compatibility: the "socket" syscall uses the default stack. <br> <p> for details see: <a rel="nofollow" href="http://wiki.virtualsquare.org/wiki/index.php/Multi_stack_support_for_Berkeley_Sockets">http://wiki.virtualsquare.org/wiki/index.php/Multi_stack_...</a><br> <p> and: <a rel="nofollow" href="http://archive.fosdem.org/2009/schedule/events/ipn_msockets">http://archive.fosdem.org/2009/schedule/events/ipn_msockets</a><br> <p> renzo<br> </div> Wed, 27 Jul 2011 16:31:15 +0000 Namespace file descriptors https://lwn.net/Articles/452575/ https://lwn.net/Articles/452575/ razb <div class="FormattedComment"> can you share an example with a code ?<br> </div> Fri, 22 Jul 2011 12:26:44 +0000 Namespace file descriptors https://lwn.net/Articles/452539/ https://lwn.net/Articles/452539/ ebiederm <div class="FormattedComment"> There were some small changes between when this article was written and when socketat was merged.<br> <p> - socketat was dropped from the patchset. It can be implemented race free in userspace and there are not yet enough userspace applications to care.<br> <p> - setns had it's aguments slightly changes and swapped. setns is now<br> int setns(int fd, int nstype);<br> Where nstype is a clone flag, instead of the original overly clever<br> ascii encoded in an integer without using a define.<br> <p> Eric<br> </div> Fri, 22 Jul 2011 04:49:44 +0000