jca@pnet01.cts.com (John C. Archambeau) (04/08/90)
coxj@tusun2.knet.utulsa.edu (Jason Cox [UCRIG]) writes: >Has anyone attempted a TCP/IP implementation for MinixPC? There's >an internet package for the PC (DOS?) by Phil Karn, KA9Q; is there >any hope (or has it been done) in converting this to MinixPC? I >understand that Karn's package includes SLIP, so even those of you >interested in IP for MinixST might look into this package (ftp from >bugs.nosc.mil). If you have heard of a MinixPC version, let me know. > >Also concerning the MinixPC, does anyone have uucp that will work >with version 1.5.5? How about News software? There are a few such >version for DOS; I'm curious if anyone has had time to port such >necesities to Minix or has everyone been busy upgrading to 1.5.x? :-) > >I realize that without a lot of work, the PC (specifically the '286) >will never have a realistic version of Minix [though it would be a >challenge to break the 64k barrier]. Because of this, would it be >save to assume that Minix will no longer support the PC (the '386 >shouldn't be considered a PC since it's price is far from personal! :-) >except at the 32-bit level? By this, is v1.5.5 the last version >available for lowly undergrads without the funds for real machines? >Anyway, something I was curious about.. Perhaps PC users should >consider starting a new group in support of upgrading MinixPC. Just >a thought.. You could always get a 386SX. The price of a 386SX motherboard is about as much as a high speed 286 board. Hell, I paid less for my 386SX w/4 Mb RAM than I did for my 16 MHz 286 w/1 Mb RAM. I don't think KA9Q will port because of the memory model of the compiler. The first thing one should try is try making it run in a small memory model (or split I&D) and if it works then try cross compiling it to Minix or running Minix's CC through it. // JCA /* **--------------------------------------------------------------------------* ** Flames : /dev/null | My opinions are exactly that, ** ARPANET : crash!pnet01!jca@nosc.mil | mine. Bill Gates couldn't buy ** INTERNET: jca@pnet01.cts.com | it, but he could rent it. :) ** UUCP : {nosc ucsd hplabs!hd-sdd}!crash!pnet01!jca **--------------------------------------------------------------------------* */
jon@wilbur.uucp (Jonathan C. Broome) (04/09/90)
In article <2137@crash.cts.com> jca@pnet01.cts.com (John C. Archambeau) writes: : coxj@tusun2.knet.utulsa.edu (Jason Cox [UCRIG]) writes: : >Has anyone attempted a TCP/IP implementation for MinixPC? [ stuff ] : I don't think KA9Q will port because of the memory model of the compiler. The : first thing one should try is try making it run in a small memory model (or : split I&D) and if it works then try cross compiling it to Minix or running : Minix's CC through it. Well, it shouldn't be totally impossible to do -- my '286 system is running a slightly modified Minix 1.2+ (I know, ancient!) that just happens to boot (diskless) using RARP & TFTP and accesses all of its filesystems via a WD8003E ethernet card using a UDP-based filesystem protocol. It doesn't do TCP (yet), but it does all the rest (IP, ICMP, UDP, ARP/RARP, etc.) The kernel is 64,928 bytes large, with both XT & AT wini drivers, a mouse driver, and virtual consoles crammed in for good measure. (Hence the delay in updating to v1.5.5) ---Jonathan Broome jon@wilbur.uucp ...!uunet!ism780c!wilbur!jon
hbetel@watserv1.waterloo.edu (Heather) (04/10/90)
>Well, it shouldn't be totally impossible to do -- my '286 system is running >a slightly modified Minix 1.2+ (I know, ancient!) that just happens to boot >(diskless) using RARP & TFTP and accesses all of its filesystems via a >WD8003E ethernet card using a UDP-based filesystem protocol. It doesn't do >TCP (yet), but it does all the rest (IP, ICMP, UDP, ARP/RARP, etc.) How did you do all this? Did you use someone else's code, or did you start from scratch. Also, are you considering posting it?[ That's the REAL question]
jca@pnet01.cts.com (John C. Archambeau) (04/10/90)
jon@wilbur.uucp (Jonathan C. Broome) writes: >In article <2137@crash.cts.com> jca@pnet01.cts.com (John C. Archambeau) writes: >: coxj@tusun2.knet.utulsa.edu (Jason Cox [UCRIG]) writes: >: >Has anyone attempted a TCP/IP implementation for MinixPC? >[ stuff ] >: I don't think KA9Q will port because of the memory model of the compiler. The >: first thing one should try is try making it run in a small memory model (or >: split I&D) and if it works then try cross compiling it to Minix or running >: Minix's CC through it. > > >Well, it shouldn't be totally impossible to do -- my '286 system is running >a slightly modified Minix 1.2+ (I know, ancient!) that just happens to boot >(diskless) using RARP & TFTP and accesses all of its filesystems via a >WD8003E ethernet card using a UDP-based filesystem protocol. It doesn't do >TCP (yet), but it does all the rest (IP, ICMP, UDP, ARP/RARP, etc.) The >kernel is 64,928 bytes large, with both XT & AT wini drivers, a mouse driver, >and virtual consoles crammed in for good measure. (Hence the delay in >updating to v1.5.5) A lot of us would like to know exactly how you did that... (Hint, hint...) // JCA /* **--------------------------------------------------------------------------* ** Flames : /dev/null | My opinions are exactly that, ** ARPANET : crash!pnet01!jca@nosc.mil | mine. Bill Gates couldn't buy ** INTERNET: jca@pnet01.cts.com | it, but he could rent it. :) ** UUCP : {nosc ucsd hplabs!hd-sdd}!crash!pnet01!jca **--------------------------------------------------------------------------* */
esposito%dipisa.DI.UNIPI.IT@cunyvm.cuny.edu (04/11/90)
This message is empty.
jpc@fctunl.rccn.pt (Jose Pina Coelho) (04/13/90)
In article <1990Apr09.083238.23610@wilbur.uucp> jon@wilbur.uucp (Jonathan C. Broome) writes: > > Well, it shouldn't be totally impossible to do -- my '286 system is running > a slightly modified Minix 1.2+ (I know, ancient!) that just happens to boot > (diskless) using RARP & TFTP and accesses all of its filesystems via a > WD8003E ethernet card using a UDP-based filesystem protocol. It doesn't do > TCP (yet), but it does all the rest (IP, ICMP, UDP, ARP/RARP, etc.) The > kernel is 64,928 bytes large, with both XT & AT wini drivers, a mouse driver, > and virtual consoles crammed in for good measure. (Hence the delay in > updating to v1.5.5) I am interested in the mouse driver and UDP, I also suspect that some of us would like to know that. I belive a reasonable number number of minixers would like to see that. To those who still have 1.2 you could post the diff's. To the rest of us, looking at the diff's would be better than nothing. To the future, if one of the Implementors gets some time to kill, maybe we will see TCP/UDP/IP et al. in version 1.5.7 or 2.0 ( Am I day dreaming or what ? ) -- ---- Jose Pina Coelho | BITNET/Internet: jpc@fctunl.rccn.pt Rua Jau N 1, 2 Dto | UUCP: jpc@unl.uucp 1300 Lisboa, PORTUGAL | ARPA: jpc%hara.fctunl.rccn.pt@mitvma.mit.edu Home phone: (+351) (1) 640767