Subject: Linux-Development Digest #309
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:     Wed, 15 Dec 93 11:13:06 EST

Linux-Development Digest #309, Volume #1         Wed, 15 Dec 93 11:13:06 EST

Contents:
  Bug ? (Meng-Fong Chen)
  Can I Init a SCSI after boot? (David J. Mayer)
  dld for Linux? (Craig Anderson)
  VFS?  How does Linux support foreign filesystems? (Peter A Dinda)
  Re: Has any one ported MAGIC v6 and SPICE3 to LINUX??? (Andreas Pohl)
  Re: xBASE for Linux? (Andrew E. Walenstein)
  Re: Booten mit Adaptec 1542C (Eric Youngdale)
  Re: Has any one ported MAGIC v6 and SPICE3 to LINUX??? (Mike Engelhardt)
  Re: Has any one ported MAGIC v6 and SPICE3 to LINUX??? (Steven Buytaert)
  Re: Merry $*!@ing Christmas! (Rob Knauerhase)
  ISDN for Linux ???
  Joystick device for Linux (Arne Stoffregen)
  Re: Using cluster0.5 +pl14 DOUBLES I/O - Performance (Mark Buckaway)
  Re: ISDN for Linux ??? (Systemkennung Linux (noalias))
  Re: What is JAM? (Re: What tools would you u (Basile STARYNKEVITCH)

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

From: v068sgyt@ubvms.cc.buffalo.edu (Meng-Fong Chen)
Subject: Bug ?
Date: Tue, 14 Dec 1993 23:41:00 GMT

Hi, I did not know if this is the sure place to report a could-be-a-bug, but
cannot find a more suitable place, so:

After I got my libc.so.4.4.4. and libm.so.4.4.4. (and relinking libc(m).so.4
 to them), everything works fine. But there is one problem:
I cannot access Tek window. I am using X86 or (X11 window, I don't know which
one is more appropriate). There are 2 selections of windows under the 
mouse button2. The other is the default: Vt window. I found that I cannot
access Tek window(the 2nd window). It just kill the window.  This would never
happen when I had my .4.3.3.  So I relink these .so.4 back to .4.3.3.  It
works fine !

     I want to verify this with someone else because I did not upgrade my
kernel from .99.9 to .99.13; I just relinking my .so.4 to .so.4.4.4. I would
like to listen to a person who has upgraded thoroughly to .99.13 to say if
his is o.k.

Mike


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

From: dmayer@netcom.com (David J. Mayer)
Subject: Can I Init a SCSI after boot?
Date: Tue, 14 Dec 1993 21:55:45 GMT

I have a removeable SCSI drive. The entire drive slides out of the docking
bay.  So when the PC reboots, the drive is not recognized.

My problem is that the app I am writing will need to _sonehow_ tell the scsi
driver (and/or host) that a drive has been inserted into the docking bay.

Does anyone know if this is possible?

Thanks,
Dave

-- 
David J. Mayer                    |     Internet:         dmayer@netcom.COM
Channelmatic, Inc.                |   Compuserve:                 70445,102
Alpine, CA.                       |       Packet:  N6RYC@n6ooi.#socal.ca.na

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

From: c4craig@csn.org (Craig Anderson)
Subject: dld for Linux?
Date: Wed, 15 Dec 1993 02:04:55 GMT

Is the dynamic linking package dld available for Linux?
If not is there some other way to do dynamic linking.
I would like to experiment with gcc objective-c and dynamic
linking.

Thanks,

Craig H. Anderson
craig@csn.org


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

From: pdinda+@CS.CMU.EDU (Peter A Dinda)
Subject: VFS?  How does Linux support foreign filesystems?
Date: Wed, 15 Dec 1993 02:55:40 GMT

We have written a filesystem that talks to the Mach Unix Server via the
VFS interface .  Some of it is somewhat Mach specific (it uses malloc, for
example), but should be relatively easy to port to VFS on a traditional
Unix.  Does Linux support VFS?  Any pointers to how to add a foreign
filesystem to Linux?

 

-- 
Peter A. Dinda (pdinda@cs.cmu.edu)
Ph.D. Student, School of Computer Science, Carnegie Mellon University

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

From: mookie@nostaki.toppoint.de (Andreas Pohl)
Subject: Re: Has any one ported MAGIC v6 and SPICE3 to LINUX???
Date: Wed, 15 Dec 1993 01:24:22 GMT


Hi !

I have a working version of magic 6.3 running under my X & Slackware 1.0.4

I think I have it from nic.switch.ch, which is another mirror of 
sunsite.unc.edu

Try ftp'ing!

CU, Andy Pohl
mookie@nostaki.toppoint.de

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

Crossposted-To: comp.databases.xbase.misc
From: walen@cs.ualberta.ca (Andrew E. Walenstein)
Subject: Re: xBASE for Linux?
Date: Wed, 15 Dec 1993 05:08:51 GMT

Robert_Broughton@mindlink.bc.ca (Robert Broughton) writes:
>Does it exist?
>Robert Broughton    Robert_Broughton@mindlink.bc.ca

I've gotten the portability version of CodeBase 5.0 to compile under
Linux (ok, a more vintage version .99.12) as a single user (no locking).
For those of you not familiar, CodeBase is a C/C++ library for handling
xBASE-type files (clipper,dbase,foxpro), just look in Dr Dobbs, etc. for
ads.

If you're interested, I compiled it "out of the box" with S4CLIPPER,
S4SINGLE, S4DEBUG, and S4OPTIMIZE_OFF switches, and only had to change one
line in p4port.h due to conflicting signatures for memmove.  Haven't really
tested its stability:  the "tests" ran without hitches.

The only drawback is that CodeBase is a commercial product--seems a
bit out of place on Linux right now....and as far as I know, the Linux
port its not officially supported by the company, Sequiter Software.

Andrew
--
walen@cs.ualberta.ca
--
Andrew Walenstein,  walen@cs.ualberta.ca

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

From: eric@tantalus.nrl.navy.mil (Eric Youngdale)
Subject: Re: Booten mit Adaptec 1542C
Date: Wed, 15 Dec 1993 06:18:39 GMT

In article <2ekmhq$6d8@internet.posc.org> waddell@posc.org writes:
>In article <CHwHCD.Ap5@ra.nrl.navy.mil>, eric@tantalus.nrl.navy.mil (Eric Youngdale) writes:
>I have a 1542C with a 2GB disk. Do I have to turn off >1GB disk support to boot
>Linux or has anyone got a fix yet? If necessary I can spare some time to help.

        Yes, hot off the press.  After the last time I posted here I got email
from someone that described how to fix the 1542 driver to "unlock" the
firmware.  I have made patches and they have been tried by a few people and
they seem to work, but I want to make sure that they really do the right thing
all of the time, and I would like to get more people to try them out.  The
patches can be found on tsx-11.mit.edu in pub/linux/ALPHA/scsi/scsidiff.pl14.
Note that these patches fix a couple of misc problems - the patches to
aha1542.c and aha1542.h are the relevant ones here.

>Trying to boot the 1542C produces the message described in the SCSI-HOWTO
>aha1542_out failed(1):aha1542.c: interrupt received, but no mail
>After the second message it just hangs.

        With the above described patches the kernel should boot normally with
the > 1Gb firmware enabled.  Same goes for the more than 2 disks and the
dynamic scan of the scsi bus firmware options.

-Eric
-- 
"The woods are lovely, dark and deep.  But I have promises to keep,
And lines to code before I sleep, And lines to code before I sleep."

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

From: engel@netcom.com (Mike Engelhardt)
Subject: Re: Has any one ported MAGIC v6 and SPICE3 to LINUX???
Date: Wed, 15 Dec 1993 07:57:32 GMT

gshin@kilby.elee.calpoly.edu asks:
 
> Has anyone ported [deleted] Berkeley's SPICE3 [deleted]?
 
I ported spice3e2.  The patch kit is available as, e.g.,
sunsite.unc.edu:/pub/Linux/X11/xapps/spice.kit.T.Z
 
--Mike Engelhardt

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

From: buytaert@imec.be (Steven Buytaert)
Subject: Re: Has any one ported MAGIC v6 and SPICE3 to LINUX???
Date: Wed, 15 Dec 1993 08:33:45 GMT

George Shin (gshin@kilby.elee.calpoly.edu) wrote:
: Has anyone ported Berkeley's MAGIC (VLSI CAD software) version 6 or/and Berkeley's  
: SPICE3 program to LINUX OS??? Currently I'm running those two programs under

 Hi,

 Download from sunsite.unc.edu in directory /pub/Linux/docs/LSM. The Linux
 software map. In there you'll find Magic, OCEAN, Spice 2g6 (IMHO still 
 superior than any version 3 spice...)

 Bye

