Subject: Linux-Development Digest #19
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, 12 Aug 94 23:13:05 EDT

Linux-Development Digest #19, Volume #2          Fri, 12 Aug 94 23:13:05 EDT

Contents:
  Re: -= good programmer's editor for X? (John Lellis)
  Re: Registrar for major device #s? (Matthias Urlichs)
  PowerPC Status? General Q's (Philippe Steindl)
  Re: IPX on Linux (Daniel Tran)
  Sony31a Problem 1.1.4x (Clint D Fast)
  Re: Few simple questions... (pommnitz%prometheus.heidelbg.ibm.com@ibmpa.awdpa.ibm.com)
  Re: Kernel panic in 1.1.44 (Martin Ludwig)
  Call for 386BSD Rel.1.0 SIG (Special Interest Group) (Jesus Monroy Jr)
  Bug in xman (N J Bailey)
  Linux Token Ring alpha release (Peter De Schrijver)
  Re: Will check_*_media_change() never be called? (Heiko Schlittermann)
  Re: BOCA ioAT66 serial card?? (Steven Charlton)
  Re: Does anyone use SONY CDU-535 CD-ROM anymore? (Cameron Grant)
  Novell NE2000 Network Card on Linux? ("B. Tucker")
  Re: Read Info docs thru WWW...Was: As; The GNU assembler docs {Q} (Per Abrahamsen)
  Re: Proposal to write a SAMBA fs client for the kernel (Pete Chown)

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

From: lellis@dmccorp.com (John Lellis)
Subject: Re: -= good programmer's editor for X?
Date: 12 Aug 1994 21:52:37 GMT

I know everyone has his favourite, but I'm still a dyed-in-the-wool EDT fan
(from countless years fighting PDPs and VAXen).  Sure am glad to find it on
Linux.  Now my fingers need only consult my spinal cord instead of bothering
my brain.  :-)

--

John Lellis (lellis@dmccorp.com)

--
... Our continuing mission: To seek out knowledge of C, to explore
strange UNIX commands, and to boldly code where no one has man page 4.




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

From: urlichs@smurf.noris.de (Matthias Urlichs)
Subject: Re: Registrar for major device #s?
Date: 12 Aug 1994 23:30:40 +0200

In comp.os.linux.development, article <1994Aug11.213948.16190@brtph560.bnr.ca>,
  denebeim@bnr.ca (Jay Denebeim P025) writes:
> In article <329nqf$ghu@smurf.noris.de> urlichs@smurf.noris.de (Matthias Urlichs) writes:
> >
> >With the new release of the MAKEDEV script, there's not much reason for
> >most drivers to use a fixed major number; MAKEDEV will find out the correct
> >number from /proc/devices.
> >register_{chr,blk}dev() just has to look for an empty slot if it's passed a
> >zero (and return the allocated number so you can unregister yourself).
> 
> This doesn't sound like a good idea to me.  The problem is every time
> the kernel changes the major devices could change.  This adds an

That's why "MAKEDEV update" exists. It recreates all device entries that
moved, in addition to removing old devices or adding new ones.

My /etc/rc script runs "MAKEDEV update" (and the setserial stuff and ...)
while mounting all the non-root partitions; thus, MAKEDEV does not delay
booting.

> initialization order dependency to the major numbers.  Also, I believe
> that replaceable device drivers will mean that either you'd have a
> dependency in the rc file, or at card insertion time.

That's what /proc/devices is for -- it lists the drivers which are
installed in the kernel _right_now_. Loadable drivers are one reason
why this is necessary, and if the a driver can be dynamically added, its
number really shouldn't matter.

-- 
Law of Annoyance:
When working on a project, if you put away a tool that you're certain
you're finished with, you will need it instantly.
-- 
Matthias Urlichs        \ XLink-POP N|rnberg  | EMail: urlichs@smurf.noris.de
Schleiermacherstra_e 12  \  Unix+Linux+Mac    | Phone: ...please use email.
90491 N|rnberg (Germany)  \   Consulting+Networking+Programming+etc'ing     42

Click <A HREF="http://smurf.noris.de/~urlichs/finger">here</A>.

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

From: psteindl@il.us.swissbank.com (Philippe Steindl)
Subject: PowerPC Status? General Q's
Date: 12 Aug 1994 11:47:46 GMT
Reply-To: ilg@imp.ch

Hullo,

what's the status of the Linux PPC port? Is it planned to run on the  
coming PCI 604 etc generation? Thanx

Philippe 

--
====================+===================================================
Philippe Steindl    |                  Any opinions expressed are my own
E-mail: ilg@imp.ch  |                  and not necessarily those of the 
                    |                  Swiss Bank Corporation.
====================+===================================================

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

From: dtran@emelnitz.ucla.edu (Daniel Tran)
Subject: Re: IPX on Linux
Date: Fri, 12 Aug 1994 14:58:57 GMT

In article <CuE3oL.62s@pe1chl.ampr.org> rob@pe1chl.ampr.org (Rob Janssen) writes:

>In <bherrmanCuDLFE.ACK@netcom.com> bherrman@netcom.com (Robert Herrmann) writes:

>>I am looking for software to route Novell IPX packets on a Linux Box.
>>IPX kernal based sockets would also be nice.

>>any pointers appreciated

>Try looking in the kernel sources...  (1.1 series)

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

Anybody got this too work??.  If so, please post your findings.  I would like 
to know and others would too.

Thanks
Daniel Tran - dtran@emelnitz.ucla.edu

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

From: cfast@plains.NoDak.edu (Clint D Fast)
Subject: Sony31a Problem 1.1.4x
Date: Fri, 12 Aug 1994 08:39:46 GMT


Well, I do not know who exactly to mail this to but, if you see this 
message should be forwarded to someone, please do.  Ever since the 1.1.4x 
patches, the Sony-31a driver won't mount or anything. I cannot confirm 
whether or not the 33a works on this, because I don't have one. But when 
it was in my fstab, it seg faulted linux. and after i took it out, and 
tried to mount it with <mount -t iso9660 /dev/cdrom /cdrom> it returned 
mount: read-only filesystem.
  So, i tried the following, and was reported this:
lazlo:/# mount -o ro -t iso9660 /dev/cdrom /cdrom
general protection: 0000
EIP:    0010:0016e29c
EFLAGS: 00010212
eax: 006bdb24   ebx: 001b224c   ecx: 00000000   edx: 00000000
esi: 00199eb0   edi: 00000000   ebp: 00000002   esp: 00242e20
ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 0018
Process mount (pid: 363, process nr: 17, stackpage=00242000)
Stack: 70000000 00000000 00000000 00007000 00000000
Code: c3 90 90 90 90 90 90 90 83 ec 04 83 3d 20 a8 19 00 00 75 4a
Segmentation fault

<there you have it. Like I said, I have no idea who should see this, if 
anyone, but I thought that since the 1.1.x is all test kernels, then I 
should report it to someone.>

--
=============================================================================
 Yet another wonderful  |Clint Fast                   |Clint Fast       
   e-mail reply from    |Email: cfast@plains.nodak.edu|
Clint "I priorities need|               OR            |
to get my order in" Fast|    cfast@badlands.nodak.edu |
==============================================================================

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

From: pommnitz%prometheus.heidelbg.ibm.com@ibmpa.awdpa.ibm.com
Subject: Re: Few simple questions...
Date: 12 Aug 1994 17:41:25 GMT
Reply-To: pommnitz%prometheus.heidelbg.ibm.com@ibmpa.awdpa.ibm.com

>Then explain me, why I get this message:
>Swansea University Computer Society NET3.016

The UNIX domain sockets are part of the standard kernel.

Best regards
    Joerg
================================================================================
Joerg Pommnitz, ARTe Team, IBM Scientific Center Heidelberg, Germany
Mail1: pommnitz%prometheus.heidelbg.ibm.com@ibmpa.awdpa.ibm.com
Mail2: jpo@vnet.ibm.com
Tel. : Germany (06221) 59 3609


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

From: ludwimax@rubc.rz.ruhr-uni-bochum.de (Martin Ludwig)
Subject: Re: Kernel panic in 1.1.44
Date: 12 Aug 1994 21:12:02 GMT

Hello!

The kernel panic happens in 1.1.35, too. I tried now swap partition and
a swapfile: both lead to the kernel panic.

Martin

Martin.Ludwig@ruba.rz.ruhr-uni-bochum.de


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

Crossposted-To: comp.os.os2.programmer.misc,comp.os.minix,comp.os.mach,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.storage,comp.sys.ibm.ps2.hardware
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Call for 386BSD Rel.1.0 SIG (Special Interest Group)
Date: Fri, 12 Aug 1994 20:32:49 GMT

 
                        -------------------------------
                        Call for Special Interest Group
                        Call for Special Interest Group
                        Call for Special Interest Group
                        -------------------------------
 
 
        OVERVIEW
        --------
        In the beginning there was BASIC and there was Bill!
 
        And then Bill said unto the users,
 
        Let there be DOS, and there was DOS
        Let there be CD-ROM, and there was CD-ROM
        Let there be Mice, and there were mice
        Let there be Windows for mice to run in, and there were.
 
        It's all very BASIC you see
        McNealy is saving Jobs,
        Sculley is out of the job, and
        Hewlett-Packard is giving us the Wave.
 
        Luckily, Cray is still Super,
        DEC is doing the Alpha,
        Wang is no longer in the Lab, and
        Philips is just one screw loose.
 
        AT&T has called it quits (or so they say),
        Xerox still can't 'C', for the life of me,
        Kodak is back into the picture, but is no longer Interactive,
        Novell had to Unix, just to be Word Perfect,
        And IBM has bitten the Apple in a RISCy sort of way.
 
        To make this perfectly clear,
        To be PC the master/slave relationship is now client/server.
        So now NT is out and Chicago, Cairo, and OLE (2.0) are on the the way.
        Sure it's great, unless your OPEN, COSE or ready to P-P-P.
 
        Mach my words, OSays I! Enterprise-wide or Right-Size,
        the biggest GUI still comes from Nintendo, and
        whether you ISDN (via a baby bell) or not,
        WAN you least expect it Bill will turn the boat.
 
 
 
                  -----------------------------------------
                  A call for a 386bsd release 1.0 SIG group
                  A call for a 386bsd release 1.0 SIG group
                  A call for a 386bsd release 1.0 SIG group
                  -----------------------------------------
 
                In the years that have past, one might consider
        casualty to  be  a detrimental commodity; it  is  not.
        Foul words,  sharp metaphors, colourful reflections and
        attributes for change  bring us volte-face.  Even today
        my considerations are  how  many more sleepless vigils
        will be necessary.
 
                Taking everything into account would be an abnormal
        expenditure of time; I can only reflect on what  might be
        considered good.   So today,  I call upon you to appraise
        the advent of release 1.0.
 
                Official - no less, this version promises more!
        "What", I can not say.   None the less, the i386 (and family)
        are  quickly  becoming the de facto  standard  for personal
        computer development.   This and the accomplishments of fast
        BUSes  (PCI and VESA)  have determined the uses and
        applications that we must adapt to.
 
                Looking more toward the future,  parallel and 64-bit
        processors are our next paradigms to consider.  Yet at the
        same time -- we are keep constant with a common neumonic set.
        This is not to say that other ideas such as RISC,  AI  and
        robotics  will not  come into  our perspective,  it is just
        that as a purely volunteer effort our resources are
        constrained.
 
                In conclusion, we must assume that our best guesses
        are only confirmable by their creativeness -- which is a factor
        of our science.
 
 
 
        What is 386BSD release 1.0?
        ---------------------------
                386BSD release 1.0 is THE OFFICIAL release from
        William and Lynn Jolitz for the computer science community.
        Rumored to be using a Tardis in his development effort,
        Bill state plainly, "This is AT&T source free."
 
                Vaporware.. is term we use to describe the undelivered
        promise.  Many companies (groups, corporations, individuals,
        clusters, cliques) are considering the "next step" (no pun
        intended).  Indeed, some fantasies consist of the belief that
        the game is played with "wild cards" and "the queen of
        spades".
 
                Certainly, one or two of you are wondering, what the
        hell I'm babbling about.   The winter of '91 was time I decide
        to join in the work for 386bsd.   Certainly, like the next
        person I have my had share of disappointments, but I believe
        I have put my differences aside.
 
                386BSD is the hope that what is familiar to us will
        return.   386BSD is more than just another effort by Bill and
        Lynn.  It is a new direction.   It is a turn -- to counter
        indifference.
 
 
        Why  a  SIG?
        ------------
                Everyone-of-us is believing that there is something
        in this  "*BSD" for us.  There is.
 
                SIGs in the past had been a mecca, have you, for
        similar "types" to gather.   Not just for consuling, but for
        a locale to conclude that the decision "to collect resources
        here"  is correct.   I still don't own a HP logic analyzer,
        but I still have the dialect to say, "What can I do?"
 
                This means that a forum must develop where new
        ideas can be discussed without the bicker of despise.
        I will ask that comp.os.386bsd.*, and others, consider
        my proposition.   After all -- this is the day when we must
        survive by our minds, not our physical abandonment.
        The aim here is, of course, to put comp.os.386bsd.* back
        on track.
 
                I ask for your help.
 
                To aid in the recover, I ask that someone start a
        newsletter.  Not just any newsletter, but  letter for
        *BSDer's.
 
 
        When will you hear more?
        ------------------------
                August the 17th is said the day to be William and Lynn
        Jolitz will discuss their new strategy for 386bsd.  We will
        meet at Sun MicroSystems in building 6.
 
            Your presence is requested.
 
            More announcements will follow.
 
 

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

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

