Subject: Linux-Development Digest #254
From: Digestifier <[email-masked]>
To: [email-masked]
Date: Sun, 2 Oct 94 07:13:06 EDT

Linux-Development Digest #254, Volume #2          Sun, 2 Oct 94 07:13:06 EDT

Contents:
  Re: i486 Word length, anyone? (Andrew F. Lee)
  Re: Could TCP/IP be implemented over SCSI? (Hamish Coleman)
  Re: Token Ring driver for Linux (Jonathan Magid)
  Re: i486 Word length, anyone? (Andrew F. Lee)
  Re: Status of Mac Linux & PPC Linux? (Zack T. Smith)
  Re: What is "makedepend," and where do I get it? (Yasuo Ohgaki)
  [Wine] "Can't build if1632.o"  Now what? (Joel M. Hoffman)
  Re: limit memory and add memory file system (Arnt Gulbrandsen)
  limit memory and add memory file system (Phil Howard)
  SCSI Printer? (mac) (James E. McNalley)
  Re: AMD/Automounter (Was Re: [STATUS] Linus Floppy Driver Development) (Mitchum DSouza)
  Anyone have info on Colorado Memory Systems' QFA-700 QIC-02 controller? (Craig A. Huegen)
  DOS 6.0 Interlnk->Linux??? (Jeremy Gordon)
  Re: Korn Shell '93 Now Available from AT&T (Darin Johnson)
  Re: Try this IPX bridging code ... (Steve Kneizys)
  DOS & Linux on 1GB drive (gil filer)

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

From: Andrew F. Lee <[email-masked]>
Subject: Re: i486 Word length, anyone?
Date: 1 Oct 1994 18:14:29 GMT

>Quite true, and the same used to apply to bytes. Nowadays, a
byte is
>accepted by most people to mean "8 bits", but I've worked on a
9-bit byte
>machine with 3 of these bytes per word. Too weird.

Yeah, these are all conventions of block codes (e.g. 8 bits is 
one byte etc).  Convolutional codes have no fixed length, thus no 
bytes or words or nibbles...Oh and pardon me, a _WORD_ is not 
defined in ANSI C, an int is (I was using the _convetional_ 
shorthand).  Otherwise, an Intel i486 uses a 32 bit word.

Andrew F Lee

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

From: [email-masked] (Hamish Coleman)
Subject: Re: Could TCP/IP be implemented over SCSI?
Date: 29 Sep 1994 22:45:26 +1000

In <ianm.780705652@miles> [email-masked] (Ian McCloghrie) writes:
>[email-masked] (myers_lincoln) writes:

>>having SoundCardNet.  Sound Cards would record each other's audio output from
>>across the room.  True short range wireless communication, though sleeping in

>Ulch.  Your error rate would be atrocious, I would imagine.

>"Hey!  John!  Turn your music down, it's making me drop packets!"

No, that shouldnt be too much of a problem -- simply have the drivers
increase the output volume as the number of errors increases.

"Hey! Ian! Turn your computer down, I cant hear the music!"

-- 
Use Linux!                                         [email-masked]
|)}>=----------------------- This space to let ----------------------=<{(|
``Life is like a grapefruit ... it's sort of orangey-yellow and dimpled on
the outside, wet and squidgy in the middle.  It's got pips inside too. Oh,
and some people have half a one for breakfast.'' -- Ford Prefect

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

From: [email-masked] (Jonathan Magid)
Subject: Re: Token Ring driver for Linux
Date: 30 Sep 1994 21:39:15 GMT

In article <[email-masked]>,
 <[email-masked]> wrote:
>does anyone know of a Token Ring driver for Linux??
>

IBM token ring support is in ALPHA testing.  You can find it on sunsite.unc.edu
in /pub/Linux/kernel/patches/network/linux-1.1.47-TR-ESDI.patch.gz.

jem.

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

From: Andrew F. Lee <[email-masked]>
Subject: Re: i486 Word length, anyone?
Date: 29 Sep 1994 20:35:52 GMT

in a message from [email-masked]
>>an apparently-BSD-ish variable called NBPW. I found its 
counterpart
>>NBBY (Number of Bits per BYte) in the include/bsd/bsd.h file, 
so I'm
>>assuming that NBPW is Number of Bytes Per Word. Of course, I 
could be...
>>I tried setting it to 32 (since the 486 is a 32-bit processor 
<shrug>),
>Hmm... This seems to be a question of definition. _I_ have 
always
>thought that a word is defined as two bytes, or 16 bits, 
independent of
>machine. But I don't know...
>Anyway, int in Linux is 32-bit, short is 16-bit, and char is 
8-bit, if
>that helps any...

A Word in ANSI C is 16 bits (specifically unsigned) i.e. the same 
size as an int.  A long is 32 bits.  The registers of a 486DX (as 
opposed to SX) have a 32 bit capacity -- but I can't see what 
that has to do with the size of a _word_ as the OS sees it?  I 
would try 16 bits...

Andrew F. Lee

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

Crossposted-To: comp.os.linux.help
From: [email-masked] (Zack T. Smith)
Subject: Re: Status of Mac Linux & PPC Linux?
Date: Sat, 1 Oct 1994 17:01:46 GMT

In article <[email-masked]> [email-masked] (Michael Sullivan) writes:
>In article <[email-masked]>, [email-masked] (msouth on BIX)
>wrote:
>
>> 
>> (get info about mac hardware)
>> 
>> Two problems:  1)  Apple documentation is intended for programmers
>> writing for the Mac OS, or manufacturers adding additional hardware.
>> 2)  There are a *lot* of variations.  Unlike the PC world,
>> standardization is in OS software, not hardware.
>> 
>> Example:  Hardware reference manual for IIsi says, in effect,
>> that 'the ADB ports are different from original Mac II, and
>> any software that talks to it directly probabally won't work.'  Not
>> explained is _how_ it's different.
>
>Actually, the mac world is very well behaved if you follow the rules....
>Direct access to i/o ports is strongly discouraged. There are i/o routines
>documented in "Inside Mac" that perform the proper i/o redirection and
>location so that the programmer really doesn't have to know the low level
>details. There are low level traps defined that permit access at even lower
>levels...if needed. There is a very large quantity of information available
>from apple and others on the mac and its programming environment that is
>availble so there is really no truth to the assertion that mac programming
>data is hard to get or obscure. Visit the local bookstore ... various
>volumes of "Inside Mac" (and other books) are usually available......
>---- Mike

A few problems with this.

1. Inside Mac is not accurate all of the time.
2. Inside Mac is deficient in many ways.
3. Inside Mac is written so as to hide important details in obscure
   parts of the manuals.
3. Mac OS calls are incredibly convoluted; they force the programmer
   to do additional work to write a normal, straightforwad, healthy interface.
4. If you want as to why Inside Mac's suggestions don't work or about
   manual deficiencies, you have to pay Apple for developer support.
5. To get Linux running you can't use high level Mac OS calls; doing so
   would alleviate the need for the Linux OS.

Zack Smith
Creator of UltraShell(tm), the C Shell for the Mac
Demo available in pub/zack @ ftp.netcom.com.

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

From: [email-masked] (Yasuo Ohgaki)
Subject: Re: What is "makedepend," and where do I get it?
Date: Sat, 1 Oct 1994 17:34:46 GMT

Joel M. Hoffman ([email-masked]) wrote:
: I thought I'd give Wine a try this weekend, but I can't even get past
: ./Configure, because that script needs "makedepend," which I don't
: have.  Where might I find it.

It's a part of imake. Install imake packeage. (^_^)

--
Yasuo Ohgaki
e-mail: [email-masked]

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

From: [email-masked] (Joel M. Hoffman)
Subject: [Wine] "Can't build if1632.o"  Now what?
Date: Sat, 1 Oct 1994 19:30:12 GMT

I found a copy of makedepend, which doesn't quite work right but seems
to work well enough, and now I'm trying to build a copy of Wine,
specifically, wine940912.  But the make keeps dying on if1632.o:

        make: *** No rule to make target `if1632.o'.  Stop.

Indeed, I can find no if1632 source file.  The README mentions a small
change to if1632.S, but I can't find that file anywhere.

Now what?

-Joel
([email-masked])


-- 
=============================================================================
|_|~~ 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:  [email-masked]

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

From: [email-masked] (Arnt Gulbrandsen)
Crossposted-To: comp.os.linux.admin
Subject: Re: limit memory and add memory file system
Date: 1 Oct 1994 20:55:27 GMT

In article <[email-masked]>,
Phil Howard <[email-masked]> wrote:
>I'm not sure which newsgroup this belongs in because I don't know if the
>My hardware supports DMA only on the first 16 megabytes of RAM although
>it will support up to 64 megabytes of RAM.  What I want to do is to have
>Linux use only the first 16 megabytes in its usual way much as if the
>machine only had 16 megabytes.  Then I want to use whatever remaining
>memory above the 16 megabyte line I happen to have installed (it is OK
>by me to have to code this somewhere) as a memory file system.

Sure.  Set up a RAM drive in /etc/lilo.conf.

Of course, linux will use it fairly efficiently of its own if you
just let the buffer cache logic do its job.  More efficiently that
you can do with a RAM drive, probably.

Oh, and re your .sig:

>\***** [email-masked] ************* Just say NO to CIX extortion ***********/
                                    Just say THANK YOU to [email-masked]

--Arnt

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

From: [email-masked] (Phil Howard)
Crossposted-To: comp.os.linux.admin
Subject: limit memory and add memory file system
Date: 1 Oct 1994 14:57:03 -0500

I'm not sure which newsgroup this belongs in because I don't know if the
answer is just a configuration setting or requires a kernel hack.

Oh, yes, I have looked in the FAQ and HOWTO ... nothing there on this.

My hardware supports DMA only on the first 16 megabytes of RAM although
it will support up to 64 megabytes of RAM.  What I want to do is to have
Linux use only the first 16 megabytes in its usual way much as if the
machine only had 16 megabytes.  Then I want to use whatever remaining
memory above the 16 megabyte line I happen to have installed (it is OK
by me to have to code this somewhere) as a memory file system.  So if
I install all 64 megabytes of RAM I could have a 48 megabyte memory file
system.

The basic question is how to do this.  Also, do you know of any particular
problems one might encounter with this?  Is there some other scheme that
would let me utilize the extra memory to gain some speed?
-- 
/***** Phil Howard KA9WGN *********** How about universal JOBS? **************\
*      Unix/Internet/Sys Admin        Let's de-Foley-ate congress in 94       *
*      CLR/Fast-Tax                   Don't let Annie get your gun!           *
\***** [email-masked] ************* Just say NO to CIX extortion ***********/

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

From: [email-masked] (James E. McNalley)
Subject: SCSI Printer? (mac)
Date: 1 Oct 1994 20:28:53 GMT

        A while ago,  a friend of  mine who had a mac SE and some sort
of laser-writer that connected with a SCSI port.  When he upgraded
to a PC, he asked me if there was any way he could use the LW on the
PC, and I said no, since he had no SCSI card.  Now that *I* have a 
SCSI  card on my linux box (1542B), I was wondering if there is a
driver for scsi printers in the linux kernel, or if patches are
aviable?  Thanks!

--
James McNalley          | "I have never let my schooling interfere with my
Linux/Unix  Hacker      | education" -Mark Twain 
Portland, OR            |  "Live free or die" -New Hampshire motto 
[email-masked] -or- [email-masked]

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

From: [email-masked] (Mitchum DSouza)
Subject: Re: AMD/Automounter (Was Re: [STATUS] Linus Floppy Driver Development)
Date: 30 Sep 1994 10:44:31 GMT

In article <[email-masked]>, [email-masked] (Rob Janssen) writes:
|> In <[email-masked]> [email-masked] (Mitchum
|> DSouza) writes:
|> 
|> >Its funny how so many people want this feature from AMD. For a very good
|> reason 
|> >(performance mainly) UFS mounts (of which a floopy is one) are made not to 
|> >timeout.
|> 
|> What is the performance impact of unmounting/mounting a floppy which has
|> not been removed from the drive?  Did you actually try this?
|> (on my machine, it re-mounts instaneously...)

I was not talking specifically about floppies but generally about UFS mounts
which are made not to timeout. There is nothing that distinguishes (from 
the amd point of view) a floppy and your hard-drive. This means that once amd
starts it adds your hard disk mounts to its internal table of mounts, for e.g 

% amq -m
"root"                sirius:(pid132)           root    1   localhost is up
/dev/sd0a             /                         ufs     1   localhost is up
/dev/sd0g             /usr                      ufs     1   localhost is up
/dev/sd0h             /export/home              ufs     1   localhost is up
/usr/etc/amd.home     /home                     toplvl  1   localhost is up
...etc...

Clearly I would not want the three hd ufs mounts to timeout ever.

In theory a type of "subufs" could be added to amd making these timeout(able),
so that removable media (floppys and cdroms) would fall into this category.

Mitch

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

From: [email-masked] (Craig A. Huegen)
Crossposted-To: comp.os.linux.help
Subject: Anyone have info on Colorado Memory Systems' QFA-700 QIC-02 controller?
Date: 1 Oct 1994 20:53:34 GMT

Does anyone have any information on Colorado Memory Systems' QFA-700 
QIC-02 controller/tape drive combo?  I purchased one for my DOS machine, 
but I'd like to be able to use it with Linux.

Problem is, Colorado Memory Systems have since discontinued the product, 
yet they aren't giving any information on programming the controller card.

I'd like to write a device driver for it, if anyone has any information 
on it.  The controller card uses Stac hardware compression, and is 
jumperless.

Thanks for any help in advance...

--Craig

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

From: [email-masked] (Jeremy Gordon)
Subject: DOS 6.0 Interlnk->Linux???
Date: 1 Oct 1994 04:10:05 GMT

i like linux so much it took over my computer, and now i don't even
have a dos partition....

but i am an atari jaguar developer, and i need to have dos, solution,
buy another computer, so i did, its a notebook (compaq contura aero)

i am trying to avoid paying $150+ for a PCMCIA ethernet card, (and the
ensuing dos networking software) so i would like to inquire on the
feasability of making dos's parallel port "network mounted drive" program
"interlnk.exe" work under linux (ie have a linux version of "intersvr.exe")

i have experience with mucking about in the linux kernel, and plenty of
C programming experience, and given the availability of parallel port source
(ie plip) it seems feasible...

bottom line, anyone know how to go about getting the protocol for interlnk??
if i just wanted to ftp, etc i'd use the crywnr patches to plip to be compat
with dos plip.com, but then i need some pc-nfs client, or samba and windows
for workgroups, all of which are $$$ and take up loads of low dos memory...

any ideas???

                                -jeremy

questions/comments/answers to [email-masked]

======================================================================
Jeremy Gordon
Senior Programmer
Hyper Image Productions
([email-masked])

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

From: [email-masked] (Darin Johnson)
Subject: Re: Korn Shell '93 Now Available from AT&T
Date: 01 Oct 1994 21:23:54 GMT

>     What does ksh do that BASH can't do?
> 
> How about coprocess communication (print/read -p ...), the "select" statement,
> builtin arithmetic, a command line editor which will drop you into vi/emacs,
> and parameter attributes (typeset -LZ ...), to name a few?

This is enough to warrant $99?  You can pay someone that amount
to add it to bash or zsh.

Also - "fc" under both bash and zsh pops up an editor for me.

I find bash and zsh much nicer for interactive use.
--
Darin Johnson
[email-masked]
       Support your right to own gnus.

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

Subject: Re: Try this IPX bridging code ...
From: [email-masked] (Steve Kneizys)
Date: 30 Sep 94 17:59:42 EST

Alan Cox ([email-masked]) wrote:
: In article <[email-masked]> [email-masked] (Steve Kneizys) writes:
: >If somebody wanted to isolate an IPX net/server from the main net
: >in terms of packet density but did not want to change the net 
: >numbers, well, bridging would be an option!  I may decide to add
: >it to my above bridge, as bridging is faster than routing.

: No bridging is normally slower than routing as you process more packets
: at the software level. 

Nah...depends on the speed of your algorithms!  Has nothing to do with
packet density, unless your algorithms are so slow that packets come 
in faster than you can filter them.  Think about it for a second...the
CPU overhead may be different, but network throughput depends on how
much time you spend processing the packet.  If I can lookup an
Ethernet address and determine what interface, if any, to send out
faster than looking up in a table, changing the hop count and
checksum, net number, then sending out then bridging is faster.

There is less CPU overhead though with routing, when packets to be 
routed are the only ones processed.  If this is what you mean by faster
I'd agree to the effect but I'd say you need to change your description
of the phenomena.

Steve...

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

From: [email-masked] (gil filer)
Subject: DOS & Linux on 1GB drive
Date: Sat, 1 Oct 1994 21:24:24 GMT

I have just installed a new HD it is Conner 1GB. I planed to put 250mb for linux and the rest for dos.
dinse dos cant use more the the first 540 mb from the 1GB I had to install Disk Manager (DM) that came with the Had disk.
but what the DM do is make the hole 1GB one partition, and making a new partition table somewhere elese so that fdisk of dos will be able to config.
now, when I run the fdisk from linux diskets, and  I am looking to the disk
I see just one partition and the 1gb is all used up, and I cant use the disk.
what to do?
please send responce to me too.
 -Sefi

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

** 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: [email-masked]

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

    Internet: [email-masked]

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