tamura@versatc.UUCP (Mark Tamura) (08/17/88)
After hearing some negative responses about upgrading V2.2 to
V2.3 I was wondering how many people were having problems and
in what instances they were occurring.
I have Ultrix V2.2 running on a VAX-11/730 and MicroVAX II and
was wondering if I should upgrade to V2.3?
Also, anyone know when V2.4 is being released. Is it at beta
sites already?
mt
[ If you are running v2.2 and have installed the patch tapes then you will
have problems installing v2.3. To resolve the problems, reinstall the
original lat_vc.o and then install the v2.3 upgrade. This should take
care of you as long as you are not running DECnet. I am still looking for
information on that.
The other big problem area is fsck. You cannot mix fsck and kernels
from v2.2 and v2.3. I.e., you must use the v2.3 fsck with the v2.3 kernel.
The reason is that the "clean file system" bit moved to a new location in
v2.3. The reason for that is that there is a bug in the v2.2 file system
code that is not caught by the v2.2 fsck. By moving the bit you are
"forced" to run the v2.3 fsck on all your file systems to clean up the
problem. But if you try to mix fsck with the wrong kernel then fsck
sets one bit and the mount(2) system call examines another and the file
system never seems to be clean. Likewise you must use the correct standalone
system because it contains a kernel.
-- Art Z. ]tamura@versatc.UUCP (Mark Tamura) (08/23/88)
After hearing some negative responses about upgrading V2.2 to
V2.3 I was wondering how many people were having problems and
in what instances they were occurring.
I have Ultrix V2.2 running on a VAX-11/730 and MicroVAX II and
was wondering if I should upgrade to V2.3?
Also, anyone know when V2.4 is being released. Is it at beta
sites already?
mtgrr@cbmvax.cbm.commodore.com (George Robbins) (08/26/88)
Reply-to: grr@cbmvax.cbm.commodore.com (George Robbins) > The other big problem area is fsck. You cannot mix fsck and kernels > from v2.2 and v2.3. I.e., you must use the v2.3 fsck with the v2.3 kernel. > The reason is that the "clean file system" bit moved to a new location in > v2.3. The reason for that is that there is a bug in the v2.2 file system > code that is not caught by the v2.2 fsck. Acutally, it may be that DEC deserves a cheer on this one. One of the known problems with the Ultrix changes to the file system was that they used a dirty flag comvention that was incompatible with 4.3BSD. Hopefully they worked a trade and the dirty bit is now BSD compatible and maybe, just maybe, BSD disk labels (aka partition tables stashed on disk) will be Ultrix compatible??? 8-) they
pete@tsc.DEC.COM (Pete Schmitt) (08/26/88)
Reply-to: pete@tsc.DEC.COM (Pete Schmitt) > > After hearing some negative responses about upgrading V2.2 to > V2.3 I was wondering how many people were having problems and > in what instances they were occurring. If you have DECnet or have installed the 2.2 patches, you do not want to install 2.3, otherwise you do. > > I have Ultrix V2.2 running on a VAX-11/730 and MicroVAX II and > was wondering if I should upgrade to V2.3? > > Also, anyone know when V2.4 is being released. Is it at beta > sites already? >From what I've heard, 2.4 will not be released as a product. 3.0 is the next major Ultrix release. V2.2 is the last version for the 11/730. pete