Subject: Linux-Misc Digest #878
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, 27 Mar 94 03:13:19 EST

Linux-Misc Digest #878, Volume #1                Sun, 27 Mar 94 03:13:19 EST

Contents:
  Re: PCMCIA modems in laptops [PCMCIA] [MODEMS] [LAPTOP] (H.J. Lu)
  Re: Slackware 1.2.0/Linux 1.0 Problems (Bogdan Urma)
  Source for xdm in XFree86-2.1? (Whitstler)
  Re: Wine status March 11, 1994 (Paul)
  Re: STRAW POLL RESULT: Linux (David Dyer-Bennet)
  Re: linux & thinkpad 750c (2.88 drive) (Paul Vojta)
  Re: STRAW POLL RESULT: Li (Rick Emerson)
  Re: "Hacker's Paradise?" (was Re: Linux-1.0-inline-asm uploaded) (Robert Sanders)
  Re: 360k floppies not supported? (H.J. Lu)
  Re: Slackware 1.2.0/Linux 1.0 Problems (Superuser)
  Re: Impressions: FreeBSD vs Linux (Herb Peyerl)
  Re: Linux (Zenon Fortuna)
  Re: STRAW POLL RESULT: Linux groups automonitoring (David Dyer-Bennet)
  What keywords to use (David Dyer-Bennet)

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

From: hjl@nynexst.com (H.J. Lu)
Subject: Re: PCMCIA modems in laptops [PCMCIA] [MODEMS] [LAPTOP]
Date: 27 Mar 1994 04:04:14 GMT

David Lesher (wb8foz@netcom.com) wrote:
: A friend has laptop with a AT&T/NEC PCMCIA Keep In Touch 
: V.42 bis modem card.

: Are there any issues relating to configuring/using same under Linux?
: End apps would be minicom now & slip/ppp eventually.

So far only Intel and Databook PCMCIA chips are known to work under
Linux. I have a Megahertz PCMCIA modem and I am using it under Linux
at this very moment with minicom 1.60. You need some black magic to
get PCMCIA modem working under Linux. Basically, you need to know how
to turn on the modem card into the I/O mode since the PCMCIA card is
supposed in the memory mode by default, even if it is an I/O card.

H.J.

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

From: bau1@cornell.edu (Bogdan Urma)
Crossposted-To: comp.os.linux.help
Subject: Re: Slackware 1.2.0/Linux 1.0 Problems
Date: Sat, 26 Mar 1994 23:03:45

>"Mr. Unix" writes,

>Slackware 1.2.0 and Linux 1.0.  Good concept, poor execution-

>Several points:

>1- Is it just me or is emacs 19.22 buggy as hell in addition to being about
>   2 times slower than version 18.59 that I'm using right now?  For example,
>   I've had emacs 19.22 crash with a segmentation violation, and then it
>   would refuse to work again, instead, on subsequent invocation just eating
>   memory until virtual memory is exhausted.  The only way I've found to
>   "fix" this is to reboot.  (this problem may be related to #3 , but I'm
>   not certain).  Also, under X (both fvwm and olvwm), emacs 19.22 opens
>   a window that's twice as wide as is needed, and everything you type is
>   initially displayed by emacs as s o m e t h i n g  l i k e  t h i s.

    What does this have to do with Slackware 1.2.0 and Linux 1.0?? To me 
this just sounds like a specific emacs problem for you. My emacs 19.22 works 
fine, and it worked fine with many other Slackware releases and kernels. If 
you want to reduce the emacs window under fvwm just edit the system.fvwmrc 
file in the menu section to specify a geometry that you want and add emacs 
to your menu.(If you want to!)


>5- The color 'ls' is just too slow for me, even if you turn off the color..
>   first order of business was to replace the 'ls' binary with the old
>   monochrome-only 'ls'.  Besides, "real" Unix types hate color.

 What do you mean by slow? Do you read while it scrolls?    
 Also, if "real" Unix types hate color, why don't you run X in monochrome??
     

  Have fun,
  Bogdan

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

