DOCUMENT ID:  0919-03

SYNOPSIS:     Interactive Unix 4.0 Frequently asked Questions and Answers

OS:           Interactive

PLATFORM:     Intel



PRODUCT:      Utilities, IUS

KEYWORDS:     Frequently asked Questions FAQ features 


Interactive Unix 4.0 Frequently asked Questions and Answers


1. Features of the 4.0 Interactive Unix product

   The following is a partial list of the major new features:

   -Long Filenames up to 512 characters are supported.

   -The standard "S5" filesystem has been updated to support
    symbolic links.

   -The ability to access more than 16MB on an ISA machine.

   -The Operating system is now distributed on a quarter inch
    cartridge, 150 MB (QIC 150) tape.

   -A new ASY driver that provides hardware flow control

2. To successfully install and use the Interactive Unix
   Operating System you must have the following hardware

   -386, 486 or Pentium ISA , EISA or Micro channel
    architecture platform.

   -4 megabytes of 32-bit Random Access Memory is enough to
    install, but at least 8 megabytes is recommended.

   -One fixed disk of at least 40 MB capacity is required.  A
    40-80 MB or larger fixed disk is strongly recommended.

   -A hard disk controller or SCSI host adapter supported by
    the Interactive Unix System is required.

   -A high-density drive that supports a 3 1/2 inch drive is
    required.  The system will boot from 5 1/4 media, but the
    complete distribution is available on only 3 1/2 inch
    diskettes or tape.

   -A monochrome, Hercules, CGA, VGA, or EGA display adapter
    and monitor, or other display that correctly emulates one
    or more of those video standards, is required.

3. The supported tapes drives for the 4.0 tape installation

   -Any SCSI 150mb tape drive that will run off an Adaptec,
    DPT, or Future Domain SCSI controllers.

    This includes Archive SCSI model 2150s, Mountain File
    Safe 7250SA, Sanyo model CP-150se, and the Wangtek
    5150 ES.

4. What to do when after the installation, the kernel will
   not boot and booting off of OLD.unix doesn't work.

    This problem can be solved by mounting the fix disk
    partition on the boot disk and copying the kernel found
    on the boot/install diskette to your fixed disk

    Insert the boot/install diskette into the diskette drive
    and press reset.

    After the "Booting the Interactive Unix System" message
    appears, press the spacebar.  Type maint and press

    At the shell prompt type /etc/fsck /dev/dsk/0s1.  Answer
    YES to the questions asked by fsck, but be aware this
    could remove some files.

    Mount the fixed disk by typing mount /dev/dsk/0s1 /mnt.
    To copy the kernel from the floppy disk type
    cp /unix/mnt/unix.
    Unmount the fix disk by typing imount /mnt.

    Remove the boot/install diskette and type shutdown.
    Press any key to reboot when prompted.

    When the system comes back up, log in as root and
    reinstall any previous installed drivers using the
    kconfig command.

5. If your installation failed, below is a procedure that
   will allow you to recover you system.

   It is possible that when something goes wrong while
   updating a 3.0.1 system to 4.0, the original system is
   left in a non-bootable state. The most likely scenario's
   are the ones where the update is done from tape and

     a) The update is interrupted because the tape cannot be
        found or appears to be too slow.

     b) While updating the disk gets full and the system

   What has happened is that important system files, most of
   them in /etc, such as partitions, have been moved away and
   not restored when the process was interrupted or stopped.
   The list of files include /etc/partitions and /etc/fstab
   which are quite essential to boot or to mount the original

   To bring your system back up:

   Boot from the Boot floppy

   When the message: Booting the INTERACTIVE UNIX System
   appears, press the space bar and then type in /maint when
   asked what to boot from

   It will bring up the system in maintenance mode running
   off a RAM disk

   Now mount the hard disk (it will probably fail, so do fsck

   fsck /dev/dsk/0s1

   mount /dev/dsk/0s1 /mnt

   Now copy all the files back:

   cp /mnt/etc/UGpartitions /mnt/etc/partitions

   You will find all the files back, with UG in the beginning
   of the name

   umount /mnt


   and reboot from the hard disk.

   Your system should come back up and you can restart the
   4.0 upgrade.


Copyright (c) 1999 Sun Microsystems, Inc.