FreeBSD Recent Entries
While installing Apache 2.2.21 in /usr/local/www/apache22, an error "/usr/local/build-1/libtool: not found" occurred.
You just need deinstall apr1, and reinstall apache22 again.
#pkgdb -F; portsclean -CDD; portsnap fetch update
# cd /usr/ports/devel/apr1
# make deinstall clean
# cd /usr/ports/www/apache22
# make install clean
MacOSX 10.7 Lion doesn't support old version of netatalk (2.0.x?). Lion won't mount older version of netatalk volume and an error occurred.
It needs to be updated to the latest version.
After the update, if CNID DB error occurred, ' cnid_metad_enable="YES" ' must be set in /etc/rc.conf, then restarting netatalk fixes this problem.
An error of FreeBSD on VMware Fusion "lnc0: Missed packet -- no receive buffer" was sometimes annoying me.
When bunch of this error stacks, virtual machine stacks too.After upgrading Fusion 3, it seems to run more stable, but this error still occurs.
I had been looking for solution to resolve this problem for several months and I found two solutions. The one is installing VMware tools and using vmxnet for Network interface, and another is editing .vmx file and add alternate NIC statement (e1000) in it.
VMware tools for fusion supports ony FreeBSD 6.3 and 7.0. Unfortunatelly I am using 6.2, so my environment was rejected by its installer.
I decieded to change NIC to e1000, and as a result it runs without problems.
I guess noone runs two FreeBSD on VMWare Fusion on Mac mini as web and mail server simultaneously with Apple Share as file server, Printer Share for printer server and Fax Modem for fax server.
I added Apple External Modem (Apple USB Modem) recently to unify VMware server, file, fax and printer server in a Mac mini.
But after that, USB was going to be dead and MacOSX was stacked while connecting Apple External Modem.
I guess it will happen even if the guest OS is Windows or Linux.
After installing SPAMASSASSIN, an error occured on its startup.
The message is
# error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/BSDPAN /usr/local/lib/perl5/site_perl/5.8.8/mach /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.8/mach /usr/local/lib/perl5/5.8.8) at (eval 19) line 2.
You can fix this Syslog.pm bug by commenting out the line in Syslog.pm (I edited "/usr/local/lib/perl5/5.8.8/mach/Sys/Syslog.pm" on my system/FreeBSD6.2.)
# use EventLog on Win32
my $is_Win32 = $^O =~ /Win32/i;
#eval "use Sys::Syslog::Win32"; # commented out this line