HDTenEightyP/NetNews huggingface dataset:
From: bob@dalek.mwc.com (Bob Hemedinger)
Newsgroups: comp.os.coherent
Subject: Re: More fun with /tboot in Coherent 4.0.1
Date: 17 Aug 92 17:58:54 GMT
Reply-To: "Coherent operating system" <COHERENT@indycms.bitnet>

> A suggestion by MWC was to abort tboot's automatic sequence (type a
> space during the five second pause), and then type "info".  Well, this
> definitely produced an interesting repsonse.
>
> Typing "info" once produces a 128 line list of attached drives number
> 0 though 127.  As there is only one hard drive, I did not put too much
> faith in this list.  Typing "info" a second time during the same boot
> attempt produced a correct one line response, so I guess it must have
> repented of its earlier fibbing.  As further suggested by MWC, I then
> typed "autoboot" and tboot proceeded to boot the system with no
> complaints whatsoever.  I examined the contents of /dev/boot_gift and
> found "autoboot" at offset 0x20.  Earlier troubled boots had apparent
> garbage at this location.


This problem appears to be the result of the internals of some AMI
bios chips. We are working on a new tboot to handle this condition.

--
		   MWC Technical Support (bob@mwc.com)
(====================]          _____	      My friends, the great experiment,
         \\             (===================) the USS Excelsior.
   (======\\======]         /// ~~~~~
           \\/             ///	 She's said to have transwarp drive.
    ===========================	 Aye, and if my grandmother had wheels, she'd
     =========================(	 be a wagon.
Newsgroups: comp.os.coherent
From: hcp@csx.cciw.ca (H.C. Pulley)
Subject: Re: Bug in Coherent 4.0 Compiler
Organization: Canada Centre for Inland Waters
Distribution: usa
Date: Mon, 17 Aug 1992 19:19:25 GMT

In article <SJE.92Aug17114818@xylos.ma30.bull.com> sje@xylos.ma30.bull.com writes:
>> -------------------------------------- cut here ------------------------
>> char *string = "Hello World\n";
>>
>> main()
>> {
>> char **pp;
>>
>> *pp = string;
>> printf("%s", *pp);
>> }
>> -------------------------------------- and here ------------------------
>>
>> This program bombs my system and dumps the core. I have tried this 
>> on other UNIX systems and even dos and it works just fine...

Check again.  Under EP/IX here the program does not dump core but no message
is printed.  Under ULTRIX, the program causes a Segmentation Violation and 
dumps a big core.

>> How can this get corrected? Do we have to wait until 4.1????
>
>It's a bug in your code.  The value of variable pp is undefined at the
>time it is dereferenced in the statement "*pp = string".  That
>assignment is either trashing four bytes somewhere or trying to write
>outside the data segment.  It is not a problem with Coherent.

Since DOS doesn't use any memory protection, this problem will only show up
if pp points to something crucial.  I still doubt, however, that the message
will be printed correctly, since *pp is not pointing to the right place.

Your problem lies with *string being a 'pointer to char' and **pp being a 
'pointer to pointer to char'.  The line
*pp=string
is attempting to set the area of memory pointed to by pp to the value string,
which is a memory location.  Since pp is uninitialized, as pointed out by
Steve, you may trash memory by assigning it a value.

I don't want to sound insulting here, but that is the wierdest 'Hello, World'
program I have ever seen. 

Harry
-- 
         hcp@csx.cciw.ca           | This message    | It takes all kinds,
   hcpiv@grumpy.cis.uoguelph.ca    | released to the | and to each his own.
-----------------------------------| PUBLIC DOMAIN.  | This thought in mind,
 Stay away from the DOS side Luke! |                 | I walk alone.
From: sjsobol@tiny.com (Steven J. Sobol)
Newsgroups: comp.os.coherent
Subject: Re: Installation of 4.0 - missing disk  2 !
Date: 19 Aug 92 07:18:38 GMT
Reply-To: sjsobol@tiny.com (Steven J. Sobol)
Organization: The Tiny Software Company, Main Office, Cleveland, Ohio

dfilip@colornet.UUCP () writes:

>kept complaining it was disk 1. I called MWC, and they informed me that some
>of the kits were shipped with two disk 1's, and that they would need to ship
>me another disk 2.
>
>Was wondering how many others have experienced this same joy ???

we will see.. in conducting my survey I have found that this is the most
common complaint....

-- 
***  **  ** | The Tiny Software Co.  23707 Glenhill  Cleveland OH 44122
 *  *   *   | Steve Sobol * President * sjsobol@tiny.com or tiny!sjsobol 
 *   *  *   | Alternate addresses: sjsobol@wariat.org or ag510@po.cwru.edu
 *    * *   | Disclaimer: I *AM* the Tiny Software Company. 
 *  **   ** |      *** DON'T SHOOT ME!! I'm too cute to die!!!! ***
From: sje@xylos.ma30.bull.com (Steven J. Edwards)
Newsgroups: comp.os.coherent
Subject: Re: 4.0, Low level IO and problems...
Date: 14 Aug 92 21:13:42 GMT
Article-I.D.: xylos.SJE.92Aug14141342
Reply-To: sje@xylos.ma30.bull.com
Organization: Bull HN, Worldwide Information Systems, Billerica, Mass., USA

> Hi there - I have had coherent installed for about 2 weeks and here is
> my report of it with the problems that I have had...
>
> 2 - forgetting to use the right type on a scanf causes a core dump
>	   eg scanf ("%d",i)  where i is an int.

Try:

	scanf("%d", &i);

because scanf, like sscanf and fscanf, wants to see pointers as the
tail arguments.

> 3 - More seriously there is no LOW LEVEL DISK TOOL in coherent unlike
>	   minix. It would be good to be able to directly modify the file
>	   system from root... There is also no limited undelete as in 
>	   minix. Are there any tools that allow a specified i-node to
>	   be turned into a file? DUMP suposedly lets you select i-numbers
>	   which are presumably i-nodes but doesnt mention how to do it.
>	   Does anyone have any clues on turning I-NODES into files PLEASE?

Well, if one is really desparate, one could always use a debugger or
patch utility on /dev/at[01][a-dx] in single user mode, but why?  All
common filesystem errors are fixable from fsck.  Lost files (those
that are allocated but have no name/parent are assigned to
/lost+found.  If it's not there, you can't recover it.

Undeletes are just too dangerous on Unix-type systems because it's too
hard to guarantee file system integrity when more than one agent is
accessing the same information.  Remeber, the Unix file system
utilities are designed with the thought that only they as a group will
be fiddling with various hidden parts; they often assume that
everything is okay, thus causing human-introduced errors to grow and
expand in avalanche fashion.

So, instead of undelete,

1) Make backups.

2) Be careful when typing "rm" and the like.

