From: segaloco via COFF <email@example.com>
To: Tomasz Rola <firstname.lastname@example.org>
Cc: Computer Old Farts Followers <email@example.com>
Subject: [COFF] Re: Useful Shell Scripts Network Connections , Logins and Block hacking attempts
Date: Fri, 12 May 2023 05:02:25 +0000 [thread overview]
Message-ID: <bn_mDi5J9AMhqq6LMm003WC33yhbZJ2U0qXejisDIkWyONPo56xeJSA3T5aVUWMrzKsTxVGJD0osp1PmNO_knpXLw3RKlCFlSJaqSpbx0u8firstname.lastname@example.org> (raw)
You can relegate any Linux grumbles from me to the cheap seats. It's my daily driver as it is for many folks, I certainly wouldn't steer discussion away, my opinions on the matter are informed by my own biases after all...
Can't complain too much though, I keep coming back to Linux for the hardware support...due to the nature of the BSD licensing there are probably a lot more BSDish drivers floating around out there than we see, but they're only in use by a select few.
- Matt G.
------- Original Message -------
On Thursday, May 11th, 2023 at 9:24 PM, Tomasz Rola <email@example.com> wrote:
> On Fri, May 12, 2023 at 12:13:17PM +1000, Greg 'groggy' Lehey wrote:
> > On Thursday, 11 May 2023 at 22:35:46 +0000, COFF wrote:
> > > That all said, yeah, I don't see this sort of email being too
> > > relevant to COFF.
> > Well, it is Unix-related. Should COFF be restricted beyond that?
> > The whole idea of the list was to provide a platform for topics where
> > TUHS was inappropriate. I don't see the distinction Unix/Linux as an
> > issue: a surprising number of Unix people have moved on to Linux. And
> > I don't think we should pontificate on the merits of the post. Some
> > are better than others.
> Myself, I have had a look at Ken's postings. Maybe I will not copy
> straight to my own scripts, maybe not, but I always look for examples
> of (shell) scripts and options to various programs which may serve as
> refresher or inspiration.
> Tomasz Rola
> ** A C programmer asked whether computer had Buddha's nature. **
> ** As the answer, master did "rm -rif" on the programmer's home **
> ** directory. And then the C programmer became enlightened... **
> ** **
> ** Tomasz Rola mailto:firstname.lastname@example.org **
next prev parent reply other threads:[~2023-05-12 5:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJXSPs92h7yVVJm9UPp06zPQwRy-XkGPDhL-=uVT5sw=hEcLkQ@mail.gmail.com>
2023-05-10 23:56 ` [COFF] Fwd: " KenUnix
2023-05-11 0:12 ` [COFF] " Niklas Karlsson
2023-05-11 5:58 ` steve jenkin
2023-05-11 9:18 ` [COFF] " Ralph Corderoy
2023-05-11 22:06 ` Dave Horsfall
2023-05-11 22:35 ` segaloco via COFF
2023-05-12 2:13 ` Greg 'groggy' Lehey
2023-05-12 2:19 ` Adam Thornton
2023-05-12 2:34 ` Larry McVoy
2023-05-12 4:30 ` Tomasz Rola
2023-05-12 8:34 ` Ralph Corderoy
2023-05-12 13:58 ` Larry McVoy
2023-05-12 4:24 ` Tomasz Rola
2023-05-12 5:02 ` segaloco via COFF [this message]
2023-05-12 8:14 ` Robert Stanford via COFF
2023-05-12 16:40 ` Adam Thornton
2023-05-12 11:42 ` Ralph Corderoy
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).