Subject: Linux-Development Digest #787
From: Digestifier <Linux-Development-Request@senator-bedfellow.MIT.EDU>
To: Linux-Development@senator-bedfellow.MIT.EDU
Reply-To: Linux-Development@senator-bedfellow.MIT.EDU
Date:     Fri, 3 Jun 94 11:13:09 EDT

Linux-Development Digest #787, Volume #1          Fri, 3 Jun 94 11:13:09 EDT

Contents:
  Re: 1.1.16 kernel doesn't want to boot! (Eugene Tyurin)
  Re: Frustrated with new kernels (Thomas Heiling)
  Re: Logitech Scanner (Re: Twain Scanner) (Giuseppe Zanetti)
  Solaris binaries? (Johannes Schindlin)
  Let's rename v1.0.9! [Was: Frustrated with new kernels] (Bjorn Ekwall)
  Re: Regarding the rlogin security hole (John F. Haugh II)
  Re: iscntrl(128) thru iscntrl(255) (Joel M. Hoffman)
  Re: Logitech Scanner (Re: Twain Scanner) (Steven M. Palm)
  Re: Let's rename v1.0.9! [Was: Frustrated with new kernels] (Byron Faber)
  Re: Let's rename v1.0.9! [Was: Frustrated with new kernels] (Thomas Heiling)
  1.1.17 and no networking won't compile (Samson H. Lee)
  Colorado Trakker 250 (The Fool On The Hill)
  Re: Frustrated with new k (Arthur Tateishi)
  Re: Busmouse on IRQ 2 works only with driver on IRQ 9 (Rob Janssen)
  linux bug or HP bug? (with solution) (Peter Parzer)

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

From: gene@insti.physics.sunysb.edu (Eugene Tyurin)
Subject: Re: 1.1.16 kernel doesn't want to boot!
Date: 03 Jun 1994 05:44:22 GMT

>>> "RJ" == Rob Janssen <rob@pe1chl.ampr.org> writes:

RJ> Probably you did not run LILO, or did not run it properly.  See
RJ> the LILO documentation.

