From: udo@umunk.GUN.de (Udo Munk)
Newsgroups: comp.os.coherent
Subject: Re: anybody care to share thier opinions on the new 32bit release?
Date: 20 Aug 92 03:46:53 GMT
Organization: umunk (private)
X-Newsreader: Tin 1.1 PL4

aph@oclc.org (Andrew P. Houghton) writes:
: udo@umunk.GUN.de (Udo Munk) writes:
: : aph@oclc.org (Andrew P. Houghton) writes:
[ lines deleted ]
: : Hm, I haven't crash the system either with 4.0-beta nor with 4.0.
: : How much memory has your system? How many virtual consoles are
: : installed? How many virtual terminals are you running with the
: : screen package? The shell can't fork another proccess, if there
: : isn't enough memory for that, but this hasn't crashed anything
: : so far here. Forget about the error numbers in the uucico logfile,
: : run uucico with -x9 and tell us what it does.
: : What did not produce the same results, lex or the compiled program
: : created by lex?
: 
: I am running a 386DX 33mhz ISA system with 4mb ram. and an AMI BIOS.
: My disk controller is a WD1006V-MM1 with a 80mb Micropolis and a
: 40mb Segate MFM drives attached.

I am running a 386DX 25MHz ISA *without* cache now with 5mb ram. My
motherboard is a Opti with AMI BIOS. My disk controller is the same
as your, but not from Western Digital, it's a compatible clone.

: During the install process, when it said to reboot your computer and
: Coherent will prompt you for the other disks, it hung my computer.
: To be more precise, when it said to reboot I took the first disk out
: and hit reset.  Coherent booted up to the point where it printed half
: a screen of port numbers, etc. and ended with what my serial number
: was, and then it hung.  I redid the install several times, but it
: would not work.  After reading the install notes and the manual
: several times, I decided that since I have a clone keyboard that I
: should try to install without virtual consoles.  When I did Coherent
: booted ok and I was able to install the whole package.  So I am
: currently running without virtual consoles.

Because my keyboard also isn't kompatible under 4.0 I'm using the
kb driver with the German keyboard table. Under 4.0-beta I've had
installed the nkb driver and virtual consoles. With this driver
I've exactely the problems described in the release notes with
both versions, but the installation runs through without problems.

: On page 220 of the "lex Lexical Analyzer" tutorial the section which
: deals with ECHO.  It has the following lex program:
[ lines deleted ]
: At this point it just echoed "abcdef 123 1234" so I typed
: <ctrl-D> and it just exited back to the shell.  Granted I
: did not follow the manual exactly but whether I edit a file
: and run lex or type the program in via stdin and run lex,
: there should be no difference in the generated code in
: lex.yy.c.  I will put it in a file and run lex and diff the
: output but I suspect that thats not the problem.  It appears
: to me that the generated parser did not recognize the space
: between the words and since the input started with the rule
: [^0-9]+ it took the whole line for that rule and thus echoed
: the whole line back to me.  I have brought over several lex
: programs I did from the Sun Galaxy here at work and they do
: not run under Coherent but work fine under the Sun.

It's no difference to run lex from a file or from stdin.
You are right, the lex of 4.0 is broken.
--
Udo Munk     | voice:      +49 2131 275348             | uucp: +49 2131 278869
Oberstr. 21  | mail :      udo@umunk.GUN.de            |     2400/1200/300 8N1
4040 Neuss 1 | ...!{mcshh,smurf,unido}!easix!umunk!udo | MYNAME=bbsuser
Fed. Rep. of | CompuServe: 100021,2515                 | login: uucp
Germany      | at first connect get ~/info  and ~/files| pwd:   public
Xref: sparky comp.os.coherent:3775 comp.mail.uucp:1674