Subject: Re: Syscalls [was Re: Support for ACLs]
To: Greywolf <greywolf@starwolf.com>
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
List: tech-kern
Date: 03/11/2001 16:22:45
--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 10, 2001 at 09:39:47PM -0800, Greywolf wrote:
> On Sat, 10 Mar 2001, der Mouse wrote:
>=20
> # Date: Sat, 10 Mar 2001 20:41:21 -0500 (EST)
> # From: der Mouse <mouse@Rodents.Montreal.QC.CA>
> # To: tech-kern@netbsd.org
> # Subject: Syscalls [was Re: Support for ACLs]
> #
> # > We could, for example, reclaim some of our syscall space
> # > (setdomainname, uname, getdomainname have not been in use since 0.9
> # > -- about 10 years ago!  How legacy can we get?).
> #
> # Why bother?  Are syscall numbers a scarce resource?
>=20
> No, but it's cruft, along with stat43 and stat12.
>=20
> I don't even support COMPAT_14, but that's probably a little extreme for
> most.
>=20
> Is there seriously stuff out there for which a binary exists without sour=
ce
> that needs to keep backwards binary compatibility?

some commercial programs, yes. (I'm aware of an architectural CAD program).

Regards,
	-is

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBOquYQTCn4om+4LhpAQEIbAf/SJGMROLZTLqX20rvKFic/8ubQD9fw269
TLIgw8cJP8ZHfNrrMSi/jQ04NtKffMM53qLjckAd3f0EEKDaOA2CBbWN+dgUCQlu
pXa54RH9Eg4FKWu/+5GNaB9KF0Z5j1q/TXcB8zjnT2qe7WJv9Xpr8IY2H3Cf30pH
XfL1zAQ9ESZxAS87wQImjEc/ys+bDvmwfLZzVwjw+Jt0hfjmAqzvbcaqrXsnHHB7
CY8gVNPx/WQLnMFJJOOSTTBiMDx3hT8suySObncbKU21ix9u7KoMsVRX1w6tdeAy
EY/kOjJ7b6r7E4FqD5dCe33IapUFQxYglsAIhDNTX6WYzXahaGR/8g==
=PfD8
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--