public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Jude DaShiell <jdashiel@shellworld.net>
To: blinux-list@redhat.com
Subject: Re: Problems with Brltty
Date: Mon, 19 Nov 2001 17:32:57 -0600 (CST)	[thread overview]
Message-ID: <Pine.BSF.4.41.0111191726310.52975-100000@server1.shellworld.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0111182218000.7615-100000@rupin.localnet>

You know what I can't figure out?  Why it is any of these versions of
Linux were ever sold that omitted the bsd learn utility package.  When I
started learning unix, I got a pointer from a friend to go and try that
out.  Admittedly it didn't cover such sysadmin things like permanently
disabling the portmap server and what could happen to your system if you
didn't get that done, but it was written at least the version I used
before 1989 and viruses were not then as they are now.  I got infested
with linsniffer by the way.  Not a pleasant experience.  I'll try exportfs
-ua to handle the portmap server since I really don't need it on.  Maybe
it will be needed for ethernet but I can't figure how.  If anyone does a
search for linsniffer, the info on it is on attrition.org.

Jude <jdashiel@shellworld.net>





  parent reply	other threads:[~ UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John J. Boyer
 ` Nicolas Pitre
   ` L. C. Robinson
     ` Nicolas Pitre
       ` L. C. Robinson
         ` Janina Sajka
           ` Dave Mielke
         ` Jude DaShiell [this message]
       ` John J. Boyer
         ` Nicolas Pitre
           ` Cheryl Homiak
             ` Dave Mielke
         ` kudzu Cheryl Homiak
           ` kudzu L. C. Robinson
         ` Problems with Brltty Dave Mielke
           ` John J. Boyer
             ` Dave Mielke
       ` Cheryl Homiak

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=Pine.BSF.4.41.0111191726310.52975-100000@server1.shellworld.net \
    --to=jdashiel@shellworld.net \
    --cc=blinux-list@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).