From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Signal/noise (Was: OSI stack (Was: Posters))
Date: Sun, 3 Feb 2019 17:54:50 -0700 [thread overview]
Message-ID: <34abdea7-db7e-3964-3b13-32cdd7d73c93@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CAPWNY8Wx87Qx+gP+bm-YskuGbvu1pXoh2=rWafA50u8zWxSY-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]
On 2/3/19 4:33 PM, Mantas Mikulėnas wrote:
> When I first subscribed to tuhs several years ago (even though I don't
> really belong in here; I'm younger than even Linux, much less any of the
> Unixen),
FULL STOP
I see no reason for you to not belong here.
I too am younger than most of the things discussed on this list.
But that doesn't some me from participating ~> discussing ~> learning.
Nor do I think it should stop you.
Just be mindful of where your roots are or aren't.
After all, Unix collectively (including Linux) is doing the wrong thing
and going the wrong way if it turns people away that want to learn about it.
Resume.
> I *very much* enjoyed reading the various stories about UUCP, about Sun,
> about X11, VMS, ARPAnet – often first-hand tales, no less.
I do too.
I also enjoy being able to discuss things with people as I'm reading
about various technologies elsewhere.
That being said, I don't know that TUHS is the best place for some
non-Unix related things. That's what the COFF mailing list is for. ;-)
> So I don't know what counts as 'signal' on this list versus 'noise',
> but I'd much rather read a million posts about OSI, CLNP and other
> networks – a history lesson and information that's been getting scarce
> in general – than kill/mute yet another thread full of generic "boo M$
> Windoze" drivel that I can already find on Reddit.
I'd suggest COFF if you aren't subscribed. I'd also suggest the cctalk
mailing list.
Also, if you've not read it, I HIGHLY suggest "Where Wizards Stay Up
Late - The Origins of the Internet".
Finally, doing. Lots of doing or trying. Even if you find out that
it's wrong. That's gaining experience that I think makes it easier to
learn from.
comp.os.vms is another good place to watch ~> read ~> learn.
> Thanks,
:-)
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4008 bytes --]
next prev parent reply other threads:[~2019-02-04 0:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 15:02 [TUHS] OSI stack (Was: Posters) Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
2019-02-03 23:33 ` [TUHS] Signal/noise (Was: OSI stack (Was: Posters)) Mantas Mikulėnas
2019-02-04 0:10 ` Arthur Krewat
2019-02-04 0:54 ` Grant Taylor via TUHS [this message]
2019-02-04 2:23 ` [TUHS] Signal/noise Warren Toomey
2019-02-04 2:37 ` Larry McVoy
2019-02-04 2:57 ` Bakul Shah
2019-02-04 3:26 ` Warner Losh
2019-02-04 3:26 ` Dan Cross
2019-02-04 4:55 ` Dave Horsfall
2019-02-04 6:20 ` Jon Steinhart
[not found] ` <CANCZdfq5PM9jFEi9=geC+CTnveXs5CprN7b+ku+s+FYzw1yQBw@mail.gmail.com>
2019-02-06 17:16 ` [TUHS] OSI stack (Was: Posters) Warner Losh
2019-02-06 17:23 ` Larry McVoy
2019-02-06 23:37 ` George Michaelson
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=34abdea7-db7e-3964-3b13-32cdd7d73c93@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).