Subject: Linux-Misc Digest #779
From: Digestifier <Linux-Misc-Request@senator-bedfellow.MIT.EDU>
To: Linux-Misc@senator-bedfellow.MIT.EDU
Reply-To: Linux-Misc@senator-bedfellow.MIT.EDU
Date:     Sun, 6 Mar 94 06:13:41 EST

Linux-Misc Digest #779, Volume #1                 Sun, 6 Mar 94 06:13:41 EST

Contents:
  Re: pronunciation of linux (Kjetil Torgrim Homme)
  Howto setup default configuration for vi? (Divya Sundaram)
  Re: Moderation by program for col.* (Re: RFD: comp.os.linux.advocacy) (Frohwalt Egerer)
  Re: Linux compatible SCSI-2 VESA cards? (Bartosz Blacha)
  Re: RFD: comp.os.linux.* moderation by program (Jim Graham)
  Re: Howto setup default configuration for vi? (Dhaliwal Bikram Singh)
  Re: A suggestion: comp.os.linux.faq (Frohwalt Egerer)
  Re: comp.os.linux.help.* groups? (Frohwalt Egerer)
  Re: Can I get Slackware 1.1.2 on CD-ROM?
  Re: Minicom 1.60 available (Charles W. Blumreich)
  Re: Which monitor/svga card should I get? (Eternal Darkness)
  Re: pronunciation of linux (J.J. Paijmans)
  SLIP Question (Young Charlie)
  HP terminal emulator? (Lucas James Sheneman)

----------------------------------------------------------------------------

From: kjetilho@ifi.uio.no (Kjetil Torgrim Homme)
Subject: Re: pronunciation of linux
Date: 6 Mar 1994 05:50:21 GMT

+--- Kevin Lentin:
| I always presumed linux would be pronounced similarly to Linus which
| I pronounce as desribed above. I'd love a definitive answer.

Linus -> /'li:nus/ or "Lee-noos" in English approximation (note that
         the 's' is not voiced, and the 'l' is "clear", like in "leaf")

Linux is then /'li:nuks/ or "Lee-nooks".

The vocal quality of "u" can vary in much the same way "u" does. Hope
this helps :-)


Kjetil T.

------------------------------

From: sundaram@egr.msu.edu (Divya Sundaram)
Subject: Howto setup default configuration for vi?
Date: 6 Mar 1994 06:51:33 GMT


Hi all,

I wanted to find out how to set up the systemwide defaults for vi 
on my Slackware system. Any pointers would be much appreciated.

Thanks

Divya



------------------------------

Crossposted-To: news.groups
From: froh@devnull.adsp.sub.org (Frohwalt Egerer)
Subject: Re: Moderation by program for col.* (Re: RFD: comp.os.linux.advocacy)
Date: Sun, 6 Mar 1994 00:56:36 GMT

Ian Jackson (iwj@cam-orl.co.uk) wrote:
: In article <2jrojh$h1f@spool.cs.wisc.edu> jimr@shorty.cs.wisc.edu (Jim Robinson) writes:
: >My wish is not to see people "converting" others to linux, but rather
: >to get the verbage out of misc.  [...]

: The problem with col.misc (and indeed col.help and col.admin) is not
: the occasional flamewar.  They're easily dealt with by killfiles, a
: good newsreader, or both.

: The problem is that the Linux community is still growing
: exponentially, and with it the traffic in col.*.

: Many of the new users don't know about the FAQs etc., because they
: don't bother reading the group at all before posting, and so don't see
: (for example) the daily posting, or the other people who've recently
: asked the same question and been answered.

What about a moderated group  comp.os.linux.faq  where all the faqs and 
howtos are posted periodically? (The 'beginner' faqs weekly, the 'advanced' 
ones monthly.)  I know there currently is c.o.l.a, but IMHO new readers do 
not realize the faqs are posted there, or they are not patient enough to wait
until the appropriate faq shows up, while they are ignorant enough not to
ftp them from the appropriate sites. The name of  c.o.l.f  would hopefully
attract people who find their questions already answered in that group.
Because of posting the 'beginner' faqs weekly, they would attract more 
attention than they currently are. Posting them more often in c.o.l.a would
annoy those people, who read c.o.l.a to get announcements, not faqs.

