running FreeBSD on Mac OS X made easy
i just realised, that there’s a port! you just need to install xhyve… and that’s it. you don’t need VMware or VirtualBox anymore. have a great virtualization!
i just realised, that there’s a port! you just need to install xhyve… and that’s it. you don’t need VMware or VirtualBox anymore. have a great virtualization!
…if everyone is trying to make your life harder. couple weeks ago I refreshed my private email server on FreeBSD. for some time spam levels were raising and I had to do something about it. old spamassassin was not handling it accurately enough anymore. enter spamd from OpenBSD. current postfix has built in greylisting server that’s working quite well. for my installation I tuned it a bit, by extending period of time that has to pass from last delivery attempt (to 1200 seconds, which is 20 minutes): ...
my old poor LSI 9211-8i RAID card, that was powering my cache NAS server, decided to die. my spare 9261-8i, to my complete suprise, was halting FreeNAS at the boot… and i was not able initially to troubleshoot the problem. it was dropping mysterious timeout errors: mfi0: COMMAND 0xfffffe000150dc08 TIMEOUT AFTER 59 SECONDS mfi0: COMMAND 0xfffffe000150dc90 TIMEOUT AFTER 59 SECONDS mfi0: COMMAND 0xfffffe000150dc18 TIMEOUT AFTER 59 SECONDS run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config my google-fu immediately shown me some potential solutions, but they were totally random nad kind of voodoo-magic (‘disable Firewire controller!’, ‘disable ATA controller!’… and so on). also, i tried to upgrade firmware version, downgrade it… the problem was still there. ...
FreeNAS is special edition of tuned-up FreeBSD, with GUI available over WWW to enable easy setup and maintenance. i had to migrate recently my old Synology 1815+ thanks to well known Intel SNAFU with Atom CPUs. interestingly enough, even Synology own service department declined to RMA the NAS, without even discussing the situation. so i managed to setup quickly 12x 3.5" bay server. i had five 3.5" 8TB HDDs from Synology that i wanted to rescue data from. the server itself is kind of old one - but solid. it’s a dual Intel L5100 series chassis (with sadly one CPU only), 64GB of RAM, LSI/Avago RAID card and Intel twin 10GE NIC. for ‘fast & dirty’ hack it was more than enough. ...
getting grip of reality after moving is not easy in some situations. when everything is still fresh, and on the other hand - so well known :) you know obviously that stopgaps tend to last for years after they were put “just for a moment”? my december cleaning started with true horror of moving my emails server from FreeBSD 9-STABLE (just EoLed) to 11-STABLE. traditional make buildworld; make kernel KERNCONF=server; mergemaster -FiU; make installworld; reboot didn’t work, but (WTF?!) the same sources were able to give me working build when i did make buildworld buildkernel; make installkernel and so on. for some reason, with the first sequence - cam.c dropped multiple warnings treated as error. and build failed. ...
i’m just finishing upgrading my different servers from FreeBSD 9 to FreeBSD 10.1-STABLE. …and i just realized, that my FreeBSD adventure started around 4.1 (well, i may have got older 3.4 CDs, but didn’t install it then yet). and it was 14 years ago today. it was just after i, like thousands of linux users around the world, tried to upgrade glibc libs on the fly on my beloved (at that time and today) Slackware installation. ...
some time ago I changed my BIND at home to Unbound, due to the change of the default DNS server in FreeBSD (yes, I do have my own DNS server at home, and it serves all local queries). actually, I have four right now ;) back in BIND times, i used a lot of scripts to add zones containing 127.0.0.1 for domains serving ads. after switching to Unbound - i forgot about it completely. ...
don’t start your php upgrade at 2:40 in the morning. as you’ll stay awake until 5am :)
interesting enhancement to transport traffic in HTTP sessions proposed by Google is starting to gain popularity and traction. while i don’t use Chrome browser, in Firefox starting from version 11 you can turn the protocol on (about:config -> network.http.spdy.enable=true). on the server side you should run mod_spdy if you’re running Apache server. it also makes sense to install Firefox extension signalling SPDY work. the end effect? SPDY gets the traffic faster (usually), as multiple sessions are initiated at the same time. ...
FreeBSD 9.0 did an unannounced appearance lately. it introduces a bunch of different features, two of which are of great interest to me. firstly, we can select different mechanisms to fight traffic congestion for TCP. to do that, you need to change sysctl net.inet.tcp.cc.algorithm from the list available under net.inet.tcp.cc.available. NewRENO, the default one, works quite OK, but in some specific configurations you can select others and check if they’d behave better. ...