From: sje@xylos.ma30.bull.com (Steven J. Edwards)
Newsgroups: comp.os.coherent
Subject: Re: Coherent 4.0.1; some bad things
Date: 15 Aug 92 00:10:08 GMT
Reply-To: sje@xylos.ma30.bull.com
Organization: Bull HN, Worldwide Information Systems, Billerica, Mass., USA

#In article <9208141233@umunk.GUN.de> udo@umunk.GUN.de (Udo Munk) writes:
# sje@xylos.ma30.bull.com (Steven J. Edwards) writes:
#: 2) There was no registration card in my package.  Perhaps this is
#: because it was an update.
#
# That's normal, I'm using Coherent since release 3.0, and I didn't
# get a new registration card for my updates. Also why I should get one?

It is often the custom that major releases (i.e., 3.x -> 4.0) from a
variety of software vendors include re-registration.  This tells the
supplier that the customer is interested in receiving information
about future releases.  It may be less important for companies like
MWC as they sell Coherent on a direct basis and so they already know
who and where the customers are.

#: 5) The update procedere is nice, but it doesn't allow the resizing of
#: the boot partition (this is clearly stated in the notes).  The install
#: procedure is nice, but it doesn't allow the automated preservation of
#: existing root partition files (also clearly stated in the notes).  But
#: I needed to both to preserve the files and increase the root
#: partition!  Take it from me folks, you want to have at least 20 Mbytes
#: on that root filesystem for serious work.
#
# That is not a problem of Coherent, there is no UNIX (like) OS out
# there, where the size of the root partition can be changed without
# installing new. Be happy, that you "only" have to reinstall Coherent
# and not AIX 3.2 or SCO :-)

It is possible to change partition sizes on unmounted filesystems
without damaging files.  There are commercial applications for Apple
Macintosh and PC machines that do this.  Of course, a filesystem may
not be reduced in size below the combined sizes of its contents and an
increase in filesystem size can only be done by appropriating
cylinders from adjacent free space.  It can be done, although it isn't
easy.  It would have been very convenient in my case.

# All 3.x binaries failed, which are using the IPC stuff, another example
# is mtalk. This programs must be recompiled under 4.0, you may read this
# elsewhere in the release notes.

Perhaps newer versions of the release notes could list the common 3.x
packages that use the now forbidden IPC.

#: 8) The lack of hardware floating point support.  I had intended to
#: bring over SCO produced character I/O binaries from work for testing.
#: I can't compile these under Coherent because they all have ANSI
#: prototyping.  But 4.0.1 won't have anything to do with these, even
#: when the FPU is intregal to the CPU (486 DX).  #*&*$(%^)!!
#
# Hm, hardware floiting point doesn't have any to to with ANSI prototyping.

If the files didn't have ANSI-specific features, then I could have
worked with the Coherent supplied floating point emulation.

# The MWC K&R compiler is just fine, be happy to have it, otherwhise you
# couldn't compile the Gigabytes of K&R stuff from the net. 

I can compile all of the (decent) K&R C source stuff from the net with
gcc as long as I don't ask for ASNI checking.

#                                                            Whoever needs
# an ANSI compiler should get gcc or buy an ANSI compiler from one of the
# third party software vendors (see release notes).

I, and many other 4.0 users, are waiting for gcc to arrive.  As an
alternative, MWC could update their cc to include ASNI facilities.

# Why you do ask us? :-) /dev/cmos points to the CMOS RAM, and the bits
# of it should be documented in the motherboard or BIOS manual.

Sadly, information of this sort is rarely provided by many PC hardware
vendors.  There are third party books available, but these are not
always appropriate.  If MWC made the device entry, then they can also
provide the documentation.  There are four devices in 4.0 with major
device number zero: 0/mem 1/kmem 2/cmos 3/boot_gift.  If MWC
documented the first two, then they can say a few words about the
second two.

#: 12) The terminfo subsystem is introduced; a good idea.  But where are
#: the tic source files?  How can I modify the terminfo for ansipc if I
#: can't find the source?
#
# The terminfo sources aren't delivered with 4.0 because this needs disk
# space, and the disks are full. Also there is no need to deliver the sources,
# use the command infocmp to decompile the binaries back to the sources.

Ah, but you have to find out about it first.  I think the only
guaranteed way of finding these utilities is to do a:

	find / -name "*info*" -print

and hope for the best.

 [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