3) Learn from others' experience, it's often less painful than
learning from your own.

 [The above opinions expressed are my own; not necessarily held by others.]
      == Steven J. Edwards           Bull HN Information Systems Inc. ==
      == (508) 294-3484              300 Concord Road         MS 820A ==
      == sje@xylos.ma30.bull.com     Billerica, MA 01821          USA ==
"That Government which Governs the Least, Governs Best." -- Thomas Jefferson
From: olpi@sbustd.rz.uni-sb.de (Oliver Pischke)
Newsgroups: comp.os.coherent
Subject: German FTP-site carrying Coh-ware ?
Date: 21 Aug 92 12:39:02 GMT

Organization: Studenten-Mail, Rechenzentrum Universitaet des Saarlandes
Hi folks,

are ther any FTP-sites in Germany carrying PD for Coherent ?
If so, could some1 please mail me the addresses ?

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

| Oliver Pischke / Bismarckstr. 22 / D-6600 Saarbruecken / Germany   |

| -------------------------------------------------------------------|

| Internet: olpi@stud.uni-sb.de          | CIS: 100112,711           |

|                                        |---------------------------|

|  |\/\/\/| gauloise@lutzifer.hh.sub.org | Phone: +49 681 638132     |

|  |      |                                                          |

|  |      | ---------------------------------------------------------|

