Subject: Linux-Development Digest #835
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, 16 Jun 94 08:13:09 EDT

Linux-Development Digest #835, Volume #1         Thu, 16 Jun 94 08:13:09 EDT

Contents:
  Re: RARP Under Linux (David Simmons)
  Re: IDE PERF. PATCH SECURITY HOLE (Jeff Epler)
  Re: dosemu/ET4000 help wanted (Carlyle George)
  Re: Subtle NFS problem in BSD and Linux (Manuel Bouyer)
  Status of PCI support? (Philip Wang)
  Re: IDE PERF. PATCH SECURITY HOLE (Rob Janssen)
  Re: getting a value from a port using inb() (Rob Janssen)
  Driver for MPU compatible MIDI interface? (Andreas Toenne)
  PLIP throughput.. (Gene Choi)
  Re: 'meta data' - the old fashioned way (Dirk-Jan Koopman)
  Re: Filesystem semantics protecting meta data ... and users data (Dirk-Jan Koopman)
  Re: 'meta data' - the old fashioned way (David Monro)
  Re: Pascal compiler for Linux? (Mr. C. P. Hsu)
  Re: Pascal compiler for Linux? (Dan Pop)
  Re: IDE PERF. PATCH SECURITY HOLE (Kevin Brown)
  Re: Pascal compiler for Linux? (Xu)
  Re: IEEE 488 (GPIB, HPIB) (Fritz Ganter)

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

From: simmons@EE.MsState.Edu (David Simmons)
Subject: Re: RARP Under Linux
Date: 15 Jun 1994 23:29:33 GMT
Reply-To: simmons@EE.MsState.Edu

In article <2tmaa8$lui@rs1-hrz.uni-duisburg.de>,
Martin Spott <sk001sp@unidui.uni-duisburg.de> wrote:
>: I am wondering if anyone can give me concise information on how to use
>: RARP under Linux.   The questions i need answered are :
>
>:         Which Kernel do I need ? ( >1.1.13 I assume)
>:         How do I get a machines IP at boot time ?
>
>: Replies Via EMAIL ONLY please.
>
>I think this is of general interest, so please dont't EMail only !

Yes, I'd be interested in hearing this as well.

-- 
David Simmons, System Administrator                 simmons@ee.msstate.edu
Mississippi State University Electrical and Computer Engineering
Visit my home page!  http://www.msstate.edu/~dls3/

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

From: jepler@herbie.unl.edu (Jeff Epler)
Subject: Re: IDE PERF. PATCH SECURITY HOLE
Date: 15 Jun 1994 18:20:52 GMT

dmw@prism1.prism1.com (David Wright) writes:

>>>>>> "FL" == Frank Lofaro <ftlofaro@unlv.edu> writes:

>  FL> The IDE performance patch has a serious security hole!  ANY USER can
>  FL> set the multiple mode and irq unmasking if they have access to the
>  FL> drive. Even if it is ONLY READ-ONLY access to one partition.

>       What about making the program mode 500 and owned by root?

Because Joe User can get the sources for hdparm and run it himself.


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

From: carlyle+@pitt.edu (Carlyle George)
Subject: Re: dosemu/ET4000 help wanted
Date: 15 Jun 1994 18:24:50 GMT

In article <2thpml$bug@charon.fns.com> wjb@fep47.com writes:
>
>I am running version Linux 1.0.8 on the hardware configuration below.  If
>I try to run dosemu version 50p11, I get the following error,
> 
>        (wjb)$ dos
>        SCREEN saves at: 0x115000
>        debug flags: -a
>        debug flags: -vsdDRWkpiwghxmIEc
> 
m-any lines deletedd--
> 
>                --Bill


Try this command:

(wjb)$ dos|more

It will report the  error that dosemu gives, thus eliminating guesswork.

I don't believe that you problem is the video card because I too have a similar
card with 2meg of ram..  I have not yet experienced anyt problem.

I believe that your broblem is that you are trying to boot dos from a non-botable hard drive.  In sert a bootable disk in drive A and try dos -A.

                                        -Carlyle

P.S. please excuse my grammar and spelling error I am using emacs on a VT340+ 

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

From: bouyer@bsdtest.ensta.fr (Manuel Bouyer)
Crossposted-To: comp.os.386bsd.development
Subject: Re: Subtle NFS problem in BSD and Linux
Date: 15 Jun 1994 18:30:32 GMT

