In message [EMAIL PROTECTED], Warner Losh writes:
In message 18334.980748975@critter Poul-Henning Kamp writes:
: 1. Say I want to use DEVFS, what should I change?
:
: Nothing. Just add DEVFS to your kernel config file.
So it updates /dev all by itself? What if I want dev nodes elsewhere
in
Once we have an extensible facility for mount options, you will be
able to say:
mount -t devfs devfs /home/jail/dev
( cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails )
mount -u -o nonewdev /home/jail/dev
Couldn't you also do "mount -t devfs -o nonewdev devfs
In message [EMAIL PROTECTED], Jordan Hubbard writes:
Once we have an extensible facility for mount options, you will be
able to say:
mount -t devfs devfs /home/jail/dev
( cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails )
mount -u -o nonewdev /home/jail/dev
Couldn't
In message [EMAIL PROTECTED] Jordan Hubbard writes:
: Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev"
: and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It
: seems that "read my lips: no new devices" should be an option you can
: set from the very initial
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Jordan Hubbard writes:
: Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev"
: and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It
: seems that "read my lips: no new devices"
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Warner Losh write
s:
In message [EMAIL PROTECTED] Jordan Hubbard writes:
: Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev"
: and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It
: seems that
I have seriously been thinking about some way to say something like
mount -t devfs -o jailset /home/jail/dev
but an elegant implementation evades me at this moment.
As bizzare as it sounds, I like Julian's hack for populating this stuff...
ie: use a hard link to propagate nodes to the
In message [EMAIL PROTECTED] Peter Wemm writes:
: As bizzare as it sounds, I like Julian's hack for populating this stuff...
: ie: use a hard link to propagate nodes to the jailed /dev.
:
: eg: mount -t devfs -o empty /home/jail/dev
: ln /dev/null /home/jail/dev/null
: ln /dev/zero
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Peter Wemm writes:
: As bizzare as it sounds, I like Julian's hack for populating this stuff...
: ie: use a hard link to propagate nodes to the jailed /dev.
:
: eg: mount -t devfs -o empty /home/jail/dev
: ln
In message [EMAIL PROTECTED], Warner Losh writes:
In message 14760.981228917@critter Poul-Henning Kamp writes:
: In message [EMAIL PROTECTED], Warner Losh writes:
: In message [EMAIL PROTECTED] Peter Wemm writes:
: : As bizzare as it sounds, I like Julian's hack for populating this stuff...
: :
In message 14918.981230622@critter Poul-Henning Kamp writes:
: Doing straight symlinks would not work.
OK.
The other idea that I had was a cpdev. It would be like a templated
mknod. It would stat the first argument and do a mknod with the
st_rdev from the stat, eg:
#include err.h
#include
In message [EMAIL PROTECTED], Warner Losh writes:
In message 14918.981230622@critter Poul-Henning Kamp writes:
: Doing straight symlinks would not work.
OK.
The other idea that I had was a cpdev. It would be like a templated
mknod. It would stat the first argument and do a mknod with the
On Sat, Feb 03, 2001 at 12:32:50PM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Peter Wemm writes:
: As bizzare as it sounds, I like Julian's hack for populating this stuff...
: ie: use a hard link to propagate nodes to the jailed /dev.
:
: eg: mount -t devfs -o empty
In message 18334.980748975@critter Poul-Henning Kamp writes:
: 1. Say I want to use DEVFS, what should I change?
:
: Nothing. Just add DEVFS to your kernel config file.
So it updates /dev all by itself? What if I want dev nodes elsewhere
in the tree, say for a jail?
Warner
To
In message [EMAIL PROTECTED] Julian Elischer writes:
: you can't.. what is the major number?
:
: You don't know because they will be dynamically assigned.
: Only the kernel knows.
: Eventually, major numbers may go away entirely, (or just be a
: comlpetely random meaningless number, present
On Sun, Jan 28, 2001 at 10:19:34PM -0800, John Baldwin wrote:
On 29-Jan-01 John Indra wrote:
2. If something change to the source tree's MAKEDEV, what should I do?
Nothing. With DEVFS, each driver in the kernel creates its own
entries automatically, so MAKEDEV isn't used.
Hrm... what
In message [EMAIL PROTECTED], Steve Ames writes:
On Sun, Jan 28, 2001 at 10:19:34PM -0800, John Baldwin wrote:
On 29-Jan-01 John Indra wrote:
2. If something change to the source tree's MAKEDEV, what should I do?
Nothing. With DEVFS, each driver in the kernel creates its own
entries
On Monday, 29 January 2001 at 16:10:24 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Steve Ames writes:
On Sun, Jan 28, 2001 at 10:19:34PM -0800, John Baldwin wrote:
On 29-Jan-01 John Indra wrote:
2. If something change to the source tree's MAKEDEV, what should I do?
On Tue, 30 Jan 2001, Greg Lehey wrote:
You can create symlinks in /dev, you cannot mknod there.
What is the reason for this? How does a program or script know
whether the system is running DEVFS or not?
I don't see any good reason why this can't be supported. We may
talk about
On Tuesday, 30 January 2001 at 8:37:56 +0600, Boris Popov wrote:
On Tue, 30 Jan 2001, Greg Lehey wrote:
You can create symlinks in /dev, you cannot mknod there.
What is the reason for this? How does a program or script know
whether the system is running DEVFS or not?
I don't see
In message [EMAIL PROTECTED], Greg Lehey writes:
You can create symlinks in /dev, you cannot mknod there.
What is the reason for this? How does a program or script know
whether the system is running DEVFS or not?
The reson for not creating device nodes is that you don't have
all the
In message [EMAIL PROTECTED], Boris Popov
writes:
On Tue, 30 Jan 2001, Greg Lehey wrote:
You can create symlinks in /dev, you cannot mknod there.
What is the reason for this? How does a program or script know
whether the system is running DEVFS or not?
I don't see any good reason
Boris Popov wrote:
On Tue, 30 Jan 2001, Greg Lehey wrote:
You can create symlinks in /dev, you cannot mknod there.
What is the reason for this? How does a program or script know
whether the system is running DEVFS or not?
I don't see any good reason why this can't be
Greg Lehey wrote:
On Tuesday, 30 January 2001 at 8:37:56 +0600, Boris Popov wrote:
On Tue, 30 Jan 2001, Greg Lehey wrote:
You can create symlinks in /dev, you cannot mknod there.
What is the reason for this? How does a program or script know
whether the system is running DEVFS or
In message [EMAIL PROTECTED], John Indra writes:
I noticed that DEVFS has been the default in GENERIC kernel. I have been
-CURRENT tracker for the past couple of months and things like DEVFS is
still new to me. Thus, a couple of questions arise and I am very glad if
someone want to explain it to
On 29-Jan-01 John Indra wrote:
I noticed that DEVFS has been the default in GENERIC kernel. I have been
-CURRENT tracker for the past couple of months and things like DEVFS is
still new to me. Thus, a couple of questions arise and I am very glad if
someone want to explain it to me, or maybe
26 matches
Mail list logo
