This is a list of open issues that need to be resolved for FreeBSD
5.0. If you think something should be listed here, please email
re@FreeBSD.org. This issue was discussed in detail at the Developer Summit
at Usenix.
| Issue | Status | Responsible | Description |
|---|
| 5.0 Documentation | -- | freebsd-doc |
As a minimum, we need to cover the areas where 5.x and 4.x
differ in the FAQ and Handbook. This entails marking some areas
with "This procedure is specific to 4.X. For more information for
5.x, please see foo(n)" or similar. This needs to happen quickly,
to give adequate time fo rthe translation teams to catch up. |
- | devd | Unknown | imp@FreeBSD.org | A devd
+ |
| devd | Prototype available, will be committed over weekend
+ of Oct 19-20, 2002 | imp@FreeBSD.org | A devd
prototype to manage the insertion and removal of devices (usb,
firewire, pccard, etc..) from the system. |
-
- | KDE / GNOME | Unknown after GCC upgrade | ports@FreeBSD.org |
- Working KDE and GNOME packages are a requirement for 5.0
- RELEASE. Before the recent GCC upgrade, there were problems
- building parts of KDE. |
-
-
| TrustedBSD MAC Framework system call interface |
- Perforce rwatson_macnewapi: in progress |
+ Perforce trustedbsd_mac: preparing for merge to main tree |
rwatson@FreeBSD.org |
Revised system call interface supporting extensible label access
from userland. This replaces the current temporary API which
supports only a subset of the available policies and is not
extensible at run-time. |
| TrustedBSD MAC Framework userland applications |
- Perforce trustedbsd_mac: in progress |
+ Perforce trustedbsd_mac: preparing for merge to main tree |
rwatson@FreeBSD.org |
Simple labeling applications including {get,set}[fp]mac(8),
as well as labeling during the login process. |
| TrustedBSD MAC Framework documentation |
FreeBSD documentation CVS HEAD: in progress |
chris@FreeBSD.org | User and developer documentation of
the new extensible security framework. Includes guides for live
deployment, development of policy modules, and implementation
information. |
| Port of LOMAC to TrustedBSD MAC Framework |
Perforce trustedbsd_mac: in progress |
green@FreeBSD.org |
Re-implementation of LOMAC to plug in via the MAC framework,
making it easier to deploy and support, as well as removing
code duplication in the LOMAC tree to improve maintenance cost. |
| Switch to GEOM as default storage management framework |
- FreeBSD CVS HEAD: in progress |
+ FreeBSD CVS HEAD: default now switched |
phk@FreeBSD.org | Move to using GEOM in the GENERIC
kernel as the default storage management framework, supporting
out-of-the-box use of new partiton types, data transforms (such
- as cryptographic swap protection), etc. |
+ as cryptographic swap protection), etc. Currently waiting on
+ bugs in sysinstall to be resolved relating to libdisk; many
+ nits have already been resolved (SCSI deadlocks, etc).
| gdb for sparc64 |
-- |
tmm@FreeBSD.org |
- gdb currently does not work on sparc64, but is a required feature
- for sparc64 to be a Tier 1 supported platform. |
+ gdb 5.3 now works with sparc64; gdb import required. |
| Sysinstall for sparc64 |
-- |
phk@FreeBSD.org |
Sysinstall currently doesn't understand disk labeling sufficiently
to correctly install on sparc64. Various approaches might be
taken, including adopting libwhisk as an extendable labeling
mechanism, but the work hasn't yet been done. For sparc64 to be
a Tier 1 supported platform, it needs sysinstall to work out
of the box. |
| UFS2 bootable on i386 |
In progress |
green@FreeBSD.org, phk@FreeBSD.org |
UFS2 can be successfully booted on sparc64, but on i386 the
emulated 64-bit instructions grow boot2 beyond the 8k traditionally
allocated for that boot loader. There appear to be some combination
of books in various bits of the boot loading mecahnism relating
to this (possibly including in the i386 emulated 64-bit instructions)
that must be resolved. In addition, the installation code now needs
to start leaving room for the larger boot blocks so that freshly
installed systems can be UFS2-bootable. |