From: slouken@talbot.cs.ucdavis.edu (Whitstler)
Subject: Source for xdm in XFree86-2.1?
Date: Sun, 27 Mar 1994 04:26:39 GMT


        I need to find the source to xdm that comes from
the XFree86-2.1 distribution. (with shadowed passwords)
I need to modify the encryption code to handle long
passwords.

I'd really appreciate any pointers mailed to me at:

        slouken@cs.ucdavis.edu

Thanks!

        -Sam


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

Crossposted-To: comp.windows.x.i386unix,comp.os.386bsd.apps
From: preacher@netcom.com (Paul)
Subject: Re: Wine status March 11, 1994
Date: Sun, 27 Mar 1994 05:01:05 GMT

        The March '94 (vol.3, num.2) 'Microsoft Developer Network News'
details MS's plans for Win32. Currently under development, NT on R4000
and AXP, Chicago on 680x0 and RISC editions of Visual C++ 2.0. Nothing
short of world domination for Bill. :)

--
Paul McGoldrick | preacher@netcom.com | CI$ 70414,1675     Nothing to excess,
4435 Redondo Bch. Blvd. #249, Lawndale, CA 90260              save excess.

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

From: ddb@terrabit.uucp (David Dyer-Bennet)
Subject: Re: STRAW POLL RESULT: Linux
Date: Sat, 26 Mar 1994 15:59:58 GMT

rick.emerson@dscmail.com (Rick Emerson) writes:

>Wait a minute, since when do you or Ian Jackson have even the
>slightest claim to define how the lists should be run?  If you want to
>say, in effect, the signal to noise ratio here stinks, fine.  Go right
>ahead.  If enough people want to do something about the issue, they
>will.  But no one person, myself included, has any right to impose
>their will on the lists; this is a collective experience.

Our right to say "it needs fixing" seems precisely equal to your right
to say "it's fine".  

Ian's right to send netmail to people suggesting the use of keywords
is equal to my own right to send them netmail suggesting they shut up
and get on with it :-), that they read the FAQ, or whatever.