comp.os.linux.faq  could also be used to maintain the faqs and keep them
current. _NEW_ questions could be sent to the moderator who forwards them
to the authors. Answers could be sent to the moderator who incorporates them
in the faqs or forwards them to the faq authors. The same applies to faqs
which get out of date with new versions of software. There also could be a 
not-yet-answered faq, which covers unsolved questions that show up.

Voting for c.o.l.faq
  Froh
-- 
Frohwalt Egerer   Drausnickstr. 36   91052 Erlangen   Germany      ///   Use
froh@devnull.franken.de     (preferred)                           ///  Linux
ftegerer@cip.informatik.uni-erlangen.de                       \\\///  
                                                               \XX/  ECG 210
Call by Reference: Throwing encylopedias at your kids until
they come to dinner.        
                  -- Larry Wall, Randal Schwartz: Programming Perl


------------------------------

From: Bartosz Blacha <bart+@CMU.EDU>
Subject: Re: Linux compatible SCSI-2 VESA cards?
Date: Sat,  5 Mar 1994 16:00:24 -0500


achen1@vmsb.is.csupomona.edu (ALAN CHEN) writes:
> I am trying to install Linux to my system which unfortunately has an Adaptec
> AHA-2842/VLB SCSI card in it at the moment.  I am searching for a replacement
> SCSI-2 card that is both supported by Linux and is also local bus.  Any 
> suggestions out there?  I've read all the docs on my Linux CD and they don't 
> seem to mention if any of the SCSI cards are VESA.  Of course this may mean
> that none are, but I hope not. Thanks.

You can try Ultrastor 34F.  It plugs into the VESA bus, and
the manual says that it does bus mastering, Fast SCSI-2, Scatter/Gather
(that's for virtual memory speed-up,) and Slackware recognizes it
by default.


--- Bartosz Blacha ---------- You are what you is, -------------------
--- Bart+@cmu.edu ---------- An' that's all it 'tis. -----------------
====================================================== Frank Zappa ===

------------------------------

From: jim@n5ial.mythical.com (Jim Graham)
Crossposted-To: news.groups
Subject: Re: RFD: comp.os.linux.* moderation by program
Date: Sat, 5 Mar 1994 20:45:59 GMT

In article <1994Mar4.181913.19884@swan.pyr> iiitac@swan.pyr (Alan Cox) writes:
>In article <1994Mar4.125248.9634@n5ial.mythical.com> jim@n5ial.mythical.com
>(Jim Graham) writes:

>>To begin with, we have a server that is going to

That should have read ``is going to have to'' ... it seems that I hit 'u'
one too many times (in vim).  I was wondering if I'd done that, and now
I know (at the time, I didn't recognize anything as being missing).

>>   2) recognize *VALID* posts by new users and *NOT* reject them,
>>      particularly in the case where said user has a long path delay
>>      (such as is the case with me---there's normally a one-day delay
>>      on e-mail, most news, etc.)

>HA! this I have to see. 

My point exactly.  But it needs to be part of the server (if there is one).
Remember my example, of where someone's machine has crashed (and the answer
isn't in the FAQ, HOWTOs, etc.), and they need help, so they post from
another machine (which might just have a long UUCP delay).  Now add to that
the possibility that their alternate posting site is a long-distance call.
It's a combination of possibilities that is very easy to imagine....
Rejecting their post because they're a new user (regardless of the fact
that they aren't...that was covered in #1, which is deleted here) wouldn't
exactly be what I would call polite behavior for any moderator, human or
otherwise.  If I were that person, and that happened to me, I'd be very
angry after something like that, and rightfully so (IMHO).

>>   3) recognize invalid posts from any users (no matter how long they've
>>      been around) and reject them

>How do you know what is invalid. Many people are stuck with marginally
>invalid headers (like mine). Nothing I can do about it..

I wasn't talking about headers.  I can't imagine the server doing much
with headers in the first place, except maybe looking at cross-posting.
Other than that, some people can't even do anything *AT ALL* with their
headers.  For example, I used to use SNEWS under dos to post.  From that
program, you can't touch the headers.  If we allow the assumption that
some people may not have posting access from their Linux machine (it
may be down, it may not be connected at all, etc.), we also allow the
assumption that they may be on such a limited system.

