Subject: Linux-Misc Digest #855
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:     Wed, 23 Mar 94 10:13:16 EST

Linux-Misc Digest #855, Volume #1                Wed, 23 Mar 94 10:13:16 EST

Contents:
  Re: Opinions wanted about SCO-unix (vs AIX/Linux). (Bill Davidsen)
  Re: ethernet transmit timeout (Erwin Embsen)
  Internet Linux Machines (Brent E Paddon)
  HD sector size (Ian Radford (Mary Wood RA))
  Re: Linux Journal (Matthew Ian Gillard)
  Re: Mosaic 2.2 with FORMS? (The Last Gunslinger)
  Re: DOOM for X (Philip Brown)
  Re: STRAW POLL RESULT: Linux groups automonitoring (David Dyer-Bennet)
  *** PLEASE READ THIS BEFORE POSTING *** (misc-2.07) (Ian Jackson)
  Re: Prepare for DOOM (parody) (Alan Cox)
  Re: Wine status March 11, 1994 (Philip Brown)
  Looking for True BASIC to C source converter (William Gladnick)
  Re: [1.0] Linux, Comments (Alastair Neil)
  Re: eexpress under 1.0  (David MacRae)
  WANTED: Busmouse Information for HOWTO (Mike Battersby)

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

Crossposted-To: comp.unix.advocacy,biz.sco.general
From: davidsen@sixhub.tmr.com (Bill Davidsen)
Subject: Re: Opinions wanted about SCO-unix (vs AIX/Linux).
Reply-To: davidsen@tmr.com (bill davidsen)
Date: Wed, 23 Mar 1994 03:49:05 GMT

In article <2makdv$6nv@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
| >Does the c compiler under ODT 3 still have optimizing bugs?
| 
| Probably not.  If it did our locally compiled code would probably have
| stumbled across it by now.  Whatever rcc, cc, and icc are doing seems
| to be pretty safe optimizations only.

  I assume that you mean "generates incorrect code" and I agree, that
only happens when you use the -Oa (generate dubious code) option.
However, use of -CSON to get maximum speed can take a *lot* of memory,
such that I have a program which won't compile in 16MB RAM + 16MB swap
(home) but will on a server with 32+64. moreover it says something like
"Horrors, I'm out of memory, I'll turn off optimization and retry," then
turns off optimization, leaves -CSON set, and runs out of memory again.

  All good things said about icc are true, but the idea of making K&R
rather than ANSI the default behavior is somewhat hard to take these
days. And it points out lots of problems with the SCO include files,
some of which appear real.
-- 
Bill Davidsen, davidsen@tmr.com      |  C programming, PC based UNIX, data
    TMR Associates, +1 518-370-5654  |  acquisition, device drivers.
_____________________________________|______________________________________
New England Winter 93-94: Many are cold but few are frozen

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

From: erwin@nioz.nl (Erwin Embsen)
Subject: Re: ethernet transmit timeout
Reply-To: erwin@nioz.nl
Date: Wed, 23 Mar 1994 10:07:49 GMT

In article 94Mar22163016@clarity.princeton.edu, trafton@clarity.Princeton.EDU (Greg Trafton) writes:
>In article <1994Mar22.170332.24382@ED.RAY.COM> heiser@TDWR.ED.RAY.COM (Bill Heiser) writes:
>
>>In SLACKWARE 1.1.2 with kernel v1.0, the following occurs:
>
>>Mar 15 15:06:34 wpc18 kernel: eth0: transmit timed out, TX status 0xc, ISR 0x0.
>>Mar 15 15:06:34 wpc18 kernel: eth0: Possible network cable problem?
>>Mar 15 15:06:34 wpc18 kernel: eth0: Transmitter access conflict.
>
>>OR
>
>>Mar 22 08:12:15 wpc18 kernel: eth0: transmit timed out, TX status 0xc, ISR 0x0.
>>Mar 22 08:12:15 wpc18 kernel: eth0: Possible network cable problem?
>
>>When this occurs, the system is no-longer able to communicate with the
>>network, and the system needs to be rebooted.  I have pretty-much ruled
>>out a local hardware problem because the same symptoms occur on another
>>LINUX machine here.
>
>>This is a 486/33/16mb with a 3C503 card.
>
>>Has anyone else seen this?
>
>>Thanks in advance,
>
>Hmmm...  Very strange!  I've been working on a system with the 3c503
>for a while now and haven't had this problem...until last night.  Last
>night for the first time in a month I got this same message.  It had
>been working fine before, working since, so kind of weird.  In any
>case, I have seen this before and I also would be interested in
>finding out what is going on...
>
>>Bill
>>-- 
>>Bill Heiser   Work-> heiser@tdwr.ed.ray.com    Home-> bill@bhhome.ci.net 
>
>Greg Trafton
>(trafton@clarity.princeton.edu)


I reported the same problem about a week ago to Donald Becker, who implemented
the 3c503 driver. He came up with the following solution:

        Edit line 156 in file /usr/src/linux/drivers/net/8390.c
        and comment out the line:

            ei_local->interface_num ^= 1;       /*  Try a different xcvr. */

        and recompile the kernel.

I'll try to explain this (correct me if I'm wrong Donald). This piece of code
was included in order to auto configure the 3c503 card (switching between the
BNC and AUI connector). The point is that if it switches from BNC to AUI (due
to transmit time outs) for some reason it will never switch back.


Hope this helps,

Erwin.

---
Name      : Erwin Embsen                Email: erwin@nioz.nl
Department: BEWON (ERSEM Project)       Phone: +31 (0)2220 - 69424 (or 69300)
Institute : NIOZ, Texel - NL            Fax  : +31 (0)2220 - 19674


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

From: ci084@cleveland.Freenet.Edu (Brent E Paddon)
Subject: Internet Linux Machines
Date: 23 Mar 1994 11:13:21 GMT
Reply-To: ci084@cleveland.Freenet.Edu (Brent E Paddon)



Hi all,

Just wondering if anyone out there has a good list of Linux
machines that are available for logins on the internet?
especially ones that provide a shell or something.

Thanks heaps,
Brent


-- 
=========================================================================
 Brent Paddon       /     ci084@cleveland.freenet.edu
 01161636           /     itb531paddon@acacia.qut.edu.au
=========================================================================

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

From: ianr@cs.man.ac.uk (Ian Radford (Mary Wood RA))
Subject: HD sector size
Date: 23 Mar 94 10:41:06 GMT

I believe that PCs (IDE at least) format their harddrives with 512 byte
sectors. Since Linux has a block size of 1024 bytes, is there any way
to format a harddrive in this way. It occurs to me that it would both
increase disk capacity and enhance efficiency.

Ian

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

Subject: Re: Linux Journal
From: gillardm@latcs1.lat.oz.au (Matthew Ian Gillard)
Date: Tue, 22 Mar 1994 03:26:16 GMT

I am in Australia and I don't have mine yet..:-(

*waits*

--
Matthew I Gillard, 3rd Year Bachelor of Computer Systems Engineering 
School of Engineering, Faculty of Science and Technology
La Trobe University, Melbourne, Victoria, AUSTRALIA, 3083
E-Mail: gillardm@latcs1.lat.oz.au

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

From: roland@cac.washington.edu (The Last Gunslinger)
Subject: Re: Mosaic 2.2 with FORMS?
Date: 23 Mar 1994 11:08:18 GMT

