"SfR Fresh" - the SfR Freeware/Shareware Archive

Member "gnuit-4.9.4/PROBLEMS" of archive gnuit-4.9.4.tar.gz:

    1 --*-outline-*--
    2 
    3 
    4 * Known GNU Interactive Tools Problems
    5 ======================================
    6 
    7 
    8 ** 1. Missing '.' directory problem
    9 -----------------------------------
   10 
   11 While working on a previous version of git, I've tried to use it to
   12 read a NFS mounted directory.  The file system was exported by a
   13 Ultrix system and mounted on a Linux system.  When I've entered the
   14 directory where the NFS mounted file system was supposed to be, git
   15 received a SIGSEGV signal.  Looking at that directory with 'ls', I've
   16 figured out that the directory was completely empty (the '.' & '..'
   17 directories were missing too) even thought the file system was
   18 reported as being succesfully mounted.  A few days later I've
   19 experienced the same problem on our HP-UX workstation, trying to mount
   20 a NFS file system exported by a SGI workstation.
   21 
   22 Starting with that version of git, I've put two tests in the routine
   23 that reads the directory (panel_read_directory()) that check if the
   24 '.' and '..' directories have been found.  If any of them is missing,
   25 git will refuse to enter the directory, in order to avoid further
   26 problems.
   27 
   28 Unfortunately, a few people have reported that git refuses to work on
   29 their machines because it can't find the '.' directory.  One of them
   30 was using Solaris 2.3 with NFS, the other one SunOS.
   31 
   32 I recently installed NFS on a machine here and I tried to fix all the
   33 problems git had under NFS.  There were lots of problems, all of them
   34 were being related to the fact that NFS does lots of strange things:
   35 
   36 1) root can enter directories where it has no permission (remember,
   37 the root id is converted by NFS to -2 (an unprivileged user), and then
   38 is unable to read files (thus there is no ".." directory).
   39 
   40 2) in some other circumstances (directories with rw- permission only)
   41 it can enter the directory, read the entries but it is unable to stat
   42 them.
   43 
   44 I don't know if the changes I've made will fix all the problems.  I
   45 have tried to emulate the ".." directory and to recover whenever
   46 possible.  Please let me know if it works for you.
   47 
   48 
   49 ** 2. cp problems
   50 -----------------
   51 
   52 "cp -f" doesn't work on all systems, so directories that are in fact
   53 symbolic links will not be copied.  If your cp does understand "-f",
   54 try modifying the panel_copy function in panel.c, replacing "cp -r"
   55 with "cp -r -f" or "cp -rf".
   56 
   57 
   58 ** 3. SCO 3.2 V 4.2 problems
   59 ----------------------------
   60 
   61 Han Holl <100327.1632@compuserve.com> has reported a problem running
   62 git-4.3.5 on SCO Unix 3.2 V 4.2:
   63 
   64 > GIT didn't work with the ordinary malloc library:
   65 > I used './configure --with-terminfo', and added -lmalloc to the LIBS
   66 > variable (it crashed with the ordinary malloc library). I used gcc.
   67 
   68 
   69 ** 4. SLACKWARE Linux 1.2.0 / 2.0.0 termcap/terminfo problems
   70 -------------------------------------------------------------
   71 
   72 a. The 'ms' flag (safe to move in standout mode) is missing from the
   73 console termcap database.  It is available only in the console
   74 terminfo database (its terminfo name is 'msgr').
   75 
   76 b. The 'sgr0' capability (according to the terminfo manual this is the
   77 terminfo name of the termcap 'me' capability) is missing from the
   78 console terminfo database but it is available in the termcap database.
   79 This is a problem for GIT when using terminfo because if we can't turn
   80 the reverse video mode or the brightness off, we should not turn them
   81 on at all.  I've solved the problem by using a hard-coded 'me' for the
   82 Linux console if I can't find 'me' in the database, but I hate this
   83 method.  This is one of the two reasons why I prefer using termcap
   84 under Linux (the second one is that the executable linked with the
   85 termcap library is a lot smaller).
   86 
   87 c. The 'smacs' and 'rmacs' ('as' and 'ae' in termcap) are missing from
   88 the console termcap database but are available in the console terminfo
   89 database.
   90 
   91 d. 'se' is \E[27m in termcap but 'rmso' (the terminfo equivalent) is
   92 \E[0m in terminfo.  Are both ok ?
   93 
   94 
   95 ** 5. Linux color_xterm problems
   96 --------------------------------
   97 
   98 Sometimes, when moving the cursor, color_xterm deletes useful
   99 informations on the screen.  This is *NOT* an git bug because when
  100 hiding/repainting the window, the garbage disappears.  I don't know
  101 how to handle this.  The normal xterm (b/w) works fine.  Other
  102 xterm terminal emulators (with color support) like Linux's rxvt and
  103 Ultrix's xterm work just fine.
  104 
  105 To reproduce the problem, start git, press the down arrow (or ^N), and
  106 then type a few spaces in the command line.  Those spaces will be
  107 displayed with the wrong color, but if you hide and the re-expose the
  108 color_xterm window, everything will be redisplayed correctly.
  109 
  110 
  111 ** 6. File systems with no support for hard links
  112 -------------------------------------------------
  113 
  114 We can't *really* move a file on such file systems.  We have to copy
  115 the source file to the destination and then remove the it.  MS-DOG
  116 programs can perform a real move by copying the directory entry in the
  117 destination directory but I don't think we can do this under UNIX and
  118 I don't feel like writing MS-DOG "file system" dependent code.  Sorry.
  119 In fact, my real problem wasn't that stupid MS-DOG file system, but
  120 the impossibility of detecting such file systems.  The 'move' command
  121 will normally fail on file systems with no support for hard links, but
  122 under Linux it *will* work with MS-DOG file systems because I know
  123 MS-DOG lacks working hard links and I've put a small test in the right
  124 place :-).
  125 
  126 
  127 ** 7. Sun's sun-cmd termcap problems
  128 ------------------------------------
  129 
  130 If you are using the sun-cmd terminal emulator under SunOS 5.4,
  131 Solaris or similar systems, it seems that the termcap library fails to
  132 work as expected.  because some capabilities are reported as missing
  133 even though they are available.  This leads to git being unable to
  134 display the frame in reverse video.  I've compiled git with the GNU
  135 termcap library and it works just fine, but the scrolling feature
  136 still has to be disabled.
  137 
  138 I recently (4.3.8) changed git to work with standout mode whenever
  139 possible.  I don't know if this problem still exists.  Please let me
  140 know if you can figure it out.  Thanks.
  141 
  142 
  143 ** 8. Linux 2.0.x kernels
  144 -------------------------
  145 
  146 If you are experiencing problems with gitview under Linux kernels >
  147 2.0.0, try updating your termcap database to termcap 2.0.8.
  148 
  149 It seems that the sequence returned by the `End' key is given by the
  150 `@7' termcap capability in the latest termcap.  GIT used to inspect
  151 `kH' for this...
  152 
  153 
  154 ** 9. UNIX System V Release 4
  155 -----------------------------
  156 
  157 If you're compiling with gcc, you're fine.  With the native compiler
  158 you need to hand edit config.h _after_ running configure, comment out
  159 HAVE_DIRENT_H and define HAVE_SYS_DIR_H instead.  While git will
  160 compile anyway, dirent will not work for some reason I haven't had the
  161 time to figure out.