Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!overload!dillon From: dillon@overload.UUCP (Matthew Dillon) Newsgroups: comp.sys.amiga.tech Subject: Re: Using Matt's UUCP on local Amiga net Message-ID: Date: 10 Jul 90 03:31:32 GMT References: <90Jun28.102517edt.2765@ois.db.toronto.edu> <90Jul6.144814edt.2682@ois.db.toronto.edu> Lines: 41 >In article <90Jul6.144814edt.2682@ois.db.toronto.edu> fche@db.toronto.edu ("Frank Ch. Eigler") writes: > >I would like to conjure up a UUCP disk set for several possible >hardware configurations that I could hand over to other folks in >the net so they could use it without any further editing, etc. >Or rather, I would like to do all configuring for a set of nodes. > >I would put all the MAN files in a ZOO file, all the binaries onto >a installed working disk, make a separate floppy with edited >lib/spool/news, etc.. Do your restrictions discourage this >kind of shuffling? > >.. Awaiting 1.07/1.08 eagerly .. > >> Matthew Dillon uunet.uu.net!overload!dillon > >--Frank When I took over the UUCP distribution I was faced with that very question. To put it frankly, if I had concentrated on making UUCP as portable as possible I would still be on version 1.03D instead of 1.06D... it simply is too difficult to do with all the features I wanted to add. Take s:crontab for example ... how do you make that portable? Another big one: filenames. To make UUCP truely portable I would have to limit file names to 8 characters and alpha-numerics. There are a billion other little things that come up to. So I've decided not to try (to make UUCP completely portable). I do not purposefully try to make it Amiga-Only, just that I do not concentrate on portability all that much. -Matt -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA