From owner-freebsd-questions@FreeBSD.ORG Thu Sep 30 15:19:42 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 015CA106566C for ; Thu, 30 Sep 2010 15:19:42 +0000 (UTC) (envelope-from nvidican@m2.vidican.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 82E568FC1E for ; Thu, 30 Sep 2010 15:19:41 +0000 (UTC) Received: by wyb29 with SMTP id 29so247810wyb.13 for ; Thu, 30 Sep 2010 08:19:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.155.143 with SMTP id s15mr3196560wbw.154.1285859979773; Thu, 30 Sep 2010 08:19:39 -0700 (PDT) Sender: nvidican@m2.vidican.com Received: by 10.216.184.212 with HTTP; Thu, 30 Sep 2010 08:19:39 -0700 (PDT) X-Originating-IP: [136.1.1.105] In-Reply-To: <4CA4A4B8.6020509@gmail.com> References: <4CA4461F.6030508@gmail.com> <4CA4988E.2000200@noc.cfi.pgh.pa.us> <4CA49F10.90603@gmail.com> <4CA4A4A0.1000007@beanfield.com> <4CA4A4B8.6020509@gmail.com> Date: Thu, 30 Sep 2010 11:19:39 -0400 X-Google-Sender-Auth: 6AqUwexie9tISmOKTpo6MCabqD4 Message-ID: From: Nathan Vidican To: Kaya Saman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Brent Bloxam , freebsd-questions@freebsd.org Subject: Re: Mother board compatibility and CF card usage as main storage device for small DNS server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Sep 2010 15:19:42 -0000 MFS == memory filesystem; aka ram-disk. The problem being that on reboot, MFS looses all its contents, therefore practices like storing the 'startup' state for a filesystem in an archive (tar file works well) and mounting/copying on startup works well. Conversely, if you need to modify that startup state you can just over-write the tarfile again. On Thu, Sep 30, 2010 at 10:54 AM, Kaya Saman wrote: > On 30/09/2010 17:54, Brent Bloxam wrote: > >> Kaya Saman wrote: >> >>> From what you mention it sounds like a bad idea as the system disk will >>> have many R/W's going through it it seems as /tmp and Swap get written to >>> all the time. >>> >>> >> You can skip swap altogether and use MFS (memory filesystem) like Brian >> mentioned for other high write partitions that don't need to be persistent >> (/tmp, /var/log). See the following article on the freebsd.org website >> about using solid state storage: >> http://www.freebsd.org/doc/en/articles/solid-state/article.html >> >> Keep in mind though that Brian's setup was for slave nameservers that >> would be caching from another master. If your nameserver is acting as >> master, you'll be storing your records on flash since you need persistent >> storage, but I don't imagine those files will be write intensive. >> >> Also, if you make /var/log MFS, you'll want to have an external syslog >> server set up ;) >> > > Thanks a lot so it should be ok then! :-) > > Yeah sounds like a good setup, and also a syslog server :-)))) this is > exactly what I need in order to check my IOS logs coming from my Cisco > boxes. I had previously imagined it to be a simple tftpboot server but > sounds like it's standalone. > > That's cool! I mean I really like having logwatch mailing me all necessary > information anyway so that coupled with a syslog server should be pretty > good :-) > > Nice ideas need to do some Google'ing now as I don't know what MFS is yet > but I will.... :-D > > Cheers and best regards, > > > Kaya > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > -- Nathan Vidican nathan@vidican.com (519) 962-9987 (Canada) (313) 586-1982 (USA)