With Freebsd it'll be character block devices, they depreciated mknod in favor of devfs. A good place to start is man devfs (8) and (5).
Thanks for the interesting discussion.
John Chatelle
Network & Systems Administration
MEDENT Electronic Health Records (EHR)
15 Hulbert Street
Auburn NY, 13021
315-255-1751
address@hidden
This message and any attachments may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by e-mail, and permanently delete this e-mail.
To: address@hidden
Sent: Thursday, May 31, 2012 2:56:45 PM
Subject: Re: [Jailkit-users] How to fix jailkit problems with /dev/null in FreeBSD
On 05/31/2012 09:19 AM, Jordi Moles Blanco wrote:
> Hi Olivier,
>
> thanks for you answer.
>
> Before trying such radical measure as copying /dev/null and running
> chmod 777 on it, I did try what you suggest, together with a bunch of
> other fixes that people talked about.
>
> none work for me, only the one that I explained.
copying just doesn't make sense. cp /dev/null just creates an empty
file. cp /dev/urandom just creates a file full of random. They both do
not create a device.
As I said, I know little of FreeBSD, but it sound to me that you should
try to find an expert that knows how to create devices outside /dev/ on
FreeBSD.
Olivier
--
Bluefish website http://bluefish.openoffice.nl/
Blog http://oli4444.wordpress.com/
_______________________________________________
Jailkit-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/jailkit-users