--
Steven Buytaert 
Interuniversity Micro Electronics Centre - Invomec Division
Kapeldreef 75, 3001 Heverlee, BELGIUM

phone   : +32 16 281 271
fax     : +32 16 281 584
e-mail  : buytaert@imec.be
                In case of danger, BREAK glass

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

Crossposted-To: comp.infosystems.www,comp.windows.x,comp.windows.x.i386unix,comp.windows.x.motif,gnu.misc.discuss,comp.sources.d
From: knauer@ibeam.intel.com (Rob Knauerhase)
Subject: Re: Merry $*!@ing Christmas!
Date: Wed, 15 Dec 1993 08:19:43 GMT

In <CHMB0z.ALE@murdoch.acc.Virginia.EDU> jeg7e@Hopper.ITC.Virginia.EDU (Jon Gefaell) writes:
[vituperation deleted]
>NCSA is not some private corporation, you do realize this don't you? It is
>paid for by the taxpayers money and should be responsive to the needs of the
>community it is intended for. If those people (your underwriters and audience)
>are complaining, you need to hear that and respond. If you want to do your
>own thing then start your own company with your own capital. In the meantime
>you work for us. 

Jon is apparently unacquainted with just what the acronym "NCSA" stands for
(National Center for _Supercomputing_ Applications).  So, unless you have a
Paragon or a Cray on your desk, they in fact *don't* work for you.

