Bruce, 

Look at your message below, and notice the apostrophes.  On my system, I
see "Comcast_s site".  You're talking to knowledgeable people, and you're
sending them HTML from a closed-source (Microsoft Outlook IMO, Build
9.0.2416, to be exact) email client.  In fact, you're not even sending
them proper ascii!  They're not going to be as friendly as you'd like.  

The HTML issue is: many people don't have HTML-rendering email clients,
and a lot of them think HTML has no place in the email world.  There's
some sense in that, if you think about archiving, scanning, indexing,
stuff like that.  Text-based tools are faster, the email is smaller. 
Plus, a lot of HTML-producing emailers don't even produce correct HTML, so
even if everyone has standards-compliant readers, they'd still be hosed. 
Plus plus, the technical world is moving away from ascii (which HTML uses)
toward other encoding systems that render *all* languages, with standard
ways to convert back and forth.  The HTML people show their unawareness or
their arrogance, depending on one's point of view.  

Suggestion: Get Pegasus or Eudora and tell me what you think.  

On Wed, 01 May 2002 11:58:04 -0400 "Bruce S. Lowden" <LowdenB@comcast.net>
wrote:

> beneficial than the one I_m on now.   I_d like to find one more tailored
> to new users, but not necessarily to neophytes.  

<netbsd-help@netbsd.org> is what I use.  There are no neophyte lists.  

> Great! Now I know how to be annoying.

Send a two-sentence apology after you have an email client with a clue. 
It'll be OK.  > Comcast grants 6 additional e-mail accounts, and 25mb of
disk space for each> in the way of a personal web page for their cable
Internet customers.  There> is a link to a GUI for the creation of user_s
site.  I_m thinking that 25mb> isn_t much in the way of space.

25 MB is plenty of space for static text.  If you have a lot of big stuff,
you can put it on my server and link to it.  I recommend you give up on
GUI HTML tools and learn the language.  It's not hard, and it's
worthwhile.  The first time someone gave me that advice, I told her she
was nuts.  I was wrong, though.  

You should be able to FTP pages from your box to Comcast's webhost.  

> Eventually, I_d like a static TCP/IP address use a firewall and host a
> server behind it.  This done, I can post links on the Comcast personal
> site that point to pages hosted here at the house.  In theory, some of
> the links can be open to everyone, and some can require login
> information.  The question is how?  

That depends on the web server and how it's configured.  You don't
actually "log in" to the OS via a browser.  Apache controls account
information with .htaccess files in the directory, but they're not real OS
accounts.  

> I_d like to explore the firewall iso you spoke of, in more detail.  As I
> mentioned, I have interest in both the firewall and a performing
> desktop/server machine.  The machine we worked on will eventually become
> the firewall _ 200mmx / 32ram / 1gig HD / etc.  It_s too small for
> anything else in my utilization realm.  

http://www.dubbele.com/

I get the feeling that an effective NetBSD
> workstation/server machine is not so much CPU intensive as it is memory
> intensive.  Memory is cheep these days_

I have 128 MB and a 233 PII as my desktop box.  Performance is fine. 
Compiles could be faster, and more RAM would help, but I have 

	$ ps -auxc |wc -l 
 	     99

tasks running at the moment, and it's using 80 MB of swap space.  

--jkl