I was talking about content.  I have now idea how the server is going to
be written to recognize valid/invalid article content, but in order for
the thing to be effective (without making the newsgroups worthless in the
process), it's going to have to be able to do just that.

>Crackpot ideas of our time..

You missed the whole point of my post, which, with that one minor goof
caused by backing up one undo level too many, is understandable.  My whole
point was that, while some of these things are going to be extremely
difficult to do (at least, they would be for me, but then, I won't be
having anything to do with the server anyways), they'll be an important
requirement for the server.  And if you can manage to do all of those
things, you can certainly do something as simple (by comparison) as
handling posts from someone who doesn't have e-mail access from the
machine they post from (psychic server, perhaps?).  And yes, I used to
be one of those people (at one site, at least).

Later,
   --jim

--
73 DE N5IAL (/4)                         < Running Linux 0.99 PL10 >
      jim@n5ial.mythical.com                 ICBM: 30.23N 86.32W
  ||  j.graham@ieee.org          Packet:  N5IAL@W4ZBB (Ft. Walton Beach, FL)
E-mail me for information about KAMterm (host mode for Kantronics TNCs).


------------------------------

From: a336dhal@cdf.toronto.edu (Dhaliwal Bikram Singh)
Subject: Re: Howto setup default configuration for vi?
Date: Sun, 6 Mar 1994 07:27:36 GMT

In article <2lbuhl$15so@msuinfo.cl.msu.edu> sundaram@egr.msu.edu (Divya Sundaram) writes:
>
>Hi all,
>
>I wanted to find out how to set up the systemwide defaults for vi 
>on my Slackware system. Any pointers would be much appreciated.

Just put your preferences in a file called .exrc in  your home directory.

In this file you can specify:
set tabstops=3
set noautoindent


and so on.....
>
>Thanks
>
>Divya
>
>


-- 
-a336dhal@cdf.toronto.edu
-bikram dhaliwal

------------------------------

From: froh@devnull.adsp.sub.org (Frohwalt Egerer)
Subject: Re: A suggestion: comp.os.linux.faq
Date: Sun, 6 Mar 1994 02:03:16 GMT

K J MacDonald (kenny@festival.ed.ac.uk) wrote:
: Manoj Kasichainula (mvkasich@eos.ncsu.edu) wrote:

: : A lot of people have been comlaining about high traffic in
: : comp.os.linux.help. I have a suggestion. How about a comp.os.linux.faq
: : group? It would be a moderated group, and not postable. The only
: : articles in it would be all Linux FAQs and HOWTOs, as well as the FAQs
Nice - I just had the same idea today. Must be a good thing (tm).

:       As you say, it would indeed be a duplication of effort and net
: bandwidth. The Linux FAQ's and HOWTO's are posted regularly to
: comp.os.linux.announce, and I'm sure the INFO-SHEET has pointers to
: other FAQ's and groups.

I don't think so. If comp.os.linux.faq existed, the faqs could be removed
from c.o.l.a.  Additionally it seems faqs in c.o.l.a are not posted
often enough, at least the faqs that direct new users to the appropriate
places. IMHO it would reduce traffic in the other linux groups significantly
if newbies would find documentation that moment they start their news reader
and enter the comp.os.linux hierarchy. c.o.l.faq would virtually SHOUT:
"Here is documentation", provided that the important stuff is posted weekly.

:       I really am against turning the c.o.l newsgroups into a general
: un*x area. New Linux users really *MUST* learn that for most things
: Linux = Un*x.

That's true, but at least there must be documentation where to find
something. And this documentation must be available all the time. Using
ftp or waiting till a faq is posted isn't good enough, people will always 
post stupid questions instead of reading the faq as long as posting stupid 
questions is easier than reading the faq.

I definiteley second the suggestion for comp.os.linux.faq

Froh
-- 
Frohwalt Egerer   Drausnickstr. 36   91052 Erlangen   Germany      ///   Use
froh@devnull.franken.de     (preferred)                           ///  Linux
ftegerer@cip.informatik.uni-erlangen.de                       \\\///  
                                                               \XX/  ECG 210
