Ling Luo writes:
> According to the devfs.readme, I disabled the devfs automount at
> boot time to enable dev file permission persistence to work( with
> /dev-state etc, etc). However doing that brought up the "Unable to
> open initial console" warning message, it also messed up my serial
> console output( undecipherable symbols jam the whole screen while
> rebooting). I tried the proposed solution: a hack to the init
> program( I have initctl file under /dev before). It didn't change
> the outcome.
I'll update the FAQ about this. It looks like you don't have a valid
/dev/console entry in your root file-system. Make one.
> Alternatively, I reenabled the automounting devfs at boot time,
> commented out "mount --bind /dev-state /dev" in the rc scripts, and
You've got that reversed! It's:
mount --bind /dev /dev-state
Did you mean what you wrote, or is that a typo? If you meant that,
it's no wonder you have a problem!
> left the permission persistence configurations enabled in the
> devfsd.conf. Everything seem to work fine now: dev file permission
> persistence is working, "Unable to open initial console" warning is
> gone, and my serial console output is back to normal. Since this is
> different from what was suggested in the readme, just want to make
> sure this won't have other side effects.
This is safe, just not as tidy and convenient, as you can't switch
back and forth between devfs and non-devfs without having to move
entries between /dev and /dev-state (I'm assuming you made a typo
above).
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|