Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Mar 2003 22:26:08 +0100
From:      Andy <andy-freebsd@splashground.de>
To:        Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: MAKEDEV lost in 5.0-CURRENT?
Message-ID:  <20030313212608.GA15179@splashground.de>
In-Reply-To: <1678.1047555924@critter.freebsd.dk>
References:  <20030313111027.GA13250@splashground.de> <1678.1047555924@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 13, 2003 at 12:45:24PM +0100, Poul-Henning Kamp wrote:
> In message <20030313111027.GA13250@splashground.de>, Andy writes:
> >On Wed, Mar 12, 2003 at 12:18:08PM -0500, Hiten Pandya wrote:
[...]
> >On 5.0-RELEASE-p4 I have
> >/usr/src/etc/MAKEDEV
> >and i use it for making the devices in jails.
> >Is there a jail devfs or is the way described in the
> >jail(8) man page still the right(tm) one?
> 
> See devfs(8)

After reading it it seems the answer is "no"
there is no special jail devfs,
but you can create your own rules for a jail.

More informative on this subject was
/usr/share/doc/papers/devfs.ascii.gz
which i quote here:
----8<----
These behaviours will be controlled with mount options, but these have not yet
been implemented because FreeBSD has run out of bitmap flags for mount
options, and a new unlimited mount option implementation is still not in place
at the time of writing.

One mount option ``jaildevfs'', will restrict the contents of the DEVFS mount-
point to the ``normal set'' of devices for a jail and automatically hide all
future devices and make it impossible for a jailed root to un-hide hidden
entries while letting an un-jailed root do so.
---->8----

OK. What a pity.

So we have to create our own, based on "MAKEDEV jail" maybe:

100 path * hide
200 path tty* unhide
300 path random unhide
400 path zero unhide
500 path null unhide
600 path fd/* unhide
700 path mdctl unhide
800 path ptyp* unhide

Now the problem is ptyp* and mdctl
don't show up, even so they got unhidden.

Also symlinking seems to require special actions:

$ ln -s null mem
$ echo mem*
mem mem
$ ls -la mem*
ls: mem: No such file or directory
ls: mem: No such file or directory

Obviously some magick happens with hidden devices,
so how can you make those links or don't we need them anymore?


Andy

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030313212608.GA15179>