jimzah/openafs
1
0
Fork 0
mirror of https://git.openafs.org/openafs.git synced 2025-01-31 13:38:01 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

STABLE14-windows-1380-20050310

Browse Source 
update issues list

update install notes for 1.3.80


(cherry picked from commit 01a4455f37921829896f47fa26465a587fd394f9)
This commit is contained in:
Jeffrey Altman 2005-03-11 07:31:24 +00:00
parent 04d86d2038
commit 9e1412c2e0
1 changed files with 31 additions and 51 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

82
doc/txt/winnotes/afs-issues.txt
View File

@ -1,4 +1,4 @@
This file is a rough list of known issues with the 1.3.72 release of OpenAFS
This file is a rough list of known issues with the 1.3.80 release of OpenAFS
on Windows. This list is not complete. There are probably other issues
which can be found in the RT database or on the mailing list.
@ -10,7 +10,7 @@ which can be found in the RT database or on the mailing list.
(3a) IP address changes cause the service to terminate due to an assertion
in smb_Listener() thread.
(3b) New IP addresses do not get bound
(3b) New IP addresses do not get bound to the SMB server
(3c) Loopback adapter hack:
(i) prevents use of AFS Gateway
@ -55,9 +55,9 @@ page faults which have since been fixed.
(12c) If network is not available must store the username and password
somewhere until such time as the network starts.
(13) Loopback adapter is not always installed with bindings to "File and
Printer Sharing for Microsoft Networks" or "Client for Microsoft
Networks". If these are not bound then SMB names will successfully
(13) Loopback adapter is not always installed without bindings to "File and
Printer Sharing for Microsoft Networks" and with bindings to "Client for Microsoft
Networks". If these are not bound correct then SMB names will successfully
be published to a list of zero which causes the AFS not to function.
We need a way to test whether the Loopback adapter is properly bound
so we know if it is safe to use. Actually, it is worse. Even with
@ -103,22 +103,12 @@ page faults which have since been fixed.
and per-machine settings. All of the new registry items need to
be added to the UI
(25) Thread initialization versus Global Drive Mapping. There is no
mechanism in the afsd_init.c to ensure that all of the threads
complete initializing in the correct sequence. In the case of
Global Drive Maps this is a problem because the Global Drive Maps
can be executed prior to the completion of the SMB registration
and service thread initialization.
(26) CIFS Remote Administration Protocol implementation is incomplete.
(25) CIFS Remote Administration Protocol implementation is incomplete.
Notifications are not made to requestors when the view of a file
or folder changes due to token acquisition; token expiration; or
token destruction
(27) The Cache Manager Flush routines do not return or check error
codes.
(28) Remove submount creation as a side effect of AFS drive mapping.
(26) Remove submount creation as a side effect of AFS drive mapping.
The AFS Submount is effectively a server side alias for a path
located in the AFS space. This alias is exported by the AFS
@ -135,37 +125,30 @@ page faults which have since been fixed.
or by the new AFS Client Service Administration tool when executed
by an authorized user.
(29) Add support for multi-homed servers
-------------------------------------------------------------------------
List of unfunded projects:
1. No longer use AFS Client Service "cell" as the default cell for individual users
2. Re-write afsd_service.exe to perform synchronized thread startup and shutdown.
Currently there is no synchronization of thread creation which results in timing
conflicts; and there is no attempt to cleanly shutdown the service which causes
problems when restarting and prevents the implementation of a persistent cache
3. Implement a persistent cache (requires item 2)
4. Prevent panic situation when the root.afs volume is not reachable and
2. Prevent panic situation when the root.afs volume is not reachable and
the AFS Client Server is not using Freelance mode
5. Prevent panic situation when the IP address to which the SMB server is bound is removed
3. Prevent panic situation when the IP address to which the SMB server is bound is removed
from the local machine's network configuration
6. Add support for Named Pipes within the afs filesystem
4. Add support for Named Pipes within the afs filesystem
(This is not currently a supported feature of AFS; it will require
changes to the servers as well as the clients.)
7. Re-write afscreds.exe to support:
5. Re-write afscreds.exe to support:
1. choosing between Kerberos 5 and Kerberos 4 on a per principal basis
2. providing users with the ability to map multiple cells to a single principal
3. providing change password functionality on a per principal basis
4. no longer include drive mapping
5. configuration of afscreds startup options in shortcut
8. Re-write afs_config.exe to be only "per user" functionality which does not require admin
6. Re-write afs_config.exe to be only "per user" functionality which does not require admin
privileges
1. default cell and principal for the user
2. drive mappings but no submounts
3. visibility of afs creds and setting of afs creds startup options
9. Create new afs_admin.exe tool to be installed in the administrator folder (or use MMS)
7. Create new afs_admin.exe tool to be installed in the administrator folder (or use MMS)
which contains
1. afs client service cell name
2. integrated logon configuration
@ -180,24 +163,24 @@ List of unfunded projects:
11. network configuration
12. miscellaneous
13. need to add support for all of the new registry values since 1.2.8
10. Identify why 16-bit DOS applications executed out of AFS fail
11. Add support for configurable Icon file representing AFS folders within the Explorer Shell
12. Documentation Documentation Documentation
13. Large File support (> 2GB) in SMB/CIFS client
14. Integrate KFW installation into the NSIS and MSI installers
15. Add support for record locking to AFS (requires changes to the servers)
16. Unicode enable the SMB/CIFS server. OEM Code Pages:
8. Identify why 16-bit DOS applications executed out of AFS fail
9. Add support for configurable Icon file representing AFS folders within the Explorer Shell
10. Documentation Documentation Documentation
11. Large File support (> 2GB) in SMB/CIFS client
12. Integrate KFW installation into the NSIS and MSI installers
13. Add support for record locking to AFS (requires changes to the servers)
14. Unicode enable the SMB/CIFS server. OEM Code Pages:
1. prevent the use of interoperable file names
2. force the use of paths no longer than 256 characters
3. force share names to be no longer than 13 characters
4. restrict authentication to ASCII only names and passwords
17. Complete implementation of CIFS Remote Administration Protocol
19. Add support for SMB/CIFS Digital Signatures
19. Development of afsmap.exe tool to provide AFS aware NET USE functionality
15. Complete implementation of CIFS Remote Administration Protocol
16. Add support for SMB/CIFS Digital Signatures
17. Development of afsmap.exe tool to provide AFS aware NET USE functionality
afsmap.exe <drive> <afs-path> [/PERSISTENT]
afsmap.exe <drive> <unc-path> [/PERSISTENT]
afsmap.exe <drive> /DELETE
20. Missing SMB/CIFS functions:
18. Missing SMB/CIFS functions:
Find
FindUnique
FindClose
@ -205,16 +188,13 @@ List of unfunded projects:
WriteBulk
WriteBulkData
Tran2::SessionSetup
21. StoreBehind mode is not implemented. Or more correctly, all data is
19. StoreBehind mode is not implemented. Or more correctly, all data is
written directly to the server and is not cached. Writes invalidate
the local cache entries which are then read back from the server.
22. The Power Management Flush Cache code does not work on Terminal
Server nor does it always successfully flush all of the dirty buffers
to the AFS servers before suspend/hibernate operations occur.
23. Develop an optional Installable File System replacement for the SMB/CIFS
20. Develop an optional Installable File System replacement for the SMB/CIFS
Server.
24. Add support for storing Extended Attributes on files
25. Add support for storing Windows ACLs on files
26. Remove submount creation as a side effect of drive creation
27. Finish conversion from string.h to strsafe.h for VS.NET 2005
28. Add support for multi-homed servers
21. Add support for storing Extended Attributes on files
22. Add support for storing Windows ACLs on files
23. Remove submount creation as a side effect of drive creation
24. Finish conversion from string.h to strsafe.h for VS.NET 2005