Re: Introducing console-tools v1 (install-tools replacemement)
 

Yup, that fixed it. FM was left in an bad state, and running pb, then hitting cancel, restored FM. Thanks

Re: Introducing console-tools v1 (install-tools replacemement)
 

Ok, this is either a N00b report, or a bug report. You tell me. :)

I have a N800, with 43-7 update installed. I have had this trouble with no additional apps installed, and with everything you can imagine installed.

I start xterm, go full screen, then type pb
I hit the arrow to close the keyboard.
I use the D pad to drop down to cfdisk.
I hit "ok"
I select /dev/mmcblk0 and hit "ok"
I close the keyboard.
I use the D pad and onscreen keyboard to delete a partition.
I select write, and then I select quit.
I get a screen that says "Processing Filesystem Changes Please be patient!!!".
I terminate xterm after a solid 5 minutes of this message
This is how I was killing File Manager before.

I get the same ting if I use fdisk. I write the changes and exit, and I get a screen that says "Processing Filesystem Changes Please be patient!!!"

So, what do I do?

Re: Introducing console-tools v1 (install-tools replacemement)
 

output (sh -x /root/.bin/new.sh 2>output):
+ export PATH=/root/.bin:/root/.bin:/home/user/apps:/usr/bin:/bin
+ parted /dev/mmcblk1 print devices
+ grep -v mtdblock
+ sed s/ /-/

It did prompt me for a source, but not for target. I have installed fuse and ntfs driver (to connect to usb hdd). Could that be a problem?

Re: Introducing console-tools v1 (install-tools replacemement)
 

I'm getting the same result. I admit I'm in over my head, but I can't help but want to try to learn this.

Re: Introducing console-tools v1 (install-tools replacemement)
 

First of all I want to say thanks to everyone for being patient and helping me resolve these issues. Especially pton, you have been very helpful in providing output I can use to debug what went wrong.

[sbox-DIABLO_ARMEL: ~/MLKDE-3/console-tools/root/.bin] > cat *.sh | wc -l
4293


When you write 4293 lines of code you get typos, I also end up making assumptions based on the output of my hardware which does not always match other peoples devices.

----------------------------------------------------------------

All I can say is bear with me and I will have a very useful tool you can use.

I have some updates, I added a new menu. pbeasy

pbeasy contains 4 options.

1) Partition, select a disk and partition it, the system will reboot

2) Clone, After you partition run this to clone flash to new partition you created. Bootmenu will be installed and system will reboot.

3)Upgrade, to the latest version of bootmenu (for future releases of bootmenu)

4)Bootmenu, This Just installs bootmenu, scans and puts all ext2/3 partitions in bootmenu

----------------------------------------------------------------

As for pb, I have made updates to it as well, please update to the latest version (1.7.8-7) and let me know how it goes.

This should fix the hanging while searching for new unformatted partitions.

Again thanks for all the help and patients, please keep your comments coming.

Links have been updated

Re: Introducing console-tools v1 (install-tools replacemement)
 

Success! If I can get it done anyone should. I did use gparted to partition instead. I look forward to learning more. Thanks!

Re: Introducing console-tools v1 (install-tools replacemement)
 

ahhhhhhhhhhh......
So here I sit, happily tapping out this on my cloned, ext3, dual booting N800!
pbeasy is just the ticket! My tablet pc died tragiclly a few nights ago, brutally thrusting my N800 into the role of primary pc for a while. Now that it's cloned and has some breathing room, I'll be able to get some work done! Great things come out of your neck of the woods Mr. Penguinbait! Yourawesome. Thanks!

Re: Introducing console-tools v1 (install-tools replacemement)
 

I had the "NA/dysfunctional bootmenu" issue after first try of cloning with pbeasy. After second try and restart I was greeted with a functioning bootmenu and could manually select the 1st SD partition for booting (but the default was booting from flash).

Also, the cloning process paused at 99% and before quitting complained something about /tmp/rval (missing?).

Trying to set new default boot device as SD afterwards using pb is also unsuccessful as the menu only displays one option (/dev/mtdblock4; jffs). Eventually it'd be nice to be able to set the default boot device as well, to save the occasional boot time fiddling with menus.

Anyways, it's a festive season here and now and booting from SD works! Thanks Penguin! :p

Re: Introducing console-tools v1 (install-tools replacemement)
 

It stays at 99% for a long time when cloning from flash because of the compression ratio of jffs2. If you clone sd to sd you it is more accurate. I will look into the rval error, I am confused why you are not seeing your disk in bootlist. Were you booted to flash or sd when you tried to set your bootmenu default. If you were booted to SD try to boot to flash and set it, let me know if you can see it in the list??

Thanks and Merry Christmas

Re: Introducing console-tools v1 (install-tools replacemement)
 

After first cloning run it finished fine but I rebooted into bootmenu with non-flash partitions "N/A". After second cloning run I got working boot menu with SD partitions available.

Then, booting (with manual boot time menu selection) to the newly cloned system on SD I tried setting the default (automatic) boot partition to SD but the only option in the pb's boot menu default-setting tool was "/dev/mtdblock4; jffs". i.e. there was no option to set the boot menu to default to booting from SD/ext3.

But it's no biggie since I can again boot from SD by selecting it at boot time.