|  | (o)(o)                                                          |

|  C      _)      project : porting PoVRAY 1.0 to SUNOS              |

|   | ,___|                                                          |

|   |   /         due to lack of sense of nccnet-sysadmin            |

|  /___\          I can no longer be reached at this site. f**k  !   |

| /     \                                                            |

 ---------------------------------------------------------------------
From: edi@edefix.han.de (E. v. Pappenheim)
Newsgroups: comp.os.coherent
Subject: Re: Coherent 4.0.1; some bad things
Date: 14 Aug 92 08:34:33 GMT
Organization: Private

X-Newsreader: Tin 1.1 PL4

sje@xylos.ma30.bull.com (Steven J. Edwards) writes:
: In article <9208120959.AA01930@dalek.mwc.com> bob@dalek.mwc.com (Bob Hemedinger) writes:
: #> [installation-tale-of-woe by sje]

[...]

: 
: 18) the uucheck program is acting a bit paranoid and is complaining
: about the absence of about six or so files that have my serial number
: as the last segment of the pathname.  Most of these were supposed to
: be in the /usr/spool/uucp directory tree.  I am afraid to try the -f
: option as I don't think any of these should exist.

uucheck does NOT allow the escaping of CR with '\' anymore, an entry in L.sys
must be in ONE line per system, then it works fine, although it deletes ALL
LCK..XX files in /usr/spool/uucp.

Ecki

:  [The above opinions expressed are my own; not necessarily held by others.]
:       == Steven J. Edwards           Bull HN Information Systems Inc. ==
:       == (508) 294-3484              300 Concord Road         MS 820A ==
:       == sje@xylos.ma30.bull.com     Billerica, MA 01821          USA ==
: "That Government which Governs the Least, Governs Best." -- Thomas Jefferson
-- 
------------------------------------------------------------------------
Eckebrecht von Pappenheim 	Eleonorenstr. 17        3000 Hannover 91
UUCP: edi@edefix.han.de			     Tel: (Voice) +49 511 443755
      ...!unido!horga!agsc!edefix!edi
------------------------------------------------------------------------
From: bill@chaos.cs.umn.edu
Newsgroups: comp.os.coherent
Subject: Re: 4.0, Low level IO and problems...
Date: 21 Aug 92 15:05:21 GMT
Organization: University of Minnesota

In <9208192524@umunk.GUN.de> udo@umunk.GUN.de (Udo Munk) writes:

>Also see dcheck, icheck and clri. It's not hard to write an I-node
>editor, but playing around with tools like this is very dangerous.

>There is a save way: substitue rm by a programm, which brings the file
>to delete into an archive (tar, zip, cpio or whatever). After that the
>file can be deleted by the new command. Write an undelete command which
>extracts the file back from the archive, and then removes it from the
>archive. Of cause this needs more or less diskspace. Take a look onto
>DR-DOS 6.0, how DRI has solved this problem.

in a back issue of unix review i recall the code for a unix undelete.
unfortunatly only parts of the code were published.
it was identified in the article that the full code could be had from
an uunet address, but we were never able to resolve it.
i finally took the magazine back home. *if* someone knows how to 
resolve uunet addresses with some degree of sucess i can bring
the info back and we can work on this.
please if you email include your ip address as this host has access
to some really poor maps.

bill pociengel
--
bill@chaos.cs.umn.edu
From: kenji@reseau.macrofield.or.jp (Kenji Rikitake)
Newsgroups: comp.os.coherent
Subject: Re: Passwords and security (Was: Who are you?)
Date: 13 Aug 92 00:42:45 GMT
Reply-To: kenji@reseau.macrofield.or.jp (Kenji Rikitake)
Distribution: comp
Organization: Macrofield Corporation, Toyonaka-city, Osaka, Japan
Posting-Front-End: Terakoya-u kaku 2.06 DEBUG 11-AUG-1992

In article <1342@pacsoft.com>
	mike@pacsoft.com (Mike Stefanik) writes:
