HDTenEightyP/NetNews huggingface dataset:
From: root@pwh.uucp (Superuser)
Subject: QIC AND SCSI tape drives
Organization: PWH Associates
Distribution: na
Date: Fri, 18 Dec 92 21:59:51 GMT
Keywords: QIC, SCSI, TAPE

Hi. I have 2 tape drives, a wangtech in my UNIX system,
and an archive on my dos system.
I don't know the model number of the Wangtech drive, but it uses
cartridges with the following info printed on them:
Large Data Cartridges
CMG-9270 (836) CM320
320MB tape crtg 116570-001
or
cartridges that hodl 525MB. they are the dc600 style.
the archive drive is an 21255, both SCSI.
the question is 
What QIC format do these units read/write?

Also, i will be using the Archive on an Adaptech 1542B.
I have read the articles in several groups, and folks
seem to recommend either the aspitar program, or aspitape.
I do not have access to ftp, so where can i get either/both of 
these programs? I looked on Adaptech's bbs and didn't see them there.
I also called Adaptech's tech support several times, and no one has
called me back yet.
I already have the aspi4dos software.
Any help would be appriciated.

Phil
Xref: sparky comp.bugs.4bsd:235 comp.bugs.sys5:146 comp.bugs.misc:170 comp.sources.bugs:296
From: haiying@cs.mcgill.ca (Haiying ZHANG)
Newsgroups: comp.bugs.4bsd,comp.bugs.sys5,comp.bugs.misc,comp.sources.bugs
Subject: A serious bug in unix2dos/dos2unix
Date: 12 Dec 92 22:41:09 GMT
Organization: SOCS - McGill University, Montreal, Canada


   I came across this bug a while ago. This has to do with using wild
card in file names with unix2dos/dos2unix.

   If you use a wild card in the file name, be it a single * or a ?
embedded in a pattern, these two handy utilities will wipe out your
entire current directory with the exception of the first file. It will
set all the rest of the file to size 0. 

   Although the man page does mention anything about wild card in
filename making one believe that it is not supported, it should not in
any case cause serious damaging to your files. While I am at it, these
two programs look like a recompile of its DOS version. It should have
provided more - options such as -Rfp etc. as in cp. 

   I hope that somebody could get hold of this and put some action into
it. For such a widely used simple utility to have these serious bug and
disfunctions is really a shame. 


					Haiying
Newsgroups: comp.bugs.4bsd,comp.bugs.sys5,comp.bugs.misc,comp.sources.bugs
From: pjh@mccc.edu (Pete Holsberg)
Subject: Re: A serious bug in unix2dos/dos2unix
Organization: The College On The Other Side Of Route One
Date: Tue, 15 Dec 1992 19:23:03 GMT

In article <1992Dec12.224109.15621@cs.mcgill.ca> haiying@cs.mcgill.ca (Haiying ZHANG) writes:
=
=   I came across this bug a while ago. This has to do with using wild
=card in file names with unix2dos/dos2unix.

Where did you find these utilities?
Xref: sparky comp.bugs.4bsd:236 comp.bugs.sys5:148 comp.bugs.misc:171 comp.sources.bugs:301
From: jbayer@ispi.COM (Jonathan Bayer)
Newsgroups: comp.bugs.4bsd,comp.bugs.sys5,comp.bugs.misc,comp.sources.bugs
Subject: Re: A serious bug in unix2dos/dos2unix
Date: 14 Dec 92 18:59:27 GMT
Followup-To: comp.bugs.4bsd
Organization: Intelligent Software Products, Inc.

haiying@cs.mcgill.ca (Haiying ZHANG) writes:


>   I came across this bug a while ago. This has to do with using wild
>card in file names with unix2dos/dos2unix.

>   If you use a wild card in the file name, be it a single * or a ?
>embedded in a pattern, these two handy utilities will wipe out your
>entire current directory with the exception of the first file. It will
>set all the rest of the file to size 0. 

>   Although the man page does mention anything about wild card in
>filename making one believe that it is not supported, it should not in
>any case cause serious damaging to your files. While I am at it, these
>two programs look like a recompile of its DOS version. It should have
>provided more - options such as -Rfp etc. as in cp. 


First, what system are you running on?  Second, what are you trying to do?
On a Sun system the dos2unix command is designed to operate on ONE file only,
sending the output to the second file specification.  The wild cards are
expanded by the shell, and all the program sees is a long list of filenames.