Crossposted-To: comp.windows.x
From: een6njb@sun.leeds.ac.uk (N J Bailey)
Subject: Bug in xman
Reply-To: een6njb@sun.leeds.ac.uk
Date: Fri, 12 Aug 1994 17:38:29 GMT

xman-3.1.5 exits with a segmentation fault when attempting to print
an emboldened bullet character from a preformatted man file.

Where observed: linux (slackware 1.2.0) kernel 1.0.8, X11R5, Xview v.3.2

Just thought you'd like to know!

Too trivial to fix.



---
===============================================================================
Nick Bailey                             Telephone: +44 532 332057
Lecturer in Electronic Engineering      Facsimile: +44 532 332032     
University of Leeds
Woodhouse Lane
Leeds LS2 9JT
United Kingdom
===============================================================================



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

Date: Fri, 12 Aug 1994 17:10:32 +0200
From: stud11@cc4.kuleuven.ac.be (Peter De Schrijver)
Subject: Linux Token Ring alpha release

Hi,

I have put the first alpha release of the token ring support for Linux as
/pub/Linux/incoming/linux-1.1.44-TR.tar.gz on sunsite.unc.edu. This is
a copy of me current linux source tree. Little testing has been done on this
version, but TCP and NFS seems to work. Source routing hasn't been tested at
all, so expect major bugs there.

Peter.

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

From: heiko@lotte.sax.de (Heiko Schlittermann)
Subject: Re: Will check_*_media_change() never be called?
Date: Fri, 12 Aug 1994 16:47:24 GMT

In article <32bc82$1id@panix3.panix.com>,
S. Joel Katz <stimpson@panix.com> wrote:
>In <CuBx8D.BB@lotte.sax.de> heiko@lotte.sax.de (Heiko Schlittermann) writes:
>
>>Im missing calles to check_*_media_change() ... I thought it would be
>>a task of some fs code to check the media_change state of the device,
>>at least when mounting it.  What happened to this call?
>
>       The check_*_media_change is now called from the operations 
>structure. The older versions of the driver had this structure two 
>elements shorter, media check and revalidate. It should be called through 
>that opreations structure now.

What's the kernel version this information is based on?  I just
looked into my include/linux/fs.h source and found a file_operations
struct one entry longer then my used (fsync is added), but no
media_change or related stuff.

-- heiko

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

From: steven@gsb019.cs.ualberta.ca (Steven Charlton)
Subject: Re: BOCA ioAT66 serial card??
Date: 12 Aug 1994 15:21:45 GMT

My apologies for forgetting useful information.  I am running under
Slackware 1.2 with the kernel upgraded to version 1.1.35, and in
actuality, the UARTS used on the BOCA ioAT66 are three 16C552 UARTs.