Subroutine: Normal behaviour at periscope depth.
                  -- Larry Wall, Randal Schwartz: Programming Perl


------------------------------

From: froh@devnull.adsp.sub.org (Frohwalt Egerer)
Subject: Re: comp.os.linux.help.* groups?
Date: Sun, 6 Mar 1994 00:17:18 GMT

Vladimir Stavitsky (vlad@dkbfpny.com) wrote:
: In article <1994Feb16.142800.6501@taylor.wyvern.com>, mark@taylor.wyvern.com (Mark A. Davis) writes:

: |> >> c.o.l.h.networking      # help with tcp/ip, slip. mail, term, etc
: |> >> c.o.l.h.install         # help with installing linux
: |> >> c.o.l.h.config          # help configuring software for your system
: |> >> c.o.l.h.other           # help with other things not mentioned above

: may be 

: ... net
: ... conf                      (this includes install, may be?)
Agreed. 'conf' should also cover all things concering complete distributions 
like Slackware, SLS and so on.

: ... x386                      
There is an own newgroup concering XFree. (comp.windows.x.386 I think) All questions 
should be directed there, there is no reason in creating another one in the c.o.l 
hierarchy. (Other than not being distributed to my site :-( )

: ... misc
Yes. Misc already seems to be used this way.

: This way we could drop 

: ... help

: and, may be, even

: ... announce

: where the traffic is extremely low.
No way. Announce is the only group carrying 0% noise 100% signal.

I also vote for a moderated newsgroup called  comp.os.linux.faq  where all the 
current faqs and howtows are posted weekly or monthly, instead of posting them 
in c.o.l.announce. 

IMHO this would reduce traffic in the other groups sigificantly. The name of the 
group would direct new users to it, just like c.o.l.help does now. Since they 
cannot post there, they would read the faqs and not create traffic.

_New_ questions (and answers, of course) can be posted by mailing them to the 
moderator. The moderator can forward them to the authors of the appropriate faqs
for inclusion in the next version.

Froh
-- 
Frohwalt Egerer   Drausnickstr. 36   91052 Erlangen   Germany      ///   Use
froh@devnull.franken.de     (preferred)                           ///  Linux
ftegerer@cip.informatik.uni-erlangen.de                       \\\///  
                                                               \XX/  ECG 210
Call by Reference: Throwing encylopedias at your kids until
they come to dinner.        
                  -- Larry Wall, Randal Schwartz: Programming Perl


------------------------------

Date: Sat, 5 Mar 1994 18:28:32 EST
From: <3JJN3@QUCDN.QueensU.CA>
Subject: Re: Can I get Slackware 1.1.2 on CD-ROM?

A TSX-11 CD is on the way for all the subscribers, Watch the c.o.l.announce
for the news this week.

Jay

PS : I do not work there full time, E-Mail christina@jana.com for any info
you need.


------------------------------

From: cwblumre@major.cs.mtu.edu (Charles W. Blumreich)
Subject: Re: Minicom 1.60 available
Date: 6 Mar 1994 08:55:41 GMT

David Lesher (wb8foz@netcom.com) wrote:
:->I have a generic minicom question.
:->I've added a second modem. Is there any way to specify more than one
:->possible modem? I'm willing to accept a different username, or if
:->needbe a separate executable (ugh), but what's the best way?
:->-- 

  My solution to a similar situation was to configure minicom (using the 
internal menus) for one modem.  Save the config file as, say, "modem1".
Then, set up for the second modem, save the config as, say, "modem2".
All you need to do is call minicom with the modem you want to use.
ie- % minicom modem1


--
Charles W Blumreich III
cwblumre@fsh.mtu.edu
cwblumre@major.cs.mtu.edu

Destroy MS-DOG!!!
Nuke MicroSLOTH Windoze!!!
Eradicate OS-half!!!
Use Linux! Free Unix for your 386/486/ Pentium !!!

Anyone who claims him/her self as God, clearly has an ego problem.
Anyone who claims him/her self as demon spawn clearly needs adjustment.

------------------------------

From: jake@acca.nmsu.edu (Eternal Darkness)
Crossposted-To: comp.os.linux,comp.os.linux.help
Subject: Re: Which monitor/svga card should I get?
Date: 6 Mar 1994 10:02:33 GMT

Michael Vargo (mvarg@ctp.com) wrote:
: Hello,
:     I have a Diamond Viper card now and noticed that linux doesn't
: support it. So I'm going to take it back and get a new one. My
: question is, which svga card is a good one for windows as well as
: good for linux? ANY info is appreciated.....Thanks....
[edit]

--
I have a Cirrus CL-GD5428 card that came built into my IBM PS/1. It ran windows
great (until I reformatted the ol' hard disk for Linux). I can send a copy of
my Xconfig to you, too. I have 1MB of video-RAM on my card, BTW. Mail me if you
get that particular card and I can send you a sample Xconfig that DOES work on
that card!

Sincerely,

Jake Skinner Garcia,
Eternal Darkness(tm)

============================================================
jake@rever.nmsu.edu                     5130 N. Dona Ana Rd.
Home & Work Phone: (505)524-4045        Las Cruces, NM 88005
============================================================
"Shying from the light, I've always loved the night.
And now you offer me Eternal Darkness." (Depeche Mode)
=====================^^^^^^^^^^^^^^^^=======================

------------------------------

From: paai@kub.nl (J.J. Paijmans)
Subject: Re: pronunciation of linux
Date: Sun, 06 Mar 94 09:04:12 GMT

In article <2lblv0$q2o@news.acns.nwu.edu> tkeidl@merle.acns.nwu.edu (Tobias Keidl) writes:
>In article <2lbf8u$85r@harbinger.cc.monash.edu.au>,
>Kevin Lentin <kevinl@bruce.cs.monash.edu.au> wrote:
>>On 5 Mar 1994 21:59:32 GMT, Yumin Yang wrote:
>>
>>> Hi, folks,
>>> How should I pronunce the letter "i" in "linux", like the one in "line" or
>>> the one in "linear"?  Thanks.
>>
...

>Oh boy, my first chance to tell people to read the faq =).  Its a 
>question on the faq and it gives the pronunciation to be like minix
>if I remember correctly.  Anyways...later...
>

Uh... how do you pronounce 'minix...'?
:-)
Paai