I already send all my mail from a program (it's called elm here).
Sending mail from an unattended program *does* seem to me somewhat
different, particularly because of its ability to pay attention to all
the messages and respond hundreds of times.  However, *I* find the
results of the straw poll a sufficiently good mandate to justify this
step.  It was clearly stated before the poll that he intended to go
ahead if the poll so indicated.  I have *absolutely no* sympathy for
people who couldn't be bothered to participate in the poll and now
don't like the results.

This is to my knowledge a new experiment on the net.  I think it's
worth trying.  I think the consequences of a *total* failure are
modest: some annoying mail for some people.  Nobody gets denied access
to the group.  I think the benefits of a moderate success are
considerable: knowledgable people can more easily find the questions
that lie within their areas of expertise.  I hope that this will
increase the number of knowledgable people who answer questions asked
in c.o.l.[ham].
-- 
David Dyer-Bennet, proprietor, The Terraboard            4242 Minnehaha Ave. S.
ddb@network.com, lynxds.mn.org!terrabit                   Minneapolis, MN 55406
Don't waste your time arguing about allocating blame;           +1-612-721-8800
There'll be enough to go around.                            Fax +1-612-724-3314

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

From: vojta@math.berkeley.edu (Paul Vojta)
Subject: Re: linux & thinkpad 750c (2.88 drive)
Date: 27 Mar 1994 06:09:41 GMT

In article <1994Mar20.230543.7262@unlv.edu>,
Frank Lofaro <ftlofaro@unlv.edu> wrote:
>In article <2mg7lt$doh@agate.berkeley.edu>,
>vojta@powdermilk.berkeley.edu (Paul Vojta) writes:
>[...]
>>Slightly less quick fix:  edit floppy.c to allow it to recognize drive type 5
>>as the same as drive type 4.  You'll then be able to use your drive as a
>>1.44MB drive under linux and as a 2.88 drive under MS-DOG.
>>
>>--Paul Vojta, vojta@math.berkeley.edu

>Why not just fix floppy.c totally? Increase the track buffer if needed (might
>be done in a .S file somewhere ...) and add a 2.88 drive type to the floppy
>table. Its really not hard. I could do it in about an hour, if I knew the
>specs (gap1, etc, etc) to be put in the table. But I don't have a 2.88 :(

I thought of that too.  I found otherwise.  In floppy.c, you'll find:

/*
 * This has only been tested for the case fdc_version == FDC_TYPE_STD.
 * In case you have a 82077 and want to test it, you'll have to compile
 * with `FDC_FIFO_UNTESTED' defined. You may also want to add support for
 * recognizing drives with vertical recording support.
 */

I tried enabling the code last April, but it didn't work.  It may have
been fixed since then, maybe not.  In any case, it seems to be a
nontrivial amount of work.

You may also be interested in the following message fragment from last
December:

| Yes, there are people working on it.  There is a floppy patch out there which
| seems to work with 1.72 MB floppies, though I can't personally vouch for it.
| There is a longer-term effort by myself and Sam Chessman to completely rewrite
| the floppy and floppy controller code with the intent of better performance,
| supporting ED (2.88MB) floppies and floppy tapes, and to make it all much
| more maintainable.  I have the fdformat code too, but it is very DOS-oriented
| and is useful mostly as a reference.  I expect we will try to stay compatible
| with the DOS fdformat.
|
| If you want to actually work on the effort, let me know.
| ---
| David C. Niemi        Perot's Lemma: Just because they're out to get him
| David.Niemi@oasis.gtegsc.com         doesn't mean he's not paranoid.

Incidentally, here's the patch I was referring to.
(It's relative to a kernel from last November, but that shouldn't
change much.)

*** floppy.c.orig       Mon Nov 29 20:19:03 1993
--- floppy.c    Mon Nov 29 20:18:09 1993
***************
*** 170,175 ****
--- 170,177 ----
        { 1440, 9,2,80,0,0x2A,0x02,0xDF,0x50,"720k" },    /* 3.5" 720kB diskette */
        { 2880,18,2,80,0,0x1B,0x00,0xCF,0x6C,"1.44M" },   /* 1.44MB diskette */
        { 1440, 9,2,80,0,0x2A,0x02,0xDF,0x50,"720k/AT" }, /* 3.5" 720kB diskette */
+       { 2880,18,2,80,0,0x1B,0x00,0xCF,0x6C,"1.44M" },   /* 1.44MB diskette */
+       { 1440, 9,2,80,0,0x2A,0x02,0xDF,0x50,"720k/AT" }, /* 3.5" 720kB diskette */
  };
  
  /* Auto-detection: Disk type used until the next media change occurs. */
