Path: utzoo!attcan!uunet!maverick.ksu.ksu.edu!kuhub.cc.ukans.edu!markv From: markv@kuhub.cc.ukans.edu Newsgroups: comp.sys.amiga.programmer Subject: A Question and a Thought (RemTask() and File servers) Message-ID: <28304.27a99513@kuhub.cc.ukans.edu> Date: 1 Feb 91 22:19:30 GMT Organization: University of Kansas Academic Computing Services Lines: 35 Simple question that could be answered with a quick test, but I'm in the planning stage of some software, and my Amiga is a few days away... Is it safe for a task to RemTask() itself? I have a parent that will spawn n (no limit beyond available mem) children tasks that can exit asynchronously to the parent. Assuming post task cleanup (like memory for the Task structure) will be done by mommy :-), can the children Terminate themselves, or does Mommy have to do it for them? If not, what about a real "Process" w/an empty seglist calling Exit()? Second, I've been working on an idea for a real simple Amiga only disk sharing via network. Suppose machine A wants to read Access on machine B. A dummy filesystem on machine A gets mounted. All it does is catch DOS packets, stuff it over the network (transport layer could be any protocol) to server process on machine B. Server Process on machine B then makes any needed temp buffers, sends the packets to a "real" file system, takes the reply, stuffs it back to machine A, where dummy file system fills in reply fields, copies data into orignal buffers, then sends it back to DOS/proccess. The advantage is simplicity (no duplication of existing intellegence in Amiga OS), no real need for client to know any details of the server like # of cyls etc (since this is done at the filesystem level), etc. Assuming reasonable verfication/integrity to the protocol, any problems/thoughts with this? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Mark Gooderum Only... \ Good Cheer !!! Academic Computing Services /// \___________________________ University of Kansas /// /| __ _ Bix: mgooderum \\\ /// /__| |\/| | | _ /_\ makes it Bitnet: MARKV@UKANVAX \/\/ / | | | | |__| / \ possible... Internet: markv@kuhub.cc.ukans.edu ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~