------------------------------

From: young933@crow.csrv.uidaho.edu (Young Charlie)
Subject: SLIP Question
Date: 5 Mar 1994 22:49:27 GMT

OK, I have setup the $remote and $local in DIP. The problem I have now
is doing stuff! How can i Telnet to other sites around the internet?
What should i set with route?



------------------------------

From: sheneman@cs.uidaho.edu (Lucas James Sheneman)
Subject: HP terminal emulator?
Date: 6 Mar 1994 02:01:40 GMT


I am looking for an HP-compatible terminal emulator that I can use within,
say, and xterm to connect to an HP machine.  Something like HP's
"hpterm" client would work nicely.

Any ideas?

Please e-mail me if you can be of service.
Thanks,
Luke.
--
+--------------------------------------------------------------------------+
|Luke Sheneman     sheneman@cs.uidaho.edu    FINGER ME (IT'S IMPORTANT)    |
+-------------------------------+--------------------------+---------------+
| Laboratory for Applied Logic, University of Idaho        |    +--------+ |
+--------------------------+-------------------------------+   /|       /| |
| Campus Linux Distributor |"She was so absolutely digital |  +--------+ | | 
+--------------------------+ to jack in now was wrong      |  | |      | | | 
| "Information wants to be | but cupid punches deck with   |  | +------|-+ |
|    free.  Believe it."   | chemicals while dark madonna  |  |/       |/  |
|               -Sterling  | sings her song."     -InfoSoc |  +--------+   |
+--------------------------+-------------------------------+---------------+


------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: Linux-Misc-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: Linux-Misc@NEWS-DIGESTS.MIT.EDU

Linux may be obtained via one of these FTP sites:
    nic.funet.fi				pub/OS/Linux
    tsx-11.mit.edu				pub/linux
    sunsite.unc.edu				pub/Linux

End of Linux-Misc Digest
******************************