In article <2tnfgn$4o7@darkstar.UCSC.EDU>, haynes@cats.ucsc.edu (James H. Haynes) writes:
|> 
|> SunOS 4.1.x has a mount option "grpid" which says, if you mount a disk
|> partition with that option, to use BSD semantics for file groups regardless
|> of the setgid bit on directories.  That is, if a disk partition is mounted
|> with the grpid option then a newly-created file anywhere in that partition
|> has the group ownership taken from the group owner of the containing
|> directory.  Without the grpid mount option the above group ownership
|> behavior occurs if the containing directory has the setgid bit turned on;
|> otherwise the group of a newly created file is the current group of the
|> creator.
|> 
|> I've found experimentally with a Sun NFS server that the grpid mount
|> option works as expected when the NFS client is a Sun, and not when the
|> client is BSD (approximately FreeBSD 0.9 plus something) or Linux
|> (approximately Slackware 1.1).
|> 
|> Specifically,  here's output from ls -lga on the server
|> drwxrwx---  2 haynes   cmp101-admin     512 Jun 15 10:58 ./
|> drwsrwx-wt  8 avg      cmp101-admin     512 Jun 14 20:51 ../
|> -rw-rw----  1 haynes   sources            8 Jun 15 10:22 junk.bsd
|> -rw-rw----  1 haynes   sources            8 Jun 15 10:22 junk.linux
|> -rw-rw----  1 haynes   cmp101-admin       8 Jun 15 10:22 junk.sparc
|> 
|> where the various junk files were created from an NFS client on the systems
|> indicated by the suffixes.

I've got the same kind of problem whith NetBSD.
This is a bug from SunOS. Whith NFS filesystem, for security reasons, the
filesystem semantic should be fixed by the server. NetBSD handle nfs like this,
and i think Linux and FreeBSD too. SunOS doesn't for the group id, but
it does or other things, like the propagation of the SGID bit.
I've fixed this by a patch of my NetBSD's NFS code, because i don't have
SunOS sources.

--
Manuel Bouyer, Ecole Nationale Superieure de Techniques Avancees, Paris
email: bouyer@ensta.fr
--

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

From: philip@cnj.digex.net (Philip Wang)
Subject: Status of PCI support?
Date: 15 Jun 1994 17:16:34 -0400

I need info about PCI support for Linux with following card or board:

SuperMicro motherboard (PCI)
PCI #9 GXE64 pro
PCI #9 GXE64
PCI ATI mach64
PCI SCSI card (NCR chipset)

If not supported now, anyone has been working on them? 
What is the anticipated dated of release (driver or kernel)?
Please write if you have any info about PCI support for Linux.
I checked PCI-Howto and found only some info.  Thanks.

Philip Wang, Senior Tech Specialist
Columbia-Presbyterian Medical Center

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: IDE PERF. PATCH SECURITY HOLE
Reply-To: pe1chl@rabo.nl
Date: Wed, 15 Jun 1994 22:49:54 GMT

In <1994Jun14.174453.28689@unlv.edu> ftlofaro@unlv.edu (Frank Lofaro) writes:

>NO ONE BUY A SEAGATE 1239A. ITS CRAP! (it even got bad sectors, yeah,
>on an IDE drive (!), after only one year!)

I have enough experience with Seagate ST-225's and ST-238's to not even
consider buying any product from this company the rest of my life....

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

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

From: rob@pe1chl.ampr.org (Rob Janssen)
Subject: Re: getting a value from a port using inb()
Reply-To: pe1chl@rabo.nl
Date: Wed, 15 Jun 1994 22:59:45 GMT

In <2tn32h$idq@coranto.ucs.mun.ca> rickp@newton.physics.mun.ca (Rick Power C-3028 x-8844) writes:

>how I compile:

>rupert:~> gcc thefileabove.c -o port_listen

>somewhere along the way of compilation the C compiler says :

>/tmp/cca013471.o: Undefined symbol ___inbc referenced from text segment
>/tmp/cca013471.o: Undefined symbol ___inb referenced from text segment

>I am hoping that someone can put me back on track :-)

Try compiling with the -O2 option...

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

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

From: atoenne@mpi-sb.mpg.de (Andreas Toenne)
Subject: Driver for MPU compatible MIDI interface?
Date: 16 Jun 1994 09:17:02 GMT

Hi!

I wonder if there is a device driver for MPU compatible MIDI
interfaces like the Roland, MQX or newer Soundblaster cards?


If such a best does not exist I will write one:
intelligent device running the MPU in dumb UART mode but having an internal
timebase to annotate MIDI events with timestamps wrt. PPQ/MIDI clock.
This will be essentially a serial driver at a fixed speed with some
extras.

        Andreas Toenne
--

        Andreas Toenne                  Voice:  x49 681 5846272
        Max-Planck-Institut             Office: x49 681 302 5363
        fuer Informatik                 e-mail: atoenne@mpi-sb.mpg.de

        Im Stadtwald
        66123 Saarbruecken, Germany

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

From: genie@sting.Berkeley.EDU (Gene Choi)
Subject: PLIP throughput..
Date: 15 Jun 1994 21:36:12 GMT


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.

-Gene

-- 
Zima zux!


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

From: djk@dirku.demon.co.uk (Dirk-Jan Koopman)
Subject: Re: 'meta data' - the old fashioned way
Date: Thu, 16 Jun 1994 10:10:39 GMT

Mark Evans (evansmp@mb5194.aston.ac.uk) wrote:
: Dirk-Jan Koopman (djk@dirku.demon.co.uk) wrote:
: : Many (many) years ago there was a (wonderful) operating system called George 3
: : (yes I was one of those programmers!). The way directory updates were done was
: : as follows:-

: : The result was a fast, very resiliant, filesystem very similar in form to a
: : unix file system (with directories etc etc).

: If I remember my Operating systems design correctly George cannot have both
: files and sub directories in the same directory.

Yes you can, there is no such restriction. Although this isn't directly relevant
the biggest restriction on the filesystem was a 245K word file length. Otherwise
you could put all sorts of files in the filesystem (including pseudo Mag tapes 
disc drives and other ICL exotica). For the VMS afficianados there is two levels 
file version numbering as well! Oh and as for the 'new' unix security features,
it has the possibility of specifying access control for individual files very
easily, as well as all the usual inheritance critiria you get in unix.

As for the spooler, well....

As I said earlier, unix is really starting to get into the 1960's...

Dirk 

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

Crossposted-To: comp.benchmarks,comp.sys.sun.admin,comp.security.unix
From: djk@dirku.demon.co.uk (Dirk-Jan Koopman)
Subject: Re: Filesystem semantics protecting meta data ... and users data
Date: Thu, 16 Jun 1994 10:14:10 GMT

Adam Sweeney (ajs@spareme.engr.sgi.com) wrote:
: >a file corrupted with zeros is still corrupted ... not a security
: >risk unless the file is critical to use of a system and causes
: >another form of fault that exposes you.
: >
: >The point is that file corruption, in particular undetectable
: >file corrupt is not necessary.
: >
: >John

: John,

: So far your proposal seems to have been to order all writes
: to file data before any of the meta-data writes which will make
: that data permanent.  While that will probably work for newly
: written files, it doesn't do much for the consistency of
: multi-block updates to an existing file unless you go to a
: no-overwrite scheme and commit all of meta-data atomically.

see the thread 'meta-data - the old fashioned way'






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

From: davem@extro.ucc.su.OZ.AU (David Monro)
Subject: Re: 'meta data' - the old fashioned way
Date: Thu, 16 Jun 1994 09:53:43 GMT

djk@dirku.demon.co.uk (Dirk-Jan Koopman) writes:

>Many (many) years ago there was a (wonderful) operating system called George 3
>(yes I was one of those programmers!). The way directory updates were done was
>as follows:-

>1) all data blocks were written to 'free' data blocks, this includes all 
>updated blocks. This means that no block was ever written back to same 
>disc address that it came from.
Isn't this going to result in horrible fragmentation for files which
have bits in the middle altered? Or don't files get modified in this
fashion very often?

[rest of description deleted]

>Once the above has been implimented then all we need is a decent 'dumper' and
>we really will have progressed into the 1960's 8-).

>Dirk


David

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

Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc
From: mahsu@news.uta.edu.uta.edu (Mr. C. P. Hsu)
Subject: Re: Pascal compiler for Linux?
Date: Wed, 15 Jun 1994 21:40:33 GMT

