Bug 153770 - important netatalk info for relnotes
Summary: important netatalk info for relnotes
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: release-notes   
(Show other bugs)
Version: devel
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Karsten Wade
QA Contact: Tammy Fox
URL: http://fedoraproject.org/wiki/FedoraD...
Depends On:
Blocks: fc-relnotes-traqr
TreeView+ depends on / blocked
Reported: 2005-04-05 19:19 UTC by Karsten Wade
Modified: 2007-04-18 17:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-06 20:40:44 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Karsten Wade 2005-04-05 19:19:54 UTC
Description of problem, bug, incorrect information, or enhancement request:

Thanks, Charles.  This pre-filled bug template is available from the relnotes
page in the Wiki, refer to the URL field in this bz report.

**Begin Note**
Macintosh File Server

This section contains information related to netatalk, software that 
makes it possible to share files between Linux and Macintosh systems.


The 2.x version of netatalk uses a different method to store resource 
forks, and may use a different file name encoding scheme. Upgrading to 
Fedora Core 4 may result in data loss. Please read the documentation of 
the netatalk 1.x to 2.x upgrade before upgrading to Fedora Core 4.

The netatalk upgrade information is available directly from the 
netatalk site:

It is also included in the netatalk installation for Fedora Core 4, the 
files are at:
/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf - numbered page 
25, document page 33.
**End Note**

Version of release notes this bug refers to:


URL of bug/enhancement (change if different):


Comment 1 Karsten Wade 2005-04-06 20:40:44 UTC
included in fc4test2 relnotes, essentially as-is.

Note You need to log in before you can comment on or make changes to this bug.