Talk:Linux namespaces

This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Linux Low‑importance This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LinuxWikipedia:WikiProject LinuxTemplate:WikiProject LinuxLinux articles Low This article has been rated as Low-importance on the project's importance scale. Computing: Software / Free and open-source software Low‑importance This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles Low This article has been rated as Low-importance on the project's importance scale. This article is supported by WikiProject Software (assessed as Low-importance). This article is supported by Free and open-source software (assessed as Low-importance).

Roxxik (talk) 12:08, 24 March 2016 (UTC)[reply]

This is my first major wikipedia contribution, having only done some minor rewordings before. I'd appreciate any help and advices on the structure or wording of this article.

This is a work in progress, especially the namespace kinds paragraph needs to be extended a lot to explain the various kinds better. Sentences need to be written from there points...

The cgroup ns controller should be mentioned somewhere.

We read in Implementation details

The inode number pointed to by this symlink is the same for each process in this namespace.

This is unclear as, if I understand correctly, a symlink does not point to an inode, unlike a hardlink. It is just an arbitrary text which may or may not meaningfully refer to a file.

That being said, the symlink text does indeed contain a numeric id, but is it an inode number (in which case, on what filesystem?)

# ls -l /proc/1974/ns/
total 0
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 cgroup -> 'cgroup:[4026531835]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 ipc -> 'ipc:[4026531839]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 mnt -> 'mnt:[4026531841]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 net -> 'net:[4026531840]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 pid -> 'pid:[4026531836]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 pid_for_children -> 'pid:[4026531836]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 time -> 'time:[4026531834]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 time_for_children -> 'time:[4026531834]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 user -> 'user:[4026531837]'
lrwxrwxrwx. 1 foo foo 0 Jan 22 13:04 uts -> 'uts:[4026531838]'

There is a T101 in your kitchen (talk) — Preceding undated comment added 12:25, 22 January 2024 (UTC)[reply]