From: chip@chinacat.unicom.com (Chip Rosenthal)
Newsgroups: comp.unix.xenix.sco
Subject: Welcome to comp.unix.xenix.sco [changes from previous version]
Date: 6 Sep 92 00:20:43 GMT
Organization: Unicom Systems Development, Austin, TX
Supersedes: <sco-xenix-diff-920807@chinacat.unicom.com>

*** /tmp/faq8051.prev-version	Sat Sep  5 19:19:20 1992
--- /tmp/faq8051.curr-version	Sat Sep  5 19:19:18 1992
***************
*** 1,4 ****
! @(#) sco-xenix 1.31 92/08/07 21:32:55
  
  Welcome to comp.unix.xenix.sco.  This newsgroup is about the XENIX
  operating system from the Santa Cruz Operation (SCO).  If you have an
--- 1,4 ----
! @(#) sco-xenix 1.33 92/09/05 18:52:02
  
  Welcome to comp.unix.xenix.sco.  This newsgroup is about the XENIX
  operating system from the Santa Cruz Operation (SCO).  If you have an
***************
*** 67,73 ****
      QC2.  Why won't XENIX recognize my SCSI disk?
      QC3.  Where is the `/u' filesystem I created?
      QC4.  `WARNING!! - mounting: <usr> as <news>' message when booting.
!     QC5.  Is disk fragmentation curable?
  
  
  ===> Communications Questions:
--- 67,74 ----
      QC2.  Why won't XENIX recognize my SCSI disk?
      QC3.  Where is the `/u' filesystem I created?
      QC4.  `WARNING!! - mounting: <usr> as <news>' message when booting.
!     QC5.  `POSSIBLE FILE SIZE ERROR' when running `fsck'.
!     QC6.  Is disk fragmentation curable?
  
  
  ===> Communications Questions:
***************
*** 533,553 ****
      Due to a bug in the `mkdev fs' program, filesystems mounted below
      the root directory are labeled wrong.  For example, if you mount
      a device `/dev/news' onto directory `/usr/spool/news', then you
!     will get a warning message when going into multi-user mode.  This
!     would not happen if the mount point for `/dev/news' was a directory
!     called `/news'.
  
      This message is merely an annoyance and will not hamper system
      operation.  To eliminate the warning, relabel the filesystem with
      the last component of the mount directory.  For the above example,
!     you may do this by running the command:
  
-         # `news' is the basename of mount dir `/usr/spool/news'
          fsname -s news /dev/news
  
  
! QC5.  Is disk fragmentation curable?
  
      Not easily.  However, the steps to slow down fragmentation are
      pretty simple.
  
--- 534,581 ----
      Due to a bug in the `mkdev fs' program, filesystems mounted below
      the root directory are labeled wrong.  For example, if you mount
      a device `/dev/news' onto directory `/usr/spool/news', then you
!     will get a warning message when going into multi-user mode.  That's
!     because `mkdev fs' labels the filesystem with the first component
!     in the pathname (`usr' in this example) when it really should be
!     the last component in the pathname (`news' in this example).
  
      This message is merely an annoyance and will not hamper system
      operation.  To eliminate the warning, relabel the filesystem with
      the last component of the mount directory.  For the above example,
!     you may change the label from `usr' to `news' by running the command:
  
          fsname -s news /dev/news
  
  
! QC5.  `POSSIBLE FILE SIZE ERROR' when running `fsck'.
  
+     If `fsck' says `POSSIBLE FILE SIZE ERROR I=nnnn' don't panic.  It
+     almost always means `fsck' found a `sparse file', not a true
+     filesystem error.  A sparse file has holes in it.  They are created
+     when a program skips over sections of a file it is writing.  The
+     XENIX filesystem fills in those sections with zeros.  The XENIX
+     filesystem doesn't even both allocating disk blocks for the sections
+     full of zeros, thus creating a sparse file.  The complaint occurs
+     because `fsck' calculates the number of disk blocks needed to
+     store the file, counts up the number of disk blocks actually used
+     by the file, and complains that the two don't match.
+ 
+     When you get a file size error from `fsck' you should note both
+     the `I=nnnn' inode number logged in the message and the filesystem
+     which was being checked.  You can see what the file is by running
+     the following command:
+ 
+ 	ncheck -i <nnnn> <fsname>
+ 
+     where <nnnn> is the number logged in the error message and <fsname>
+     is the pathname of the filesystem device, e.g. `/dev/u'.  Chances
+     are the file will either be a dbm(S) database file (in which case
+     ignore the complaint, it's expected) or a `core' dump (in which
+     case delete the `core' file).
+ 
+ 
+ QC6.  Is disk fragmentation curable?
+ 
      Not easily.  However, the steps to slow down fragmentation are
      pretty simple.
  
***************
*** 842,851 ****
  
  QD8.  How do I change the 16550A trigger level?
  
!     If installing a 16550A UART to helped but didn't totally fix a
!     lost character problem, and your system is heavily loaded, then
!     there is something else you can try.  If you installed a 16550A
!     and there was no effect at all, then skip this -- it won't help.
  
      The XENIX `sio' driver initializes the 16550A with a trigger level
      of 14.  This means that under continual data streams the UART will
--- 870,879 ----
  
  QD8.  How do I change the 16550A trigger level?
  
!     If installing a 16550A UART helped but didn't totally fix a lost
!     character problem, and your system is heavily loaded, then there
!     is something else you can try.  If you installed a 16550A and
!     there was no effect at all, then skip this -- it won't help.
  
      The XENIX `sio' driver initializes the 16550A with a trigger level
      of 14.  This means that under continual data streams the UART will
***************
*** 1214,1218 ****
      [Thanks to Jeff Liebermann.]
  
  
! [ end of sco-xenix 1.31 ]
  
--- 1242,1246 ----
      [Thanks to Jeff Liebermann.]
  
  
! [ end of sco-xenix 1.33 ]