Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!swrinde!cs.utexas.edu!devnull!rgp From: rgp@mpd.tandem.com (Ramon Pantin) Newsgroups: comp.unix.bsd Subject: Re: ulimit() Message-ID: <2272@devnull.mpd.tandem.com> Date: 20 Aug 92 05:25:00 GMT References: <1992Aug13.091855.28615@rz.uni-karlsruhe.de> <10955@platypus.uofs.uofs.edu> Sender: news@devnull.mpd.tandem.com Organization: Tandem Computers, Micro-Products Division Lines: 24 In article <10955@platypus.uofs.uofs.edu> bill@platypus.uofs.edu writes: >In article <1992Aug13.091855.28615@rz.uni-karlsruhe.de>, walter@insu1.etec.uni-karlsruhe.de (Reiner Walter) writes: >|> I want to port the system call ulimit() from INTERACTIVE to BSD/386. > >Why??? >Most people stuck on SYSV spend most of their waking hours trying to >find a way to do away with it. What possible use could you have for >something as limiting (or dare I say brain-dead) as ulimit?? > >bill I agree, brain damaged. Just as brain damaged as BSD's setrlimit(2), readv(2), writev(2), job control, and all the other useless stuff. Just as brain damaged as the sig*(2), priocntl(2) and all the other madness in SVR4 or all the efforts of standardizing the heck out of unimplemented stuff in POSIX, ANSI-C++, X/Open, OSI, ... Not to mention editors and window managers that require megabytes just to be able to crawl (they never seem to "run"). It would seem that nobody learned anything from UNIX (except for the Plan 9 folks, of course). Where did the thrive for simplicity, coherency and minimalism go ? Ramon Pantin