User manual NOVELL CLIENT 1.0 FOR LINUX README

[. . . ] You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to www. novell. com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. [. . . ] Users Not Prompted to Change an Expired Password if it has Expired General Issues . . 5 7 9 . 9 . 9 . 9 . 9 10 10 10 10 10 10 11 11 11 12 12 12 12 12 12 12 12 13 13 14 Contents 5 6 Novell Client for Linux Readme Novell Client for Linux Known Issues Readme This document includes information on known issues that have not been resolved for Novell® ClientTM 1. 0 for Linux. Additional Documentation For documentation on installing and configuring Novell Client for Linux, see the Readme files contained in the download. Documentation Conventions In this documentation, a greater-than symbol (>) is used to separate actions within a step and items within a cross-reference path. A trademark symbol (®, TM, etc. ) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as UNIX* or Linux*, should use forward slashes as required by your software. Novell Client for Linux Known Issues Readme 7 8 Novell Client for Linux Readme 1 Novell Client for Linux This Readme describes issues that have not been resolved for Novell® ClientTM 1. 0 for Linux. The issues are divided into the following areas: "Installation Issues" on page 9 "Login Issues" on page 10 "General Issues" on page 12 To access the installation and administration documentation for Novell Client for Linux, see the readme files included in the download. Installation Issues Install Only on 32-Bit Hardware Novell Client for Linux supports 32-bit hardware platforms only. Even though Novell Linux Desktop might support some 64-bit hardware platforms, Novell Client 1. 0 for Linux is designed for 32-bit hardware only. Uninstall Previous Version before Installing When you are installing Novell Client for Linux, you must first uninstall any previous version of Novell Client for Linux (this includes beta versions). If you do not uninstall previous versions, the novfs kernel driver might not load correctly. If you installed version 1. 0 without uninstalling previous versions and you experienced problems, uninstall Novell Client and then install version 1. 0. Package Failed Error During YaST Installation On NLD workstations not running SP1 or SP2, if a dialog box indicating that the YaST installation of a package failed appears during installation, select Show Details. If the following three error messages appear, select Retry. error: cannot get exclusive lock on /var/lib/rpm/Packages error: cannot open Packages index using db3 - Operation not permitted (1) error: cannot open Packages database in /var/lib/rpm Novell Client for Linux 9 Install Script Contains Fatal Error Messages But Still Installs Correctly When running the installation script, two fatal error messages appear, but Novell Client for Linux installs correctly. The errors are: 7706 Segmentation fault ERROR: Module novfs does not exist in /proc/modules These messages will be rewritten in the future to avoid any confusion. They should be ignored in version 1. 0. Login Issues Integrated Login Not Provided This version of Novell Client for Linux does not provide an integrated login experience with the initial workstation login screen. Users who have migrated from Windows* desktops to Linux do not have the same experience and must log in to the workstation and then log in to the network using the Novell Client for Linux. CN User Identifier Variable Displays the Wrong Information If the CN user identifier variable is used in the login script, it displays the wrong information if the Other Name field is filled in. This results in drive mappings not being made. Depending on how the variable login script is used, errors might occur. Supported MAP Command Login Script Syntax The following is a sample of valid login script syntax for the MAP command: map my_projects:=server/vol:path map f:=server/vol/path map f:=vol:path map f:=vol:\path map display on f:=server\vol:path map display off f:=server\vol:path map "my projects":=server/vol:path map f:=\\server\vol\path map *1:=server\vol:\path TIP: Linux does not support backslashes on the command line. UNC names can be written with forward slashes. For example, map f:=//server/vol/path Map Command Differences from Windows Behavior The MAP command works differently based on whether you run it from a login script or at the command line. The following is a list of differences in how the MAP command behaves at the command line in Linux versus how it works at the command line in Windows. 10 Novell Client for Linux Readme UNC names must be designated with forward slashes instead of backslashes Separate map requests on a single line with a comma instead of semicolon. map j:=server1/vol:/path;server2/vol:path map errors on/off is parsed but does not do anything map ins j:=server/vol:/path the ins is ignored map root j:=server/vol:/path the root is ignored map change is not implemented map physical is not implemented Login Script Commands Not Implemented in Novell Client for Linux The following login script commands currently are not implemented in the Novell Client for Linux. DRIVE MAP S1:=server/vol:/path (Search drives are not implemented but default to creating symbolic links S1. . S16) IF Statement Does Not Work without the THEN Statement In Linux, the IF statement cannot be used without the THEN statement. [. . . ] Without this information, users might map over an already mapped resource without knowing that the drive is already in use. There is no current fix for this issue. Extended (Swedish) Characters Are Not Displayed Correctly through Object Properties Extended characters are mapped from workstation to server (and back again) incorrectly, resulting in odd or even characters that cannot be displayed. This will be fixed with the next release. Man Page Issues Man Pages Included for Utilities Not Included Man pages exist for the NWSEND, NWPURGE, and NWSALVAGE utilities. However, these utilities were not included with version 1. 0. Manpath Issue Requires a Different Utility to Call Man Pages There is a known bug related to the manpath environment variable on both NLD and SUSE® Linux Professional. [. . . ]