It appears that you may be using it improperly.


JB
-- 
Jonathan Bayer		Intelligent Software Products, Inc.
(908) 248-1853		37 Winthrop Rd. 
jbayer@ispi.COM		Edison, NJ   08817
Newsgroups: comp.bugs.4bsd
From: zierke@rzdspc24.informatik.uni-hamburg.de (Reinhard Zierke)
Subject: Re: A serious bug in unix2dos/dos2unix
Organization: University of Hamburg, FRG
Distirbution: world
Date: 16 Dec 92 08:03:29 GMT

jbayer@ispi.COM (Jonathan Bayer) writes:

> haiying@cs.mcgill.ca (Haiying ZHANG) writes:
> 
> >   I came across this bug a while ago. This has to do with using wild
> >card in file names with unix2dos/dos2unix.
> 
> >   If you use a wild card in the file name, be it a single * or a ?
> >embedded in a pattern, these two handy utilities will wipe out your
> >entire current directory with the exception of the first file. It will
> >set all the rest of the file to size 0. 
> 
> >   Although the man page does mention anything about wild card in
> >filename making one believe that it is not supported, it should not in
> >any case cause serious damaging to your files. While I am at it, these
> >two programs look like a recompile of its DOS version. It should have
> >provided more - options such as -Rfp etc. as in cp. 
> 
> First, what system are you running on?

A student of mine had the same problems on a SPARCstation with SunOS 4.1.2

>                                         second, what are you trying to do?
> On a Sun system the dos2unix command is designed to operate on ONE file only,
> sending the output to the second file specification.  The wild cards are
> expanded by the shell, and all the program sees is a long list of filenames.
> 
> It appears that you may be using it improperly.

This explains what dos2unix does, but not WHY it has such strange behaviour.
Using software improperly MUST NOT lead to such damaging results. Beware
of such bad software engineering!

At least unix2dos/dos2unix has to check that it is invoked with exactly two
arguments, first of which is the input filename and the second one the output
filename, not a directory name.  Better still, unix2dos/dos2unix should behave
similar to mv/cp and allow an arbitrary number of files when the last argument
is a directory name.

Reinhard

-- 
Reinhard Zierke                   Universitaet Hamburg, FB Informatik
zierke@informatik.uni-hamburg.de  Vogt-Koelln-Strasse 30, D-2000 Hamburg 54
                                  Tel.: (040) 54715-295   Fax: -206
Organization: K.U.Leuven - Academic Computing Center
Date: Friday, 18 Dec 1992 18:20:41 +01
From: Paul Bijnens <FFAAC09@cc1.kuleuven.ac.be>
Newsgroups: comp.bugs.4bsd
Subject: Re: A serious bug in unix2dos/dos2unix
 <zierke.724493009@rzdspc24> <id.87XV.OQH@ferranti.com>

In article <id.87XV.OQH@ferranti.com>, peter@ferranti.com (peter da silva) says:
>
>Agreed. NO program on UNIX should EVER use the
>
>        command inputfile [outputfile]
>
>syntax. It's dangerous, counterintuitive (you can't use it as a filter), and
>inflexible. Indent does the same thing, which is why I have indent in a script
>that does "indent -st" here.

And don't forget "uniq"; it hasn't even a flag... :-(

Does anyone actually USE the behaviour of such programs?
(I mean: specifying the outputfile as an optional second argument)
Will there a lot of scripts be broken when you change this stupid
syntax?
--
Paul Bijnens             -- MS-DOS is the world's most widespread virus.
Linguistics dept., K. University Leuven, Belgium
Polleke@cc1.kuleuven.ac.be
From: peter@ferranti.com (peter da silva)
Subject: Re: A serious bug in unix2dos/dos2unix
Organization: Xenix Support, FICC
Date: Thu, 17 Dec 1992 17:40:12 GMT

In article <zierke.724493009@rzdspc24> zierke@rzdspc24.informatik.uni-hamburg.de (Reinhard Zierke) writes:
> This explains what dos2unix does, but not WHY it has such strange behaviour.
> Using software improperly MUST NOT lead to such damaging results. Beware
> of such bad software engineering!

Agreed. NO program on UNIX should EVER use the

	command inputfile [outputfile]

syntax. It's dangerous, counterintuitive (you can't use it as a filter), and
inflexible. Indent does the same thing, which is why I have indent in a script
that does "indent -st" here.

