From: Todd C. Miller Date: Thu, 26 Aug 1999 09:04:45 +0000 (+0000) Subject: cosmetic cleanup X-Git-Tag: SUDO_1_6_0~102 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5d5133d4ccc98cbd3a2176cd98e30ea134eb0081;p=sudo cosmetic cleanup --- diff --git a/PORTING b/PORTING index fb6db446f..18e8e66a2 100644 --- a/PORTING +++ b/PORTING @@ -2,27 +2,27 @@ Sudo porting hints ================== Before trying to port sudo to a new architecture, please join the -sudo-workers mailing list (see the README) and ask if anyone has a -port working or in-progress. Sudo should be fairly easy to port. -Since it uses a configure script, most of the work should be done -for you. +sudo-workers mailing list (see the README file) and ask if anyone +has a port working or in-progress. Sudo should be fairly easy to +port. Since it uses a configure script, most of the work should +be done for you. If your OS is an SVR4 derivative (or some approximation thereof), it may be sufficient to tell configure you are runnng SVR4, something like: configure foo-bar-sysv4 where foo is the hardware architecture and bar is the vendor. -A possible pitfall is getdtablesize(2) which is used to get the maximum -number of open files the process can have. If an OS has the POSIX sysconf(2) -it will be used instead of getdtablesize(2). ulimit(2) or getrlimit(2) can -also be used on some OS's. If all else fails you can use the value of -NOFILE in . - -Sudo tries to clear the environment of dangerous envariables like LD_* -to prevent shared library spoofing. If you are porting sudo to a new -OS that has shared libraries you'll want to mask out the variables that -allow one to change the shared library path. See badenv_table() in -sudo.c to see how this is done for various OS's. +A possible pitfall is getdtablesize(2) which is used to get the +maximum number of open files the process can have. If an OS has +the POSIX sysconf(2) it will be used instead of getdtablesize(2). +ulimit(2) or getrlimit(2) can also be used on some OS's. If all +else fails you can use the value of NOFILE in . + +Sudo tries to clear the environment of dangerous envariables like +LD_* to prevent shared library spoofing. If you are porting sudo +to a new OS that has shared libraries you'll want to mask out the +variables that allow one to change the shared library path. See +badenv_table() in sudo.c to see how this is done for various OS's. It is possible that on a really weird system, tgetpass() may not compile. (The most common cause for this is that the "fd_set" type