On 12/18, Neil Horman wrote: > > On Tue, Dec 18, 2012 at 09:06:04PM +0100, Oleg Nesterov wrote: > > > Perhaps its best just to restrict this patch to adjusting the root fs > > > location > > > for the chroot case. > > > > Probably... at least for the start. > > > > BTW. Of course this is subjective, but personally I think that "||" > > looks strange. Perhaps it would be better to add something like > > --croot argument? > > > The || is ambiguous with its simmilarity to a shell 'or' command,
Ah, I didn't mean this. I meant, this is not flexible. We can implement --croot, then we can (may be) add --switch_ns. If you use "||" now for chroot, what will you do for switch_ns? > but I don't > think the --croot argument is much better on that front, as that then becomes > ambiguous with arguments supplied to the pipe reader directly. Not sure I understand... why? > The token should > be leading the pipe_reader string in core_pattern to indicate a change in > environment independent of the executable path. Do you mean that || at the front is more "visible" ? True, but I am not sure this is that important. But I won't insist. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/