FreeBSD ports tree (read-only mirror)
88fb181c88
FreeBSD's writev(2) implementation is rather unreliable when large number of vectors is submitted - it returns EINVAL despite the fact that all arguments are pretty valid. This caused serious problems with GNOME's oaf and prevented Nautilus from working properly. The problem disappeared when I've replaced writev(2) call with appropriate loop based around ordinary write(2). Perhaps this should be investigated and the real source of the problem fixed instead, but I do not have a time for this right now. For those who interested I'm ready to provide a step-by step instruction on how to reproduce the bug. Special thanks to: andersca @ nautilus#irc.gnome.org |
||
---|---|---|
accessibility/atk | ||
arabic | ||
archivers | ||
astro | ||
audio | ||
benchmarks | ||
biology | ||
cad | ||
chinese | ||
comms | ||
converters | ||
databases | ||
deskutils | ||
devel | ||
dns | ||
editors | ||
emulators | ||
finance | ||
french | ||
ftp | ||
games | ||
german | ||
graphics | ||
hebrew | ||
hungarian | ||
irc | ||
japanese | ||
java | ||
korean | ||
lang | ||
math | ||
mbone | ||
misc | ||
Mk | ||
multimedia | ||
net | ||
net-im | ||
net-mgmt | ||
net-p2p | ||
news | ||
palm | ||
picobsd | ||
polish | ||
ports-mgmt | ||
portuguese | ||
russian | ||
science | ||
security | ||
shells | ||
sysutils | ||
Templates | ||
textproc | ||
Tools | ||
ukrainian | ||
vietnamese | ||
www | ||
x11 | ||
x11-clocks | ||
x11-fm | ||
x11-fonts | ||
x11-servers | ||
x11-themes | ||
x11-toolkits | ||
x11-wm | ||
.cvsignore | ||
INDEX | ||
LEGAL | ||
Makefile | ||
README |
This is the FreeBSD Ports Collection. For an easy to use WEB-based interface to it, please see: http://www.freebsd.org/ports For general information on the ports collection, please see the FreeBSD Handbook which is available from: file://localhost/usr/share/doc/handbook/handbook.html (if you installed the doc distribution on your machine) Or: http://www.freebsd.org/handbook/handbook.html for the latest official version from FreeBSD-current. The section "The Ports Collection" will tell you how to use the ports and packages and the "Porting Applications" section describes how one can contribute to the ports collection. If you would like to search for a given port, you can do so easily by saying: make search key="<keyword>" Which will generate a list of all ports matching <keyword>. NOTE: This tree can GROW significantly in size during normal usage! The distribution tar files can and do accumulate in /usr/ports/distfiles, and the individual ports will also use up lots of space in their work subdirectories unless you remember to "make clean" after you're done building a given port. /usr/ports/distfiles can also be periodically cleaned without ill-effect, though if you don't have the original distribution tarball(s) for something on CDROM then you will need to pull it all over your network connection again if you ever try to build the associated port.