Nope, I did! At least what I did was correct for all other versions
(right now I'm succesfully running pl17). Here is one interesting
e-mail response that I've got:

======>
From: romano@pimac2.iet.unipi.it (Romano Giannetti)

It happen to you only with new kernels? We here had a problem with the
same symptom, but happened with kernels 1.0.9 and 1.1.6 and 1.0.0, the
90% of the time. At the end it was a (not better understand) hardware 
problem between the ide controller and the mother board.
<------

Rather weird, isn't it?

--
--                       MIME mail is welcome                      --
Active Ingredient: Eugene Tyurin  <gene@insti.physics.sunysb.edu>
                   http://insti.physics.sunysb.edu:80/~gene/plan.html
                   Bio-degradable, made of 100% recycled substance.
                   Handle with care: fragile, toxic and flammable.



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

From: tom@wpzd07.pzlc.uni-wuerzburg.de (Thomas Heiling)
Subject: Re: Frustrated with new kernels
Date: 3 Jun 1994 10:13:24 GMT

Jay Allen (jay@caeser.geog.pdx.edu) wrote:

: I thought that 1.0 was the only "production" kernel out, and that 1.1* was
: considered Experimenters/developers only?  Is there some functionality that
: you need from 1.0+ kernels?

  Two things come to my mind : 8 k NFS and the cluster-code.

  My main machine *is* for testing and trying, and I don't  worry
  much about reliablity - for the system, but it would be nice if
  user programs would be stable.
  And it is ( from time to time ) fun to try new ideas.
  I tried the ide-patches,pc-speaker patches and the accounting patches.
  And I try to look for new ideas in the
  kernel ( I search for a HP27252A Ethernet Driver ), but if I don't
  find documentation, what programs will not run, it's frustrating.
  
  BTW With Kernel 1.1.17 it looks good...
  This machine here ( a very small 386 with 4 MB ) must be stable,
  because it is our Internet machine.

--
===================================================
Thomas Heiling Pharmacist & Doctorate at 
Pharmazeutisches Institut Uni Wuerzburg - Germany 
Email phar006@rzbox.uni-wuerzburg.de (HP-UX)
      tom@wpzd07.pzlc.uni-wuerzburg.de (Linux)
or phar006@vax.rz.uni-wuerzburg.de ( VAX )
===================================================

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

From: beppe@maya.dei.unipd.it (Giuseppe Zanetti)
Subject: Re: Logitech Scanner (Re: Twain Scanner)
Date: 3 Jun 1994 12:29:27 +0200

In article <1994Jun2.132603.21781@excaliber.uucp>,
Joel M. Hoffman <joel@wam.umd.edu> wrote:
>Hmm.  I'm tyring to use the logi32 driver with my scanman256.  The
>driver can talk to the scanner, but something's going slightly wrong.
>Each scanned line is shifted to the right, so that a straight vertical
>line ends up diagonal.  I suspect the scanman256 is sending protocol

with my Scanman32 some lines only are left badly shifted. I think that is
a problem with interrupt or my (slow ??? a 386/33) machine.

Is here someone with this problem ? A solution ?

Giuseppe


-- 

                                 Giuseppe Zanetti


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

From: dscho@cip.informatik.uni-wuerzburg.de (Johannes Schindlin)
Subject: Solaris binaries?
Date: 3 Jun 1994 11:16:47 GMT

Hi!
Is it possible to run Solaris binaries on Linux?
Thanx,
Dscho.


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

From: bj0rn@blox.se (Bjorn Ekwall)
Subject: Let's rename v1.0.9! [Was: Frustrated with new kernels]
Date: 3 Jun 94 11:34:01 GMT

There are a lot of people that haven't been able to understand
the different aims of 1.0.X and 1.1.X, but beleive that the
kernel with the "highest" sequence number is meant for everyone.

I have a suggestion:

Let us rename 1.0.9 to 1.2.0!

This way, those who haven't read the notices from Linus et al
will go for that version, and stay away from 1.1.X...
That would make everyone happy, wouldn't it?  :-)


Bjorn Ekwall == bj0rn@blox.se

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

From: jfh@rpp386 (John F. Haugh II)
Subject: Re: Regarding the rlogin security hole
Reply-To: jfh@rpp386.cactus.org (John F. Haugh II)
Date: Fri, 3 Jun 1994 03:05:59 GMT

In article <2shn88$apc@kralizec.zeta.org.au> nick@kralizec.zeta.org.au (Nick Andrew) writes:
>In <CqA2AL.4LG@cichlid.com> aab@cichlid.com (Andy Burgess) writes:
>
>>Are we vulnerable if we are using tcpwrapper to restrict rlogin and telnet
>>access?
>
>Yes - to all sites which are allowed to rlogin in ...

Here is the official patch for lmain.c.  It should close all of the
holes that have been posted and a few that haven't.  The patch has
been tested to insure that it can be applied to every version of
lmain.c that has ever existed.
--
*** lmain.c.orig        Thu Jun  2 22:01:26 1994
--- lmain.c     Thu Jun  2 22:01:38 1994
***************
*** 370,375 ****
--- 370,376 ----
        char    tty[BUFSIZ];
        int     reason = PW_LOGIN;
        int     retries;
+       int     arg;
        int     failed;
        int     flag;
        int     subroot = 0;
***************
*** 388,393 ****
--- 389,405 ----
         */
  
        name[0] = '\0';
+ 
+       /*
+        * Check the flags for proper form.  Every argument starting with
+        * "-" must be exactly two characters long.  This closes all the
+        * clever rlogin, telnet, and getty holes.
+        */
+ 
+       for (arg = 1;arg < argc;arg++) {
+               if (argv[arg][0] == '-' && strlen (argv[arg]) > 2)
+                       usage ();
+       }
  
        /*
         * Get the utmp file entry and get the tty name from it.  The
-- 
John F. Haugh II  [ NRA-ILA ] [ Kill Barney ] !'s: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 251-2151 [GOP][DoF #17][PADI][ENTJ]   @'s: jfh@rpp386.cactus.org
 There are three documents that run my life: The King James Bible, the United
 States Constitution, and the UNIX System V Release 4 Programmer's Reference.

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

From: joel@wam.umd.edu (Joel M. Hoffman)
Subject: Re: iscntrl(128) thru iscntrl(255)
Date: Fri, 3 Jun 1994 12:18:52 GMT

>>I notice that iscntrl returns true for characters 128 through
>>255, while under, say, SunOS or IRIX the same function returns
>>false.  Who is correct?  Are these really control characters?
>
>According to ANSI X3.159-1989: "... the term _control character_
>refers to a member of an implementation-defined set of characters
>that are not printing characters."  And in an accompanying
>footnote mention: "In an implementation that uses the seven-bit
>ASCII character set, ... the control characters are those whose
>values lie from 0 (NUL) through 0x1F (US), and the character 0x7F
>(DEL)."
>
>So, if the character set for Linux/gcc (in the C locale) is
>defined to be 7-bit ASCII then Linux seems to go against the
>recommondation of the ANSI C standard. 

I regularly program with 8-bit strings and char. constants in C under
Linux.  The high bits are used for Hebrew.  Most s/w under Linux
(including GCC) seems to work fine with 8bit char. strings, so it
seems that iscntrl should be false for those high chars.

-Joel
(joel@wam.umd.edu)


-- 
=============================================================================
|_|~~ Germany, Europe. 1943.    "The diameter of the bomb was 30 centimeters,
__|~| 16 Million DEAD.           and the diameter of its destruction, about 7
                                meters, and in it four killed and 11 wounded. 
 cnc  Bosnia, Europe. 1993.     And around these, in a larger circle of  pain
 cnc  HOW MANY MORE?          and time,  are scattered two  hospitals and one
                          cemetery.   But the young woman who was  buried  in
                    the place from where she came, at a distance of more than
             than 100 kilometers, enlarges the circle considerably.   And the 
      lonely man who is mourning her death in a distant  country incorporates
into the circle the whole world.  And I won't speak of the cry of the orphans
that reaches God's chair and from there makes the circle endless and godless."
=============================================================================
     Tell Clinton to stop the genocide:  president@whitehouse.gov

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

From: smp@agape.sol.net (Steven M. Palm)
Subject: Re: Logitech Scanner (Re: Twain Scanner)
Date: Wed, 01 Jun 94 22:20:07 GMT

In article <1994May30.233515.20383@pertron.central.de> keichwa@gwdg.de writes:
>
>module `logi32' (3 pages @ 0x01818000) created
>initializing module `logi32', 8928 (0x22e0) bytes
>  init entry @ 0x0181a0d4, cleanup entry @ 0x0181a1c4
>LOGITECH handheld scanner driver  version 0.1a
>Scanner-interface is incompatible.
>logi32.c: scanner interface not found

 This would indicate to me that the interface for your ScanMan 256
 is not compatible with the logi32 software.   Neat how that's
 worded to avoid pointing fingers at software, huh? :)

>And when I try it again:
>
>module `logi32' (3 pages @ 0x01818000) created
>initializing module `logi32', 8928 (0x22e0) bytes
>  init entry @ 0x0181a0d4, cleanup entry @ 0x0181a1c4
>LOGITECH handheld scanner driver  version 0.1a
>logi32.c: cannot register major number

 This might indicate that the module isn't cleaning up properly.
 I would "assume" that you should get the same error message both
 times, unless the module somehow loaded itself the first time, and
 requires you to remove it before attempting a second load.

>Another question: Is there any OCR oder grafik scanner software?

 I haven't seen any, but I don't see much from my connection.  If
 anyone knows of some that will/might work with the logi32 driver,
 please post.


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

From: btf57346@uxa.cso.uiuc.edu (Byron Faber)
Subject: Re: Let's rename v1.0.9! [Was: Frustrated with new kernels]
Date: 3 Jun 1994 12:52:29 GMT

bj0rn@blox.se (Bjorn Ekwall) writes:

>There are a lot of people that haven't been able to understand
>the different aims of 1.0.X and 1.1.X, but beleive that the
>kernel with the "highest" sequence number is meant for everyone.

>I have a suggestion:

>Let us rename 1.0.9 to 1.2.0!

>This way, those who haven't read the notices from Linus et al
>will go for that version, and stay away from 1.1.X...
>That would make everyone happy, wouldn't it?  :-)


>Bjorn Ekwall == bj0rn@blox.se

I say let them mess around in their own ignorance.

Byron Faber
-- 
`Playing this disk at loud volume may permanently damage your speakers or
other sound components.'                                -LFO
                b-faber@uiuc.edu & http://www.cen.uiuc.edu/~bf11620/

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

From: tom@wpzd07.pzlc.uni-wuerzburg.de (Thomas Heiling)
Subject: Re: Let's rename v1.0.9! [Was: Frustrated with new kernels]
Date: 3 Jun 1994 13:09:11 GMT

Bjorn Ekwall (bj0rn@blox.se) wrote:
: There are a lot of people that haven't been able to understand
: the different aims of 1.0.X and 1.1.X, but beleive that the
: kernel with the "highest" sequence number is meant for everyone.
: I have a suggestion:
: Let us rename 1.0.9 to 1.2.0!

  A very good Idea :-)
  
: This way, those who haven't read the notices from Linus et al
: will go for that version, and stay away from 1.1.X...
: That would make everyone happy, wouldn't it?  :-)

  The notice was from Alan Cox, and it was hard to find.
  Here it is again for the new NET3-code with Kernels > 1.1.xx:

iiitac@uk.ac.swan.pyr (Alan Cox) writes:

>The NET3 code is in the current kernel. In addition as of 1.1.13 its a lot
>faster over unreliable links. You'll be delighted to know that apart from
>net032d, bootpc and dosemu no other programs need replacing to go from 1.0
>to 1.1.13. bootpc will even continue to work just wont recompile until you
>get the new one.

>'The' archive for net3 code is sunacm.swan.ac.uk:/pub/Linux/Networking. It
>is mirrored on sunsite.unc.edu. 

 If you missed this post, you had a hard time with new Kernels.
 
 Hope this helps someone.
 Thomas
--
===================================================
Thomas Heiling Pharmacist & Doctorate at 
Pharmazeutisches Institut Uni Wuerzburg - Germany 
Email phar006@rzbox.uni-wuerzburg.de (HP-UX)
      tom@wpzd07.pzlc.uni-wuerzburg.de (Linux)
or phar006@vax.rz.uni-wuerzburg.de ( VAX )
===================================================

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

From: shl0@ihd117d.CC.Lehigh.EDU (Samson H. Lee)
Subject: 1.1.17 and no networking won't compile
Date: Fri, 3 Jun 1994 12:58:31 GMT

I applied patch17 yesterday and tried recompiling the kernel.  I had
been including network support for TCP/IP and SLIP but decided to
remove network support until I really needed it.  (My university is in
the process of setting a SLIP server, but it's not ready yet.)  So I
tried leaving it out when I ran 'make config'.  I then ran 'make
mrproper' and 'make dep'.  Finally, I ran 'make zImage'.  After an
hour of compiling (I on a 486SX-25 w/4MB ram) I got an error that
"_dev_init" and "_???" (another symbol) were not defined.  I narrowed
it down to function calls in socket.c to functions defined in dev.c
which was not compiled because networking was disabled.

I've been applying patches since 1.1.13 and only have two additional
patches:  apm.diff and ide20.patch.  Before 1.1.13 I ran 1.0.8
distributed with Slackware 1.20.  On 1.0.8 I could compile without
networking support.  Since 1.1.13 I decided to inlcude networking
support until now.  So I don't know when this broke or if the apm.diff
or ide20.patch patches are the problem.

Anybody out there know what's the problem?  Let me know if this is
unclear and I'll try to explain things in more detail.  Thanks for any
and all help.

Sam.
=====
shl0@lehigh.edu
Tell him that Dr. Fleischman is the kind of enterprising, young
professional who's chosen to stake his claim right here on the 
banks of the Alaskan Riviera.
   Tell him I'm being held against my will.
                                Maurice and Joel to businessmen (1.4)
                                Northern Exposure

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

From: emrys@cellar.org (The Fool On The Hill)
Subject: Colorado Trakker 250
Date: Fri, 03 Jun 94 07:24:24 EDT


        Does a driver exist to allow me to access my Trakker?  If so, could
I please get a pointer to it?  If not, why?  Is it _that_ difficult to
access the tape on the parallel port?  Hell, if MS can do it, we oughta be
able to!!

        Mitch

Mitch Gorman                                    emrys@cellar.org

               "...And if we forget how to breathe
                This is where we live
                We'll paint the ending in ourselves"

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

From: ruhtra@turing.toronto.edu (Arthur Tateishi)
Subject: Re: Frustrated with new k
Date: 3 Jun 94 00:42:42 GMT

In article <2slqgh$6e@charm.magnus.acs.ohio-state.edu>,
Elaine Walton <ewalton@magnus.acs.ohio-state.edu> wrote:
>What I wanted was someone considerate enough to compile a package BEFORE
>gzip'ing it into a package.  I know that these altruistic developers are
>doing this on their own time--and I am truly grateful.  However, if they
>want other developers--like myself, I suggest that a minimum set of
>requirements be met before making it public.  Compilability comes to mind.
>I mean, how am I supposed to test the work if I can't run it.

I would doubt that very much. They compile and do some tests before
releasing. However, if you don't have the same version of the libraries,
compiler, possibly some odd piece here or there then you will have
problems. Documentation for just about everything DOES exist is some
form or other someplace and prospective developers should probably
join a relevant mailing list for two weeks before starting.

The Linux groups have also become rather cluttered over time so the
people who can help you will sometimes/often miss a relevant post.  I
don't think there's a simple solution for any of this. However, I do
believe many people could use some more patience. My other gripe with
many posters is the "I'm a complete Unix newbie. Please help!" types
that don't take the time to go out and read a unix book first before
jumping into Linux.

I point to the recent fellow who had trouble with serial ports going
from v1.0.0 to v1.1.16. After the NUMEROUS posts indicating that
the v1.1.* kernels are the *bleeding* edge (I emphasize the _bleeding_
part) releases, he should expect to do some investigation on his own.
First off, it would be nice to at least narrow things down to one
patch level of changes. My answering machine broke going from 99pl15h
to 99pl15i. I localized the code, waited for other problem reports and
later found some bugs in my own code that surfaced with the newer
kernel.

I'm not singling you out as out of line but I don't think your
statement quoted above is fair. If everyone released things by adding,
"It's in rough shape but at least it works for me" would you feel any
better?

arthur
-- 
Choices don't scare me. However, a lack of choices does.
Arthur Tateishi                           ruhtra@turing.utoronto.ca

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Busmouse on IRQ 2 works only with driver on IRQ 9
Reply-To: pe1chl@rabo.nl
Date: Thu, 2 Jun 1994 17:37:20 GMT

In <klaus.472.2DED8D29@mail.sz.etc.tu-bs.de> klaus@mail.sz.etc.tu-bs.de (Klaus Troja) writes:

>Hi there!

>I have got an ATI Bus Mous on a Graphics Vantage. The driver sources for bus 
>mice are set for IRQ 5. I changed them to IRQ 2 without success.
>You have to set it to IRQ 9 in the driver to get the mouse working. Because of 
>the cascaded two Interrupt Controllers IRQ 2 on the first refers to IRQ 9 on 
>the second controller which is asked first.

That is true for all uses of IRQ 2...  But most drivers automatically assume
you mean '9' when you say '2'.
As a general rule, always specify '9' when you have jumpered a card
for IRQ 2, it won't hurt.

Rob
-- 
=========================================================================
| Rob Janssen                | AMPRnet:   rob@pe1chl.ampr.org           |
| e-mail: pe1chl@rabo.nl     | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU     |
=========================================================================

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

From: fc4@aixfile1.urz.uni-heidelberg.de (Peter Parzer)
Subject: linux bug or HP bug? (with solution)
Date: 3 Jun 1994 13:33:07 GMT



I had the problem that the lp driver would not recognize if my
HP LaserJet 4p was power off. I solved this problem, at least for
the polled version of the driver. The key of the problem was that
the printer returned as state 0x87 when power off (state means
the result of LP_S(minor)). The linux lp driver takes this as OK
and assumes that the char was printed. I dont know if this is a bug
in the lp driver or if this is a problem with HP since I have no
idea about the official specifications of line printers.

Another curious thing is that my HP deskjet 550c somtimes returns
0x87 and sometimes returns 0x4f (line-off) when power-off.

Anyhow, with a dirty hack I solved this problem for me (I am using
1.0.8, but I think the lp driver does not change very much, so this
hack should work with other versions too). I replaced lines 56-57 of
drivers/char/lp.c (function lp_char_polled())

     } while(!(status & LP_PBUSY) && count < LP_CHAR(minor));
     if (count == LP_CHAR(minor)) {

to

     } while(!(status & LP_PBUSY) && count < LP_CHAR(minor));
     if (status == 0x87) return 0;
     if (count == LP_CHAR(minor)) {


thats all.


Peter Parzer
fc4@ix.urz.uni-heidelberg.de
peter_parzer@krzmail.krz.uni-heidelberg.de

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


** 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-Development-Request@NEWS-DIGESTS.MIT.EDU

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

    Internet: Linux-Development@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-Development Digest
******************************
