Xref: utzoo comp.lang.c:26506 comp.misc:8384 Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!texbell!ficc!morrison From: morrison@ficc.uu.net (Brad Morrison) Newsgroups: comp.lang.c,comp.misc Subject: Re: Silly Copyrights (was Re: Legal uses of lex & yacc) Message-ID: <.L:1W7xds13@ficc.uu.net> Date: 2 Mar 90 19:42:32 GMT References: <34421@ucbvax.BERKELEY.EDU> <659@mwtech.UUCP> Reply-To: morrison@ficc.uu.net (Brad Morrison) Organization: Ferranti International Controls Corp. (NYSEG SCADA) Lines: 38 In article dgh@unify.UUCP (David Harrington) writes: >In article <659@mwtech.UUCP> martin@mwtech.UUCP (Martin Weitzel) writes: >>In article <34421@ucbvax.BERKELEY.EDU> jwl@ernie.Berkeley.EDU.UUCP (James Wilbur Lewis) writes: >>Experience tells, that companies do in fact silly things with >>copyrighting: >>3) I quote from my license for my ISC 386/ix: >> "... [you may] either (a) make one (1) copy of the Software >> solely for backup purposes or (b) transfer the Software to >> a single hard disk provided you keep the original solely >> for backup or archival copies" >> (no kidding: It seems, that I am not allowed, to make regular >> backup-copies of the hard disk to several tapes. This *is* silly.) >Hey, they're doing you a favor. With favours like that, who needs bugs? >Why do you want to back up the OS regularly? 1) In case of disk failure 2) When installing a new disk or disks a) Replacing everything b) Moving part of the system to another mounted filesystem >Are you making changes to the kernel, and if so, how? Possibly; it's not uncommon to link a new kernel. >Binary or hex? Irrelevant. >Not backing it up saves tape, and time. Well, that's the big trade-off. You can save time now by not doing backups, or you can save time later by having backups. -- Brad Morrison (713) 274-5449 | "OK. Come back tomorrow. Ferranti International Controls Corporation | Bring two apples and uunet!ficc!morrison morrison@ficc.uu.net | a hammer."