operation not permitted on entropy file

Polytropon freebsd at edvax.de
Tue Aug 12 05:28:36 UTC 2014

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.

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

More information about the freebsd-questions mailing list