home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.transputer
- Path: sparky!uunet!mcsun!sun4nl!dutrun!dutrun2!dutncp8!telnet
- From: rob@pact.nl (Rob Kurver)
- Subject: Re: Format of .btl files
- Message-ID: <telnet.727717819@dutncp8>
- Sender: news@dutrun2.tudelft.nl (UseNet News System)
- Nntp-Posting-Host: dutncp8.tn.tudelft.nl
- Organization: PACT, Delft, The Netherlands
- References: <1993Jan22.114632.24686@dcs.warwick.ac.uk>
- Date: Fri, 22 Jan 1993 15:50:19 GMT
- Lines: 23
-
- In <1993Jan22.114632.24686@dcs.warwick.ac.uk> markhill@dcs.warwick.ac.uk (M Hill) writes:
-
- >When the iserver boots a transputer network with a .btl file, is the
- >iserver just sequentially picking up bytes from the file and throwing
- >them at the C011? This would imply that the .btl file had all the necessary
- >bootstrap code for the whole network inside it, in addition to the
- >program code that will eventually run on each processor on the network.
-
- Indeed. The bootable file (.btl for Inmos, .run for PACT) contains the
- prebooter, main booter, network booter, system processes, user processes,
- network configuration information, and whatever else is needed to start
- the program. It is fully selfcontained - the iserver or pserver merely
- dumps the file to the link interface, without any interpretation.
-
- >Mark
-
- Rob
-
- --
- PACT Rob Kurver
- Foulkeslaan 87 rob@pact.nl
- 2625 RB Delft ph: +31 15 616864
- The Netherlands fax: +31 15 610032
-