>The choice of password is obviously important, but since the encryption
>method is well known, having the encrypted password readable by the public
>is simply not a good idea.

Knowing an encryption method does not mean that encrypted object 
is easily decipherable. See US NIST's DES or NTT's FEAL - they are 
well-described in a bunch of academic papers but very few (if ever) 
might have succeeded to break the code. (I've heard none)

By using a good one-way hashing function, making the password file 
readable to public may do little on compromising the system 
security. (Choosing passwords is COMPLETELY ANOTHER ISSUE...)

// Kenji
_.. .   .___ .___ .____ _... _.. _.._ _.._. ...__   _ ___ _.__ ___ _. ._ _._ ._
"Humour is by far the most significant behaviour of the human mind."
                                -- Edward de Bono, "I am Right - You are Wrong"
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.coherent
Subject: Re: Access to I/O ports from user processes
Date: 21 Aug 92 22:16:25 GMT
Distribution: comp
Organization: University of Helsinki

In article <SJE.92Aug21133028@xylos.ma30.bull.com> sje@xylos.ma30.bull.com writes:
>A recent post mentioned that Coherent 4.0, like 3.x, allows processes
>to access I/O ports directly using the "in" and "out" instructions.
>This could lead to problems in those cases where multiple rocesses did
>I/O with the same port.

That's not the main problem: the biggest problem is that allowing
user-space IO is a surefire way to a unstable system: a rogue process
can essentially reboot the machine or do DMA over the kernel or
whatever.  Braindamage. 

>Intel has designed the 386+ CPUs to allow security level assignment
>for I/O access on a task descriptor basis.  This feature could be used
>to provide hardware enforcement of port prohibition for some or all
>processes.

Indeed.  On a 386, you can disallow port access on a port-by-port basis,
or simply allow/disallow all IO.

>But I think that it is not necessarialy a good idea.  I have a number
>of programs that fiddle with the various I/O ports that control
>hardwarre on PC machines.  Not all of these ports have corresponding
>/dev files.  Therefore, there is a real need for user processes to
>access I/O ports.  To eliminate such access would be removing an
>important part of COherent 4.0 functionality

There is /not/ enough of a "real need" to warrant free access to the IO
space - I assume 'crashme' is able to crash coherent in no time at all
if coherent truly does allow free IO port access.  There are several
ways you can implement IO port access:

 - /dev/port or whatever - slow but safe and clean
 - ioperm() system call that allows superuser processes to access all IO
   addresses and cli/sti. Unsafe, but only the superuser can do it, and
   even he must first do the system call.
 - limited IO access by using the IO bitmap.  Safer than the above (you
   might limit it just to the VGA registers or whatever, and cli/sti are
   disallowed), but you still need some kind of authorisation: being the
   super-user, or possibly being able to open "/dev/kmem" or similar. 

None of the above is complicated: linux has all three.  But allowing
full access by default is braindead - you might as well run DOS for all
the protection you give from misbehaving processes.  Just /dev/port is
enough for most things: and things that need more speed are usually
special in some way, and should be executed by root anyway.  This
includes things like device drivers, windowing systems etc. 

		Linus
Newsgroups: comp.os.coherent
From: tbuck@teal.csn.org (Timothy E. Buchanan)
Subject: assorted problems
Organization: Colorado SuperNet, Inc.
Date: Fri, 21 Aug 1992 17:15:29 GMT

I earlier reported my troubles w/ uucico & C4.00 to this group. I 
thought they were solved but evidently not. Ystdy, uucico again 
would dial, connect, then timeout w/ an Acu problem. Then, it 
decided not to pick up the phone at all.
 
This morning, it again decided to dial, but have an Acu problem. I 
made NO changes except to remove LCK files, and once to chmod 
/dev/com4r to 0666. uucico promptly changed this back to 0700.
 
Well, I thought I would try the Taylor uucp, which I got (zipaa-ar) 
from raven and catted together to uucp.zip. I dl'd unzip.tar.Zaa-c 
from mwcbbs (from the 32bit dir, size 137K if I remember right).
 
I catted unzip.tar.Z, uncompressed to unzip.tar, then ran ustar -xf 
unzip.tar. I got an Insert second volume msg, which leads me to 
believe that something is missing. But there was an executable file 
unzip in the resulting unzip dir, so I ran that on uucp.zip.
 
I got some header missing msgs. So at this point I can't try to 
install the Taylor uucp to replace the broken Coho uucp because I 
can't unzip the uucp archives cuz the unzip archives are broken or 
missing.
 
I have been beating my head against this os for several weeks now. 
I bought it to set up a newsreader; can anyone help me to fix the 
mwc uucp or install the Taylor uucp or the unzip utility?
 
Feeling quite frustrated,
Timothy.
From: mauritz_c@spcvxb.spc.edu
Newsgroups: comp.os.coherent
Subject: Re: Re: anybody care to share thier opinions on the new
Date: 17 Aug 92 03:49:12 GMT
Organization: SPC Community Access System

In article <1992Aug16.023939.6722@acme.gen.nz>, kilroy@acme.gen.nz (earthbound misfit, I) writes:
> root@mordor.com (Chris Mauritz - SysGod) writes:
> 
>> Well, I think it is time that us "loyalists" start exercising our
>> money back guarantee until such time as the product is stable.  I
>> think, after seeing all the recent traffic here, that I will cancel
>> my order and wait for a more stable update or just migrate to OS/2
>> for my "traditional unix tasks."
> 
> Chris, while I can understand you're annoyed at not receiving your update
> yet (something I can relate to) your comments about waiting for a "stable"
> product are puzzling. Read the messages you quoted: 1 person who said they
> were having problems with 4.0 and 2 who said it was running fine. I don't
> know where the "recent traffic" about 4.0 problems you refer to, maybe
> you're reading another newsgroup?

Actually, I finally did receive my update.  (Sorry for the previous
post...I trieid to cancel it but was unsuccessful...should've taken
a deep breath first...)

Anyway, I still can't use the update.  Disk #2 is a mirror image
of Disk #1 so the installation is unable to complete itself.  I
was able to "sneak" into the system and double check that Disks 1 and 2
are indeed the same.  Grumble...

In addition, the system absolutely refused to boot off the installation
disk until I disabled my SRAM cache controller on my 486.  Is anyone
else having this problem?  Coherent 3.2 cohabitated with my cache
without any complaints.

Regards,

Chris

  
> 
> 						- k
> -- 
> Craig Harding            kilroy@acme.gen.nz             ACME BBS +64 63 3551342
> "Jub'f Xvob?"
From: lentz@CHARM.GANDALF.CA
Newsgroups: comp.os.coherent
Subject: Re: Unable to install 4.0.1
Date: 20 Aug 92 19:33:08 GMT
Reply-To: "Coherent operating system" <COHERENT@indycms.bitnet>


 Try it with the turbo switch set for low speed or you your cache disabled.

--
                                       OOoo^ ^^
                                             ||           Jim Lentz
                           [__]_[__]_+--+_[____]>      lentz@gandalf.ca
                            00   00   00   0  0
Newsgroups: comp.os.coherent
From: draper@ais.org (Patrick Draper)
Subject: Modem control under Coherent
Organization: UMCC
Date: Sat, 22 Aug 1992 19:29:54 GMT

Hi,

Since installing version 4.0.1, I've had the desire to either write or
acquire a terminal program for Coherent that will offer me some of the
features that I use the most in Telemate (which I currently use under DOS).

Investigating the situation more closely, I discovered that the device
driver asy is what I need to control.

I gather that the ioctl interface is what I need to use. Also, it seems that
the header termio.h plays a part in this, but I could be mistaken.

The books I've read indicate that the unix version 7 method of device
interface was outlined in <sgtty.h>, but the System V method is outlined in
<termio.h>. Since Coherent uses the latter, is it safe to say that Coherent
is actually closer to System V than it is to version 7?

I'd like to figure out how to read and write characters from the modem which
is under control of the asy device driver. Any help in this is appreciated.

Thanks,



------------------////////////////////\\\\\\\\\\\\\\\\\\\\------------------
| Patrick Draper           Disclaimer:  I can't control my fingers,        |
| draper@umcc.ais.org                   I can't control my toes! - Ramones |
| University of Michigan                                                   |
| Computer Club                We are a nation of laws, not people         |
------------------\\\\\\\\\\\\\\\\\\\\////////////////////------------------
From: ralf@ark.abg.sub.org (Ralf Stephan)
Newsgroups: comp.os.coherent
Subject: Re: Prospective Coherent buyer's question
Date: 16 Aug 92 09:34
Organization: Private Coherent 4.0.1 site Augsburg/Bavaria/Germany

udo@umunk.GUN.de (Udo Munk) writes:
> 
> ... If you want to run gcc you should have
> 8MB of memory. For the first steps your 4MB are fine, if you
> don't connect to much terminals/modems to your system.

Does that mean gcc/g++ won't run on my 2 MB / one user system?

Another question:  Did someone try to run empire on 4.0.1?  It compiled
fine but when run dumps core. How much memory does it need?

--ralf
-----------"Life - loath it or ignore it, you can't like it."  - Guess who?
Newsgroups: comp.os.coherent
From: jtgoh@athena.mit.edu (Joo T Goh)
Subject: DOS progs. and Coherent.
Organization: Massachusetts Institute of Technology
Date: Fri, 14 Aug 1992 17:34:10 GMT

Sorry if this is a FAQ but I am a newbie as far as UNIX is
concerned.
I am presently  using a lot of DOS progs. - MS Fortran 5.1,
PCTex 386, and occasionally Windows. I would like to get
my hands dirty with UNIX, and for $100 an OS - Coherent
seems a good choice. However, I want to be able to 
continue using my DOS programs even with Coherent loaded , i.e
running them side by side. Can I do that? I am using a 486-33,
8 MB Ram, & a 120MB HD.

Thanks in advance

JT
Newsgroups: comp.os.coherent
From: geis@miles.com (Jerry Geis)
Subject: setting which modemcap entry to use???
Organization: Miles Inc., Diagnostics Division, Elkhart, IN
Distribution: usa
Date: Wed, 19 Aug 1992 16:14:56 GMT

Where do you setup which modemcap entry to use? It seems my
system is defaulting to hayes1200 and I want to change
it to be just hayes. Where do you set this up?????

jerry geis  geis@miles.com
-- 
---
Jerry Geis				Miles, Inc. Elkhart, IN
geis@miles.com 				(219) 262-6591 Phone
uunet!rde!nstar!miles!geis		(219) 262-6309 Fax
Newsgroups: comp.os.coherent
Subject: uucico322.Z wont leave mwcbbs
From: cs.dal.ca!iisat!duncan!root  (David John Murdoch)
Organization: Duncan Computer Centre and Home Brewery
Date: Sun, 16 Aug 1992 05:42:14 GMT
Reply-To: djm%duncan%iisat@cs.dal.ca (David John Murdoch)

	Has anyone else found that the new 286 uucico version at
mwcbbs!/usr/spool/uucppublic/downloads/updates/uucico322.Z is
unavailable for download?

David
-- 
 __________________________________________________________________________
 David Murdoch * cs.dal.ca!iisat!duncan!djm * Halifax, Nova Scotia, Canada  
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Newsgroups: comp.os.coherent
Subject: Do I have to recompile Cnews, WHEN I get my 4.0?
From: cs.dal.ca!iisat!duncan!root  (David John Murdoch)
Organization: Duncan Computer Centre and Home Brewery
Date: Tue, 18 Aug 1992 01:27:25 GMT
Reply-To: djm%duncan%iisat@cs.dal.ca (David John Murdoch)

	I am patiently waiting for my 4.0 update to arrive and I
wonder if I will have to recompile Cnews for 4.0? 

Thanks,

David
-- 
 __________________________________________________________________________
 David Murdoch * cs.dal.ca!iisat!duncan!djm * Halifax, Nova Scotia, Canada  
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~