Steve

steve@mainland.ab.ca   or   steven@cs.ualberta.ca

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

From: gandalf@vilnya.demon.co.uk (Cameron Grant)
Subject: Re: Does anyone use SONY CDU-535 CD-ROM anymore?
Reply-To: Gandalf@vilnya.demon.co.uk
Date: Fri, 12 Aug 1994 21:05:52 +0000

In article <CuBAnG.GAs@ccult1.comcons.nl>
           dehartog@ccult1.comcons.nl "Hans de Hartog" writes:

>YES! PLEASE keep the Sony535 as a standard in future kernels!
>I'm currently stuck with 1.0.<something> because of this!

It patches okay into 1.1.22

-- 
_.-=======================================================================-._
|  Cameron Grant  | GCS/M/S -d+(--) H s--:--- g+ p5+ au++++ a-- w+ v+ C++++ | 
| Hardware//CodeX | UL++++ !P L++ 3 N+++ K++ W(-) M-- V- -po+ Y+ t+ 5+ !j R |
|     gtg@IRC     | G? tv b+++ D+ B--- e* u+(-) h(!) f(+) r-->++ n- !y+(**) |
|  SRD: 24/07/94  | gandalf@vilnya.demon.co.uk : 100031.2265@compuserve.com |
`-=========================================================================-'



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

From: "B. Tucker" <btucker@medsup.com>
Subject: Novell NE2000 Network Card on Linux?
Date: Fri, 12 Aug 94 13:14:34 CDT

Newsgroups: comp.os.linux.development
Path: btucker
From: btucker@medsup.com (B. Tucker)
Subject: Novell NE2000 Network Card on Linux?
Organization: Medical Support Services
Date: Fri, 12 Aug 1994 18:14:31 GMT
Message-ID: <1994Aug12.181431.11578@medsup.com>

Does the Slackware version of Linux have support for the Novell NE2000
Ethernet card?  If not, are there plans for this card being used by Linux?

Please reply via e-mail to:
btucker@medsup.com

Thanks for any info!

Brian Tucker


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

From: abraham@iesd.auc.dk (Per Abrahamsen)
Crossposted-To: alt.religion.emacs
Subject: Re: Read Info docs thru WWW...Was: As; The GNU assembler docs {Q}
Date: 13 Aug 1994 00:34:22 GMT


Just in defence of us certified Emacs bigots...  Some of us prefer
HTML to info too, we just use w3.el to read it :-) 

HTML looks much better with XEmacs than info.

Followups redirected since this has nothing to do with the development
of Linux. 

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

From: pc@dale.dircon.co.uk (Pete Chown)
Subject: Re: Proposal to write a SAMBA fs client for the kernel
Date: Fri, 12 Aug 1994 11:31:25 GMT

In article <1994Aug9.103118.3352@ritz.equinox.gen.nz> grantma@ritz.equinox.gen.nz (Matthew Grant) writes:

> As you all know, the SAMBA server and ftp like samba client are available for
> Linux, and they do work.

(Perhaps people don't know: Samba is an implementation of NetBIOS for
Unix, so Unix boxes can interact with Windows for Workgroups PCs etc.)

> A SAMBA fs client in the kernel would 
> offer a way out for us all.  With the upcoming release of 1.2.0, I propose
> to port/write this for the kernel based on the 1.2.x source for patching
> into 1.3.x or for use with the 1.2.0 kernel.

This is already being done - not exactly in the way you anticipate,
but as a client of userfs.  I suspect this may well be better, since
it will keep as much code as possible out of the kernel, which is big
enough already.

> I would like to be able to pump 1 MB/s through it, as I have seen how
> slow nfs is at present.

You will not get 1M/s; this would saturate the ethernet even before
allowing for acknowledgements, collisions and so on.  A more sensible
target would be to get a speed comparable to FTP - about 250k/s on an
isolated ethernet (and with a reasonable quality network card).
--

==========================================================================
Pete.Chown@dale.dircon.co.uk          "The Pen is mightier than the Quill"
                                      -- anonymous

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


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