[rsbac] device 00:00

[Amon Ott]

On Donnerstag, 8. Juli 2004 12:38, Bencsath Boldizsar wrote:
> I tried to install a fresh 2.6.7 kernel with rsbac 1.2.3 +bugfix 1,2,3
> (patched by hand) onto a system. This is my first trial with 1.2.3 and
> 2.6.X.
> 
> I tried to reset rsbac rules from a backup script. It seemed to be o.k.,
> but rebooting with the non-maintenance kernel results in hangs. It seems
> that rsbac forgot all the "global" rules (like rc types, rc roles etc.)
> only the fd settings remained (like /bin is rc_type_3).
> 
> I think the problem is that rsbac thinks the root device badly and tries
> to save the data to a wrong device. rebooting in maintenance also did not
> work.
> 
> I think the false root device is 00:00. I don't really see what's 00:00 
is
> (no initrd, but autofs, devfs, sysfs is active, and some weird usb
> keyboard exists)

This seems to be a sysfs related problem, which already someone else 
reported. It might require devfs to be triggered, but I am not sure about 
it. The solution that worked was to enable RSBAC delayed init and set the 
root device to the real root device with
rsbac_delayed_root=major[:minor]

Amon.
-- 
http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22
-------------- nächster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde geschreddert...
Dateiname   : nicht verf?gbar
Dateityp    : application/pgp-signature
Dateigr??e  : 189 bytes
Beschreibung: signature
URL         : http://www.rsbac.org/pipermail/rsbac/attachments/20040710/4ce46927/attachment.bin