Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.

On Fri, 17 Mar 2006, Michael Kerrisk wrote:
> > 
> > My personal opinion is that having a different set of flags is more 
> > confusing 
> 
> How is it confusing?  And who is it confusing for?

It's confusing because
 - it's just more flags to keep track of
 - it's all the same issues that clone() has
 - it's an opportunity for future incoherence

> It will potentially require kernel developers to think for just 
> a moment about what is going on.  But why care about them -- 
> they don't have to *use* this interface; userland programmers do.

All the confusion is equally a userland issue, don't try to just enforce 
your own opinions as somehow being "facts" by repeating them over and over 
again.

			Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
    • From: "Michael Kerrisk" <[email protected]>

• References:
  • Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
    • From: "Michael Kerrisk" <[email protected]>

• Prev by Date: Re: [2.6.16-rc6-m1 PATCH] Connector: Filesystem Events Connector try 2
• Next by Date: [PATCH] i386: run BIOS PCI detection before direct
• Previous by thread: Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
• Next by thread: Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]