Return to BSD News archive
Xref: sserve comp.unix.sys5.r4:8946 comp.unix.pc-clone.32bit:7903 comp.unix.misc:15289 comp.unix.bsd:15746 comp.sys.powerpc:30730 comp.sys.intel:27159 comp.os.misc:3597 comp.os.linux.misc:32448 comp.os.linux.development:21797 comp.os.386bsd.misc:4565 comp.os.386bsd.development:2917 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!bubba.ucc.okstate.edu!newsfeed.ksu.ksu.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!news.sprintlink.net!internex.net!usenet From: muzaffer@smixedsignal.com Newsgroups: comp.unix.sys5.r4,comp.unix.pc-clone.32bit,comp.unix.misc,comp.unix.bsd,comp.sys.powerpc,comp.sys.intel,comp.os.misc,comp.os.linux.misc,comp.os.linux.development,comp.os.386bsd.misc,comp.os.386bsd.development Subject: Re: Interested in PowerPC for Linux / FreeBSD / NetBSD? Date: Sat, 24 Dec 94 18:56:21 PDT Organization: InterNex Information Services, Inc. Lines: 28 Message-ID: <NEWTNews.3137.788324467.muzaffer@omer1.smixedsignal.com> References: <3dh116$frs@hustle.rahul.net> NNTP-Posting-Host: 199.2.10.75 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Newsreader: NEWTNews & Chameleon -- TCP/IP for MS Windows from NetManage In article <3dh116$frs@hustle.rahul.net>, <dwelch@rahul.net> writes: > I think it's an issue of whether you like how Winblows multitasks or > how Unix multtasks. I think most of us Unix heads have decided we > prefer Unix multitasking over Windog or MacOS multitasking. In Unix > (generally), you can put a process in the background and expect a > reasonable amount of CPU time to be given to the background process. > In Winblows or MacOS, you can't expect this to be the case. > > Case in point -- I was running UUCP under MacOS up until recently when > I finally got NetBSD up and running reasonably. Whenever I tried to do > anything while UUCP was transferring files, UUCP transfers would slow > down or stop. > I think you are confusing the OSs here. Windows 3.x and MacOS are cooperative multitasking OSes and they have the problem you mention. But Windows NT is a different beast altogether. Windows NT supports the preemptive multitasking which we came to like and you can do background processes under NT as easily and nicely as Unix. But there is a tiny catch. Under NT workstation, the default scheduling prefers to give the foreground processes much more time to run than Unix does. To change this default, go into control panel, system and click on tasking button and choose the option which suits you better. I think the second option is closer to most unix implementations. Muzaffer