and forth. This would allow me to put the 2200 in a real box with serial
port and stuff. While here, a card with proper monitor support would help
as well. Thanks.
looks, at least not for me):
- Remove <p></p> which are removed by tidy anyway.
- Remove <b> inside <h?> tags since CSS should handle layout, and our
current CSS makes all the <h?> tags bold anyway.
while. Currently only one of the systems is up and it hasn't been
updated in 2+ years.
If rtp systems come back the page can easily be resurrected, but for now
it's just more confusing having the page around.
projects (based on discussions with netchild and rwatson):
- AutoFS: Adam Martin has been working on this since Google SoC 2006 and it
looks like we will see an implementation announced soon.
- Magic symlinks: Several implementations exists, so we don't need more
people looking at this right now.
- Tarfs: Eric Anderson is already working on this in p4.
- ZFS: No need to have this here, pjd has been hacking on ZFS for FreeBSD
for quite some time now.
- Cam layer locking: My understanding is that scottl is about to commit
his locking work to CVS soon.
- FPU subsystem overhaul: Not suitable as a Google SoC project.
- Linuxulator: We already have several committers (netchild, jkim, kib)
and past SoC students (Roman Divacky) working on this, so remove it
from the list.
- Process Checkpointing: Not suitable as a Google SoC project.
- Flight mode: Does not belong on the list. benjsc has implemented
this functionality (not yet committed though).
- Zeroconf: Already available on the Networking wiki page.
- NSS/LDAP/HESIOD/NIS/YP: Michael Bushkov did this as part of
Google SoC 2006 so this isn't suitable for Google SoC 2007. Not
committed yet.
More to come...
can help pjd with here, but they need to contact him first. We need to
decide if this item should still be on the TODO list.
Note that jb's work on dtrace is a significant work-in-progress so to
contact him. Does this need to be a todo item?
Note that the "use floating point in kernel rah rah rah" item requires
experimental validation -- the task isn't to hack code, but to decide if
the hacked code was a good idea. Does this need to be a todo item?
Note that the DFBSD process checkpointing facility is both experimental and
incomplete. Another "Don't just port this" sort of thing. Do we want this
to be a todo item?
In the Linuxulator update task, note that Roman is doing this. Do we need
this todo item anymore?
Add fine-grained locking to syscons task. Some of the items in this idea
are silly.
Note that the PXE HTTP idea requires someone to implement TCP in pxeboot,
add networking experience on the requirements list.
Add gnn to the TCP/IP regression suite idea, as he's working on such a
thing.
Make it clear in the distributed audit daemon task that portable C coding
is required.
"Skip section navigation" and thus add the missing space between them
PR: www/105026
Submitted by: Rudolf Cejka <cejkar@fit.vutbr.cz>
Approved by: keramida (mentor)
with the press page and easier to read, as well
PR: www/105527
Submitted by: Rudolf Cejka <cejkar@fit.vutbr.cz>
Approved by: keramida (mentor)
Discussed on: freebsd-doc, freebsd-www