Hans Vermeulen (vermeule@wi.leidenuniv.nl) wrote:
: Hello,

: I am looking for a Pascal compiler for Linux.
: Is there one out there? I don't like to use a pascal-to-c translator and gcc.
: So, anybody got a clue? After all, there is modula-2/3, eiffel, fortran, ....,
                                                                  ^^^^^^^^
I would like to know where I can get Fortran compiler for Linux.  Thanks.

cph




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

Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc
From: danpop@cernapo.cern.ch (Dan Pop)
Subject: Re: Pascal compiler for Linux?
Date: Thu, 16 Jun 1994 10:59:36 GMT

In <1994Jun15.214033.2920@news.uta.edu> mahsu@news.uta.edu.uta.edu (Mr. C. P. Hsu) writes:

>I would like to know where I can get Fortran compiler for Linux.  Thanks.

Apart from the f2c converter, available on the most popular Linux
distributions, there is no native Fortran compiler available for Unix.

g77, the FSF F77 compiler is still in private alpha tests.
Use "finger -l fortran@gate.gnu.ai.mit.edu" for the latest news about it.

Dan
-- 
Dan Pop 
CERN, CN Division
Email: danpop@cernapo.cern.ch
Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland

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

From: kevin@frobozz.sccsi.com (Kevin Brown)
Subject: Re: IDE PERF. PATCH SECURITY HOLE
Date: Wed, 15 Jun 1994 20:44:46 GMT
Reply-To: kevin@frobozz.sccsi.com (Kevin Brown)

In article <2tn06k$sm@bmerha64.bnr.ca>, Mark Lord <mlord@bnr.ca> wrote:
>In article <CrFA2D.2IK@ucdavis.edu> kevin@frobozz.sccsi.com writes:
>..
>>2.  "Read-only" access to a device means just that: you can read
>>    attributes, data, etc. from the device, but you can't make any
>>    changes to either the status or the data.  Changing a device
>>    to multiple-mode should thus require write access to the device,
>>    since that's an attribute change.
>
>Hmm.. on my system, I want my "read-only" devices to be just as fast
>as my read-writable ones.

...and for normal operations (i.e., data reads/writes), it isn't a problem,
because the open() system call takes care of access control.

The ioctl() interface is different, of course, but do you really
use it often enough that speed is enough of a concern that it would
override implementing the "correct" behavior?

>  I'll add a check for superuser to the ioctls,
>and possibly a per-partition enable/disable for the package.

Not what I would consider to be the right answer...oh, well....:-)


-- 
Kevin Brown                                     kevin@frobozz.sccsi.com
This is your .signature virus: < begin 644 .signature (9V]T8VAA(0K0z end >
            This is your .signature virus on drugs: <>
                        Any questions?

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

From: xu@tansei.cc.u-tokyo.ac.jp (Xu)
Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc
Subject: Re: Pascal compiler for Linux?
Date: 16 Jun 1994 01:07:09 GMT

You can find the binary for linux at sunsite.unc.edu:/pub/Linux/Incoming.

Good Luck.


M. Lu


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

From: ganter@fvkmapc02.tu-graz.ac.at (Fritz Ganter)
Subject: Re: IEEE 488 (GPIB, HPIB)
Date: 16 Jun 1994 11:40:11 GMT

Carles Perello (carlesp@cnm.es) wrote:


: Hello!

: Some weeks ago I saw a post from someone interested in a 
: IEE488 driver for linux. As I am willing to use a National
: Instruments PC2A.2 with linux, I am also *very* interested
: in using or helping to develop such a thing. 

: At the moment I do not have any technical information from
: the NI card, and NI didn't answer a request of info for this
: card. Maybe because I am overseas :)

: Hope I got some answer! Thanks!

Write to clausi@chemie.fu-berlin.de



--

Fritz, always linuxing...

Fritz Ganter                            Graz University of Technology, Austria
Email:               ganter@fvkmapc02.tu-graz.ac.at, ganter@vkma.tu-graz.ac.at
HAM-Radio: OE6FAD@OE6XYG.AUT.EU, OE6FAD@OE6FAD.AMPR.ORG, Tel. +43 316-873-7222
 ****************     Linux... try it, use it, love it.     *****************

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


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