Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Nov 2004 18:19:57 +0100
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        "Daniel Eriksson" <daniel_k_eriksson@telia.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: DEVFS problems 
Message-ID:  <52421.1100798397@critter.freebsd.dk>
In-Reply-To: Your message of "Thu, 18 Nov 2004 18:18:51 +0100." <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAA9RfmA9mmNEKtShqvfgVooQEAAAAA@telia.com> 

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
In message <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1P
dsKAAAAQAAAA9RfmA9mmNEKtShqvfgVooQEAAAAA@telia.com>, "Daniel Eriksson" writes:
>
>With a system compiled from sources from yesterday (2004.11.17.12.00.00),
>hiding and unhiding devfs devices does not work.
>
>Normally I do something like this to only expose the devices I really want
>in the chroot/jail environment:
>
>mount_devfs devfs /some/path/dev
>devfs -m /some/path/dev rule apply hide
>devfs -m /some/path/dev rule apply path null unhide
>devfs -m /some/path/dev rule apply path zero unhide
>devfs -m /some/path/dev rule apply path random unhide
>
>With recent CURRENT, the devfs rules results in this error message:
>devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device

My bug, just fixed a minute ago.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?52421.1100798397>