Date: Thu, 16 Apr 1998 00:37:16 +0300 From: Antti-Pekka Liedes <apl@mail.cs.hut.fi> To: John Birrell <jb@cimlogic.com.au> Cc: hackers@FreeBSD.ORG Subject: Re: adding new syscalls, part two Message-ID: <19980416003716.44636@hutcs.cs.hut.fi> In-Reply-To: <199804152125.HAA12395@cimlogic.com.au>; from John Birrell on Thu, Apr 16, 1998 at 07:25:34AM %2B1000 References: <19980415190528.18498@hutcs.cs.hut.fi> <199804152125.HAA12395@cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 16, 1998 at 07:25:34AM +1000, John Birrell wrote: > If you are going to play with new syscalls, it is wise to bump the minor > version number of libc so that you don't hose the existing programs > by replacing a good libc with a bad one. If you've already hosed your > system by doing this and you don't have a backup of the last good libc, > you can try deleting the bad library and creating a symlink to the last > avialable shared libc. This might not work if the library is too old. > This is not a problem, I got my system working ok with an older libc. I "fixed" the libc problem by making syscalls from the original syscalls.master, ie. without my new addition, and then compiled libc. But this is quite awkward, I would like to be able to make a working libc with the new syscall added. > -- > John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ > CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 -- Antti-Pekka Liedes * apl@IRC * There's no sign of the JMT 6 B 406 * apl@iki.fi * morning coming, you've been 02150 ESPOO * +358 - 9 - 468 3121 * left on your own, like FINLAND * +358 - 40 - 5873 593 * a rainbow in the dark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980416003716.44636>