home *** CD-ROM | disk | FTP | other *** search
- From: guy%gorodish@Sun.COM (Guy Harris)
- Date: 29 Jan 87 06:53:29 GMT
- Reply-To: guy@sun.UUCP (Guy Harris)
- Organization: Sun Microsystems, Mountain View
-
- >Increasing the length can still cause binary compatibility problems, but
- >there are (ugly) ways of dealing with binary compatibility.
-
- Not even that ugly; yes, they leave loose bits of crud floating
- around in your kernel, but most UNIX distributions these days have
- lots of this sort of loose crud. It's aesthetically unpleasant, but
- it beats the hell out of supporting aesthetically- and
- technically-unpleasant interfaces because you can't declare a flag day and
- nuking those interfaces.
-
- Most, if not all, implementations based on UNIX could just assign a
- new system call number to a new improved "uname" and leave the old
- one around with its old number for binary compatibility. You can
- write a library that contains a "uname" that uses the old call, or
- uses the new call and throws away the extra characters.
-
- Volume-Number: Volume 9, Number 37
-
-