Re: vfork specs

Roland McGrath (roland@frob.com)
Fri, 15 Jan 1999 15:22:29 -0500

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Charles Cazabon: "Re: *** next draft - press release ***"
Previous message: Riccardo Facchetti: "Re: *** next draft - press release ***"

All true vfork implementations in all systems have had these restrictions,
whether cleared stated by their documentation or not. If you think about
it, the issue is inherent in the memory sharing behavior vfork is specified
to have.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Charles Cazabon: "Re: *** next draft - press release ***"
Previous message: Riccardo Facchetti: "Re: *** next draft - press release ***"