Rob
--
Rob Knauerhase   [knauer@ibeam.intel.com]   Intel Mobile Software Lab
  "... the industry's future may be taking shape in a secluded Intel
   Corporation laboratory tucked among the farm fields of Oregon."
     -- John Markoff, _New York Times_


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

From: alex@psyalex.psy.gu.se ()
Subject: ISDN for Linux ???
Reply-To: alex@psyalex.psy.gu.se
Date: Wed, 15 Dec 1993 09:45:22 GMT

Hi !

Is there anybody in Europe (maybe Germany) working with some
kind of ISDN support for Linux.

We are about to get ISDN connections next year and I would just
love to keep Linux on my machine....


/Alex

--
--
+-------------------------------+------------------------------------------------+
| Alex Frausin                  | Haven't been able to steal any good .sig       |
| Gothenburg University         | file lately.                                   |
| Department of Psychology      |                                                |
| Gothenburg, Sweden            | Opinions all mine.......                       |
|                               |                                                |
| alex@psyalex.psy.gu.se        |                                                |
+-------------------------------+------------------------------------------------+

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

From: stoffre@uni-muenster.de (Arne Stoffregen)
Subject: Joystick device for Linux
Date: Wed, 15 Dec 1993 12:11:44 GMT

Hi world!
Sorry if this has been thoroughly discussed before, but
I wanted to know, if anyone has bothered to write a joy-
stick device for Linux. I haven't looked at the source,
but I cannot remember any file with a name like that.
Cleverly I have looked for a /dev/joystick and found none,
so I assumed it does not exist. :-))
I am writing on a 3D kind of a program and would like to
rotate objects with the joystick.
If anyone could give me a hint on who did this before or
how to write a device (I think there is a FAQ for that??)
I would be grateful.

Thanks
Arne

-- 
Arne Stoffregen, Germany
Email:stoffre@uni-muenster.de
  I am Clinton of Borg. Resistance if futile. You will be assimilated.

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

From: mark@datasoft.com (Mark Buckaway)
Subject: Re: Using cluster0.5 +pl14 DOUBLES I/O - Performance
Date: Wed, 15 Dec 1993 04:19:55 GMT

RAINER SCHIELE INFORMATIK (81264@novell1.rz.fht-mannheim.de) wrote:
: Hello out there

: I have installed the new cluster packages on my machine and my I/O - 
: Performance going up to 1,2MB (600kb without). I'm using a DEC DSP3160 and a 
: Adaptec 1542B. My Testtools are Bonnie and Iozone.

: Thanks Eric. Great Work.

: But why is'nt the cluster package in the Kernel!

Hmmmmmmmmmmm....I have not heard of this cluster package. What is it and where
do I get it?

