Date: Tue, 12 Aug 2014 07:28:32 +0200 From: Polytropon <freebsd@edvax.de> To: David Benfell <benfell@parts-unknown.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: operation not permitted on entropy file Message-ID: <20140812072832.da0166dc.freebsd@edvax.de> In-Reply-To: <20140812022709.GA84770@home.parts-unknown.org> References: <20140810070239.GA80734@home.parts-unknown.org> <20140810103119.GA26958@slackbox.erewhon.home> <20140810124433.da498898.freebsd@edvax.de> <20140810224038.GD24036@home.parts-unknown.org> <20140811101822.41851cc7.freebsd@edvax.de> <20140811142707.GA10186@home.parts-unknown.org> <CA%2BtpaK2RC0w7Y4etxs%2Byx59_gAURNEtB38h=sV8pEFkBRWVFWQ@mail.gmail.com> <20140811171653.b7c60e58.freebsd@edvax.de> <20140811153535.GA30506@home.parts-unknown.org> <20140811183912.ef0f20a6.freebsd@edvax.de> <20140812022709.GA84770@home.parts-unknown.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 11 Aug 2014 19:27:09 -0700, David Benfell wrote: > On Mon, Aug 11, 2014 at 06:39:12PM +0200, Polytropon wrote: > > > > > I'm not remembering if they were > > > presented as options in the install or if I selected those options. > > > (This isn't stuff I ordinarily think much about.) > > > > Probably you chose the "use the whole disk" setting. > > > This part I'm sure of. Yes, I chose the "use the whole disk" setting. > It's a server meant to be continuously accessible, so a multiple boot > choice would be ... weird. ;-) In that case, putting everything on one / partition also looks a little bit strange, but I assume the disk is more than sufficiently big enough. :-) Sidenote: Many server admins seem to prefer creating different partitions just for the case some program runs amok. What if /home gets filled? Or /tmp? Or /var? In this case, the _whole_ system would be affected... > And it had been too long since I'd last run FreeBSD as a server to be > sure of how I would allocate partitions anyway. (In my experience, the > sizes people tell you are never right *for* *you* and I'm not sure > it's really an advantage to partition up a disk this way, anyway.) There actually are advantages, but the case is: You hope that you never need them. Still size "calculation" is probably nothing more than a WAG, and if everything runs fine during the life span of the server, you'll be happy. It's actually hard to say how big partitions should be when you don't know what services you will run and _how_ they will run (amount of users, of transactions, of data- bases, of logfiles and so on). Even with a big disk, you can say you made all partitions "big enough" and still hit a limit in three years. > Having gone through the fsck -fy already, I don't think I can recover > /tmp/fsck.txt--I just looked, and I had just enabled /tmp cleanup, so, > no, it isn't still there. The text is kept in the console buffer until reboot. Of course saving something to /tmp when you have enabled a cleanup for /tmp isn't optimum. In this case, choices like /root/fsck.txt or even /fsck.txt (for temporary storage) would have been okay. For the next time: You can use mdconfig to temporarily allocate a RAM disk, then use script to record the whole console session (including fsck output), afterwards run "mount -a" and copy the log fron the RAM disk to a more permanent place. Just in case. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140812072832.da0166dc.freebsd>