Subject: Linux-Development Digest #844
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:     Sun, 19 Jun 94 13:13:04 EDT

Linux-Development Digest #844, Volume #1         Sun, 19 Jun 94 13:13:04 EDT

Contents:
  Strange bug: can you explain? (Archie Cobbs)
  SLIP panic now in 1.1.20 (Frank Lofaro)
  Re: 1.1.20 pdksh & csh problems (Heiko Schroeder)
  PLIP problems... (Richard Whittaker)
  1.1.20 - Mosaic 2.4 broken? (Karsten Steffens)
  Re: IDE PERF. PATCH SECURITY HOLE (Shannon Hendrix)
  Re: IDE PERF. PATCH SECURITY HOLE (Dances With Geeks)
  Re: IDE PERF. PATCH SECURITY HOLE (Dances With Geeks)
  Re: IDE PERF. PATCH SECURITY HOLE (Dances With Geeks)
  Re: 1.1.20 - Mosaic 2.4 broken? (whywhyZ)
  wanted: Some simple sample serial stuff (Moss A D)
  Re: 1.1.20 - Mosaic 2.4 broken? (Ralph Sims)
  Re: 1.1.20 - Mosaic 2.4 broken? (James Smith)

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

From: archie@qin.CS.Berkeley.EDU (Archie Cobbs)
Subject: Strange bug: can you explain?
Date: 19 Jun 94 05:14:47 GMT

I had a weird bug happen yesterday, and am just wondering if
someone could offer an explanation if one exists.

I realize that my kernel etc. is not the most recent, so
this may very well be already known... even so I'd like to
understand what happened.

Backgroud:

        Linux 1.0 kernel (from SlackWare 1.2.0)
        IDE performance patch version 2.0 (ext2fs filesys)
        mgetty+sendfax version 0.20

What happened:

        A phone call came in but the caller (me, on another line)
        hung up as soon as the call was answered. mgetty picked up
        the phone, paused to listen for a fax tone, heard none,
        turned on carrier, got no response, and hung up like normal.

        While this was going on, I was playing around in a directory
        with about 6 files in it. I did an "ls" and suddenly about
        30 new files had appeared in the directory with weird lower
        case names like "sfsc" and "umlrd" and "t". All these files
        had zero length, and the original 6 files were still there,
        unharmed.

        I just deleted the funny files and went on as normal. So far
        nothing else weird has happened.

Any ideas about what may have caused this?

-Archie


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

From: ftlofaro@unlv.edu (Frank Lofaro)
Subject: SLIP panic now in 1.1.20
Date: Sun, 19 Jun 94 06:35:26 GMT

The saga of the SLIP panic continues!
ping -l 100 slipserver still panics
EIP is 1. Not too useful. With 1.1.19 it was in sl_xmit in the
pointer dereference in the line following sl_encaps. That 
portion of the code is now changed. Perhaps skb is still garbaged 
(containg the value 1 perhaps) possibly at the call to 
dev_kfree_skb(skb, FREE_WRITE). It dies a very nasty death, bitching 
about Corrupted stack page and Aieee, killing interrupt handler, then 
prints kernel panic, not syncing, etc, then repeats with a different 
EIP in the kernel which I didn't check (it was in die_if_kernel with the 
1.1.19 panic, not too useful). It halts after the second Kernel panic...
not syncing message.

Kernel 1.1.20 unhacked.
8MB RAM.
16550A connected to 9600bps modem, 57600bps to modem. RTS/CTS flow control.
CSLIP/576 MTU.


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

From: heiko@messua.informatik.rwth-aachen.de (Heiko Schroeder)
Subject: Re: 1.1.20 pdksh & csh problems
Date: 19 Jun 1994 08:44:57 GMT

mimi@mimine.kaist.ac.kr (Seo Hongwon) writes:

>Stephen Beaton-Snook (steve1@morgan.ucs.mun.ca) wrote:
>: Since Ive patched up to 1.1.20 Ive been haveing problems with pdksh and csh.
>: bash seems to work ok.

>: Command line history on the pdksh seems to have broken and when i type a
>: command as simple as 'man stty' or some such it gets sent to the background
>: and I cant forground it. I can run a program like 'dip -t' but when I try
>: to go to terminal mode it puts dip into the background and Im back to my
>: command line prompt. Anyone else experience this and is there a fix?

>me too. how can I fix it?
>plz mail to mimi@baram.kaist.ac.kr

>: Steve


I had similiar problems when I recompiled the kernel without doing
a "make clean" first.  A second try with "make clean" fixed it for me.

CU
   Heiko
-- 
 Email:                                 | Snail-mail:  Heiko Schroeder
                                        |              Lerchenweg 120
  heiko@pool.informatik.rwth-aachen.de  |              52223 Stolberg
                                        |              GERMANY

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

Crossposted-To: comp.os.linux.admin
From: rwhittak@orion.docwhitehorse.doc.ca (Richard Whittaker)
Subject: PLIP problems...
Date: Sun, 19 Jun 94 05:32:40 GMT

Greetings from Whitehorse!.. :-)..

I'm trying to setup a connection between this machine, and another using a
PLIP connection. I've got a genuine LapLink(r) cable, and have the crynwyr
compatible PLIP drivers for the Linux machine.. I'm running plip.com on the
remote machine (a DOS based 386SuX) with the NCSA telnet package. The
problem I'm having is that when I try to Telnet to the Linux box from the
DOS box, I get an "initial" connection, and then nothing. I know the Linux
box is GETTING the packets, because every time I hit return on the DOS
machine, the packet counts reported by Ifconfig on the RX side of things
goes up by one. I also know things are working the other way, because doing
a ping to the remote machine from the Linux machine nets a response from the
remote machine.. I've setup the routes and everything to what (I think) they
should be set to.. Following is what IFConfig reports abotu the interfaces,
as hopefully that'll help..

======
lo        Link encap Local Loopback  
          inet addr 127.0.0.1  Bcast 127.255.255.255  Mask 255.255.255.0
          UP LOOPBACK RUNNING  MTU 2000  Metric 0
          RX packets 0 errors 0 dropped 0 overrun 0
          TX packets 4460 errors 1 dropped 0 overrun 0

sl0       Link encap AMPR AX.25  HWaddr VY1RW-1
          inet addr 44.135.192.1  Bcast 44.135.192.0  Mask 255.255.255.0
          UP BROADCAST RUNNING  MTU 256  Metric 0
          RX packets 0 errors 0 dropped 0 overrun 0
          TX packets 0 errors 0 dropped 0 overrun 0

sl1       Link encap AMPR AX.25  HWaddr LINUX-1
          inet addr 142.92.174.100  P-t-P 142.92.174.1  Mask 255.255.0.0
          UP POINTOPOINT RUNNING  MTU 1500  Metric 0
          RX packets 120601 errors 0 dropped 0 overrun 0
          TX packets 157751 errors 0 dropped 298 overrun 0

sl2       Link encap AMPR AX.25  HWaddr LINUX-1
          inet addr 142.92.174.100  P-t-P 142.92.174.101  Mask 255.255.0.0
          UP POINTOPOINT RUNNING  MTU 1500  Metric 0
          RX packets 113411 errors 0 dropped 0 overrun 0
          TX packets 150485 errors 0 dropped 0 overrun 0

plip1     Link encap 10Mbps Ethernet  HWaddr FD:FD:8E:5C:AE:64
          inet addr 142.92.174.100  P-t-P 142.92.174.103  Mask 255.255.255.0
          UP POINTOPOINT RUNNING  MTU 1500  Metric 0
          RX packets 1020 errors 7 dropped 0 overrun 0
          TX packets 275 errors 52 dropped 0 overrun 0
=====

I don't know if this is enough to go on or not, but the errors reported in
plip1 occured on a different machine from the one I'm trying this on now.

E-Mail is the preferred method of response/inquiry..

Thanks in advance!..
                                        Cheers,
                                        Rich W.
--
Richard Whittaker: Snailmail: 1102 Pine St, Whitehorse YT Y1A 4E8
  Internet E-Mail: rwhittak@orion.docwhitehorse.doc.ca 
Geographic Coords: 60 Deg., 45', 53" N., 135 Deg., 7', 17" W. 
    Amateur Radio: VY1RW, VY1RW@VY1DX, VY1RW@VY1BBS, 145.010 MHz         

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

From: karsten@kshome.ruhr.de (Karsten Steffens)
Subject: 1.1.20 - Mosaic 2.4 broken?
Date: Sun, 19 Jun 1994 08:00:17 GMT

After going from 1.1.19 to 1.1.20 Mosaic 2.4 is obviously broken. I cannot
connect anymore to any www-server; all of them tell me the following:

"ERROR
Requested document (URL http://<any address tried>) could not be accessed.
The information server either is not accessible or is refusing to serve the
docu ment to you."

This definitely only happens with 1.1.20, going back to 1.1.19 cures the
problem. Going back to 1.1.20 reintroduces the problem, so I'm back to 1.1.19
again now. As I'm using SLIP as my interface to IP, maybe there has been
introduced a new problem in the SLIP-Code in 1.1.20. BTW, the other
IP services work ok in 1.1.20, i.e. telnet, ftp, smtp. In addition I
give my kernel config-file, maybe it helps:

#
# Automatically generated make config: don't edit
#

#
# General setup
#
# CONFIG_MATH_EMULATION is not set
  CONFIG_BLK_DEV_HD = CONFIG_BLK_DEV_HD
# CONFIG_BLK_DEV_XD is not set
  CONFIG_NET = CONFIG_NET
# CONFIG_MAX_16M is not set
  CONFIG_SYSVIPC = CONFIG_SYSVIPC
  CONFIG_M486 = CONFIG_M486

#
# Networking options
#
  CONFIG_INET = CONFIG_INET
  CONFIG_IP_FORWARD = CONFIG_IP_FORWARD

#
# (it is safe to leave these untouched)
#
# CONFIG_INET_PCTCP is not set
# CONFIG_INET_RARP is not set
  CONFIG_INET_SNARL = CONFIG_INET_SNARL
# CONFIG_TCP_NAGLE_OFF is not set
  CONFIG_IPX = CONFIG_IPX

#
# SCSI support
#
# CONFIG_SCSI is not set

#
# Skipping SCSI configuration options...
#

#
# Network device support
#
  CONFIG_NETDEVICES = CONFIG_NETDEVICES
  CONFIG_DUMMY = CONFIG_DUMMY
  CONFIG_SLIP = CONFIG_SLIP
  SL_COMPRESSED = SL_COMPRESSED
# CONFIG_PPP is not set
# CONFIG_SLAVE_BALANCING is not set
# CONFIG_PLIP is not set
# CONFIG_NE2000 is not set
# CONFIG_WD80x3 is not set
# CONFIG_ULTRA is not set
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_EL3 is not set
# CONFIG_HPLAN is not set
# CONFIG_LANCE is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_DE600 is not set
# CONFIG_ATP is not set

#
# CD-ROM drivers
#
# CONFIG_CDU31A is not set
  CONFIG_MCD = CONFIG_MCD
# CONFIG_SBPCD is not set

#
# Filesystems
#
  CONFIG_MINIX_FS = CONFIG_MINIX_FS
# CONFIG_EXT_FS is not set
  CONFIG_EXT2_FS = CONFIG_EXT2_FS
# CONFIG_XIA_FS is not set
  CONFIG_MSDOS_FS = CONFIG_MSDOS_FS
  CONFIG_PROC_FS = CONFIG_PROC_FS
  CONFIG_NFS_FS = CONFIG_NFS_FS
  CONFIG_ISO9660_FS = CONFIG_ISO9660_FS
# CONFIG_HPFS_FS is not set
# CONFIG_SYSV_FS is not set

#
# character devices
#
  CONFIG_PRINTER = CONFIG_PRINTER
# CONFIG_BUSMOUSE is not set
# CONFIG_PSMOUSE is not set
# CONFIG_MS_BUSMOUSE is not set
# CONFIG_ATIXL_BUSMOUSE is not set
# CONFIG_SELECTION is not set
# CONFIG_TAPE_QIC02 is not set
  CONFIG_FTAPE = CONFIG_FTAPE
  NR_FTAPE_BUFFERS = 3

#
# Sound
#
# CONFIG_SOUND is not set

#
# Kernel hacking
#
# CONFIG_PROFILE is not set
-- 
==================>    Dipl.=Phys.Karsten Steffens   <=====================
   karsten@kshome.ruhr.de          |      steffens@ikp.uni-muenster.de
Marl - close to Recklinghausen     |         Institut fuer Kernphysik
  North of the Ruhrgebiet          |   Westf.Wilhelms-Universitaet Muenster

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

From: shendrix@escape.widomaker.com (Shannon Hendrix)
Subject: Re: IDE PERF. PATCH SECURITY HOLE
Date: Sun, 19 Jun 1994 02:41:17 GMT

Brandon S. Allbery (bsa@kf8nh.wariat.org) wrote:
: In article <c9108932.771832337@sage.newcastle.edu.au>, c9108932@sage.newcastle.edu.au (Simon Ferrett) says:
: +---------------
: | rob@pe1chl.ampr.org (Rob Janssen) writes:
: | >In <1994Jun14.174453.28689@unlv.edu> ftlofaro@unlv.edu (Frank Lofaro) writes:
: | >>NO ONE BUY A SEAGATE 1239A. ITS CRAP! (it even got bad sectors, yeah,
: | >I have enough experience with Seagate ST-225's and ST-238's to not even
: | >consider buying any product from this company the rest of my life....
: | 
: | I have a seagate ST3655A and it works absolutely fantastically...
: | I dont think seagate is a bad compay at all - maybe you just made a couple
: | of bad choices?
: +------------->8

: Seagate has a severe quality control problem:  sometimes you'll get a good
: drive that works reliably, but it's a crapshoot.  I had better luck than many
: with their older drives (ST225 and ST251N) back when I didn't know any better
: :-) but I don't consider it worthwhile to play games of chance with my data as
: the chips...

I don't understand this.  Seagate drives are known as some of the most
reliable in the business.  Empirically proven over many years.  Some
of them were bad but no drive company has a flawless record.  I know
a system with two 10 year old 251's that have been running almost every
day since then.  I have a 225 that is 8 years old, retired because 20
megs just doesn't cut it anymore.  Museum piece ya know.

You know, Western Digial Caviar's are very popular and very reliable.
But WD didn't always enjoy a good reputation...

: ++Brandon
: -- 
: Brandon S. Allbery       kf8nh@kf8nh.ampr.org          bsa@kf8nh.wariat.org
: Friends don't let friends load Windows NT.            Linux iBCS2 emulation
-- 
csh
===========================================================================
shendrix@escape.widomaker.com (UUCP)     | Amd486/40 Linux system
shendrix@pcs.cnu.edu (Internet)          | Christopher Newport University

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

From: lilo@slip-6-2.ots.utexas.edu (Dances With Geeks)
Subject: Re: IDE PERF. PATCH SECURITY HOLE
Date: 19 Jun 1994 13:35:14 GMT

On 14 Jun 1994 02:32:00 GMT, Jeff Epler (jepler@herbie.unl.edu) wrote:

> >He doesn't seem to be talking about having the partition MOUNTED read-only,
> >he seems to be talking about the user having access to the DEVICE entry
> >read-only, which would not be the same thing, of course....

> Having hard-drive partitions (or the whole device) world (or group)
> readable might still be a bad idea.

*MIGHT?* :)

> Is there a good reason to have the hard drive readable by those you
> can't trust to not screw you with hdparm?

DEFINITELY NOT.


lilo

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

From: lilo@slip-6-2.ots.utexas.edu (Dances With Geeks)
Subject: Re: IDE PERF. PATCH SECURITY HOLE
Date: 19 Jun 1994 13:38:54 GMT

On 14 Jun 1994 08:41:38 +0200, Matthias Urlichs (urlichs@smurf.noris.de) wrote:

> You misunderstood. If there's read-only access to _any_ partition, the user
> can turn on the performance stuff, which will of course affect other
> partitions on the same disk, presumably mounted R/W.

But there's no REASON to allow ANYONE but root access to your disk
partitions.

> It might be a good idea to limit access to the performance switches
> to /dev/hd[ab], and to return an error if somebody tries them with
> /dev/hd[ab][1-9].

This is not necessary.  Even read access to disk partitions by a user other
than root is a *mistake*.  It's an unnecessary security exposure.


lilo

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

From: lilo@slip-6-2.ots.utexas.edu (Dances With Geeks)
Subject: Re: IDE PERF. PATCH SECURITY HOLE
Date: 19 Jun 1994 13:42:10 GMT

On Tue, 14 Jun 94 17:53:59 GMT, Frank Lofaro (ftlofaro@unlv.edu) wrote:

> Also look at my other post where I suggest a reason for giving a user read 
> only access to just ONE partition. hdparm /dev/hda2 will work if you 
> have read-only access to /dev/hda2. It affects the whole drive, of course.

Um, implement the security fix and send the patches to the author?  I'm sure
someone can use them.  :)


lilo

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

From: yyz@video.ne (whywhyZ)
Subject: Re: 1.1.20 - Mosaic 2.4 broken?
Date: 19 Jun 1994 15:20:46 GMT

Karsten Steffens (karsten@kshome.ruhr.de) wrote:
: After going from 1.1.19 to 1.1.20 Mosaic 2.4 is obviously broken. I cannot
: connect anymore to any www-server; all of them tell me the following:

