Technical contact: &a.alfred;
-Create the autofs file system from a specification. - Kernel transport and interaction with the "amd" automounter - needs to be completed.
-Adam Martin did work - on AutoFS for FreeBSD as part of Google Summer of Code 2006. It - is not yet ready for prime time, but he is working on getting it - commit ready.
-Requirements:
-Technical contact: &a.jwd;
-Patches: http://people.FreeBSD.org/~jwd/magiclinks.tgz
-Experimental patches exist against 4-STABLE, though the DragonFly - implementation using the setvar utility should be examined (interesting - files in the DragonFly CVS: sys/kern/init_sysent.c, sys/kern/kern_varsym.c, - sys/kern/syscalls.c, sys/kern/syscalls.master, sys/kern/vfs_lookup.c, - sys/sys/syscall-hide.h, sys/sys/syscall.h, sys/sys/syscall.mk, - sys/sys/sysproto.h, sys/sys/sysunion.h, bin/varsym/varsym.1, - bin/varsym/varsym.c).
-Andrey V. Elsukov has begun porting - this to FreeBSD, and some initial patches for CURRENT can be found here and here. -
-Requirements:
-Fix MDFS lockups when using async operation modes. - -
Technical contact: &a.rwatson;
-Implement a simple read-only &man.tar.1; file system that could be used as - a root file system for network booting, etc. Right now, we mount UFS from an - mdimage, but using &man.tar.1; images avoids having to build UFS images with - memory disks etc.
-Eric Anderson has a working version. He is finishing - up some bug testing/fixing and a few features.
-Requirements:
-Technical contact: - -
Technical contact: &a.pjd;
-References: What is ZFS?, - Porting - ZFS
-
OpenSolaris™ gained support for a new file system called ZFS (Zettabyte - File System) as of build 27a. ZFS is a new approach to file - system design and data management, and includes several interesting features - such as transactional semantics, snapshots and good scalability. &a.pjd; - has created - a largely functional - work-in-progress port to FreeBSD.
-Requirements:
-Technical contact: &a.scottl;
-&a.scottl; has been working on this for a while, and he has patches in - Perforce.
-Requirements:
-The current kernel statistics do not know how to calculate the CPU usage @@ -503,40 +382,6 @@
Port DragonFly's MMX/XMM optimized memcpy/bcopy/bzero/copyin/copyout code - (this includes an FPU subsystem overhaul). Interesting files in the - DragonFly CVS are sys/i386/gnu/fpemul/fpu_system.h, - sys/i386/i386/bcopy.s, sys/i386/i386/genassym.c, sys/i386/i386/globals.s, - sys/i386/i386/machdep.c, sys/i386/i386/math_emu.h, - sys/i386/i386/mp_machdep.c, sys/i386/i386/pmap.c, sys/i386/i386/support.s, - sys/i386/i386/swtch.s, sys/i386/i386/trap.c, sys/i386/i386/vm86bios.s, - sys/i386/i386/vm_machdep.c, sys/i386/include/asmacros.h, - sys/i386/include/globaldata.h, sys/i386/include/md_var.h, - sys/i386/include/npx.h, sys/i386/include/pcb.h, sys/i386/include/thread.h - sys/i386/isa/npx.c, sys/i386/i386/bcopy.s and sys/i386/i386/bzero.s. A more - detailed writeup can be found in this compressed - file. This includes a mail from Matthew Dillon with suggestions on how - to do this in FreeBSD (including a small benchmark which shows 35%-55% speed - improvement for at least those benchmarks).
-Attilio Rao has almost completed - this work, but he would like to receive more feedback. In particular, a - thorough performance evaluation is required to determine whether these - improvements are purely theoretical or practical
-Requirements:
-Technical contact: - -
FreeBSD provides Linux binary compatibility through a Linux system call - table that is invoked when Linux ELF binaries are executed. The - implementation on amd64 machines only provides support for 32bit (x86) - executables. This needs to be coordinated with the emulation mailinglist regarding - the userland part of the linuxulator.
-Requirements:
-Technical contact: - -
Technical contact: &a.bruno;
-Process checkpointing allows to migrate some processes to other machines or - to let some processes "survive" a reboot (subject to some constraints). - Interesting files in the DragonFly CVS repository are sys/sys/ckpt.h, - sys/checkpt/* and sys/kern/imgact_elf.c; however, this implementation is - both highly experimental and incomplete.
-Requirements:
-Technical contact: - -
Technical contact: Emulation mailing list, &a.netchild;, Roman Divacky
-FreeBSD provides Linux binary compatibility through a Linux system call - table that is invoked when Linux ELF binaries are executed. This - implementation should be compared with an up-to-date Linux kernel so that - important missing syscalls can be added to ensure that all mainstream - applications continue to work on FreeBSD. More information about the current - status can be obtained from the wiki page.
-Roman Divacky had - a 2006 Summer of Code Project on this topic, and has continued his work - following the end of the summer project.
-Requirements:
-Not every airline allows to use radio transmitters like WLAN-NIC's in - airplanes (yet). The goal of this entry is to provide an entry in the - loader which prohibits drivers for devices which transmit radio signals - to attach to the device. One way of providing this functionality would - be to add a menu entry to the loader which sets a "flight mode" loader - tunable which would have to be queried by every driver which is able to - transmit radio signals to decide if the normal operation is allowed or - if the device has to be disabled. The loader-menu should be able to - detect this tunable in loader.conf and indicate which way of booting is - the current default (in case the user adds it there to be on the safe - side in the airplane).
-Patches are available for testing here.
-Requirements:
-Technical contact: - -
Technical contact: Fredrik Lindberg
-URL: Zeroconf on - FreeBSD NetBSD zeroconf - SoC project
-Add Zeroconf (Rendezvous/Bonjour) support to FreeBSD.
-Requirements:
-Since LDAP is very popular today, it would be beneficial to have - NSS-LDAP support available by default. The license of the NSS - LDAP module should however be investigated first.
-Benefits:
-Michael Bushkov is working on - importing NSS LDAP as part of Google Summer of Code 2006.
-Requirements:
-Technical contact: - -
Currently HESIOD is build statically into libc. Since LDAP is more - popular today, it is not necessary to provide this name service to - every consumer of libc by default.
-Benefits:
-Michael Bushkov is working on - moving HESIOD out of libc as part of Google Summer of Code 2006.
-Requirements:
-Currently NIS/YP is build statically into libc. Since LDAP is more - popular today, it is not necessary to provide this name service to - every consumer of libc by default.
-Benefits:
-Michael Bushkov is working on - moving NIS/YP out of libc as part of Google Summer of Code 2006.
-Requirements:
-Currently FreeBSD supports only single byte collation. Multibyte