Path: utzoo!attcan!uunet!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!think!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!voder!pyramid!cbmvax!amix!ag From: ag@amix.commodore.com (Keith Gabryelski) Newsgroups: comp.sys.amiga Subject: Re: More random Unix topics Message-ID: <299@amix.commodore.com> Date: 14 Mar 90 12:53:28 GMT References: <296@amix.commodore.com> Reply-To: ag@amix.commodore.com (Keith Gabryelski) Organization: Commodore Amix Development Lines: 37 In article mwm@raven.pa.dec.com (Mike Meyer) writes: >In article <296@amix.commodore.com> ag@amix.commodore.com (Keith Gabryelski) writes: > >>Infact, I just took a current system and removed all networking/man >>pages and things and I ended up with 27meg used. That doesn't seem to >>bad since it was a fully operation R4 system (minus any trace of a >>network). > >That's nice to know. Now, put the man pages back - doing development >sans online man pages isn't a win. Hard copy is acceptable, and you can put them back on if you want. >If you've only got one machine, you don't really need the networking >stuff for development. Unless you're developing networking code, in >which case you also desperately need another machine. Of course, with >another machine and a network, you can use NFS to share non-critical >things so the disk space growth isn't linear. Networking was removed from my example above. Again, the individual parts I removed can be put back. >Which brings up a really strange point - at DEC, we use CI (think of >it as super-SCSI) as an IP pathway. Will Amix allow running IP over a >SCSI net so that those operating on a shoestring budget can get >networking without having to buy the ethernet hardware? Hopefully our price will fit a shoestring budget. Hopefully SLIP will be available. As for you suggestiong, I haven't looked into it. It sounds interesting, though. Pax, Keith -- ag@amix.commodore.com Keith Gabryelski ...!cbmvax!amix!ag