1 |
On 10/14/2013 12:34 PM, William Hubbs wrote: |
2 |
> On Mon, Oct 14, 2013 at 10:46:38AM -0400, Richard Yao wrote: |
3 |
>> On 10/14/2013 10:11 AM, Rich Freeman wrote: |
4 |
>>> On Mon, Oct 14, 2013 at 9:52 AM, Richard Yao <ryao@g.o> wrote: |
5 |
>>>> The Linux kernel also supports far more architectures than we do. That does not mean that we must support them too. |
6 |
>>>> |
7 |
>>>> With that said, how does changing things benefit/affect users, especially non-systemd users? |
8 |
>>> |
9 |
>>> Better support for namespaces, for one. |
10 |
>>> |
11 |
>>> If this is actually going to actually break something, by all means |
12 |
>>> speak up. Otherwise this really comes across as the whole |
13 |
>>> I-DONT-LIKE-CHANGE argument. I get it. By all means don't make your |
14 |
>>> /etc/mtab a symlink, and if down the road something doesn't work as a |
15 |
>>> result feel free to fork it unless you can convince somebody else to |
16 |
>>> make it work. So far the only concrete issues that have been raised |
17 |
>>> seem minor - pertaining to NFS and PAM (both having solutions |
18 |
>>> available). |
19 |
>>> |
20 |
>>> If this causes trouble for the FreeBSD folks I'm interested in what |
21 |
>>> kinds of compromises can be reached. I think a challenge is that |
22 |
>>> Linux and FreeBSD seem to be very slowly diverging - for software that |
23 |
>>> lives near the kernel/userspace boundary that could make things |
24 |
>>> interesting. There doesn't seem to be much desire to limit Linux |
25 |
>>> distros to purely POSIX behavior. |
26 |
> |
27 |
> As I said earlier in the thread, the planned baselayout change will only |
28 |
> affect Linux. |
29 |
> |
30 |
>> My main concern is that some of the configure flags being proposed could |
31 |
>> make packages that worked on Gentoo FreeBSD stop working there. I am not |
32 |
>> making changes, but I think that there should be some benefit and that |
33 |
>> care should be taken not to break things for everyone else. |
34 |
> |
35 |
> Richard, the packages we are discussing (nilfs-utils and nfs-utils) |
36 |
> are linux-specific, so there is nothing to worry about on the *bsd side |
37 |
> for them. |
38 |
|
39 |
That is good to hear. There were a few situations int he past where |
40 |
changes were made for Gentoo Linux that broke Gentoo FreeBSD, so I |
41 |
wanted to be certain that we were not going to have a repeat of that here. |
42 |
|
43 |
>> That being said, mgorny said that this adds support for mount |
44 |
>> namespaces, but I have yet to hear an explanation of what that actually |
45 |
>> means. What are the use cases? |
46 |
> |
47 |
> There has been a lot written on this; you might want to google |
48 |
> "per-process namespaces". |
49 |
|
50 |
If this merits discussion on the list, then it should merit answers for |
51 |
these questions: |
52 |
|
53 |
1. What are mount namespaces? How do they integrate with the kernel? |
54 |
2. What does systemd do with them? What does systemd's use of them |
55 |
provide to users? |
56 |
|
57 |
Saying to google "per-process namespaces" does not really answer that. |
58 |
Per-process namespaces provide a means to isolate processes into |
59 |
containers that they have their own pid numbers and can neither nor |
60 |
interact with processes outside of the container via traditional IPC |
61 |
mechanisms such as signals. It is similar to the concept of FreeBSD |
62 |
jails. That does not tell me what a "mount namespace is" or why systemd |
63 |
has anything to do with it. |