In article <2mkk9j$ici@hearst.cac.psu.edu>,
>
>However, this will not fix the forms problem.  I have libc 4.5.21,
>XFree 2.1, and kernel 1.0.2 on my system.  Forms are still broken.
>
>The only way to type into a form is by holding down all 3 mouse buttons
>while you do so.  :(  Somebody said there's a bug in the current
>Motif libs for linux.
>

Also, once you start Mosiac, clone the window, then close the original. 
Forms should work in the second cloned window. I haven't a clue why this 
doesn't work for you all, I'm the one who compiled the Mosaic-2.2 bins on 
sunsite and they work perfectly for me (libc4.5.8, Motif-1.2.2, XF-2.0/1)

*shrugs* I guess there is a fix on sunsite now..
- liem

-- 
=======[roland@cac.washington.edu]=====[The Last Gunslinger]==================
Outside of a dog, computers are a man's best  | UCS Consulting
friend, inside a dog it's too dark to type.   | UW Ice Hockey 
http://topquark.cecer.army.mil/~roland/       | Linux/WWW/tcl/tk/LOTRmush

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

From: philb@cats.ucsc.edu (Philip Brown)
Subject: Re: DOOM for X
Date: 22 Mar 1994 20:53:14 GMT


In <1994Mar22.043659.17515@pdact.pd.necisa.oz.au> dbell@pdact.pd.necisa.oz.au (David I. Bell) writes:

>I think you are all forgetting that X11 is a MULTI-TASKING window system.
>Any particular client does not own the whole screen.


Really? I missed the part where it says that in the X11R5 release notes.

-- 
 ----------------------------------------------------------------------
Philip Brown, CIS major, UC Santa Cruz
Author of "kdrill", and "xmandel"
Winging my way out of academia soon...
philb@cats.ucsc.edu philb@soda.berkeley.edu

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

From: ddb@terrabit.uucp (David Dyer-Bennet)
Subject: Re: STRAW POLL RESULT: Linux groups automonitoring
Date: Wed, 23 Mar 1994 07:17:22 GMT

mlord@bnr.ca (Mark Lord) writes:

>In article <2mk21e$3dd@lyra.csx.cam.ac.uk> iwj@cam-orl.co.uk writes:
>...
>Yet another net.facist is born.

Ad hominem.  Clean up your act.

>>I think that this gives me a fairly clear mandate to go ahead; I'm not
>>going to apply the overmajority rules that apply to group creation.

>Really?  I came to exactly the opposite conclusion!

Well, two of the groups would have passed by the full voting
guidelines.  I don't think it's unreasonable to consider that a
"fairly clear mandate" for those groups.  Others passed by clear, but
smaller, majorities.  What it sounds like to me is you lost.  Deal
with it.

>>As I said during the discussion period, I've been convinced that
>>Subject line tags are more technically feasible than Keywords at the
>>moment (shame on you, newsreader authors).

>Sure, let's change the whole way usenet works for the sake of this shmuck.

Ad hominem, again.  It doesn't contribute anything to the discussion,
and tends to obscure any valuable points that might be forthcoming in
the ensuing discussion with the smoke and flames.  

And I don't understand what point you're trying to make, either.

>>I'll therefore arrange for the monitoring program to expect Subject
>>lines of the form
>>  Subject: [keyword] rest of subject

>A real pity this scheme ain't good enough for his own posts.

Since the keywords haven't been selected and the scheme hasn't been
put into place, I don't know what you expected.

>>Note that discussion of this probably belongs in news.groups;

>Logical.  Since maybe nobody will notice it until "too late" there. :)

And it's still the "right" place by my understanding of netiquette /
policy.  There's been considerable discussion here, and the straw poll
CFV was posted here.  It hasn't exactly been a stealth proposal!

>An "unmoderated" newsgroup is exactly that:  unmoderated.

And the proposal and straw vote was on implementing a new experiment,
something that was neither precisely unmoderated nor precisely
moderated.  I understand that you don't like it, but again this
assertion doesn't further your position.

>Get a life!

Hmmm; his attempt to reduce the time spent going through these
newsgroups (both by him and by the rest of us) somehow leads you to
infer that he requires more life?  The avowed purpose of his scheme,
after all, is to save all of us time.  Time to spend on our "lives",
or on important things like Linux :-)
-- 
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: ijackson@nyx.cs.du.edu (Ian Jackson)
Subject: *** PLEASE READ THIS BEFORE POSTING *** (misc-2.07)
Date: Wed, 23 Mar 1994 11:03:01 GMT

Please do not post questions to comp.os.linux.misc - read on for details of
which groups you should read and post to.

