Subject: Linux-Development Digest #39
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:     Thu, 18 Aug 94 09:13:04 EDT

Linux-Development Digest #39, Volume #2          Thu, 18 Aug 94 09:13:04 EDT

Contents:
  Report on SVNET: Bill Jolitz's Talk; Mind Overload. (Jesus Monroy Jr)
  Re: Matrox Ultima drivers????
  Re: sbpcd ejects on umount in 1.1.44 (Chris Tilbury)
  Re: Which linux 1.1.x versions are stable? (Hans-Christoph Rohland)
  Lack of support for > 1G hard drives and fix (Thomas E Zerucha)
  Re: Adaptec AHA 2940 (Doug McIntyre)
  Segmentation fault in ping? (Sam Oscar Lantinga)
  Re: Suggestion for Linux (Bruce Stephens)
  LOOPBACK Driver needs a little work. (Chip Edwards)
  Re: SCSI out of mailboxes (Tin Le)
  Re: Novell interfacing experience? Anyone using samba? (Rob Janssen)
  Compiling NN for NNTP support. (lcvanveen@et.tudelft.nl)
  Re: 1.1.43 WD8003 broken? (Hannes Reinecke)
  Re: Which linux 1.1.x versions are stable? (S.G. de Bruijn)
  SCO Ingres and Linux ? (Janne Soimasuo)
  Re: 1.1.45 floppy bug (Rick)
  mount(2) parameters (Jim Trocki)

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

Crossposted-To: comp.unix.bsd,comp.os.386bsd.development,comp.os.386bsd.bugs,comp.os.386bsd.apps,comp.os.386bsd.questions,comp.os.386bsd.misc,comp.os.os2.programmer.misc,comp.os.minix,comp.os.mach,comp.unix.pc-clone.32bit
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Report on SVNET: Bill Jolitz's Talk; Mind Overload.
Date: Thu, 18 Aug 1994 09:40:12 GMT

 
 
                A review of Bill Jolitz's talk with the SVNET
                _____________________________________________
                
                My mind is on overload, but here are some of the details. 
 
                As many of you know the SVNET has been a supporter
            of Bill Jolitz's work, 386BSD,  tonight seemed to be no
            exception in the things we see from Bill and Lynn.
 
            First is first: The release date....
 
                    The word was: the CD is still "under production".
                    In Bill and Lynn's words, "The actual shipping
                    date is up to the Editors of DDJ."
                    Call it skirting the issue or passing the buck,
                    the words are now in concrete and a release must
                    be made.
 
            Second: The issue of code reuse....
 
                    Bill and Lynn plainly stated that the code is
                    freely re-distributable and freely re-modifiably,
                    *AS ALWAYS*.
 
            Third: Encumbrance.........
 
                    Always was AT&T code free, always will be.
 
            Fourth: The CD-ROM
 
                    The CD-ROM and the annotations may *NOT* be placed
                    on any FTP'able site for redistribution.
 
            Fifth: Availability of the source.....
 
                    Bill plans, somehow, to setup a FTP'able site
                    for the code's availability.   NO specifics
                    were given on how this was to be accomplished.
                    "It is something for the future", Bill said.
 
            Sixth: BUS support....
 
                    The standard buses (ISA, EiSA) are still in support.
                    However, Bill would like to see *someone*
                    develop code support for PCI and PCMCIA.
 
            Seventh: The VM.......
 
                    The VM has been completely rewritten.
                    In Bill's own words, "We had to rewrite the whole
                    thing, from bottom up"
 
 
            There is more.   It is on video tape.
 
            Person or persons wishing a transcription or a copy
            of the video tape, please contact me.
 
            If you'd like to *bad mouth something* about what
            I said, try a cold shower for twenty minutes
            a stiff drink of scotch,  and have sex for two or three
            hours,,,, then post your message or e-mail me.
 
 
            Last words, from Lynn, "This is brand new and different.
            People will have to consider things carefully before
            throwing in their favorite widget;  after all this is
            supposed to be an educational tool."
 
 

-- 
Jesus Monroy Jr                                          jmonroy@netcom.com
Zebra Research
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________

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

Date: Wed, 17 Aug 1994 23:06:16 CDT
From: <U62323@uicvm.uic.edu>
Subject: Re: Matrox Ultima drivers????

Looks like you are not the only one, who is interested in drivers
for Matrox. If you find out any thing about it, please let me know
My E-mail is rgebis@ernie.eecs.uic.edu.
Thanx.  R.J.G

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

From: cjt@aspen.estate.warwick.ac.uk (Chris Tilbury)
Subject: Re: sbpcd ejects on umount in 1.1.44
Date: 18 Aug 1994 10:17:50 GMT

Patrick Doyle (wdoyle@hilbert.coe.northeastern.edu) wrote:

: I decided I didn't like this feature either, so I poked around sbpcd.c
: and found that the only reference to EJECT was something of the form:

: #ifdef EJECT
:   yy_SpinDown(...)
: #endif

: Which means the yy_SpinDown will be called regardless of the value of
: EJECT.  I simply placed an "#if 0/#endif" pair around this piece of
: code and now the CDROM does not eject automatically.  I found this
: feature particularly annoying when I started "workbone", started
: playing a CD, and exited workbone.  Upon exit, the CD ejected!  (Thus
: making it dificult to continue listening to the lyrical tones of Billy
: Joel :-).

Over on c.o.l.h someones already suggested perhaps an option in the
kernel makefile to turn this feature off; how difficult would it be to
extend this a little further, to add a new mount flag "noeject" (or
"eject") which changed the behavouir at mount time?

Just a thought ...

--
Chris Tilbury, Estates Office, Warwick University, Coventry, CV4 7AL, England
INET:    C.Tilbury@warwick.ac.uk           PHONE:    +44 1203 523430 (phONEday)
Click <a href="http://information.estate.warwick.ac.uk/~cjt/">here</a>.

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

From: hrohlan@gwdg.de (Hans-Christoph Rohland)
Subject: Re: Which linux 1.1.x versions are stable?
Date: Thu, 18 Aug 1994 09:30:14 GMT

pageone@netcom.com wrote:

:       That's the question... I'm trying to figure out which versions are
: safe to use... or should I just stick with 1.0.9 for a while?
:       I've been seeing a lot of complaints over the 1.1.4x releases, and
: I might need a umsdos-compatible kernel, which probably excludes the non-
: slackware 1.0.9 :(...
:       If anyone can post responses in the group, I'd sure like them!  Thanks.

I used 1.1.3 for ~4 months without any problems, but it was the old
networking stuff. My box is running as a NFS-Server for 7 Doses.
Just now I am trying 1.1.36 since two weeks. Until now no probs, but you
have to change some networking tools...
IBCS is running under 1.1.36. I tried the wp.demo. Really nice.

:       - Chad Page

Christoph

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

From: zerucha@shell.portal.com (Thomas E Zerucha)
Subject: Lack of support for > 1G hard drives and fix
Date: 18 Aug 1994 02:52:47 GMT

I have noticed that many SCSI drivers don't implement biosparam correctly
for disks > 1G.  What follows is code that exactly duplicates the Qlogic
DOS driver's parameter returns.  It is possible that a DOS version of one
of the older drivers also cannot support >1G drives.  Here is the list:


Drivers that cannot go above 1GB (because they only support 64/32/<1024).

aha152x         aha1740         pas16           t128            wd7000


Drivers that implement large partitions (though may not do the 8Gb
truncation, and may not do exactly 1Gb partitions the same)

aha1542         buslogic


Drivers that have a custom system for determing this

fdomain         segate          ultrastor       53c7,8xx


The following is my code for this function and has been verified:
---cut here--- 
int                 qlogic_biosparam(Disk * disk, int dev, int ip[])
{
/* This should mimmic the DOS Qlogic driver's behavior exactly */
        ip[0] = 0x40;
        ip[1] = 0x20;
        ip[2] = disk->capacity / ( ip[0] * ip[1] );
        if( ip[2] > 1024 ) {
                ip[0] = 0xff;
                ip[1] = 0x3f;
                ip[2] = disk->capacity / ( ip[0] * ip[1] );
                if( ip[2] > 1023 )
                        ip[2] = 1023;
        }
        return 0;
}
---cut here---
Notes: The first three lines of the routine handle <= 1Gb partitions.
Since ip[2] is number of cylinders v.s. the dos call which returns the
largest cylinder, 1024 under Linux will be 1023 under DOS and will fit
in the appropriate API calls.  The code within the first if handles larger
disks.  Normal DOS cannot return cylinder numbers higher than 1023, so the
last if truncates it (notice that I duplicate the 1023 as used by the DOS
driver although 1024 would work).

Advanced DOS BIOSes can go up to 4096 cylinders.  I don't know if any SCSI
drivers allow this.  I also don't know if any DOS drivers only support <1Gb
SCSI disks, so adding the above code to a driver would confuse the DOS
side on such a card.  It is also possible that different drivers have a
different 1Gb or 8Gb cutoff.

---
zerucha@shell.portal.com - main email address


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

From: merlyn@icicle.winternet.com (Doug McIntyre)
Subject: Re: Adaptec AHA 2940
Date: 18 Aug 94 00:00:02 GMT

dt10596@renoir.cftnet.com (Jeff Redding) writes:
>If your the hardy type, you might want to take a crack at converting
>the aha274x driver.  I've been working on the aha284x driver, and I
>know the 294x is AIC7770 based too.  It shouldn't be a big deal
>to hack the one you need.

Nope, the 2940 uses the AIC7870 chip. It is extremely simular, but
of course is different from the AIC7770 used in the 274x and the 284x
cards. 
I don't have the low down docs to see what kind of registers and or
sequencer instructions are different.


--
Doug McIntyre                           merlyn@winternet.com

Write to info@winternet.com for more information about Winternet's
Internet services and dialups. 

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

From: slouken@cs.ucdavis.edu (Sam Oscar Lantinga)
Subject: Segmentation fault in ping?
Date: Thu, 18 Aug 1994 02:31:04 GMT


        I am using Linux 1.1.45 and libc 4.5.26 and I get a
segmentation fault it seems whenever I try to create a socket
with ICMP as the protocol type.  I was debugging traceroute,
and here is what I got (running as root):

Breakpoint 1, main (argc=1, argv=0xbffffc6c) at traceroute.c:500
500             if ((s = socket(AF_INET, SOCK_RAW, pe->p_proto)) < 0)
{
(gdb) s
socket (family=2, type=3, protocol=1) at socket.c:13
Source file is more recent than executable.
13              args[0] = family;
(gdb)
14              args[1] = type;
(gdb)
15              args[2] = protocol;
(gdb)
6       _syscall2(long,socketcall,int,call,unsigned long *,args);
(gdb)

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.

        The odd thing is that when running as a normal user,
I get the proper operation not permitted message.  This test
was run on a system mounted on a umsdos root filesystem and
using 3c507 ethernet card.  I have no problems on another system
running the same OS and libs, but with ext2 filesystem and slip
networking.

        Any ideas?

BTW, kudos to the networking people!  I wanted to make a second
loopback device, and it was as simple as adding a second loopback
device entry to the device chain in Space.c 

Thanks!

        -Sam            (slouken@cs.ucdavis.edu)



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

From: bruce@liverpool.ac.uk (Bruce Stephens)
Subject: Re: Suggestion for Linux
Date: Thu, 18 Aug 1994 10:43:45 GMT

>>>>> On 15 Aug 1994 21:16:21 GMT, dranch@ecst.csuchico.edu (David A. Ranch) said:

> Oh Man....  can you say file-name completion?  I believe its been in
> Unix since its inception.

I don't think so.  It has been around for a while, however.  Now that
more Unix boxes have a default shell that has completion, perhaps
there'll be fewer such questions.

(As a plug for zsh, it has programmable completion: that is, you can
set it up so that ghostview, for example, only completes on .ps files,
and ignores others, and that lpr should complete on any file, unless
the -Pps option is given, in which case it should complete on .ps
files, and if -Pdvi is given, it should complete on .dvi.)

-- 
Bruce                    Institute of Advanced Scientific Computation
bruce@liverpool.ac.uk    University of Liverpool

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

From: gt6444c@prism.gatech.edu (Chip Edwards)
Subject: LOOPBACK Driver needs a little work.
Date: 17 Aug 1994 20:53:38 -0400

I have noticed for some of the latter releases of Linux that the loopback
driver is somewhat sloppy.  (kernel 1.1.x and up I believe.) I am presently
running v1.1.45.
   If I do a:

        ping -f loopback

It has a packet loss of about 90% or more! I've noticed every once in a 
while, errors are reported in the loopback device when I do a ifconfig.
Just wondered if anyone else has this problem.
Chip Edwards
-- 
Chip Edwards (gt6444c@prism.gatech.edu)
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp:     ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt6444c
Internet: gt6444c@prism.gatech.edu

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

From: tin@szebra.Saigon.COM (Tin Le)
Subject: Re: SCSI out of mailboxes
Date: 17 Aug 1994 22:54:29 -0700

In article <321dmh$dmo@sun.cais.com>,
Eric Youngdale <ericy@cais2.cais.com> wrote:
>In article <yeul.776016964@marsh>, Loong Yeu <yeul@cs.curtin.edu.au> wrote:
>>
>>Kernel panic : scsi_devices corrupt (sd)
>>In swapper task - not syncing
>
>       This problem should have been corrected in 1.1.40.  The problem 
>with out of mailboxes may also have been fixed along with a bunch of 
>other assorted things.

With two 742A Buslogic adapter, I get out of mailbox panics consistently.
Very light load is ok, but the minute I put any load, such as copying a
large dir tree from a drive on one adapter to a drive on the second will
cause the panic.

This is with 1.1.44.  I did not have a lot of time to look into it, so
tried a few fast things such as increasing number of mailboxes in
drivers/scsi/buslogic.c but that does not help.  With one adapter, it
is rock solid... albeit not as fast as it would with two... :-(

Tin Le

-- 
============
Tin Le       Internet: tin@TLsoft.COM   _or_   tin@Wuarchive.wustl.edu
Moderator of comp.binaries.ms-windows | Submissions to cbmsw@Saigon.COM
CBMSW Archive on Wuarchive.wustl.edu  | Questions to cbmsw-request@Saigon.COM

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

Crossposted-To: comp.os.linux.misc,comp.os.linux.help
From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Novell interfacing experience? Anyone using samba?
Reply-To: pe1chl@rabo.nl
Date: Thu, 18 Aug 1994 07:02:48 GMT

In <32tq0t$ksc@linda.teleport.com> zaphod@teleport.com (Zaphod Beeblebrox) writes:

>If anyone has any good or bad experiences attempting to network up with
>novell, can you please give me any words of advice?  I have this linux
>package called samba that does interfacing to novell.  Does anyone have
>this installed in their system?

>Any and all comments are appreciated.  Thanx in advance!

I advise you to first read its documentation.  Samba and Novell have
nothing to do with eachother.

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

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

From: lcvanveen@et.tudelft.nl
Subject: Compiling NN for NNTP support.
Date: 18 Aug 94 12:59:17 +0200

Anyone ever tried to compile NN for Linux?
The files in src, that come with the nn.tgz file
in slackware, sure ain't much help.
Any help is very appreciated.
Thanks a lot in advance.
Martijn.

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

From: hare@zarquon.mathi.uni-heidelberg.de (Hannes Reinecke)
Subject: Re: 1.1.43 WD8003 broken?
Date: 18 Aug 1994 11:48:15 GMT

Hi all,
i think i had the same problem some years ago while working ( or
merely trying to work ) on an old 386DX with an 8003 card. 
If i remember rightly, the trick was to explicitly declare in the
kernel sources that the 80x3 should be probed as an 8003 ( somewhere
in linux/drivers/net/CONFIG (?) ). But i thought this was solved in
the more recent kernels.
Anyhow, the SMC Ultra works great :-).

Hope this helps

Hannes
======
Hannes Reinecke                      |
<hare@vogon.mathi.uni-heidelberg.de> |  XVII.: WHAT ?
                                     |  
PGP fingerprint available            |          T.Pratchett: Small Gods
see  'finger' for details            |          

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

From: debruijn@cs.utwente.nl (S.G. de Bruijn)
Subject: Re: Which linux 1.1.x versions are stable?
Date: Thu, 18 Aug 1994 11:39:18 GMT

Holger Mueller (holgi@rbg.informatik.th-darmstadt.de) wrote:
: pageone@netcom.com wrote:

: :     That's the question... I'm trying to figure out which versions are
: : safe to use... or should I just stick with 1.0.9 for a while?

: I could just post my experience:
: 1.1.3x --> 1.1.44 were more or less instable for me, having panics and more.

: 1.1.45 now works again since a few days without any panic.
: Before 1.1.45 i was using 1.1.9 all the time which never crashed on my machine.

: Remember, this is only MY experience, but you may go and try it out.
: Keep a copy of your old kernel handy!

: Maybe you should just cp your old vmlinuz to vmlinuz.rescue and add an
: rescue entry into your lilo.conf.

I have had great stability with 1.1.17 and 1.1.36. Stick with it until I see no more
problems with the new ones... (ftape/1.1.45 for example)

Bye,
Steef
==============
S.G. de Bruijn              E-Mail: debruijn@cs.utwente.nl
Twente University of Technology, Dept. of Computer Science 
Enschede                                   The Netherlands
Phone: Work: +31 53 894191             Home: +31 53 334812
=========================== @@ ===========================
signature: file not found

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

From: jsoi@cs.joensuu.fi (Janne Soimasuo)
Subject: SCO Ingres and Linux ?
Date: Thu, 18 Aug 1994 11:50:51 GMT

[ Article crossposted from comp.databases.ingres ]
[ Author was Janne Soimasuo ]
[ Posted on Thu, 18 Aug 1994 11:47:48 GMT ]

Has anyone tested SCO ingres binaries with Linux + ibcs-module ?

I've heard that Oracle and Informix will work but how about Ingres ?

janne


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

From: pclink@qus102.qld.npb.telecom.com.au (Rick)
Subject: Re: 1.1.45 floppy bug
Date: Thu, 18 Aug 1994 00:13:37 GMT

ftlofaro@unlv.edu (Frank Lofaro) writes:

>There is a bug in the 1.1.45 floppy driver.

>34: 21:18:27: /: whitney# swapon /dev/fd0H1440
>floppy: disk absent or changed during operation
>floppy I/O error
>dev 021C, sector 0

It's not just swap - try booting a ramdisk.  Haven't tracked
the problem yet.

Rick.
-- 
Rick "JT" Lyons   | C/C++/x86/X           | What claim?  Dis claim!
Telecom Australia | Unix/DOS/Novell       | Usenet before net uses you.
ACN 051 775 556   |                       | 
work:pclink@qus102.qld.npb.telecom.com.au | play:rick@razorback.brisnet.org.au

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

From: trockij@Cyanamid.COM (Jim Trocki)
Subject: mount(2) parameters
Reply-To: trockij@Cyanamid.COM
Date: Thu, 18 Aug 1994 12:06:50 GMT

  I need to use the mount(2) call from one of my utilities, but I'm not sure of
the last two parameters, which are "unsigned long rwflag, const void *date".
I need to mount a floppy w/MSDOS filesystem as read-only. Here's what I
am doing:

mount ("/dev/fd0", "/mnt", "msdos", 0, "");

(since I am unsure of correct values for those params). It doesn't work.

  I'd search this out in the kernel if I knew where to go :), but I'm not familiar
with the layout of the kernel source tree.

  Any help is appreciated.

Jim Trocki




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


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