Won't mount READ-ONLY

[jrogers]

I had always used Kraven's tivolater for 3.1, but on my third T-60, I decided to go with Superzap's Xtreme, but both of my Kraven systems mount read only with the "mount -o remount,ro /" command. My Superzap system does not do that automatically when I put that command in my rc.remote-login file. I don't understand as the system will mount read only if I type that command in once the tivo has completely booted up. Any suggestions??

thanks

[captain_video]

There's a command in xPlusz that will make your DTivo read-only. Use #44,1 to make it read-only and #44,0 to make it read/write.

[jrogers]

does it make it read only always? Is it persistant across reboots? otherwise it is kinda useless, as a random reboot isn't noticed if it happens in the middle of the night, and then it's no longer on read only.

thanks though, I hope it is...

justin

[captain_video]

I believe that once you set it as read only it stays that way until you change it.

[BubbleLamp]

Originally posted by captain_video
I believe that once you set it as read only it stays that way until you change it.

Wrong, it needs to be set to ro in the rc file. The default will be rw otherwise.

[jrogers]

that's what I thought, and I have it set in the RC file, but it doesn't take. the other operations are taking, maybe I'm doing something wrong... thanks for the clarification though

[captain_video]

I'll have to admit that there's little or no documentation about this option in xPlusz that clearly delineates what it does so I took my best shot at explaining it. I'm a kludge at Linux (actually, an absolute moron) and some of the senior members waste no time in setting me straight if I make an erroneous statement (as they should).

So BL, you're saying that if I set my DTivo to ro using the xPlusz command it will somehow reset to a rw state? Does it stay set at ro if I don't reboot or what? It seems to me that if you make the DTivo read only using xPlusz it will stay that way until something converts it to read/write again. I doubt that it changes back on its own, correct?

[BubbleLamp]

Originally posted by captain_video
So BL, you're saying that if I set my DTivo to ro using the xPlusz command it will somehow reset to a rw state? Does it stay set at ro if I don't reboot or what? It seems to me that if you make the DTivo read only using xPlusz it will stay that way until something converts it to read/write again. I doubt that it changes back on its own, correct?

If you run xPlusz, it resets the setting to ro for you each time you boot. It remembers the settings. A Tivo without xPlusz doesn't change the partition to ro without a command to do so, usually placed at the end of rc.sysinit. HTH

PS, My guess at the problem is you are changing rc.remote-login, which is called by rc.net. For some reason the mount command isn't being recognized from that file. Move the command to the end of rc.sysinit and it should work.

PPS, A stock Tivo doesn't mount the partition ro anyway. This was added around the time folks were looking for ways to prevent upgrades they didn't want. No writing to the root partition should happen on a normal system anyway.

[captain_video]

I believe that once you set it as read only it stays that way until you change it.

If you run xPlusz, it resets the setting to ro for you each time you boot. It remembers the settings.

OK, so tell me what you said that was any different than what I stated. I was referring to setting it as read only using xPlusz, not a DTivo without xPlusz. This comment was a carry over from the previous post and inferred that xPlusz was being used. I think we pretty much said the same thing but went about different ways of stating it.

[BubbleLamp]

Originally posted by captain_video
OK, so tell me what you said that was any different than what I stated. I was referring to setting it as read only using xPlusz, not a DTivo without xPlusz. This comment was a carry over from the previous post and inferred that xPlusz was being used. I think we pretty much said the same thing but went about different ways of stating it.

He never said he was using Xplusz. ;)

[captain_video]

I had always used Kraven's tivolater for 3.1, but on my third T-60, I decided to go with Superzap's Xtreme

Looks to me like he's got xPlusz. His original post asked how to set up his DTivo as read only and I believe that's what I did using the xPlusz commands he had available to him. Was I in error in my line of thinking?

[BubbleLamp]

Originally posted by captain_video
Looks to me like he's got xPlusz. His original post asked how to set up his DTivo as read only and I believe that's what I did using the xPlusz commands he had available to him. Was I in error in my line of thinking?

Well this is way off topic at this point, but you asked. He has a system which can use xPlusz. He never said he was using that feature. I did not assume he was using it, you did. Hence, branched paths to different solutions.

For the record, I've used SZ's Xtreme too because it had a file layout I liked, and the first thing I did was remove xPlusz. I like to do control things myself.

[captain_video]

I didn't assume he was using anything. I just pointed out the fact that he could use the xPlusz command to make his system read-only since it was available on his DTivo with SZ's upgrade. You are correct, though. Different paths to the same solution.