***************
*** 1237,1243 ****
  {
        struct floppy_struct *base;
  
!       if (code > 0 && code < 5) {
                base = &floppy_types[(code-1)*2];
                printk("fd%d is %s",drive,base->name);
                return base;
--- 1239,1245 ----
  {
        struct floppy_struct *base;
  
!       if (code > 0 && code < 6) {
                base = &floppy_types[(code-1)*2];
                printk("fd%d is %s",drive,base->name);
                return base;

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

Subject: Re: STRAW POLL RESULT: Li
From: rick.emerson@dscmail.com (Rick Emerson)
Date: Sat, 26 Mar 94 22:06:00 -0640

 @SUBJECT:Re: STRAW POLL RESULT: Linux groups automonitoring          N
DA> 
DA> While I don't necessarily agree with the proposal, I would say the
DA> outcome did give some "mandate" to go ahead with an official vote
DA> on the proposal per USENET voting rules.  I don't see anything
DA> wrong with using some kind of informal polling to see if there
DA> is any interest.

I don't think anyone's challenged the idea of putting automatic
moderation to a vote.  Maybe we should get on with it so we can shoot
the idea dead for once and all.

Rick  
...
 * ATP/Linux 1.42 * With consequences,  the unexpected always predominate.

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

From: gt8134b@prism.gatech.edu (Robert Sanders)
Subject: Re: "Hacker's Paradise?" (was Re: Linux-1.0-inline-asm uploaded)
Date: 27 Mar 1994 01:29:16 -0500

btf57346@uxa.cso.uiuc.edu (Byron Faber) writes:

>least.  As things are progressing now with IBCS2 and the talk on Libc and
>Qmagic executables, I don't see how we'll be able to have an 'old, stable
>kernel' at all.

Er, what?  QMAGIC has been in the kernel for quite some time before v1.0,
and libc is, well, libc, not the kernel.

>I think the rule of thumb is.  If you 'NEEEEEDDDD' stable software, buy a
>version that doesn't change for decades.  (not to start a flame war).  But

Or just use a version that is stable and don't upgrade.  It's not part of
the license that you have to upgrade, you know.

>I don't think we can halt/stop linux development to please a few people.

On the contrary: Linux development is proceeding to please quite a few people.

>So.. maybe I just don't like newbies who ask dumb questions (on c.o.l.help)?

Or oldbies who port stupid responses.

-- 
 _g,  '96 --->>>>>>>>>>   gt8134b@prism.gatech.edu  <<<<<<<<<---  CompSci  ,g_
W@@@W__        |-\      ^        | disclaimer:  <---> "Bow before ZOD!" __W@@@W
W@@@@**~~~'  ro|-<ert s/_\ nders |   who am I???  ^  from Superman  '~~~**@@@@W
`*MV' hi,ocie! |-/ad! /   \ss!!  | ooga ooga!!    |    II (cool)!         `VW*'

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

From: hjl@nynexst.com (H.J. Lu)
Subject: Re: 360k floppies not supported?
Date: 27 Mar 1994 06:50:30 GMT

Thomas Quinot (thomas@melchior.frmug.fr.net) wrote:
: Lloyd Miller (lloyd@lfmcal.cuc.ab.ca) wrote:
: : Alex Ramos (ramos@engr.latech.edu) wrote:

: : > I've been unable to mount or to use mtools on /dev/fd1, an
: : > old 360k drive. Is there anything I'm overlooking?

: : I am also having trouble using an old 360/pc floppy drive with linux.
: Double Density disks (5"1/4 360 Kb as well as 3"1/2 720 Kb) are *not*
                 ^^^^^
Did you mean to say "drives"?

: supported by Linux. And it *must* be in the FAQ, since I know it...


On the machine I am writing this article. I have a 3.5" 720Kb floppy
mounted in my 3.5" floppy drive.

H.J.

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

Crossposted-To: comp.os.linux.help
From: root@fusion.cuc.ab.ca (Superuser)
Subject: Re: Slackware 1.2.0/Linux 1.0 Problems
Date: Sun, 27 Mar 1994 06:37:02 GMT

bau1@cornell.edu (Bogdan Urma) writes:
> >"Mr. Unix" writes,
> 
> >Slackware 1.2.0 and Linux 1.0.  Good concept, poor execution-
> 
> >Several points:
> 
> >1- Is it just me or is emacs 19.22 buggy as hell in addition to being about
> >   2 times slower than version 18.59 that I'm using right now?  For example,
> >   I've had emacs 19.22 crash with a segmentation violation, and then it
> >   would refuse to work again, instead, on subsequent invocation just eating
> >   memory until virtual memory is exhausted.  The only way I've found to
> >   "fix" this is to reboot.  (this problem may be related to #3 , but I'm
> >   not certain).  Also, under X (both fvwm and olvwm), emacs 19.22 opens
> >   a window that's twice as wide as is needed, and everything you type is
> >   initially displayed by emacs as s o m e t h i n g  l i k e  t h i s.
> 
>     What does this have to do with Slackware 1.2.0 and Linux 1.0?? To me 
> this just sounds like a specific emacs problem for you. My emacs 19.22 works 
> fine, and it worked fine with many other Slackware releases and kernels. If 
> you want to reduce the emacs window under fvwm just edit the system.fvwmrc 
> file in the menu section to specify a geometry that you want and add emacs 
> to your menu.(If you want to!)

That's not what's happening- it seems that emacs thinks that the font
is twice as wide as it really is and is creating a window to suit.  I
think it might have something to do with not specifying *exactly*
which font I want it to use (ie, using the -*- convention in the font
name rather than specifying all the numbers).

Other problems such as the segmentation violation may be related to
kernel bugs or a bad compile of emacs in Slackware 1.2.0- I'm not
sure, which is why I've posted here.  Does anyone know what options
emacs 19.22 under Slackware 1.2.0 was compiled with?  It's over 1.3
megs in size where the comparable 18.59 binary with X11 support was
just over 600k.  Sort of gives credence to the errno joke: EMACS-
editor too big..  or maybe that should be EMAX...

> >5- The color 'ls' is just too slow for me, even if you turn off the color..
> >   first order of business was to replace the 'ls' binary with the old
> >   monochrome-only 'ls'.  Besides, "real" Unix types hate color.
> 
>  What do you mean by slow? Do you read while it scrolls?    

type 'ls' in a large directory, /usr/bin for instance, it takes much
longer before the file list starts with the color 'ls' than with the
old monochrome 'ls'.  It might be fine for you, but I consider it
annoying..  If you want to categorize your files, just use the '-F'
option.  I find it's much more intuitive to see a '/' after a name to
know it's a directory rather than see a name in red or whatever color
and try to remember what that means.  The colors also tend to
contribute to screen clutter and make searching for a particular file
in a listing harder because the colored entries call too much
attention to themselves- if the file you want happens to be one of the
colored entries, great, otherwise it just makes it that much harder to
find.  Each to his own though...

>  Also, if "real" Unix types hate color, why don't you run X in monochrome??

I sort-of do..  I've got a new "color" scheme in grey shades..

>   Have fun,
>   Bogdan
-- 
Christopher Lau- "Mr. Unix"    |     /       Fusion: Playing With Fire!
StarBright Research            |    / /      H + H -> He + 24 MeV
            --                 |   /_/_/_    "Bring back Trudeau!"
root,lauc@fusion.cuc.ab.ca     |____________ "This space for rent"

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

From: hpeyerl@sidney (Herb Peyerl)
Crossposted-To: comp.os.386bsd.misc
Subject: Re: Impressions: FreeBSD vs Linux
Date: 26 Mar 1994 20:46:22 GMT

Rob Newberry (rob-n@clark.net) wrote:
: IMHO, *BSD has a LONG way to go before its ready for users like me.  I

Perhaps that can be rephrased to say "I have a long way to go before
I'm ready for *BSD". :-)

: way to talk to my modem -- kermit is not there, I can't get tip
: to work, and there's just not any instructions anywhere.  Plus, when

*BSD is an operating system. kermit is an application. XFree86 is also
an application as is TeX and many other things.  Should every conceivable
application be shipped with the operating system?  

As far as 'tip' goes; typing "man tip" points you in the right direction
for setting up the "remote" and "phones" files.

: says, "Perhaps someone should tell us what all these options actually
: mean."  I thought that's what the *!@# FAQ was for!

Then complain to the maintainers of the FAQ.  That's surely not the fault
of *BSD.  The FAQ maintainers are volunteers also so it's hardly their
blame.

: It's not just the FAQ's, either.  The man pages are screwy.  I wanted
: to add some users.  In linux, "adduser" does the trick.  So I do a 
: "man adduser", and it says that this is a command for adding new users,

Wrong. It says (and I quote:)

----
ADDUSER(8)              NetBSD System Manager's Manual              ADDUSER(8)

NAME
     adduser - procedure for adding new users
----

"procedure"... Not "command". And reading further (yes; I know it's
a whole paragraph down but sometimes you need to have patience) you
see that it suggests you use "vipw(8)".

: did finally find out to use "vipw" (Thanks, O'Reilly), but that's
: just plain dumb.

No. It's not.

: Linux.  Linux installed on my system, and I added the users I needed,
: and they had POP accounts immediately, and I could run "DIP" to set

What if I don't *want* my users to have POP accounts?

--
hpeyerl@novatel.ca                           |  NovAtel Commnications Ltd.
hpeyerl@fsa.ca                               | <nothing I say matters anyway>
       <NetBSD: A drinking group with a serious computing problem!>

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

From: zenon@resonex.com (Zenon Fortuna)
Subject: Re: Linux
Date: Sat, 26 Mar 1994 22:57:21 GMT

In article <2mvugs$b2@geraldo.cc.utexas.edu> lilo@slip-12-5.ots.utexas.edu (lilo) writes:
>On 21 Mar 94 12:59:00 -0500, Melvin Parrish
>(Melvin.Parrish@f370.n109.z1.fidonet.org) wrote:
>
>> I was woundering if anyone knows where I can get the "complete"
>> Linux package? I would rather not get by ftp, because it takes too 
>> long. Maybe someone has it, and I can Freq. it  Thanks for any help.
>
>Melvin,
>
>Unfortunately, where you are located out in the, um, boondocks of Linux, as
>it were, sites tend not to have the latest material.  Stuff available via
>f'req from FidoNet sites tends to be a little uneven.  If there's any way at
>all you can ftp from ftp.cdrom.com or one of its mirror sites, I'd really
>recommend doing so....the material will be a lot more consistent and
>up-to-date....
>
>
>lilo

I you would like to get the SLACKWARE.1.2.0 on DAT (tar or cpio format)
I can make a copy and send it to you COD. It is about 70 MB in size
so floppies would be unconvenient ...

        zenon@resonex.com

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

Crossposted-To: news.groups
From: ddb@terrabit.uucp (David Dyer-Bennet)
Subject: Re: STRAW POLL RESULT: Linux groups automonitoring
Date: Sat, 26 Mar 1994 16:07:59 GMT

cgschott@psu.edu (Carl Schott) writes:

>Everyone in favor of this seems to be completely overlooking the
>intangible effects this campaign has had on the groups.  

I'm not overlooking it.  I simply have a different opinion from you.

The situation is clearly relatively bad.  The people best able to
answer questions are always the people with the most other things to
do with their lives.  They're first out when things get bad.

While the current argument is not helping any, I blame that on those
arguing against the proposal.  None of the arguments against that I've
seen seems to me to have the slightest merit -- until this one of
yours.

I'm new around here, a month or so, so your statements about Ian's
history are of some interest to me, and might indirectly indicate
possible problems coming up.  On the other hand, what Ian has said so
far doesn't seem to me compatible with what you've said.  One possible
hypothesis is that some of the earlier events happened as you
described, and Ian has learned some things since since then.
-- 
David Dyer-Bennet, proprietor, The Terraboard            4242 Minnehaha Ave. S.
ddb@network.com, lynxds.mn.org!terrabit                   Minneapolis, MN 55406
Don't waste your time arguing about allocating blame;           +1-612-721-8800
There'll be enough to go around.                            Fax +1-612-724-3314

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

Crossposted-To: news.groups
From: ddb@terrabit.uucp (David Dyer-Bennet)
Subject: What keywords to use
Date: Sun, 27 Mar 1994 05:08:08 GMT

damien@b63519.student.cwru.edu (Damien Neil) writes:

>At least let's get some discussion started about what keywords to use! I'm
>sick and tired of all this bickering. 

I think we need keywords in two dimensions: what technical area the
question is in (things like serial driver, swapping, slip, modems),
and what state the question and its answers is in (things like
question, new information, need more information, solution,
suggestion, desperate).  The problem with the second type is that
they probably need to be changed for each followup; that might present
a problem.  On the other hand, A lot of the filtering I'd like to do
involves the second class of information.

How about some really basic parameters?  I've been assuming that
multiple keywords should be used as appropriate, and I guess the above
structure implies a minimum of two, one from each class.  That could
be too complicated.  On the other hand, I'm not sure how much benefit
there'd be from a one-keyword scheme.  I can usually pick the basic
subject area out of the subject line pretty quickly anyway.
-- 
David Dyer-Bennet, proprietor, The Terraboard            4242 Minnehaha Ave. S.
ddb@network.com, lynxds.mn.org!terrabit                   Minneapolis, MN 55406
Don't waste your time arguing about allocating blame;           +1-612-721-8800
There'll be enough to go around.                            Fax +1-612-724-3314

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


** 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
******************************
