Okay, every once in a while I'm messing at the shell prompt and I get that error which tells me I've been a bad boy and didn't set things to read-only after I was done with 'em. But I know that I did.

I wonder if it's related to this...

I often use the Hijack web interface to set the player to read-write and read-only, using the commands http://empeg/?rw&NODATA and http://empeg/?ro&NODATA , and then watching the screen to make sure it responds appropriately.

But just now I set the player to read-write with the HTTP command, then I went to the shell via serial and Q'd out of the player. Got the BASH prompt, all was fine.

And then tried to do something at the shell prompt and it complained that the filesystem was read-only. But I'd just set it read-write!

Does the player try to set things read-only when it exits out to the BASH prompt or something? And perhaps maybe it only sets one thing read-only and not the other? And when I try to use hijack in this half-state, things go wonky?

Who sets what read-only and when?