Subject: Linux-Development Digest #845
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:     Mon, 20 Jun 94 03:13:11 EDT

Linux-Development Digest #845, Volume #1         Mon, 20 Jun 94 03:13:11 EDT

Contents:
  Re: Frustrated with new kernels (Brad Midgley)
  Re: PLIP throughput.. (las@light-house.uucp)
  How come this doesn't work in Linux? (code included) (Steven Webb the all-knowing)
  IPX Netware Protocol (Peddlesden M J)
  COmpile errors on 1.1.20... (Richard Whittaker)
  Re: assembly language & Linux (ATTN!) (Norbert J. Girardi)
  Re: please help me... (Carsten Schabacker)
  Re: cp truncate some dos files, why? (Beverly J. Brown)
  Re: IPX Netware Protocol (Rob Janssen)
  Re: IDE PERF. PATCH SECUR (John Will)
  Re: Filesystem semantics protecting meta data ... and users data (John Miller -- sysadmin)
  Re: beginners question to Xlib programming (Christopher Key)
  Re: 1.1.20 pdksh & csh problems (Stephen Beaton-Snook)
  Re: PLIP throughput.. (Peter Bauer)
  Vadem pcmcia? (Dan Ridge)
  Re: 1.1.20 - Mosaic 2.4 broken? (Karsten Steffens)

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

From: bmidgley@peruvian.cs.utah.edu (Brad Midgley)
Subject: Re: Frustrated with new kernels
Date: 19 Jun 1994 16:34:22 GMT

Rob Janssen (rob@pe1chl.ampr.org) wrote:
: atoenne@mpi-sb.mpg.de (Andreas Toenne) writes:

: >At the heart of my problem lies the *EMPTY* Changes list for Linux >= 1.0.0

: But Russ Nelson has posted such lists for some time!
: Are they archived somewhere?  Would there be some way to get them included
: in the README, e.g. at the release after the one it refers to?

Is there any reason that the changes lists can't be posted to
comp.os.linux.announce? 

Maybe it's not in the .announce charter to announce alpha software,
but it seems like we constantly see announcements there for other
programs which are less stable than the bleeding-edge kernel...

I realize nobody wants to encourage casual users to follow the latest
kernel (and post endlessly with configuration/compilation problems).
It would be nice to see the changes list for the 1.0.* releases
posted in .announce anyway.

--
bmidgley@peruvian.cs.utah.edu

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

From: las@light-house.uucp
Subject: Re: PLIP throughput..
Date: Sat, 18 Jun 1994 22:12:06 GMT
Reply-To: whome!light-house!las@planix.com

Gene Choi (genie@sting.Berkeley.EDU) wrote:

: Hello there,

: I was experimenting with PLIP 1.02 and linux kernel 1.1.0.
: I connected a 386/20 and a 386/33 together with a parallel laplink
: cable.  I noticed that throughput with FTP was only about 14Kbytes/sec.
: Sure this is way better than any serial connection will give.  However,
: I'm wondering if there is any way to increase this number, and to
: ask if these are the kinds of results I should expect?

: If I remember correctly, using LapLink, some people were copying
: things over the parallel port at least 50-100kbytes/sec,  Sure
: linux is not DOS, but it sure would be nice to have these kinds of results,
: especially using NFS as I plan between the two computers.


That sounds like a very low transfer rate. I remember exchanging email
with a guy in Germany about 2 months ago, and he reported something like
30 Kbps throughtput talking to a DOS machine using a hacked PLIP.

I suspect your parallel ports are not bidirectional, so you don't have a full
8-bit data path.
 

: -Gene

: -- 
: Zima zux!


=============================================================================
Keyboard error: keyboard not detected. Press F1 to continue
=============================================================================

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

From: webbs@CS.ColoState.EDU (Steven Webb the all-knowing)
Subject: How come this doesn't work in Linux? (code included)
Date: Sun, 19 Jun 1994 19:12:15 GMT


begin 644 socket_stuff.tgz
M'XL( $!$!"X  ^V574_;,!2&>TM^Q5'0IA1"24K3BW4@5:-#"%$FVEU,#$6I
MX[;64KNS75"'^.^SXY:/=F+<,#;M/%(5^_CU\7'<O"8%HUS72.4%B:.HV6A 
M!2S1RA,@KM<C@*09Q5&C'C7V3"1*&HT*1"]9U)*9TID$J$@A]%.ZWXW_HVPR
M3HI93N&]TCD3M?&!]R T5[MZ/J5J/:P$^4;UXSBG.A^LA9CY[3)NX]YF3H>F
M#Y_.SOO=SZ<0)U%\%SSM]'KMHP[XO3(W]*G2ON=-,L:#JG?C,:Y!Y2V/C,V!
M#6;#(947]:1YV?*4EC-B!LV\+,]ERC@H*J^HY-F$W@V/A=+FOPY;MM'R/)7#
M/KA]!.V/Z7&WTP^A=_;A).WUSSOMTQ"BJI%9M1&.J+:MP=SF#/Q"D*RP =]J
M!D1,YQ#8_L[!.+5%A!"4A6Y5X>U],37%^&)X*2XH'^FQS;(B&V835LS-THOB
M6JN"J9"VLL7+- F(X)R:G08J-\NOO)652D)0[ <5P^ ^5+5%7$NFJ<NP.) [
MY:)O99)FN1.Y@PC!G(2)3Z4YI6'@D])68&?G (Z$AJ$4D\61O(,WZBOW0S?/
M3"&%4.6"IGWKO?;W\+_A#N5U_3].DGO_;\;6_YO1'OK_G^ O\'_G\-;=,SDB
M(3C;-.VKB\NE[\O4>@U)K?\7@H^@E.]'S[P-W#W@V2S/\?PG+/B1B==4^3#C
MQ]WVX>%YVNY^>2!9\^<!XWG@MO)+=W[DRTM'+IB]MMRTQ#IT+N#&VR!N+QDA
M=*J?2!J9L'U9MFEF;SCG)NFZ=V\LS=MY0FG>DGZ?F6L8-N%-;ET[V]ZVRL4E
MX;+X9R=^"'LV7GIY&38]\VG?PO68%489H[DC"((@"((@"((@"((@"((@"((@
."(*\+#\!J:/\NP H   ]
 
end


This compiles on almost every UNIX box that I can get my hands on, but not in
Linux.  What gives?  Actually, it compiles, but it core dumps and pukes up
everything in every way.  It's just some simple code to test sockets in a very
basic fashion.

Please help!

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

From: peddmv@sunlab40 (Peddlesden M J)
Subject: IPX Netware Protocol
Date: 19 Jun 1994 19:54:54 GMT

Can someone tell me if the IPX/SPX networking protocol has been
implemented in the networking support of Linux?

What I would like to be able to do is to link my Linux box up
to the DOS/Netware Lite lan I have running at home.....

Comments? (hehe except for - change all your machines to a
decent OS like Linux <G>)

--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Matthew Peddlesden peddmv@essex.ac.uk           |
                   captain@megabyte.embassy.com | Witty comment
USS MegaByte BBS -> 0449 675967, 24 hours (UK)  | still under
Everything you could ask for, provided it's     | construction
legal :)                                        |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


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

Crossposted-To: comp.os.linux.admin
From: rwhittak@orion.docwhitehorse.doc.ca (Richard Whittaker)
Subject: COmpile errors on 1.1.20...
Date: Sun, 19 Jun 94 20:19:16 GMT

Greetings (again) from Whitehorse!..

I've applied the pl19 and pl20 patches to my pl18 kernel, did a make clean,
and a make dep, and went to do a mek zImage, and got to the point where the
file "exec_domain.c" was being made, and a whole load of errors issued forth
from the compiler.. These errors follow here..

=====
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit
-frame-pointer -pipe -m486 -c fork.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit
-frame-pointer -pipe -m486 -c exec_domain.c
exec_domain.c:111: redefinition of `ident_map'
exec_domain.c:9: `ident_map' previously defined here
exec_domain.c:118: redefinition of `default_exec_domain'
exec_domain.c:16: `default_exec_domain' previously defined here
exec_domain.c:128: redefinition of `exec_domains'
exec_domain.c:26: `exec_domains' previously defined here
exec_domain.c:132: redefinition of `no_lcall7'
exec_domain.c:30: `no_lcall7' previously defined here
exec_domain.c:137: redefinition of `lookup_exec_domain'
exec_domain.c:35: `lookup_exec_domain' previously defined here
exec_domain.c:152: redefinition of `register_exec_domain'
exec_domain.c:50: `register_exec_domain' previously defined here
exec_domain.c:168: redefinition of `unregister_exec_domain'
exec_domain.c:66: `unregister_exec_domain' previously defined here
exec_domain.c:184: redefinition of `sys_personality'
exec_domain.c:82: `sys_personality' previously defined here
exec_domain.c:204:FATAL:Symbol _no_lcall7 already defined.
make[1]: *** [exec_domain.o] Error 1
make: *** [linuxsubdirs] Error 1
Orion:/usr/src/linux#
=====

Has anyone else had a similar problem?.. If so, do they know the fix?..

Any E-Mail suggestions would be much appreciated!..

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: girardi@rniil.rni.sub.org (Norbert J. Girardi)
Subject: Re: assembly language & Linux (ATTN!)
Date: Sun, 19 Jun 1994 09:36:26 GMT

Linus Torvalds (torvalds@cc.Helsinki.FI) wrote:

: Any porters out there should feel happier knowing that DEC is shipping
: me an AlphaPC that I intend to try getting linux running on: this will
: definitely help flush out some of the most flagrant unportable stuff. 

So, finally one of the BIG players *DID* wake up.

Never expected DIGIAL EQUIPMENT to do it first :-)

Would be nice if they gave you access to the DECnet and Pathworks
sources, too.

BTW, don't you have to move to a bigger apartment soon with all these
workstation class machines rolling in? ;-) 

- Norbert

-- 
SSSSSS            SQUAREDANCE is FRIENDSHIP set to MUSIC.
S  QQSQQQ      Norbert J. Girardi < girardi@rniil.rni.sub.org >
SSSQSS  Q       Voice: +49 621 493417 (h) +49 621 381-3260 (w)
   QQQQQQ  If you know how to REPAIR YOUR SQUARE :-) drop me a line

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

Date: Fri, 17 Jun 1994 06:26:00 +0200
From: Carsten_Schabacker@p39.rollo.central.de (Carsten Schabacker)
Subject: Re: please help me...

Hi,

Qi Y. Zeng@2:2437/209.0 hat am 16.06.94 geschrieben:

>From: qizeng@acsu.buffalo.edu (Qi Y. Zeng)
>
>Dear Netters:
>
>I partitioned my 240 MB HD into
>2 parts with 120 MB each. One
>part is for DOS and Wins while
>another is for linux.
>
>Because I have a project which
>needs more space, I want to purge
>Linux for the time being and use
>that space as, for example, drive D.
>
>Could you tell me howw to do it?

You can mount the msdos-partition with:

mount -t msdos /dev/hda1  /mnt


Tschau Carsten...




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

From: bjb@shore.net (Beverly J. Brown)
Subject: Re: cp truncate some dos files, why?
Date: 19 Jun 1994 18:27:30 -0400
Reply-To: bjb@shore.net

In article <1994Jun17.170538.27707@rosevax.rosemount.com>, Grant Edwards wrote:
> Romano Giannetti (romano@pimac2.iet.unipi.it) wrote:
> 
>   [file being truncated when cp'ed]
> 
> 
> Since PC-DOS (and MS-DOS) were "derived" from CP/M, and many of the
> early PC-DOS applications were ports of CP/M applications, the
> convention of using a ctrl-Z as an EOF marker persisted, even though
> PC-DOS (at least in 2.0 and later) keeps track of how long files are
> and will return EOF when you try to read past the last "real" data
> byte in the last block.
> 


Linux shoud NOT rely on CTRL-Z. It should do the right thing as DOS has 
since, as you pointed out, version 2.0.


Beverly J. Brown
bjb@shore.net
beverly@datacube.com

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: IPX Netware Protocol
Reply-To: pe1chl@rabo.nl
Date: Sun, 19 Jun 1994 22:31:26 GMT

In <2u27qe$h5n@seralph0.essex.ac.uk> peddmv@sunlab40 (Peddlesden M J) writes:

>Can someone tell me if the IPX/SPX networking protocol has been
>implemented in the networking support of Linux?

>What I would like to be able to do is to link my Linux box up
>to the DOS/Netware Lite lan I have running at home.....

>Comments? (hehe except for - change all your machines to a
>decent OS like Linux <G>)

You can access Netware from dosemu, where you can load the usual
Netware client software.
IPX is in the Linux networking, but SPX and NCP aren't, so you can't
do it directly from Linux.

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

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

Subject: Re: IDE PERF. PATCH SECUR
From: john.will@dscmail.com (John Will)
Date: Sun, 19 Jun 94 20:32:00 -0640

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

I think you'll get lots of argument about the ST-251, that model was 
likely the worst Seagate ever produced, and is no doubt responsible for
a lot of their bad reputation!  I'm very impressed that you have them
running for anything close to that amount of time, but I can assure
you, you're in the minority!  I would hate to count the ST-251 & ST-277
drives that I replaced that had severe stiction.  I still have a platter
from a ST-251 with the head firmly cemented to the disk, that's the way
it came out of the HDA.  I have to agree about the 225, but for several
years, Seagate had no idea how to make plated media drives!

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

Crossposted-To: comp.benchmarks,comp.sys.sun.admin,comp.security.unix
From: jsm@n4vu.Atl.GA.US (John Miller -- sysadmin)
Subject: Re: Filesystem semantics protecting meta data ... and users data
Date: Sun, 19 Jun 1994 22:10:21 GMT

Dan Swartzendruber (dswartz@pugsley.osf.org) wrote:
: In article <idletimeCrM850.Dqp@netcom.com> idletime@netcom.com (Totally Lost) writes:

: [deleted]

: If this is all so clear-cut and obvious, how about coming up
: with an actual design, and putting it out for review?  If you
: really know what you're talking about, it shouldn't be that
: difficult, no?  And if you actually come up with an implementation
: which is clearly superior FT-wise, and performs well, you could
: end up saving all these poor users who are getting file corruption,
: instead of keeping news spools filled.

Yeah, what he said!

In the Valley of the Blind, the one-eyed man is . . . nuts.  

This highly esoteric discussion has been amusing, but if Bro. 
idletime's vision is so much further advanced than the rest 
of us mortals, he would do us all a favor by disappearing into 
the cellar and spending some time in practical, rather than 
theoretical, development.  
-- 
John Miller, N4VU                 Linux!                    Fayetteville
jsm@n4vu.Atl.GA.US                DoD #1942                    (Atlanta) 
{emory,gatech}!n4hgf!n4vu         AMA #671301                     GA, US

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

From: skip@metronet.com (Christopher Key)
Subject: Re: beginners question to Xlib programming
Date: Mon, 20 Jun 1994 02:31:31 GMT

In article <1994Jun12.231207.14529@kf8nh.wariat.org>,
Brandon S. Allbery <bsa@kf8nh.wariat.org> wrote:
>
>And no, you do not want to change this.  You could never replace a routine in
>a library with your own version otherwise.  (For example, you would never be
>able to use a debugging malloc.)

Sure you could.  Most of the linkers I use under MS-DOS have multiple ways
of dealing with this one.  They always link object code rather than
libraries.  In addition, several of them have ways of specifying that
particular libraries need multiple passes, and specifying specific modules
from particular libraries.

Skip


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

From: steve1@morgan.ucs.mun.ca (Stephen Beaton-Snook)
Subject: Re: 1.1.20 pdksh & csh problems
Date: 20 Jun 1994 03:27:44 GMT

Heiko Schroeder (heiko@messua.informatik.rwth-aachen.de) wrote:
: 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.

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

'make clean' did it, guess I shouldnt try compileing kernels at 4am in the 
morning :) much thanks for pointing out what I should have done in the
first place :)

Steve

--

 Stephen Beaton-Snook                             Memorial University of NFLD
 steve1@morgan.ucs.mun.ca                         St John's, Newfoundland
                                                  Canada.


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

From: pbauer@rnivh.rni.sub.org (Peter Bauer)
Subject: Re: PLIP throughput..
Date: Sun, 19 Jun 1994 15:42:49 GMT

bde@kralizec.zeta.org.au (Bruce Evans) writes:


>No, it's very i/o intensive.  PLIP takes a minimum of about 15 i/o
>instructions per byte.  This takes about 20 usec on most systems with
>an 8 MHz ISA bus, so it's hard to get more than 50K/sec throughput.
>386's are reasonably fast at shifting and even a 386/20 can reassemble
>a byte in about 1 usec, at least if everything is kept in registers.
>-- 

I've donw some experimets with plip and have build a synchronous version,
where the sender puts the nibbles out with a fixed rate, and the receiver
has to be fast enough to reassemble them. There was also a algorythm in
which tries to adjust the sender's speed as low as possible. The result
I found is, that at about 50K the hardware-limit (= the wire) seems
to be reached, because the receiver was easily able to receive all data,
and the sender was still not at the max possible speed (needed delay-
loop), when the transmission errors started to increase.
Gruss PB

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

From: newt@cs.umd.edu (Dan Ridge)
Subject: Vadem pcmcia?
Date: 20 Jun 1994 00:22:31 -0400

Hi. 

What is the stat of a Vadem PCMCIA controller driver for Linux?

Is this a distict kind of controller or is this really an intel clone?

Please email replies

(The vadem is the controller that my Dell Latitude 433 laptop says is has)

Thanks,
        newt@cs.umd.edu


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

From: karsten@kshome.ruhr.de (Karsten Steffens)
Subject: Re: 1.1.20 - Mosaic 2.4 broken?
Date: Mon, 20 Jun 1994 06:30:18 GMT

Ralph Sims (ralphs@locus.halcyon.com) wrote:
: whywhyZ (yyz@video.ne) wrote:

: 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... ????

296. Increasing to 966 did not help, either. So there must be another
problem. I even tried MTU 1500... no use. And Mosaic 2.4 is working with
1.1.19, only 1.1.20 makes the problems.

Karsten

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

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


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