This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 252180

Summary: [DOCUMENTATION] Updated information about Fedora Directory Server
Product: [Fedora] Fedora Reporter: Răzvan Sandu <razvan.sandu>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: dennis
Target Milestone: ---Keywords: screened
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-14 12:22:14 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Răzvan Sandu 2007-08-14 11:21:43 EDT
Description of problem:


Despite the fact that fedora-ds-base-1.1.0 is present in Fedora repository,
there are many missing pieces of information on that prevents a clean, problem-free

Missing information prevents practical installation; small number of
installations means less testing and less contributions from the final users.

To make FDS practically usable on Fedora 7, please provide on the site minimal
information about:

- installation instructions for *recent* versions of Fedora (Fedora 7 or 8 test 1);

- basic configuration of FDS after RPM installation (instructions must match the
actual file layout installed by RPM)

- a clear and updated list of actual prebuilt rpm packages that compose FDS, in
the current version

- instructions how to install a *recent* version of Java - why all information
refer to Sun or IBM java 1.4.2 or 5, when the most recent version is 6 ?

- instructions of how to install and use recent Java RPMs for Fedora 7 (maybe
from or

- an explicit roadmap and possible timelines for future development


Version-Release number of selected component (if applicable):

How reproducible:

Actual results:
There are missing pieces of information on,
preventing practical RPM installation of FDS without ugly manual hacking, even
for minimal usage and testing.

A clear and supported procedure of installing Java 6 on F7 is not given.

Information on is very old (refers to many
obsoleted pieces of software or procedures).

Expected results:
At least minimal installation (supported) procedures should be provided - about
latest Java and FDS itself - to allow practical installations, from prebuilt
RPM, on the latest version of Fedora.

Recommended Java installation procedure should not interfere with other programs
installed on the system, that use Java.

The final goal is to easily obtain a fully functional FDS, at least for testing
and practical minimal usage, from recent prebuilt RPMs.
Comment 1 Rich Megginson 2008-01-14 12:22:14 EST
I think all of your issues have been addressed.  Please refer to the Fedora DS
web site for the latest information about Fedora DS 1.1.