Hi,
Regarding vn subsystem: since about 4.6-RELEASE vnconfig -d no longer disables /dev/vn
entry.
That means that...
vnconfig -e /dev/vnsomething file
vnconfig -d /dev/vnsomething
vnconfig -e /dev/vnsomething anotherfile
...gives vnconfig: VNIOCATTACH: Devise busy...
and only kldunload vn
Hi,
Hello
Regarding vn subsystem: since about 4.6-RELEASE vnconfig -d no longer disables
/dev/vn entry.
That means that...
vnconfig -e /dev/vnsomething file
vnconfig -d /dev/vnsomething
vnconfig -e /dev/vnsomething anotherfile
gives vnconfig: VNIOCATTACH: Devise busy
On Fri, Nov 29, 2002 at 09:20:52AM +0300, Fred Souza wrote:
Regarding vn subsystem: since about 4.6-RELEASE vnconfig -d no longer disables
/dev/vn entry.
[]
Actually, it does disable it (or at least, using the same words from
the manpage, if it's possible). Your problem most likely
That's right, thank you! But why this simple detail isn't in the manpage??
I agree it's not crystal clear there, but somehow it's mentioned. The
manpages says that vnconfig configures and enables vnode pseudo disk
devices, and that the first form of the command will associate the
special
On Fri, 29 Nov 2002, Yury Tarasievich wrote:
Hi,
Regarding vn subsystem: since about 4.6-RELEASE vnconfig -d no longer disables
/dev/vn entry.
That means that...
vnconfig -e /dev/vnsomething file
vnconfig -d /dev/vnsomething
^
Don't you mean -u?
--
Doug White
On Thu, Feb 28, 2002 at 02:32:03PM -0800, Patrick Thomas wrote:
thank you - I am glad to see that this is a good way of doing things Two
quick items:
1 How do I give each jail a 'proc' filesystem in its /proc using this
configuration ?
mount -t procfs proc
thank you - I am glad to see that this is a good way of doing things. Two
quick items:
1. How do I give each jail a 'proc' filesystem in its /proc using this
configuration ?
2. Is there any downside to this whatsoever ? This seems infinitely
better than a new partition for each jail, so was
one other thing:
How many mount points (jails, in this case) can I run ? I see that there
are 8 existing vn0X device files in /dev - can I just create more of them
using MAKEDEV (or mknod) and keep going ?
What is the maximum ? 256 ?
also, do I need to alter the kernel to support more vn0X
Patrick Thomas wrote:
How many mount points (jails, in this case) can I run ? I see that there
are 8 existing vn0X device files in /dev - can I just create more of them
using MAKEDEV (or mknod) and keep going ?
What is the maximum ? 256 ?
Depends. Expect 256 to be available in all
partitions seems the
safest route.
But, what about using vnconfig to create files of fixed sizes and then
mounting them?
Is this reasonable ?
Is there a limit to how many vnconfig files I can mount as filesystems ?
Is there a way to mount a directory _inside_ a vnconfig mount as a 'proc'
filesystem
At 2002-02-27T20:49:18Z, Patrick Thomas [EMAIL PROTECTED] writes:
I would like to put a large number of jails (16 or 20) on a server for
testing purposes.
I have two options so far: create 16 or 20 partitions OR just put them all
in one partition, but the downside of that is that then I
On Wed, Feb 27, 2002 at 03:03:11PM -0600, Kirk Strauser wrote:
At 2002-02-27T20:49:18Z, Patrick Thomas [EMAIL PROTECTED] writes:
I would like to put a large number of jails (16 or 20) on a server for
testing purposes.
I have two options so far: create 16 or 20 partitions OR just put
Hey.
OpenBSD suports an option (-k) to vnconfig(8) that causes it to prompt
for a key which is used to encrypt whatever passes through the device. Are
there plans to port this functionality in to FreeBSD? Thanks.
--
--Spike Gronim
[EMAIL PROTECTED]
Oh yes
In message [EMAIL PROTECTED], Spike Gronim writes:
Hey.
OpenBSD suports an option (-k) to vnconfig(8) that causes it to prompt
for a key which is used to encrypt whatever passes through the device. Are
there plans to port this functionality in to FreeBSD? Thanks.
Yes, but not using
On Wed, Aug 01, 2001 at 11:35:32AM +, Julian Stacey wrote:
So something is momentarily making the image unreadable.
Should FreeBSD [mount/kernel ?] be changed to avoid denying access ?
When you do a mount it automatically HUP's mountd which then
re-exports NFS filesystems. I suspect what
In message [EMAIL PROTECTED], David Malone writes:
When you do a mount it automatically HUP's mountd which then
re-exports NFS filesystems. I suspect what is happening is that
the the filesystem mountlist is being cleared for a moment and that
is upsetting the cp.
Yes, the mountd-kernel
David Malone wrote:
On Wed, Aug 01, 2001 at 11:35:32AM +, Julian Stacey wrote:
So something is momentarily making the image unreadable.
Should FreeBSD [mount/kernel ?] be changed to avoid denying access ?
When you do a mount it automatically HUP's mountd which then
re-exports NFS
I have successfully used vnconfig to add swap file and mount disk image
files. However, I am still not sure about the following two things:
(1) What does the count in "pseudo-device vn count" stand for? My guess
is that if it is 2, then we can use /dev/vn0x and /dev/vn1x. If it is
I have successfully used vnconfig to add swap file and mount disk image
files. However, I am still not sure about the following two things:
(1) What does the count in pseudo-device vn count stand for? My guess
is that if it is 2, then we can use /dev/vn0x and /dev/vn1x. If it is 1,
then we can
19 matches
Mail list logo