: "ERROR
: Requested document (URL http://<any address tried>) could not be accessed.
: The information server either is not accessible or is refusing to serve the
: docu ment to you."

: This definitely only happens with 1.1.20, going back to 1.1.19 cures the
: problem. Going back to 1.1.20 reintroduces the problem, so I'm back to 1.1.19
: again now. As I'm using SLIP as my interface to IP, maybe there has been
: introduced a new problem in the SLIP-Code in 1.1.20. BTW, the other
: IP services work ok in 1.1.20, i.e. telnet, ftp, smtp. In addition I
: give my kernel config-file, maybe it helps:

yes, i concur, same problem here, i compiled mosaic 2.4.1 several different
ways, and unndid my own kernel hacks (new unblemished tree, twice), 1.1.20
has problems with mosaic.


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

From: mossap@sunlab45.sx.ac.uk (Moss A D)
Crossposted-To: comp.os.linux.help
Subject: wanted: Some simple sample serial stuff
Date: 19 Jun 1994 15:19:15 GMT


Hi!

Could someone please help mebefore I go mad!?

ALL I want to do is blow strings into a modem in
a C program.

What I've been doing is fopen-ing the /dev/modem
device and fprintf-ing strings at it, ie ATZ,
ATDT123456, etc.

HOWEVER, this seemed to have stopped working
roundabout kernel version 1.1.3

So...

* Could some kind soul with a new-ish kernel PLEASE
  give me some short sample C code (needn't be more
  than a couple of lines!) which does the job?

I don't know what I'm doing that the old kernel
likes but the new kernel barfs at.

What's actually happening with the new kernel is that
the modem device is closed (the modem resets?) when
a string's written to it, or something like that.

I've tried opening, fopening, writing, fputc-ing,
fputs-ing, fprintf-ing.... they're all doing the same!

It's driving me mad.  :(


Thanking you very much, in advance!

Adam.

--
     |\   /|           ------------------------------------------------
    /| \_/_|           Adam D. Moss                  mossap@essex.ac.uk
__--|\_/   _\          ------------------------------------------------
    /_    (o \___o      "A smartass once accused me of being subtle. I
   /_      ----= /     decked him with a short right over the heart and
    /__  \ -----'         an elbow in the trachea." - Harlan Ellison
       \ //            ------------------------------------------------
      _/
 __/_/          "If music be the food of love" then let a famine rage -   
/_-/         to starve my childish innocence before it comes of age.

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

From: ralphs@locus.halcyon.com (Ralph Sims)
Subject: Re: 1.1.20 - Mosaic 2.4 broken?
Date: 19 Jun 1994 16:25:42 GMT
Reply-To: ralphs@halcyon.com

whywhyZ (yyz@video.ne) wrote:
: Karsten Steffens (karsten@kshome.ruhr.de) wrote:
: : After going from 1.1.19 to 1.1.20 Mosaic 2.4 is obviously broken. I cannot
: : connect anymore to any www-server; all of them tell me the following:

: : "ERROR
: : Requested document (URL http://<any address tried>) could not be accessed.
: : The information server either is not accessible or is refusing to serve the
: : docu ment to you."

: yes, i concur, same problem here, i compiled mosaic 2.4.1 several different
: ways, and unndid my own kernel hacks (new unblemished tree, twice), 1.1.20
: has problems with mosaic.

What is your MTU setting?  You might try running 966, if you've been
using a much lower setting.  Or, beef up your lower setting in increments
of 40 MTU's until the problem goes away (if, in fact, it DOES go away).
I'd suggest data fragmentation due to blocksizes incompatible with
Mosaic.  Since Mosaic is the only constant in your equation... ????



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

From: smith@meishan.animal.uiuc.edu (James Smith)
Subject: Re: 1.1.20 - Mosaic 2.4 broken?
Date: 19 Jun 1994 16:32:16 GMT

yyz@video.ne (whywhyZ) writes:

>Karsten Steffens (karsten@kshome.ruhr.de) wrote:
>: After going from 1.1.19 to 1.1.20 Mosaic 2.4 is obviously broken. I cannot
>: connect anymore to any www-server; all of them tell me the following:

>: "ERROR
>: Requested document (URL http://<any address tried>) could not be accessed.
>: The information server either is not accessible or is refusing to serve the
>: docu ment to you."

>: This definitely only happens with 1.1.20, going back to 1.1.19 cures the
>: problem. Going back to 1.1.20 reintroduces the problem, so I'm back to 1.1.19
>: again now. As I'm using SLIP as my interface to IP, maybe there has been
>: introduced a new problem in the SLIP-Code in 1.1.20. BTW, the other
>: IP services work ok in 1.1.20, i.e. telnet, ftp, smtp. In addition I
>: give my kernel config-file, maybe it helps:

>yes, i concur, same problem here, i compiled mosaic 2.4.1 several different
>ways, and unndid my own kernel hacks (new unblemished tree, twice), 1.1.20
>has problems with mosaic.


i got the same problem.
also when compile 1.1.20 it has 2 warning on personallity.h

supat


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


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