Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!daffy!uwvax!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!news.sprintlink.net!vodka.intele.net!usenet From: Barnacle Wes <wes@intele.net> Newsgroups: comp.unix.bsd.misc,comp.unix.freebsd.misc Subject: Re: FreeBSD Date: 5 Jul 1995 04:31:57 GMT Organization: The briney, briney deep Lines: 47 Message-ID: <3td4ju$941@vodka.intele.net> References: <3tao55$9m2@linux2.dlsu.edu.ph> NNTP-Posting-Host: slcmodem1-p1-2.intele.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 1.1N (X11; I; BSD/386 uname failed) To: gavin@linux1.dlsu.edu.ph X-URL: news:3tao55$9m2@linux2.dlsu.edu.ph gavin@linux1.dlsu.edu.ph (Gavin Lim) wrote: >I have a question and I don't know if this is the right place to post it to. >Anyway, does FreeBSD 2.0 have the same design as 4.3BSD? Close. FreeBSD 2.x is based on 4.4BSD-Lite. >We are trying to build a PROCESS MIGRATION facility, and currently, we're >trying to build it under Linux. However, Linux does not have any design >documents -- not one! We're thinking of shifting to FreeBSD if it has >design documents. Boy, are you going to get pounded by Linux Community for this one! ;^) I've seen lots of Linux user's guides on the shelves of bookstores, but not really anything for the kernel hacker, other than RTFS. >We also have the book entitled "The Design and Implementation of 4.3 BSD >UNIX Operating System" by Leffler, et al. Are the design details stated >there applicable to FreeBSD 2.0? Only sort of. The process model changed quite a bit between 4.3 and 4.4, as did the memory management. The FreeBSD team has been hacking away at the memory management and buffer cache management, and I assume they have moved even farther from what is documented in Leffler et al. The basic strategies, at least as of 2.0, are still similar. I'm not sure exactly what you mean by process migration facility -- the ability to move a process from one system to another? With some sort of checkpoint/restart capability? If so, you may want to look into the procfs (memory process virtual files) in FreeBSD 2.0; they provide enough control over a process for a debugger, which means they may provide enough to be able to checkpoint and restart a job. You may run into trouble with allocated memory blocks, but everything else should be straightforward. Good luck. I've cross-posted this to comp.unix.freebsd.misc, which is probably a more appropriate forum; please direct all followup to that newsgroup. >We need a lot of help guys -- and fast! Hope we can get replies soon! I answered as soon as I read it! Honest! ;^) -- Wes Peters | Yes I am a pirate, two hundred years too late Softweyr | The cannons don't thunder, there's nothing to plunder Consulting | I'm an over forty victim of fate... wes@intele.net | Jimmy Buffet