Re: devfs ruleset 4 (jails)

On Wed, 5 Apr 2006, John Baldwin wrote:

> On Wednesday 05 April 2006 10:27, Raphael H. Becker wrote:
>> On Wed, Mar 29, 2006 at 11:54:17AM -0500, John Baldwin wrote:
>>> On Wednesday 29 March 2006 11:32, Raphael H. Becker wrote:
>>>> On Wed, Mar 29, 2006 at 06:07:05PM +0200, Raphael H. Becker wrote:
>>>>> PS: the box crashed just while writing this (while using devfs
>>>>> <something>) so I'll need to powercycle it before leaving my office.
>>>> crash:
>> [...]
>>>> I don't know much about the debugger, so I just resetted the box by
>>>> typing "reset" at the prompt.
>>>> Hope that helps a little.
>>> Well, it means that it's broken in HEAD as well at least.
>>
>> Is there a workaround to hide "critical" devices from a mounted devfs?
>> ... any patches to test?
>>
>> From my point of view this is a critical situation for machines with
>> jails and "foreign" roots in them while I (host admin) cannot hide disk
>> devices (and other critical stuff) from the jails.
>
> No, someone needs to sit down and debug it.

I don't know about the crash but the usual thing from startup scripts:
 	jail_foo...=...
 	jail_foo_devfs_ruleset="devfsrules_jail"
 	jail_foo...=...
does the right thing on a RELENG_6 box so things must work. It even
works for some manually added rulesets. See /etc/defaults/rc.conf
for a complete sample.
And it did also work some days or perhaps weeks ago on current.

Perhaps looking what is done in /etc/rc.subr (from /etc/rc.d/jail)
might be a good start to find out how to do things correctly.
I suspect the
>>>> # devfs -m /data/jails/pinserv3j01.p-i-n.com/dev/ ruleset 4
is missing an apply?

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT