Subject: Linux-Development Digest #834
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 00:13:04 EDT

Linux-Development Digest #834, Volume #1         Thu, 16 Jun 94 00:13:04 EDT

Contents:
  Re: IDE PERF. PATCH SECURITY HOLE (Mark Lord)
  Re: SCSI NCR drivers (John G. Wagner)
  Re: Why is Linux writing to Port 0x80? (Matthias Urlichs)
  Re: Pascal compiler for Linux? (Timothy Murphy)
  'meta data' - the old fashioned way (Dirk-Jan Koopman)
  Re: Linux and symmetrical multiprocessing (Eric Youngdale)
  Re: assembly language & Linux (ATTN!) (Dan Pop)
  ASM with Linux? (Moss A D)
  Re: SCSI NCR drivers (John G. Wagner)
  Re: SCSI NCR drivers (John G. Wagner)
  getting a value from a port using inb() (Rick Power C-3028 x-8844)
  Re: PGP 2.6 for Linux (Eugene Crosser)
  Subtle NFS problem in BSD and Linux (James H. Haynes)
  TCP connections too slow to initialize (David Simmons)
  Re: dosemu/ET4000 help wanted (DL83-08)
  Re: dosemu: pre51_26.tgz does not work with 1.1.19 (J. Lawrence Stephan)
  BusLogic SCSI Controllers Good? (Craig)
  Re: dosemu/ET4000 help wanted (Robert G. Smith)
  Re: dosemu: pre51_26.tgz does not work with 1.1.19 (Robert G. Smith)
  Re: 'meta data' - the old fashioned way (David Holland)

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

From: mlord@bnr.ca (Mark Lord)
Subject: Re: IDE PERF. PATCH SECURITY HOLE
Date: 15 Jun 1994 13:37:24 GMT

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.  I'll add a check for superuser to the ioctls,
and possibly a per-partition enable/disable for the package.
-- 
mlord@bnr.ca    Mark Lord       BNR Ottawa,Canada       613-763-7482

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

From: jwagner@mental.mitre.org (John G. Wagner)
Subject: Re: SCSI NCR drivers
Date: 15 Jun 1994 13:55:14 GMT
Reply-To: jwagner@mental.mitre.org (John G. Wagner)


In article <2tl4l6$6m0@csnews.cs.Colorado.EDU>, drew@kinglear.cs.colorado.edu (Drew Eckhardt) writes:
|>In article <2tkfep$pln@linus.mitre.org>,
|>John G. Wagner <jwagner@mental.mitre.org> wrote:
|>>
|>>Anybody heard anything about when the drivers for the PCI/SCSI NCR chip
|>>is going to be ready? 
|>
|>No, because there hasn't been an announcement as to the release date,
|>and won't be one since there's no way to accurately estimate the amount
|>of time it will take to finish debugging and what else will come up 
|>(like moving, sister's highschool graduation, week long business 
|>trips, etc).

Geez you mean you let your personal life get in the way???
What's this world coming too? :)

|>
|>>a month ago it was this month
|>
|>This month is only half over :-)

Opps, I'll post again at the end of the month :)
 
|>
|>>any update on the release date? 
|>
|>Nope.  I finally have more time to spend on the driver, and probably
|>put in more hours on it last night than I had in the last two 
|>weeks combined, and fixed a lot of nasty bugs, but they're not quite 
|>ironed out yet.
|>
|>Of course, if Novell were to actually sell a Linux derrived product,
|>hire us developers, and let us work full time on fixing our toys 
|>rather than fixing BASIC compilers like we do at our day jobs, 
|>things might happen a lot faster.

BASIC? geez and I thought I was the only one that still used it as a
programming tool!!!!!!!!!!!! :) <thank god for old companies>

|>
|>-- 
|>Drew Eckhardt drew@Colorado.EDU
|>1970 Landcruiser FJ40 w/350 Chevy power
|>1982 Yamaha XV920J Virago
|>

No rush on the drivers, I am not a programmer at heart, so I'll just keep
my mouth shut and my eyes open for any news.

-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+       Heck even I don't know what I do, so the company can't.         +
+         empire isn't a game, it a world ruled by elves! :)            +
+     Bowling IS a sport, and if you don't believe me, I'll beat'ya     +
+                  and YES I mean with a BIG stick!! }:@                +
+          jwagner@mitre.org | John Wagner | PH# (703)883-3740          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

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

From: urlichs@smurf.noris.de (Matthias Urlichs)
Subject: Re: Why is Linux writing to Port 0x80?
Date: 15 Jun 1994 15:07:51 +0200

In comp.os.linux.development, article <2tkqs0INN2hi@vision.uccs.edu>,
  news@vision.uccs.edu writes:
> I have a POST-card (Power On Self Test) installed in my Linux-box;
> it decodes and displays data written to port 80H, and during boot
> all sorts of stuff is displayed.  Even after boot, some commands,
> like 'ls' spew data to the port.
> 
Linux uses 0x80 as a convenient port to output dummy data to, in order to
delay I/O accesses when the target can't grok more than one read or write
per however many microseconds. See /usr/src/linux/asm/io.h.

You can define a special macro (SLOW_IO_BY_JUMPING) when compiling the
kernel if you want to replace this with two null jumps.

-- 
Finagle's Rules:
   1) To study an application best, understand it thoroughly before you
      start.
   2) Always keep a record of data. It indicates you've been working.
   3) Always draw your curves, then plot the reading.
   4) In case of doubt, make it sound convincing.
   5) Program results should always be reproducible. They should all
      fail in the same way.
   6) Do not believe in miracles. Rely on them.
-- 
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: tim@maths.tcd.ie (Timothy Murphy)
Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc
Subject: Re: Pascal compiler for Linux?
Date: 15 Jun 1994 18:08:05 +0100

lellis@dmccorp.com (John Lellis) writes:

>Where can one get GNU PASCAL?  GNU FORTRAN?  Not p2c or f2c, but the real thing?

GPC is not, I think, an official GNU product,
although it uses gcc as a base.
From the README:

        Anonymous ftp:

        Newest "public" gpc snapshot is available via anonymous
        ftp in host kampi.hut.fi in directory jtv/gnu-pascal

                                Juki
                                jtv@hut.fi
        
                                Jukka Virtanen
                                Helsinki University of Technology,
                                Computing Centre,
                                Finland

I don't believe GNU Fortran is yet available,
though it has been under development for some years.


-- 
Timothy Murphy  
e-mail: tim@maths.tcd.ie
tel: +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

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

From: djk@dirku.demon.co.uk (Dirk-Jan Koopman)
Subject: 'meta data' - the old fashioned way
Date: Wed, 15 Jun 1994 17:26:34 GMT

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.

2) all intermediate directory entries (cos the block assignments were done
on a file by file in a directory basis - no inodes as such) would then be
updated, again into new 'free' blocks.

3) recurse the above procedure until there was only one block that needed to
be written (and it was guaranteed by the hardware that, once started, the 
block would be written regardless of what happened to the power etc). That one
block (which could be the equivalent of the super block or simply the 
the file's directory block) then overwrote the block from which it came from
(ie NOT a new block).

This was made possible by the fact that the filesystem knew what it was
dealing with and how best to update the directed graph necessary to do a 
consistant update of the dirty blocks it had to hand.  

The trick is to write all the CHANGED blocks to NEW addresses except
the last one (for any one file) and to do it in the correct order.
In fact all the updates to new blocks could be done in any order so long 
as the updates that were done to SAME blocks were done last.  

The result is that for any update of a file you could guarantee that it
either was 'as it was' or it is now changed - not some halfway house.

There were no 'synchronous' writes done (there was the equiv of a 'sync()'
system call) at all.

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

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

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

From: ericy@cais.cais.com (Eric Youngdale)
Subject: Re: Linux and symmetrical multiprocessing
Date: 15 Jun 1994 21:59:41 GMT

In article <2tkmju$a5d@bigblue.oit.unc.edu>,
Jonathan Magid <jem@bittyblue.oit.unc.edu> wrote:
>Ah ha! Just as I always suspected, "Alan Cox" is a codename for the entire
>computer society!
>
>Now if we can just figure out the organization which lurks behind the 
>nom-de-compute "Eric Youngdale".

        I need to get a life.  Perhaps I should say that we need to get a 
life :-).

-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: danpop@cernapo.cern.ch (Dan Pop)
Subject: Re: assembly language & Linux (ATTN!)
Date: Wed, 15 Jun 1994 13:59:24 GMT

In <2tmpm0$ejg@klaava.Helsinki.FI> torvalds@cc.Helsinki.FI (Linus Torvalds) writes:

>Any porters out there should feel happier knowing that DEC is shipping
>me an AlphaPC that I intend to try getting linux running on: this will
>definitely help flush out some of the most flagrant unportable stuff. 
>The Alpha is much more different from the i386 than the 68k stuff is, so
>it's likely to get most of the stuff fixed. 
>
Unfortunately, the AXP cpu has the same endianess as i386. :-)

>I've generally tried to hide *most* of the assembly code in macros or
>inline functions, but sometimes I'm lazy and then you end up with
>explicit __asm__ stuff in the code (and sometimes I do count on
                                                   ^^^^^^^^^^^^^
>endianess, silly me). 
 ^^^^^^^^^
Dan
-- 
Dan Pop 
CERN, CN Division
Email: danpop@cernapo.cern.ch
Mail:  CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland

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

From: mossap@sunlab40.sx.ac.uk (Moss A D)
Subject: ASM with Linux?
Date: 15 Jun 1994 17:22:02 GMT


Hi!

I've been using assembly language under DOS for quite
a while now, and would like to start using assembly
under Linux.

The question is - how?  I have an assembler (gnu?) which
came with a recent Slackware distribution, but I do
not know how to use it, and I do NOT know the peculiarities
of their assembly language - the only assembly language
I've seen for Linux has looked somewhat unlike it's
DOS counterpart - different typing, etc.

I am also unaware of considerations pertinant to
writing assembly code for a pure 32-bit multitasking
operating system.

If anyone can point me towards a downloadable manual,
FAQ, or anything, I'd be very grateful.

Thanks!

Adam.
--
     |\   /|           ------------------------------------------------
    /| \_/_|           Adam D. Moss                  mossap@essex.ac.uk
__--|\_/   _\          ------------------------------------------------
    /_    (o \___o      "A smartass once accused me of being subtle. I
   /_      ----= /     decked him with a short right over the heart and
    /__  \ -----'         an elbow in the trachea." - Harlan Ellison
       \ //            ------------------------------------------------
      _/
 __/_/          "If music be the food of love" then let a famine rage -   
/_-/         to starve my childish innocence before it comes of age.



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

From: jwagner@mental.mitre.org (John G. Wagner)
Subject: Re: SCSI NCR drivers
Date: 15 Jun 1994 14:26:21 GMT
Reply-To: jwagner@mental.mitre.org (John G. Wagner)


In article <1.9276.2382.0N27CFED@dscmail.com>, john.will@dscmail.com (John Will) writes:
|>JS>I have a new Pentium system just waiting to get Linus on it...
|>
|>I don't know how heavy Linus is, but I sure wouldn't want him on my
|>new Pentium! :-)
|>

Heck I have a VERY firm case!! Will fall from large buildings without
even a scratch. <maybe I should try it with yours?> :)

-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+       Heck even I don't know what I do, so the company can't.         +
+         empire isn't a game, it's a world ruled by elves! :)          +
+     Bowling IS a sport, and if you don't believe me, I'll beat'ya     +
+                  and YES I mean with a BIG stick!! }:@                +
+          jwagner@mitre.org | John Wagner | PH# (703)883-3740          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

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

From: jwagner@mental.mitre.org (John G. Wagner)
Subject: Re: SCSI NCR drivers
Date: 15 Jun 1994 14:29:27 GMT
Reply-To: jwagner@mental.mitre.org (John G. Wagner)


In article <CrFCz5.543@ucdavis.edu>, kevin@frobozz.sccsi.com (Kevin Brown) writes:
|>In article <2tkfep$pln@linus.mitre.org>,
|>John G. Wagner <jwagner@mental.mitre.org> wrote:
|>
|>>Anybody heard anything about when the drivers for the PCI/SCSI NCR chip
|>>is going to be ready? a month ago it was this month, any update on the
|>>release date? I have a new Pentium system just waiting to get Linus on it
|>                                                               ^^^^^
|>>but I can't load it without the drivers.
|>
|>Yeah, but is Linus "just waiting: to get on your Pentium?  One suspects he's
|>not quite *that* much ... erm, um ... *interested* ... in computers.
|>
|>:-) :-) :-)
|>
|>
|>
Stranger things have happened? Ok I guess I should use commas alittle more
often, and read my posts before I send them out, but then agin, NAAAHHHH.

Geez I mean LINUX!! OPPS they are kinda close on the keyboard you know.
I also have fingers that look like boxcars. :) 
-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+       Heck even I don't know what I do, so the company can't.         +
+         empire isn't a game, it's a world ruled by elves! :)          +
+     Bowling IS a sport, and if you don't believe me, I'll beat'ya     +
+                  and YES I mean with a BIG stick!! }:@                +
+          jwagner@mitre.org | John Wagner | PH# (703)883-3740          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

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

