The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Aron Insinga <aki@insinga.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Sad but not unexpected news about the LCM-L
Date: Tue, 25 Jun 2024 18:29:58 -0700	[thread overview]
Message-ID: <20240626012958.GH23135@mcvoy.com> (raw)
In-Reply-To: <bcfc1aed-c994-4573-a436-ce02e982aeaf@insinga.com>

This is almost completely unrelated but somewhat in the "write your
will/trust the right way".

My dad made me trustee of their estate.  OK, fine.   He passed first,
then my mom passed and there was a decent amount, not a lot but enough
you'd notice it.  3 kids, divided equally.  But I had made enough money
that it seemed unfair to me to take my third when my brother, a PhD from
Cornell, was busy convincing everyone that how they were going about
saving the Everglades was wrong, and he was broke.  I could just hear
my dad saying "Larry, you are fine, Chris is not".

So I gave him my third but it is a pain in the butt.  You can only
gift so much each year without a tax implication.  

The point being that none of the trust people had ever heard of, or
thought of, the idea that one of the kids would be willing to give
up their share.

Since we're mostly old folks, maybe put something in your trust that
says any kid can yield any portion to whoever they want and it is as
if you wrote that into the trust/will.  We did that with our trust 
and the lawyer had to be told 3 times.  She kept saying that's not
what happens, the kids argue about they should get more, nobody
says they should get less.  Turns out I'm the odd ball.

On Tue, Jun 25, 2024 at 08:56:43PM -0400, Aron Insinga wrote:
> I am not a lawyer, but as I've mentioned before, people building a
> collection or creating a Museum should form a non-profit organization (with
> a business plan to support it) to take ownership of it and keep it out of
> the estate, because there is no guarantee one's heirs will give a $#!^ about
> any of it other than for the gold that can be harvested from it.?? Do it
> straight away because you likely won't know in advance of when your time is
> up.
> 
> And even if all you have is one or a few items (let's say, a missile
> guidance computer, or someone's unpublished notes from lectures) at least
> make sure you have a valid will to try very hard to require it to be sent
> someplace that can accept it, or that will appoint (a) right-thinking
> representative(s) to handle said item(s).
> 
> Or at least make sure you've actually succeeded in educating your family on
> the importance of said items, and places that can accept them.
> 
> As someone from the Smithsonian Air & Space Museum once said to me, "They
> [TCM=>CHM] were lucky to get that, we don't have one."
> 
> But IMHO the LCM might be the biggest such failure of responsibility to
> computing history ever.
> 
> Best,
> 
> - Aron (a docent at The Computer Museum when it was at DEC in Marlborough)
> 

-- 
---
Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat

  reply	other threads:[~2024-06-26  1:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 18:17 [TUHS] " Clem Cole
2024-06-26  0:56 ` [TUHS] " Aron Insinga
2024-06-26  1:29   ` Larry McVoy [this message]
2024-06-26  3:34     ` [TUHS] Re: Trust stuff, " John Levine
2024-06-26  9:22     ` [TUHS] Wills. (Was: Sad but not unexpected news about the LCM-L) Ralph Corderoy
2024-06-26  1:42 ` [TUHS] Re: Sad but not unexpected news about the LCM-L George Michaelson
2024-06-26 17:22   ` aki
2024-06-26  1:44 ` Paul Guertin
2024-06-26  1:46   ` Dan Cross
2024-06-26  2:46     ` Paul Guertin
2024-06-26  5:36     ` Lars Brinkhoff
2024-06-26 14:30       ` [TUHS] Planning for the future was " Will Senn
2024-06-26 15:18         ` [TUHS] " Al Kossow
2024-06-26 21:57         ` [TUHS] Re: Planning for the future Warren Toomey via TUHS
2024-06-30 13:05           ` Will Senn
2024-06-26 16:56       ` [TUHS] Re: Sad but not unexpected news about the LCM-L aki
2024-06-25 18:45 Noel Chiappa
2024-06-25 18:53 ` Al Kossow
2024-06-27 15:19 Noel Chiappa
2024-06-27 17:06 ` Al Kossow
2024-06-27 17:32   ` John Levine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240626012958.GH23135@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=aki@insinga.com \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).