Silly Copyrights (was Re: Legal uses of lex & yacc)
Brad Morrison
morrison at ficc.uu.net
Sat Mar 3 06:42:32 AEST 1990
In article <l177spv at unify.uucp> dgh at unify.UUCP (David Harrington) writes:
>In article <659 at mwtech.UUCP> martin at mwtech.UUCP (Martin Weitzel) writes:
>>In article <34421 at ucbvax.BERKELEY.EDU> jwl at 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 at ficc.uu.net | a hammer."
More information about the Comp.lang.c
mailing list