If the command *requires* an outputfile (mv, cp, ln) it needs to do sanity
checks, and accept multiple input files. The output file should NEVER be
optional in this case:

	command inputfile outputfile
	command inputfile... outputdir

If you NEED an optional output file, and for some reason redirects don't
work, then flag it:

	command file... [-o outputfile]

I don't know what dos2unix and unix2dos do, but they should be using one
of these alternatives.
-- 
Peter da Silva                                            `-_-'
Ferranti International Controls Corporation                'U` 
Sugar Land, TX  77487-5012 USA
+1 713 274 5180                            "Zure otsoa besarkatu al duzu gaur?"
Newsgroups: comp.bugs.4bsd
From: jdeitch@baron.mrms.navy.mil (Jim Deitch)
Subject: TU81 tape drive fix
Keywords: tmscp TU81
Organization: COMNAVSURFPAC  San Diego, CA
Date: Fri, 18 Dec 1992 18:29:43 GMT

Does anyone have a fixed driver for a TU81 tape drive under 4.3 Tahoe?

The tmscp.c that comes with the distribution tends to crash the system
with a mchk 10 error.

Thanks,
Jim
-- 
jdeitch@ns2.mrms.navy.mil			deitch@mrms-simasd.navy.mil
(619)556-0332
Xref: sparky comp.bugs.sys5:150 comp.unix.sys5.r4:844
From: hmc@cs.hw.ac.uk (Hugh Conner)
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
Subject: Problem with mailx in ESIX 4.0.4
Date: 15 Dec 92 15:45:11 GMT
Organization: Dept of Computing & Electrical Engineering, Heriot-Watt University, Scotland

We have several 486 based systems running ESIX 4.0.4. When using the mailx
command to read mail messages a problem occurs if the first word on a line
of the message is 'from'. I notice that when sending mail if the first word
is 'From' with a capital F it replaces it with '>From' which I assume is meant
to stop the mail reader treating it as the start of a new message. This does
happen with 'from' and although /bin/mail reads the message ok, mailx
decides that the line starting 'from' is a new message. Does anyone know a
patch for this or should I just compile a decent mail reader and scrap mailx.
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
From: bam@jutland.ColumbiaSC.NCR.COM (Bo Muldbak)
Subject: Re: Problem with mailx in ESIX 4.0.4
Reply-To: Bo.Muldbak@ColumbiaSC.NCR.COM
Organization: NCR Corporation, MCPD Columbia SC.
Date: Wed, 16 Dec 92 20:05:18 GMT

In article <1992Dec15.154511.27086@cs.hw.ac.uk>, hmc@cs.hw.ac.uk (Hugh Conner)
writes:
|> We have several 486 based systems running ESIX 4.0.4. When using the mailx
|> command to read mail messages a problem occurs if the first word on a line
|> of the message is 'from'. I notice that when sending mail if the first
|> word
|> is 'From' with a capital F it replaces it with '>From' which I assume is
|> meant
|> to stop the mail reader treating it as the start of a new message. This
|> does
|> happen with 'from' and although /bin/mail reads the message ok, mailx
|> decides that the line starting 'from' is a new message. Does anyone know a
|> patch for this or should I just compile a decent mail reader and scrap
|> mailx.

This is a known problem in mailx. Individual messages are supposed to be
divided
by lines starting with "From ", not "from" or "from ".  But mailx is doing
this without
looking at the case. You need a fix from your vendor. Or a decent mailreader
like
ELM. :-))

	Regards
		Bo

-- 
Bo Asbjorn Muldbak             // Email:  Bo.Muldbak@ColumbiaSC.NCR.COM
Unix Systems Business Unit     // Phone:  +1 (803) 791-6871
NCR Corporation, MCPD-Columbia // Fax  :  +1 (803) 739-7371
All standard disclaimers apply // Wizards? Where, when, why? I'm an atheist..
Newsgroups: comp.bugs.sys5
From: wd@pcsbst.pcs.com (wd)
Subject: Re: putenv() is clobbering static data! NCR 3xxx NCR OS 2.0 (SVR4)
Organization: PCS Computer Systeme GmbH
Date: Mon, 14 Dec 1992 06:15:35 GMT

rick@rei.com (Richard J. Barton) writes:

>You may want to check the amount of combination argv, envp string space
>that's being used.  Then look at the kernel parameter ARG_MAX (usually
>defaults to about 5K).  If you're repetitively doing putenv() this may
>be a problem.  This is just a hunch...

Not in any implementation of putenv() I can look at (and this in- 
cludes SVR4). If necessary putenv() realloc's what it needs. 

Wolfgang

==================================================================
Name    : Wolfgang Denk                         (+49)-89-68004-288
Company : PCS GmbH, Pfaelzer-Wald-Str. 36,  8000 Munich,  Germany.
UUCP    : ..[pyramid ;uunet!unido]!pcsbst!wd  (PYRAMID PREFERRED!!)
DOMAIN  : wd@pcsbst.pcs.[ COM From rest of world; DE From Europe ]
###################################################################
#  "UNIX was not designed to stop you from doing stupid things,   #
#   because that would  also stop you from doing clever things."  #
#   -- Doug Gwyn                                                  #
###################################################################
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
From: les@chinet.chi.il.us (Leslie Mikesell)
Subject: Re: Problem with mailx in ESIX 4.0.4
Organization: Chinet - Public Access UNIX
Date: Wed, 16 Dec 1992 16:21:58 GMT

In article <1992Dec15.154511.27086@cs.hw.ac.uk> hmc@cs.hw.ac.uk (Hugh Conner) writes:
>We have several 486 based systems running ESIX 4.0.4. When using the mailx
>command to read mail messages a problem occurs if the first word on a line
>of the message is 'from'. I notice that when sending mail if the first word
>is 'From' with a capital F it replaces it with '>From' which I assume is meant
>to stop the mail reader treating it as the start of a new message. This does
>happen with 'from' and although /bin/mail reads the message ok, mailx
>decides that the line starting 'from' is a new message. Does anyone know a
>patch for this or should I just compile a decent mail reader and scrap mailx.

Pre-sysvr4 mail used lines starting with "From " as the delimiters between
messages in the mailbox file, and added the leading ">" to any such
lines in the body of a message.  SysVr4 mail uses a Content-Length: header
to encapsulate the body and does not restrict or modify the content
of the body.
I'd recommend getting the current version of ELM which understands this
convention and is a lot nicer than mailx anyway.

Les Mikesell
 les@chinet.chi.il.us
Newsgroups: comp.bugs.sys5
From: rick@rei.com (Richard J. Barton)
Subject: Re: putenv() is clobbering static data! NCR 3xxx NCR OS 2.0 (SVR4)
Date: Fri, 11 Dec 1992 16:43:36 GMT
Organization: Recognition Equipment, Inc.

aland@informix.com (Colonel Panic) writes:

>I've run into a nasty bug on NCR, but I can't yet be sure whether this
>is a USL-generic thing or NCR-specific.

>The scenario: I have a socket-accepting daemon that forks children for
>each new accepted connection over an RF link.  Pretty basic stuff.
>At one point, I call putenv() to replace PATH in the user's environment
>(a security measure; long story).  I assemble my new variable into a 
>(static) character buffer declared above main (*not* an automatic
>variable, I'm not *quite* that punchy yet), call putenv(), putenv()
>returns zero, AND CLOBBERS MY SOCKET HANDLE! (a (static) int). 
>What was (5) becomes (1835413345) as an immediate result of the putenv().  
>The string being putenv'd is about 340 bytes long.  I don't know yet 
>if anything else gets clobbered.

>All of this works fine on Sun and HP/UX (among others), but this is
>the first SVR4 we've tried it on.    

>Any ideas out there?

You may want to check the amount of combination argv, envp string space
that's being used.  Then look at the kernel parameter ARG_MAX (usually
defaults to about 5K).  If you're repetitively doing putenv() this may
be a problem.  This is just a hunch...

-- 
rick
:-)
rick@panic.com [Personal]
rick@rei.com   [Plexus Software, A Division of Recognition Equipment Inc.]
From: miket@frog.CRDS.COM (Michael C Tiernan)
Newsgroups: comp.bugs.sys5
Subject: Test suite for SVR2 or SVR3 tools.
Summary: Searching for test suite for tools.
Date: 16 Dec 92 17:14:35 GMT
Organization: Charles River Data Systems


	Does anyone know of a test suite for the tools associated with
	UNIX SVR2 or R3?  This can be either PD (in some form) or
	Commercial for purchase.

	Thanks all for your time.
