Notices

I never did reflash to my eMMC, I heard in the last eMMC image the some files/folders changed their location... The question is if I did the backup now, and after reflash of the new eMMC, can I restore this backup ?

Did I say it may? I don't recall seeing the word 'may' anywhere in that sentance...
That being said, I could have used 'this may produce a broken backup', but I felt that wasn't strong enough knowing how it works internally. 'this will produce a broken backup' is more correct, but leaves out the edge-cases(i.e. tar finished but locked up somehow). So "can and WILL" it is. I used that because I remember seeing that turn of phrase elsewhere and thought it sounded nice.

Edit: Oh, btw, does anyone know of a good way to take a plaintext password string and validate it against the (DES encrypted? ) passwd file? I can do everything but the encrypting of the password to compare... anyone know a tool that'll do that?

@RobbieThe1st

out of topic but can i copy your oc freq settings on you sig????? looks like its more stable on 1150mhz than my settings

I was simply pointing out that the turn of phrase, while sounding nice is somwhat redundant. It is like saying:

i.e. Always true! Excuse my boole!

Surely you would attempt to decrypt the the encrypted data with the plaintext and then run some kind of check to to see that the decrypted output is logical, given the nature of DES you would simply have to check if the output file was garbage or not.

Is this what you are asking?

edit: oopz, misread what you said. nvm.

double edit: john the ripper, possibly in the repos as 'john'.

Also, as you are using busybox (?) in backup menu, can I have a shell as an option so I can run a forced FSCK on my file system?

Hmmm, and what with my question ? Please

You can use openssl to do this. You'll need to get the salt for the password from the passwd file (the first two characters of the encrypted password), then do:

@_vi:
We've been over this several times in this thread: We have /no/ framebuffer, which means no screen output for a shell. You could try porting a shell or building a wrapper which directly writes the screen as needed(how text2screen does it), but other than that you're basically stuck.


@Schturman:
Uh, probably? Just make sure to restore /both/ optfs and rootfs at the same time or things won't work properly.

@Rob1n: PERFECT.

So... Password protection is coming! When? As soon as I stop playing TF2 and spend a couple hours on it.
As far as implementation details goes, I'm thinking that to enable it you will crreate a file named "lock-enable.txt" in /usr/share/backupmenu/. If you leave the contents blank, it will validate against the encrypted root password in /etc/passwd, allowing for easy changes. Alternately, you'll be able to put a password hash in the lock-enable file, and it will use that instead - I'll have to figure out a command for /creating/ such a hash, though. Probably something with "openssl passwd...".

As far as other things...
1. In the process of doing the above, I'll make a generic text-entry function which can be used later. This could easily be used for a better run-command box.
2. ext2-4 modules are now copied by default; I'll have to figure out a way to autodetect the correct one to mount if I want support for anternate filesystems for mydocs/sd/opt.
3. mkfs.ext* support for reformatting the optfs should be doable, I'll just have to add an option for it.

Oh, this brings me to another problem: Is there a good way to do an "include" of shell-script code in another file such that I can use pre-defined variables inside it? My main program file's getting big and complicated, and I'd like to just move chunks into their own files.

edit: Missed a post!
@gabby131:
Uh, yes and no. You can use it if you want; It's a free world. But I doubt it'll work for you - That's tuned to be exactly right for /my/ sample, which won't be the same as yours.
What you want to do is - for each frequency - lock your n900 to that frequency, play a video via mplayer; something that will max out the cpu. If it plays, change the voltage down 1 # and repeat the test. Keep going down until the system crashes or you get decoding errors, then take that value and add two to it. That should be the minimum stable voltage for that frequency.
If you get crashes at a particular frequency later, up the voltage another 1 or 2 if it still has issues.
I'll take an hour or so to calibrate for all frequencys, but it's nice to have no instability.

You should be able to pull in other files by doing ". filename.sh" - that'll run the file within the same process space (so any variables set will be remain when returning to the main script).

noob question: if you have backed up using backupmenu then install power kernel can you use the backup you made prior to that to restore back to before power kernel or do you need to re-install stock kernel beforehand??

if the answer is no i now know where i've been going wrong lol