Novell CLIENT 1.0 FOR LINUX - README User manual

Novell
www.novell.com
Novell Confidential Manual (99a) 21 December 2004
ClientTM for Linux
1.0
October 12, 2005
README

Novell Confidential Manual (99a) 21 December 2004
Legal Notices
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express
or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to
make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties
of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software,
at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables.
You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the
U.S. export laws. 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.
Copyright © 2005 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or
transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without
limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents/ and
one or more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Novell Client for Linux Readme
October 12, 2005
Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see
www.novell.com/documentation.

Novell Confidential Manual (99a) 21 December 2004
Novell Trademarks
ConsoleOne is a registered trademark of Novell, Inc., in the United States and other countries.
NetWare is a registered trademark of Novell, Inc., in the United States and other countries.
Novell is a registered trademark of Novell, Inc., in the United States and other countries.
Novell Client is a trademark of Novell, Inc.
SUSE is a registered trademark of Novell, Inc., in the United States and other countries.
Third-Party Materials
All third-party trademarks are the property of their respective owners.

4Novell Client for Linux Readme
Novell Confidential Manual (99a) 21 December 2004

Contents 5
Novell Confidential Manual (99a) 21 December 2004
Contents
Contents 5
Novell Client for Linux Known Issues Readme 7
1Novell Client for Linux 9
Installation Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Install Only on 32-Bit Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Uninstall Previous Version before Installing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Package Failed Error During YaST Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Install Script Contains Fatal Error Messages But Still Installs Correctly . . . . . . . . . . . . . . . . . . . . . . . 10
Login Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Integrated Login Not Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
CN User Identifier Variable Displays the Wrong Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Supported MAP Command Login Script Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Map Command Differences from Windows Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Login Script Commands Not Implemented in Novell Client for Linux . . . . . . . . . . . . . . . . . . . . . . . . . 11
IF Statement Does Not Work without the THEN Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Cannot Log In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Login Requires a Server Name for Trees Not Registered with DNS . . . . . . . . . . . . . . . . . . . . . . . . . 12
PAUSE Command in Login Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Login Script Does not Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Users Not Prompted to Change an Expired Password if it has Expired . . . . . . . . . . . . . . . . . . . . . . . 12
General Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
FAM/iNotify Causes File Copy to Hang . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Invalid Connections Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Receive Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
File and Folder Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Man Page Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6Novell Client for Linux Readme
Novell Confidential Manual (99a) 21 December 2004

Novell Client for Linux Known Issues Readme 7
Novell Confidential Manual (99a) 21 December 2004
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.

8Novell Client for Linux Readme
Novell Confidential Manual (99a) 21 December 2004

Novell Client for Linux 9
Novell Confidential Manual (99a) 21 December 2004
1Novell 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

10 Novell Client for Linux Readme
Novell Confidential Manual (99a) 21 December 2004
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.