-- 
<< MCT >>  Michael C Tiernan. - GEnie:M.Tiernan - AOL:M Tiernan/BCS Mike 
UUCP = alfalfa!pro-angmar!m.tiernan OR miket@frog.UUCP
      It's too bad that it takes almost half of our life
	to realize that it was a "Do-It-Yourself" project.
Newsgroups: comp.realtime
From: drodman@pacific.mitre.org (David B Rodman)
Subject: Re: real_time systems
Organization: The MITRE Corporation, McLean, VA, USA
Distribution: comp
Date: Wed, 16 Dec 1992 21:30:18 GMT

>ZS>Is it true to say that, preemption is an essential characteristic of
>ZS>a real_time system? if not how can we make sure that all tasks will
>ZS>meet their deadlines?

Elliot Chaplin>If a cooperative roundrobin won't fill the bill, a watchdog timer can be
Elliot Chaplin>added.  See an article by Jack Woehr in DrDobbs maybe a year ago.
>---

Is preemption an essential charateristic of a real time system? No, consider a 
system where the deadline of every task is longer than the utilization time of 
that task plus the latency of every other task executing... as in the roundrobin
scheduling suggested by Chaplin.

What you need to investigate is Rate Monotonic Analysis, it is a way to look at 
tasks utilization, their deadlines, and the blocking they have by equal priority 
(round robin scheduling) and higher priority tasks (preemptive priority scheduling).

David Rodman
drodman@mitre.org   My opinions are my own, you can't sue my employer for them and 
                    I don't have any money.
From: miket@frog.CRDS.COM (Michael C Tiernan)
Newsgroups: comp.realtime
Subject: Re: Publisher of Journal of Real-Time Systems?
Date: 15 Dec 92 18:23:36 GMT
Organization: Charles River Data Systems

ishioka@con.sdl.melco.co.jp (Takuya Ishioka) writes:
>In article <9s0suB2w165w@ade.no> kai@ade.no (Kai Atle Myrvang) writes:
>> If you mean REAL TIME MAGAZINE, it is:
>Or if you mean "The Journal of Real-Time Systems",
>Kluwer Academic Publishers, Manufactured in The Netherlands.

	Or, if you mean "Real-time Magazine"
	Published by:
		RT Publications
		Diepenbeemd 5
		B1650 Beersel
		Belgium
		Tel & FAX : 32-2-520.55.77
-- 
<< MCT >>  Michael C Tiernan. - GEnie:M.Tiernan - AOL:M Tiernan/BCS Mike 
UUCP = alfalfa!pro-angmar!m.tiernan OR miket@frog.UUCP
      It's too bad that it takes almost half of our life
	to realize that it was a "Do-It-Yourself" project.
Newsgroups: comp.realtime,comp.unix.ultrix,comp.sys.m68k
From: solomon@becks.comm.mot.com (James Solomon)
Subject: SUMMARY: Is there a pSOS Emulator for Unix?
Organization: Land Mobile Products Sector, Motorola INC.
Date: Thu, 17 Dec 1992 10:53:37 GMT
Keywords: psos,real,time,unix,emulator


My original post:

>Does anyone know of a software emulator for pSOS that runs as a user process
>under Unix, more specifically under Ultrix?  Please respond via Email and I'll
>summarize if there's enough interest.

The situation, unfortunately, is not very pretty.  Here is the relevant
information:

1)  Integrated Systems Inc. (ISI), the makers of pSOS, does *not* offer a pSOS
    emulator for Unix.  As steve@vienna.ericsson.se (Steve Reynolds) pointed
    out, the more of us who hound ISI for such a product, the better the
    chances of having them write one!.  Similarly, neither AMC, HP, Tecktronix,
    nor Microtec offers such a product.

2)  A number of people pointed out that pSOS and applications written to it run
    quite nicely (but not particularly swiftly ;-) under x-ray+ which is
    Microtec's M68k simulator which runs on a number of Unix platforms.

Thanks to all who responded.  Please hound ISI and request that they write a
software emulator for pSOS:  (708-498-7380).

Regards,
--
Jim Solomon (solomon@comm.mot.com)
Disclaimer:  It's my fault, not Motorola's.
Newsgroups: comp.realtime
From: uhde@ollie.jsc.nasa.gov (Jo Uhde)
Subject: Re: real_time systems
Organization: NASA/ Johnson Space Center
Distribution: comp
Date: Thu, 17 Dec 1992 21:08:26 GMT