Please do not crosspost anything between different groups of the comp.os.linux
hierarchy.  See Matt Welsh's introduction to the hierarchy, posted weekly.

If you have a question about Linux you should get and read the Linux Frequently
Asked Questions with Answers list from sunsite.unc.edu, in /pub/Linux/docs, or
from another Linux FTP site.  It is also posted periodically to c.o.l.announce.

In particular, read the question `You still haven't answered my question!'
The FAQ will refer you to the Linux HOWTOs (more detailed descriptions of
particular topics) found in the HOWTO directory in the same place.

Then you should consider posting to comp.os.linux.help - not
comp.os.linux.misc.

Note that X Windows related questions should go to comp.windows.x.i386unix, and
that non-Linux-specific Unix questions should go to comp.unix.questions.
Please read the FAQs for these groups before posting - look on rtfm.mit.edu in
/pub/usenet/news.answers/Intel-Unix-X-faq and .../unix-faq.

Only if you have a posting that is not more appropriate for one of the other
Linux groups - ie it is not a question, not about the future development of
Linux, not an announcement or bug report and not about system administration -
should you post to comp.os.linux.misc.


Comments on this posting are welcomed - please email me !
--
Ian Jackson  <ijackson@nyx.cs.du.edu>  (urgent email: iwj10@phx.cam.ac.uk)
2 Lexington Close, Cambridge, CB4 3LS, England;  phone: +44 223 64238

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

From: iiitac@uk.ac.swan.pyr (Alan Cox)
Subject: Re: Prepare for DOOM (parody)
Date: Tue, 22 Mar 1994 15:38:08 GMT

In article <ARMB.94Mar18111001@hamsta.setanta.demon.co.uk> armb@setanta.demon.co.uk (Alan Braggins) writes:
> If you are going to be pedantic, there is no product called Xwindows.
> "Its a window system called X, not a system called X windows".
Ah yes of course 'Cross Windows' 8-)


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

From: philb@cats.ucsc.edu (Philip Brown)
Crossposted-To: comp.windows.x.i386unix,comp.os.386bsd.apps
Subject: Re: Wine status March 11, 1994
Date: 22 Mar 1994 20:58:03 GMT


In <1994Mar22.164834.8123@uk.ac.swan.pyr> iiitac@uk.ac.swan.pyr (Alan Cox) writes:
>In article <1994Mar20.183234.27732@mksinfo.qc.ca> pierre@mksinfo.qc.ca (Pierre Benard) writes:
>>and IBM's OS/2 for Windows. Maybe MS is realizing that letting people
>>run Windows apps. on something other than MSDOS is a good thing.


[sorry I have to reply through heresay, I missed the original article]

ON the other hand, I am happy to find out that apple is FINALLY
liscensing its system as "Apple/Macintosh Destop" or something.
Announcements were made yesterday or something that sun and apple have
signed agreements to do a nice port to sparcs, and I think other
manufacturers have things in the works.

HOPEFULLY, they will do a FULL port (unlike "WABI"), and get all the
multimedia stuff, audio, quicktime, etc, etc in there.

I'd MUCH rather have that, than an MS windoze interface.

-- 
 ----------------------------------------------------------------------
Philip Brown, CIS major, UC Santa Cruz
Author of "kdrill", and "xmandel"
Winging my way out of academia soon...
philb@cats.ucsc.edu philb@soda.berkeley.edu

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

From: wglad@new-orleans.NeoSoft.com (William Gladnick)
Subject: Looking for True BASIC to C source converter
Date: 21 Mar 1994 21:06:06 -0600

Does anyone know where I can find a True BASIC to C source converter
for Linux? True Basic is very slow :^)
 
                                          
____
William Gladnick
wglad@new-orleans.neosoft.com


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

From: ajn@resumix.portal.com (Alastair Neil)
Subject: Re: [1.0] Linux, Comments
Date: 22 Mar 94 16:59:34 GMT
Reply-To: ajn@resumix.portal.com


->w6f192@rick.cs.ubc.ca (Shawn Jeremye Smith) writes:
->
->>The Xmodmap call I was using no longer works and has to be
->>done manually??  Terminal setting in rxvts seem to be broken as backspace and
->>delete chars no longer get interpreted properly.  I am recompling the kernel
->>to try and fix this.  The rxvt problem seem to stem from the new libc -21.
->>Recompiling seems to solve the problem, altho remote telnets no longer 
->>set terminal types correctly. 
->
->XFree86-2.1 tries to initialise the X key map from the current Linux keymap.
->Often this will mean that your Xmodmap call no longer works.
->For example, if you make your Backspace key produce 0177 (Delete) under Linux
->then the X initialisation code already does the equivalent of
->      xmodmap -e "keysym BackSpace = Delete"
->and if you try to do this yourself as well, it will fail because there is
->no keysym Backspace anymore.
->So, it seems you need to adapt (or possibly just remove) your xmodmap calls.

Sorry to come in at the end of a thread, I posted a query about something
similar to comp.os.linux.help some days ago - but got no response. My 
problem is that Xterm key bindings for my keypad no longer work after going
to 1.0. I imagine this is a related problem. Can anyone bring me up to 
speed about the cause and/or possible solutions?


Thanks Alastair.


---
+-----------------------------------------------------------------------------+
|..Alastair Neil.......(44)-0(206-872861).......[ajn@plasparc3.essex.ac.uk]...|
|....Visne scire quod credam? Credo luctationes omnes praestitutas esse!......|
+-----------------------------------------------------------------------------+



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

From: dmacrae@hocomms.demon.co.uk (David MacRae)
Subject: Re: eexpress under 1.0 
Reply-To: Dmacrae@hocomms.demon.co.uk
Date: Wed, 23 Mar 1994 12:35:09 +0000

In article <Cn2AJn.L17@hermes.hrz.uni-bielefeld.de> carsten@techfak.uni-bielefeld.de writes:

>Hi
>A week ago somebody had problems installing a etherexpress
>card with pl15.
>There was no reply, or I missed it. 
>I have to install the eexpress driver by
>myself and would like to know if there is a real problem
>in 1.0 with that card.
>    Thanks 
>         carsten        carsten@phys1.uni-bielefeld.de
>      
>
I have to install an eexpress card myself, (I assume that you mean
the Intel EtherExpress card, Oh I hope you do).
I've got version 1.0 but can't find the source file for this card. 
Could soeone please point me in the right direction.

Ta
-- 
Dave MacRae                      |The views expressed here are mine and mine
John Menzies (UK) Ltd            |alone and do not reflect the views of my
Edinburgh                        |employers in any way.
Scotland                         |
dmacrae@hocomms.demon.co.uk      |

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

From: mike@starbug.apana.org.au (Mike Battersby)
Subject: WANTED: Busmouse Information for HOWTO
Date: 23 Mar 1994 23:34:05 +1000

  I'm trying to upgrade the Microsoft Busmouse mini-HOWTO to a complete
Busmouse HOWTO consisting of information for all of the varied types of
busmice supported under Linux.  If you've got a working busmouse under
Linux, I would greatly appreciate if you would read the mini-HOWTO at the
end of this message and mail me any corresponding information regarding
your mouse type.

cheers

 - Mike

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

            The Microsoft Busmouse mini-HOWTO v0.3, 26 Feb 94
              by Mike Battersby <mike@starbug.apana.org.au>

INDEX

        0.      Introduction
        0.1     Disclaimer
        0.2     Where to find help
        0.3     Feedback
        0.4     Acknowledgements

        1.      Getting things going
        1.1     How do I know if I have a Microsoft busmouse?
        1.2     Setting the mouse interrupt.
        1.3     Compiling the kernel
        1.4     /dev/mouse
        1.5     Testing your mouse
        1.6     Using selection
        1.7     Using Xfree86
        1.8     Xfree86 and selection

==============================================================================
0.      Introduction

        This document is a guide to getting your Microsoft busmouse working
        with Linux.  I've written this in the hope that the ten people a
        week who post "how do I get my busmouse to work" questions in
        comp.os.linux.announce will read it first, though I won't be
        holding my breath.  Busmouse support has been in the kernel for as
        long as I can remember, and hasn't changed in a long time (at least
        as of now, 0.99.15), so this document should work with any version
        of Linux you're likely to have.  In the near future this document
        will likely be merged into a full busmouse howto.

0.1     Disclaimer

        The information in this document is correct to the best of my
        knowledge, but there's a always a chance I've made some mistakes,
        so don't follow everything too blindly, especially if it seems wrong.
        Nothing here should have a detrimental effect on your computer, but
        just in case I take no responsibility for any damages incurred from
        the use of the information contained herein.

        Microsoft(R) is a Trademark of Microsoft Corporation.

0.2     Where to find help

        If you've pored over this document hundreds of times and still can't
        get your mouse to work, feel free to contact me any time at
        <mike@starbug.apana.org.au> and I'll see if I can help you out.
        The comp.os.linux.help newsgroup is the appropriate forum for
        discussion and/or questions regarding mice - please don't post
        questions to other groups, and especially don't crosspost
        questions to two or more of the Linux groups, they are more than
        cluttered enough as it is!

0.3     Feedback

        If you find any mistakes in this document, have any comments about
        its contents or an update or addition, send them to me at the
        address listed in section 0.2.

0.4     Acknowledgements

        The following people have been invaluable in the production and
        updating of this mini-HOWTO.

            Daniel R Barlow             <Daniel.Barlow@sjc.ox.ac.uk>
            Thomas B. Fox               <lestat@deeptht.armory.com>


==============================================================================
1.      Getting things going

1.1     How do I know if I have a Microsoft busmouse?

        Microsoft mice are relatively easy to recognize.  They are two
        button mice with the left button bigger than the right, a rounded
        "ergonomic" shape that I have been told looks like a bar of "dove"
        soap (at least to Americans :-), and in most cases the word
        "Microsoft" written on the top.  If you follow the mouse cord to
        the back of the machine and it ends in a small round detachable
        plug, about 9mm in diameter, with 9 pins and a notch in one side,
        its a good bet you've got a Microsoft busmouse.  (Note: I have
        heard that there are new teardrop shaped Microsoft busmice. If
        anyone has one of these beasties, please get in touch with me.)

1.2     Setting the mouse interrupt

        First things, you'll need to know which interrupt number your
        mouse is using, and make sure it doesn't conflict with any other
        peripherals you have installed.  If you open up your computers
        case and look at the card which your mouse plugs into, you should
        notice a block of jumpers near the bottom middle of the card
        labeled "INTERRUPT" with positions for interrupt (otherwise
        known as IRQ) numbers 2,3,4 and 5.  You should make sure that
        your mouse is not trying to use the same interrupt as any of your
        other devices, and change the interrupt by moving the jumper to an
        unused interrupt setting if it does.

        ***************************************************
        ***     MAKE SURE YOUR COMPUTER IS TURNED OFF   ***
        ***     BEFORE CHANGING THE JUMPERS AROUND.     ***
        ***************************************************

        In most cases IRQ4 is used for the first serial port (/dev/ttyS0),
        IRQ3 for the second (/dev/ttyS1), and IRQ5 for some SCSI adaptors.
        Check the documentation for all your peripherals to see which
        interrupt they use.  In my experience, IRQ2 seems to cause the least
        hassle in most cases.

1.3     Compiling the kernel

        In order for your Microsoft busmouse to operate correctly you
        will need to recompile your kernel with the busmouse support
        compiled in.  Change to your kernel directory (here assumed to
        be '/usr/src/linux') and do a

            make config

        and answer 'y' to the 

            Microsoft busmouse support (CONFIG_MS_BUSMOUSE) [n]

        question.
        Next, edit the file '/usr/src/linux/include/linux/busmouse.h',
        and change the line which says

            #define MOUSE_IRQ               5

        to reflect the interrupt number for your mouse (see section 1.3
        for details on finding your interrupt number).  Due to the
        vagaries of the PC architecture, if you have set your mouse to
        use interrupt 2, you must set the #define to use interrupt 9.

        Examples

            For a mouse on interrupt 3, you should change the line to
            read

            #define MOUSE_IRQ               3

            For a mouse on interrupt 2, you should change the line to
            read

            #define MOUSE_IRQ               9

        Next, compile your kernel as per the instructions which come
        with it, and boot from the new kernel.  You should now have
        the busmouse support correctly compiled in.

1.4     /dev/mouse

        The Microsoft busmouse device is accessed through the
        /dev/bmousems device (on some machines you may have a
        /dev/importbm instead - if so, simply substitute that for
        bmousems for the rest of this section), major 10 minor 2.  If
        you don't have such a device, you can make one by changing to
        the /dev directory and executing the following command as 'root'.

            mknod /dev/bmousems c 10 2

        You should then make a symbolic link from this device to
        /dev/mouse, and use that to refer to the mouse from then on. The
        link can be made with the following command (again as 'root')

            ln -fs /dev/bmousems /dev/mouse

1.5     Testing your mouse

        Get the file 'selection-1.5.tar.gz' from your local Linux ftp
        site and compile the program 'test-mouse' within it, according
        to the instructions (all you should need to do is type 'make
        test-mouse').  Run the program like this

            test-mouse -t bm

        If your mouse is working correctly, you should be able to
        paint on the screen by holding down the right or left mouse
        button and dragging the mouse.  Push both mouse buttons together
        to exit the program.

1.6     Using selection

        Selection is a program which allows you to do mouse based 'cut-
        and-paste' between virtual console under Linux.  Selection can
        be found as the file 'selection-1.5.tar.gz' at your friendly
        Linux FTP site (such as sunsite.unc.edu), and contains instructions
        for getting it compiled.  Once compiled, selection should be run
        like this:

            selection -t bm &

        You should then be able to cut and paste text between virtual
        consoles using the mouse buttons.  Read the documentation with
        selection, or do a 'man selection' for more information on how
        to operate it.

1.7     Using Xfree86

        To use your Microsoft busmouse under Xfree86, your Xconfig file
        should contain the following lines which pertain to mouse support.
        You should comment out any other mouse related lines.

            Busmouse        "/dev/mouse"
            Emulate3Buttons

        To emulate the use of the middle mouse button on three button
        mice, press both mouse buttons simultaneously.

1.8     Xfree86 and selection

        Unlike serial mice, you cannot share busmice between processes.
        This means you will have to kill any copies of 'selection' (see
        section 1.6) you have running before you start up Xfree86.  If
        you try to run X with selection running, you will get errors
        like the following

            Fatal server error:
            Cannot open mouse (Device or resource busy)

        The following script is a short wrapper around selection which
        will record its process ID in '/etc/selection.pid'.

        ----------------------------- CUT HERE ----------------------------
        #!/bin/sh
        #
        # startselection        A selection wrapper script to save the pid.
        #

        echo $$ > /etc/selection.pid
        exec /usr/sbin/selection $*

        ----------------------------- CUT HERE ----------------------------

        I have this script installed as 'startselection' in /usr/sbin
        (the same directory as selection), and my rc.local file includes
        the following line

        /usr/sbin/startselection -t bm &
        
        When you are starting up X, you can easily kill selection by
        doing

            kill `cat /etc/selection.pid` && rm -f /etc/selection.pid

        (the last part being to remove the pid file, since we aren't using
        it any more).  You will probably want to add this to your startx
        script or some other appropriate place (such as an rc.* file).

=============================== END mini=HOWTO ===============================
-- 
  Mike Battersby   <mike@starbug.apana.org.au>   <mib@bruce.cs.monash.edu.au>
          CompSci honours student, Linux user and part time beggar.
           GCS d-(--) p c++ l++(+++) u+ e+ m+@ s+/- n+(---) h--(*)
                           f(+) !g w+ t++@ r(+) y?

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


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