devfs ruleset 4 (jails)

Raphael H. Becker rabe at p-i-n.com
Wed Mar 29 16:07:15 UTC 2006


Hi John,

On Mon, Mar 27, 2006 at 01:31:38PM -0500, John Baldwin wrote:
> On Monday 27 March 2006 02:49, Raphael H. Becker wrote:
> > On Mon, Mar 27, 2006 at 09:35:03AM +0200, Raphael H. Becker wrote:
> > > Hello *,
> > > I hope this is not a FAQ: what is wrong about 
> > > # devfs -m /data/jails/pinserv3j01.p-i-n.com/dev/ ruleset 4
> > 
> > found this one for 6.0-RELEASE-p4:
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=93423
> > 
> > But still no solution as as far I can see.
> 
> Have you tried on a current box perhaps?

I cvsup'ed to "." today, recompiled and installed -CURRENT just 15 minutes ago.

After starting the jail with "jailctl start pinserv3j01.p-i-n.com",
everything is running but <jail>/dev still has those critical nodes:

root at pinserv3# pwd
/data/jails/pinserv3j01.p-i-n.com/dev
root at pinserv3# ls -1 amr* cua*
amr0
amrd0
amrd0s1
amrd0s1a
amrd0s1b
amrd0s1c
amrd0s1d
amrd0s1e
amrd0s1f
cuad0
cuad0.init
cuad0.lock
cuad1
cuad1.init
cuad1.lock

I, again, use jailctl-0.71, which uses devfs to apply the ruleset 4 to
/data/jails/pinserv3j01.p-i-n.com/dev 

Same setup as in my original mail using 6.1-PRERELEASE.

Any idea?

What additional information / debug output do you need?


Regards
Raphael Becker

PS: the box crashed just while writing this (while using devfs
<something>) so I'll need to powercycle it before leaving my office.


More information about the freebsd-current mailing list