From: rickp@newton.physics.mun.ca (Rick Power C-3028 x-8844)
Subject: getting a value from a port using inb()
Date: 15 Jun 1994 14:26:25 GMT


Hi, I have a program which I have listed here to get the value at a port
using the inb() routine in linux. Somehow I manage to screw up - the
program is a test -- before I start hacking at ieee 488 controller code
I want to get the basics down - My program follows -- could someone tell
me what I am doing wrong

==============================beginning of C program=======================
#include<stdio.h>
#include<asm/system.h>
#include<asm/io.h>
main()
   {
   unsigned int PORT_ADDRESS;
   unsigned int PORT_VALUE;

   PORT_ADDRESS = 0x300;
   PORT_VALUE = inb(PORT_ADDRESS);

   printf("PORT address %d contains value %d \n", PORT_ADDRESS, PORT_VALUE );

   }
==============================end of C program=============================

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 :-)

thanks in advance for any help........Rick.

-- 
I claim not to have controlled   ---------  Richard Power ----------
events, but confess plainly      -------  Physics Department -------
that events have controlled me.  Memorial University of Newfoundland
   ABRAHAM LINCOLN (1864)        E-MAIL>> rickp@kelvin.physics.mun.ca

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

From: crosser@pccross.msk.su (Eugene Crosser)
Subject: Re: PGP 2.6 for Linux
Date: 15 Jun 1994 20:29:23 +0400

In <061394122515Rnf0.78@runic.mind.org> thantos@runic.mind.org (Alexander Williams) writes:

>>If anyone knows what's up, I would appreciate a hint.  As a side comment, I
>>wonder if any linux site is going to carry the binary of PGP 2.6...

>You might be better of grabbing the pgp2.6ui version off of demon.cc.uk if
>at all possible. You'll get much better response of compilation problems 
>from matthew than from the NSA-employed MIT slaves. ;)

I must admit that pgp2.6ui compiles out of the box.  It has "linux" target
in the Makefile.

Eugene

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

From: haynes@cats.ucsc.edu (James H. Haynes)
Crossposted-To: comp.os.386bsd.development
Subject: Subtle NFS problem in BSD and Linux
Date: 15 Jun 1994 17:58:47 GMT


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.
-- 
haynes@cats.ucsc.edu
haynes@cats.bitnet

"Ya can talk all ya wanna, but it's dif'rent than it was!"
"No it aint!  But ya gotta know the territory!"
        Meredith Willson: "The Music Man"


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

From: simmons@EE.MsState.Edu (David Simmons)
Subject: TCP connections too slow to initialize
Date: 15 Jun 1994 23:15:54 GMT
Reply-To: simmons@EE.MsState.Edu

On a recent linux installation, I noticed that TCP connections took far
too long to initialize.  Telnet and finger would hang for a minute or
so before giving a login prompt or a finger connection.  The problem
only seemed to occur when connecting to another Linux machine; connections
to Suns were normal.  The other linux machines could connect fast to this
one.

While it was hanging, if I hit an ctrl-] to get a telnet prompt (to abort),
it would actually display the ^], and wouldn't give me a telnet prompt until
I hit enter, signifying that the terminal was still set for line buffering.

I disabled the TCP Wrapper (that comes with Slackware) and the identd's
(in the inetd.conf) to eliminate those from the problem.

I originally ran the 1.1.14 kernel on this machine, then upgraded to 1.1.19
in hopes of fixing the problem, but to no avail.  A quick 'sum' showed that
the 'telnet' binary was identical to the one on the other machines, which
leads me to believe that the problem must lie somewhere in the kernel
networking code...

David

-- 
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: s21008@cc.ntnu.edu.tw (DL83-08)
Subject: Re: dosemu/ET4000 help wanted
Date: Thu, 16 Jun 1994 02:57:53 GMT

Bill Buie (wjb@fep47.com) wrote:

: 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
:  
: which from the release notes I presume is related to me having an ET4000
: video card.  On the other hand, I can't build dosemu version dosemu0.51
: (with or without pre51_17), which I presume is because I don't have the
: latest linux kernal available (it's using a VIF_MASK #define that isn't
: declared anywhere on my system).
:  
: So:
:  
:         Is there a dosemu out there that will run on my current OS/HW
:         configuration?  If so, where can I get it?
:  
:         If not, where can I get whatever I need to have dosemu/Linux
:         running on my current HW?

: My hardware:
:  
:         386SX/33
:         ET4000 video w/ 1MB RAM
:         16MB RAM
:         200 MD HD
:  
: All help is appreciated.
:  
:                 --Bill

I was running DOSEMU 0.5pl1 on the exact same HW, except I have 386DX/33. To
tell you the truth, it was so slow, I could not even use DOS's EDIT. That is
not the way to go with a 386.

However, I do believe that you may not have set the harddisk image
correctly. Try booting off of a bootable DOS floppy (DOS -A) and then rerun
fdisk and sys on C: (the name used for the harddisk image).

--

 /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
%v  Curtis Dean Smith                      Internet: s21008@cc.ntnu.edu.tw   |
0j  Institute of Chinese Language & Literature                               |
?3  National Taiwan Normal University            Bitnet: NTNUS239@TWNMOE10   |
 \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

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

From: jlarry@marlin.ssnet.com (J. Lawrence Stephan)
Subject: Re: dosemu: pre51_26.tgz does not work with 1.1.19
Date: 15 Jun 1994 22:23:39 -0400

Michael Will (michaelw@desaster.student.uni-tuebingen.de) wrote:
: Hello,
[since Terry has kindly answered your first question, I'll skip to the 
second one: ]
: What next?

: How can I get onto the dosemu-list?

Look in DOSEMU-HOWTO.txt, the instructions are there.

Larry Stephan

jlarry@ssnet.com


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

From: tracker@netcom.com (Craig)
Subject: BusLogic SCSI Controllers Good?
Date: Wed, 15 Jun 1994 22:14:15 GMT




Are the BusLogic SCSI controllers more bug-free in their drivers and
on-board BIOS than most of the Adaptec line?  Also, how's BusLogic
compatability, performance, etc.. compared to other brands?
How's the voic support that BusLogic offers?
Can most of the BusLogic drivers be loaded high?
Thanks in advance.


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

From: rob@bip.anatomy.upenn.edu (Robert G. Smith)
Subject: Re: dosemu/ET4000 help wanted
Date: 16 Jun 1994 02:59:41 GMT

Bill Buie (wjb@fep47.com) wrote:

:         Is there a dosemu out there that will run on my current OS/HW
:         configuration?  If so, where can I get it?
:  
:         If not, where can I get whatever I need to have dosemu/Linux
:         running on my current HW?

The new release of dosemu is worth waiting for and using,
for it is quite a bit faster, has lots of bugs fixed, and
the cursor works nicely in text mode inside an xterm (at last!).
You can get the latest pre-release of dosemu at:

  tsx-11.mit.edu:pub/linux/ALPHA/dosemu/private/devel/pre51_xx

 where xx is the version number.  If you can wait just a few more
days, the official release will be out.

The new dosemu requires a recent kernel.  You can get the
most recent ones either by patching your own from the
original source at:

  ftp.funet.fi:pub/OS/Linux/PEOPLE/Linus/v1.1

or at several mirror sites, e.g.:

  linuxftp.caltech.edu:pub/Linux/Linus/v1.1

or the kernels already patched:

  linuxftp.caltech.edu:pub/Linux/patched-kernels

Note that a new /sbin/update is required and this is
supplied ("bdflush") in the v1.1 directories.

Hope this helps...

Rob Smith 

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

From: rob@bip.anatomy.upenn.edu (Robert G. Smith)
Subject: Re: dosemu: pre51_26.tgz does not work with 1.1.19
Date: 16 Jun 1994 03:07:48 GMT

Michael Will (zxmgv07@studserv.zdv.uni-tuebingen.de) wrote:

: thereafter it opens /dev/fd0 and gets into trouble:
: open("/dev/fd0", RDWR|RDWR, 0) = 6
: ...and it dumps to the screen. (no core-dump, though).

: Now, any ideas?

Follow the directions to make a bootable hdimage.
Make sure you've configured dosemu to boot from A at first,
then once you've got a bootable hdimage, change it to boot
from C.  Check to make sure that /usr/bin/dos is suid root.
I've had the pre51 and pre52 versions going very nicely
with the recent kernels very nicely, no problems at all.

Rob Smith


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

Subject: Re: 'meta data' - the old fashioned way
From: dholland@husc7.harvard.edu (David Holland)
Date: 15 Jun 94 22:43:33


evansmp@mb5194.aston.ac.uk's message of Wed, 15 Jun 1994 19:48:25 GMT said:

 > : 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.

I don't believe you. Care to explain why? (in mail if you like...)

--
   - David A. Holland          | "The right to be heard does not automatically
     dholland@husc.harvard.edu |  include the right to be taken seriously."

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


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