In article <BzEsnz.6nn@cs.uiuc.edu>, feng@cs.uiuc.edu (Wuchun Feng) writes:
> 
> borch@ugli.tsd.itg.ti.com (Mark Borcherding) writes:
> 
> >David,
> >
> >Are there any recommended books (papers) that cover Rate Monotonic Analysis?
> >
> >
> >Regards :)
> 
> Well, my name's not David; but the classical paper on rate monotonic
> analysis is
> 
> Liu, C.L. and Layland J.W. "Scheduling Algorithms for Multi-Programming in
>   a Hard-Real-Time Environment", Journal of the Association for Computing
>   Machinery, Vol. 20, No. 1, January 1973, pp. 46-61
> 
> Another good paper is
> 
> Sha, L., Klein, M.H., and Goodenough, J.B. "Rate Monotonic Analysis for
>   Real-Time Systems", pp. 169-185 (Unfortunately, I don't remember which
>   journal this is from off-hand)
>

This appears as a technical report from the Software Engineering Institute
(SEI) at Carnegie-Mellon University which is numbered

CMU/SEI-91-TR-6
ESD-91-TR-6

This has the same title and authors as cited above, and is dated March 1991.
I'm not sure about the page numbering, because my copy begins at page 1.

I think another good paper for when one begins to worry about high priority
aperiodics, and implementing the Period Transformation technique is the 
following:

Sprunt, Brinkley, and Sha, Lui "Implementing Sporadic Servers in Ada",
CMU/SEI-90-TR-6 ESD-90-TR-207, May 1990

The above is also a technical report from the SEI.

Hope this helps,

DrJo
 
> -Wu
> 
> -- 
> Wuchun Feng // feng@cs.uiuc.edu // University of Illinois // Urbana, IL 61801
> 
> 
Newsgroups: comp.realtime,comp.arch.bus.vmebus
From: wybo@adi.com (Dave Wybo)
Subject: consultant broadcast?
Organization: Applied Dynamics
Distribution: usa
Date: Mon, 14 Dec 1992 19:39:19 GMT

What does nettiquette say about consultants putting up short blurbs in select
newsgroups in order to drum up some (badly needed) business?
-- 
--
Dave Wybo  Applied Dynamics, 3800 Stone School Road, Ann Arbor, MI 48108
(313) 973-1300  Internet: wybo@adi.com  uucp: (sharkey|heifetz)!amara!wybo
--
Newsgroups: comp.realtime,comp.arch.bus.vmebus
From: murray@rocky.raleigh.ibm.com (Charlie Murray)
Subject: Re: consultant broadcast?
Date: Fri, 18 Dec 1992 14:55:00 GMT
Distribution: usa
Organization: IBM, Research Triangle Park, North Carolina

In article <1992Dec14.193919.16000@adi.com>, wybo@adi.com (Dave Wybo) writes:
|> What does nettiquette say about consultants putting up short blurbs in select
|> newsgroups in order to drum up some (badly needed) business?
|> -- 
|> --
|> Dave Wybo  Applied Dynamics, 3800 Stone School Road, Ann Arbor, MI 48108
|> (313) 973-1300  Internet: wybo@adi.com  uucp: (sharkey|heifetz)!amara!wybo
|> --

We do it all the time over in misc.jobs.contract, of course, that's what that
group is for.  I say have at it.

--------------------------------------------------------------------
  Charlie Murray           CompuServe:  73707,1752
  Consulting at IBM        Internet:    73707.1752@compuserve.com

  NOTE:  If sending email use the addresses given in this .sig,
         not the one in the header of this message.
--------------------------------------------------------------------
Newsgroups: comp.realtime
From: R.Sheikhan2@lut.ac.uk (ZAGROS) 
Subject: Real_time systems
Reply-To: R.Sheikhan2@lut.ac.uk (ZAGROS)
Organization: Loughborough University, UK.
Date: Wed, 16 Dec 92 12:07:23 GMT

Hi Real_timers,

Is it true to say that, preemption is an essential characteristic of 
a real_time system? if not how can we make sure that all tasks will
meet their deadlines? 
Any comments and views on this will be much appreciated.

yours
Z