Mark
--
==============================================================================
Mark Buckaway           | root@datasoft.com         |  DataSoft Communications
DataSoft Communications | uunorth!datasoft!root     |  62 Rock Fernway
System Administrator    | Voice: +1 416 756 4497    |  Willowdale, ON M2J 4N5
==============================================================================
    "UNIX and OS/2 are operating systems. Windows is a shell, and
                         DOS is an boot virus"
==============================================================================

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

From: linux@informatik.uni-koblenz.de (Systemkennung Linux (noalias))
Subject: Re: ISDN for Linux ???
Date: 15 Dec 1993 15:17:19 GMT

|> Is there anybody in Europe (maybe Germany) working with some
|> kind of ISDN support for Linux.
|> 
|> We are about to get ISDN connections next year and I would just
|> love to keep Linux on my machine....

One very cheap solution for that problem is using a second PC running
MSDOS and KA9Q. The performance and reliability isn't very high, but
it's very cheap. But if someone could supply hardware docs for the
Teles S0 ISDN card or even better Linux drivers, I'd appreciate that
very much.

-- 
Ralf Baechle

Internet: linux@informatik.uni-koblenz.de
Fido:     Ralf Baechle 2:245/5618.2

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

From: basile@soleil.serma.cea.fr (Basile STARYNKEVITCH)
Subject: Re: What is JAM? (Re: What tools would you u
Date: Wed, 15 Dec 1993 15:56:47 GMT
Reply-To: basile@soleil.serma.cea.fr

JAM is a make-like tool with different syntax and functionalities.

It built straight out of the box on Linux

Jam is Copyright 1993 Christopher Seiwald

You can find it with archie in  /news/comp.sources.unix/volume27 archives

(A big part of)  the jam man page is

JAM(1)                    User Commands                    JAM(1)



NAME
     jam - make(1) redux


SYNOPSIS
     jam [ -n ] [ -d debug ] [ -f Jambase ] ... [ -t target ] ...
     [ target ] ...


DESCRIPTION
     Jam recursively builds target files from their source files,
     using  a  Jambase to define rules and a Jamfile to lists the
     targets and sources in terms of those rules.  Together  they
     define  the dependency tree and the updating actions for all
     targets:  jam does not rely on suffix-driven implicit  rules
     or  directory  contents.  A default Jambase is provided with
     jam; the user supplies the Jamfile.

<< skipped OPTIONS section >>

THE JAM LANGUAGE
     The jam language supports defining and using rules,  setting
     variables,  and flow of control structures.  The Jambase and
     Jamfile share this common language.

  Lexical Features
     Jam treats its input files as whitespace  separated  tokens,
     with  two  exceptions:  double  quotes  (") can enclose whi-
     tespace to embed it into a token, and everything between the
     matching  curly  braces  ({})  in  the  definition of a rule
     action is treated as a single string.  A backslash  (\)  can
     escape a double quote.

  Targets
     Targets and sources (collectively "targets") are files to be
     updated  and  the  files  used in updating those targets.  A
     target is simply a filename, either rooted  or  relative  to
     the  directory  of  Jam's  invocation.   The special syntax,
     file(member), refers to an ar(1) library member.   The  spe-
     cial  syntax,  <grist>file,  perturbs a file name to distin-
     guish it from other files with the same name.   The  <grist>
     is stripped from the name during binding (see below).

  Rules
     Jam's basic entity is called a rule, which is used to relate
     targets  to  their sources.  A rule is defined in two parts:
     the jam statements to  execute  when  the  rule  is  invoked
     (essentially  a procedure call), and the actions (shell com-
     mands) to execute in order to  update  the  targets  of  the
     rule.   A  rule may have a procedure definition, actions, or
     both.

     The jam statements for defining and invoking  rules  are  as
     follows,   where   <targets>  and  <sources>  are  lists  of
     filenames, <statements> are jam statements, and <string>  is
     a shell script:

          rule <rulename> { <statements> }

          actions [ modifiers ] <rulename> { <string> }

          <rulename> <targets> [ : <sources> ] ;

     The first  form  defines  a  rule's  procedure;  the  second
     defines  the  rule's updating actions; the third invokes the
     rule.  Redefining a rule's procedure or actions replaces the
     previous definition.

     Invoking a rule executes the procedure for the rule (if any)
     and  associates  any  update  actions for the targets.  More
     than one update action may be associated with a target: they
     are executed in the order in which they are added.

     In both the  rule's  precedure  definition  and  the  rule's
     actions,  the  special  variables $(<) and $(>) refer to the
     <targets> and <sources> given at rule invocation.   However,
     in  the  rule's actions $(<) and $(>) refer to the <targets>
     and <sources> after they have  been  bound  by  the  binding
     phase  (see  below).   Jam  issues a warning if $(<) or $(>)
     have elements not in the dependency tree.

     The following action modifiers are understood:

     actions ignore
          The return status of the shell commands is ignored.

     actions piecemeal
          The shell commands are repeatedly invoked with a subset
          of $(>) small enough to fit in a command buffer.

     actions quietly
          The action is not echoed to the standard output.

     actions together
          The $(>) from multiple instances of the same action  on
          the same target are glommed together.

     actions updated
          $(>) includes only targets marked for updating.

  Builtin Rules
     Jam has six builtin  rules,  none  of  which  have  updating
     actions:

     DEPENDS <targets> : <sources>
          Makes <sources> dependents of <targets>.

     ECHO <args>
          Blurts out the message <args> to stdout.

     INCLUDES <targets> : <sources>
          Makes <sources> dependents of anything of  which  <tar-
          gets> is a dependent.

     NOCARE <targets>
          Marks <targets> as possibly being bogus  (see  binding,
          below).

     NOTIME <targets>
          Marks  <targets>  as  not  being  files  (see  binding,
          below).

     TEMPORARY <targets>
          Marks <targets> as temporary (see binding, below).

  Flow of Control
     Jam has several simple flow of control statements:

          include <a> ;

          for <a> in <args> { <statements> }

          switch <a> { case <v1> : <statements>  ;  case  <v2>  :
          <statements> ; ... }

          if <cond> { <statements> } else { <statements> }

     The include statement includes the named file; the  path  is
     relative to the directory from which jam was invoked.

     The for loop executes <statements> for each value in <args>,
     setting  the variable <a> to the value.  <a> is not variable
     expanded.

     The switch statement executes zero or one  of  the  enclosed
     <statements>, depending on which value <a> matches.  The <v>
     values are not variable expanded.  A <v> value of *  matches
     anything, but there is no other wildcarding (sorry).

     The if statement  does  the  obvious;  the  else  clause  is
     optional. <cond> is built of:

          <a>       true if <a> is a non-zero length string
          <a1> = <b1>    strings equal
          <a1> != <b1>   strings not equal
          <a1> < <b1>    string less than
          <a1> <= <b1>   string less than or equal to
          <a1> > <b1>    string greater than
          <a1> >= <b1>   string greater than or equal to

          ! <cond>       condition not true
          <cond> && <cond>    conjunction
          <cond> || <cond>    disjunction
          ( <cond> )          grouping

     In comparisons, the arguments may (through  variable  expan-
     sion) be more than one token, but only the first token takes
     part in the comparison.  If through variable  expansion  the
     argument  is  zero  tokens,  a single token of a zero length
     string is used instead.

  Variables
     Jam variables are lists of strings, with zero or  more  ele-
     ments.   An unset variable is indistinguishable from a vari-
     able whose value is an empty  list.   Variables  are  either
     global  or  target specific. All variables are referenced as
     $(VARIABLE).

     A variable is set with:

          <variable> = <values> ;


          <variable> default = <values> ;

          <variable> on <targets> = <values> ;

     The  first  form  sets  <variable>  globally  to  the  given
     <values>;  the  second  form only sets the variable if it is
     unset; the third form arranges for <variable> to take on the
     <values> only when binding and updating <targets>.

     On program startup, jam  imports  the  environment  variable
     settings  into  jam  variables.   Jam  variables are not re-
     exported.

  Variable Expansion
     Before executing a statement jam performs variable expansion
     on  each  token  that  is  not  a keyword or rule name. Such
     tokens with embedded variable references are  replaced  with
     zero  or  more  tokens.  Variable references are of the form
     $(v) or $(vm), where v  is  the  variable  name  and  m  are
     optional modifiers.

     Variable expansion in a rule's actions is similar  to  vari-
     able  expansion in statements, except that the action string
     is tokenized at whitespace without regards for quoting.

     The result of a token after variable expansion is  the  pro-
     duct of the components of the token, where each component is
     a literal substring or a list substituting a variable refer-
     ence.  For example:

          $(X)      -> a b c
          t$(X)          -> ta tb tc
          $(X)z          -> az bz cz
          $(X)-$(X) -> a-a a-b a-c b-a b-b b-c c-a c-b c-c

     The variable name and modifiers  can  themselves  contain  a
     variable  reference,  and  this  partakes  of the product as
     well:

          $(X)      -> a b c
          $(Y)      -> 1 2
          $(Z)      -> X Y
          $($(z))        -> a b c 1 2

     Because of this product expansion, if any variable reference
     in  a  token is unset then the result of the expansion is an
     empty list.

     Modifiers to a variable are  of  two  varieties:  subelement
     selection and filename editing.  They are:



     [<n>]
          Select only element number <n> (starting at 1).  If the
          variable  contains  fewer than <n> elements, the result
          is a zero element list.

     [<n>-<m>]
          Select only elements number <n> through <m>.

     [<n>-]
          Select only elements number <n> through the last.

     :G=<grist>
          Replace the grist of the filename with <grist>.

     :D=<path>
          Replace directory component of filename with <path>.

     :B=<base>
          Replace base part of filename with <base>.

     :S=<suf>
          Replace suffix of filename with <suf>.

     :M=<mem>
          Replace archive member name with <mem>.

     :R=<root>
          Prepend <root> to whole name, if not already rooted.

     :<components>
          Replace all components not listed with an empty string;
          components is one or more of the string GDBSM.

OPERATION
     Jam has three phases of  operation:  parsing,  binding,  and
     updating.

  Parsing
     Jam parses the file Jambase, which by default includes  Jam-
     file.   The  results  of parsing are: the dependency tree of
     targets; update actions associated  with  the  targets;  and
     variables set to specific values.

  Binding
     After parsing, jam recursively decends the dependency  tree,
     attempting to locate each target file and determine if it is
     in need of updating.

     By default, a target is located at the actual  path  of  the
     target,  relative  to the directory of jam's invocation.  If
     $(LOCATE) is set to a directory name, jam locates the target
     in  that  directory; else if $(SEARCH) is set to a directory
     list, jam first searches along the directory  list  for  the
     target file.  If the target name has a rooted directory com-
     ponent then $(SEARCH) and $(LOCATE) do not apply: the target
     is located at the actual path of the target.  If a target is
     marked as not being a file (using the builtin rule  NOTIME),
     it is left unbound to a file name.

     A target is marked for  updating  if  either  it  cannot  be
     found,  it's  filesystem modification time is older than any
     of its dependents, or if any of its  dependents  are  marked
     for  updating.   If a target is missing, no updating actions
     are associated with the target, and the target has not  been
     marked  with  the  builtin rule NOCARE, jam emits a warning.
     If a target is missing and it is marked as  temporary  (with
     the  builtin rule TEMPORARY), then its parent's modification
     time is used when comparing against dependents.  If a target
     is  marked  as  not  being  a  file  (using the builtin rule
     NOTIME), it is marked for updating only if any of its depen-
     dents are marked for updating.

     If a target is a source file that includes header files, jam
     invokes  the  rule  $(HDRRULE)  on  the  target  giving  the
     (unbound) names of the headers file as sources.  A target is
     scanned for header file dependencies if $(HDRSCAN) is set to
     an regexp(3) pattern with ()'s surrounding the include  file
     name.

     Between binding and updating, jam announces  the  number  of
     targets to be updated.

  Updating
     After binding, jam again recursively decends the  dependency
     tree, this time executing the update actions for each target
     that was marked for update during the binding phase.   If  a
     target's  updating  actions fail, then all targets dependent
     on that target are skipped.



---

Basile STARYNKEVITCH   ----  Commissariat a l Energie Atomique
DRN/DMT/SERMA * C.E. Saclay bat.470 * 91191 GIF/YVETTE CEDEX * France
fax: (33) 1- 69.08.23.81;    phone: (33) 1- 69.08.40.66
email: basile@soleil.serma.cea.fr;  homephone: (33) 1- 46.65.45.53


N.B. Any opinions expressed here are solely mine, and not of my organization.
N.B. Les opinions exprimees ici me sont personnelles et n engagent pas le CEA.



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


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