OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: hannes on January 27, 2007, 07:01:22 pm
-
I'm using an SL C1000 with OZ/GPE and after some tweaking, uninstalling and installing my root partition has arrived at almost 90% use, whereas my home partition sits there at an idle 3%. I know I can always install software to /home, but I was wondering if there is a way (in OZ, I mean) to repartition the internal flash and mount all of it on /, maybe by moving root to sd with altboot, repartition and move root back again? would that work?
-
Someone needs to look at the work the pdaX people did to allow a single partition and implement this for OZ (flasher and some kernel changes iirc).
Si
-
I think it was Koen (correct me if I'm wrong) who wrote on this forum something in the line of OZ neither needing nor wanting changes to the default partitioning, so I'm not sure if this will ever be officially implemented. The main point is, can a single flash partition be booted by the sharp bootloader + altboot (pdaxrom uses uBoot instead)?
-
OpenZaurus never supported and will not support resizing of flash partitions.
-
OpenZaurus never supported and will not support resizing of flash partitions.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=152738\")
But changing the partitioning of the MicroDrive is supported by the OZ installer. I've never heard the logic behind not partitioning flash, but at least you can repartition on the 3ks.
EDIT: You could try [a href=\"http://wiki.openzaurus.org/HowTos/Root_Filesystem_on_external_media]RootFS on External media[/url]
-
Changing the MicroDrive partitioning is much more uncritical than changing flash partitioning.
-
OpenZaurus never supported and will not support resizing of flash partitions.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=152738\")
That's the second time I read a categorical statement like this on this forum ([a href=\"https://www.oesf.org/forums/index.php?showtopic=20870&hl=root+partition]here[/url] is the other one) - would you mind to explain the reasons behind this, Hrw or Koen? - thank you
-
OpenZaurus never supported and will not support resizing of flash partitions.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=152738\")
That's the second time I read a categorical statement like this on this forum ([a href=\"https://www.oesf.org/forums/index.php?showtopic=20870&hl=root+partition]here[/url] is the other one) - would you mind to explain the reasons behind this, Hrw or Koen? - thank you
[div align=\"right\"][a href=\"index.php?act=findpost&pid=152755\"][{POST_SNAPBACK}][/a][/div]
it's probably because its easier to implement and there are less things that can go wrong if you stick to something that is known and not let users have option to create many different partition sizes and risk user creating absurd partition layouts or sizes.
that said, the OZ updater script is rather simple (only looked at the C3000 script). it just whacks the kernel and initrd onto the nand and extract the hdimage to the microdrive.
i've secretly written an updater script for OZ using pdaXrom's one as a guide which pops up a menu similar to the pdaXrom one which then allows you to repartition the microdrive. it could easily do the same with the nand, but since the C3000 doesn't have much nand space to play with anyway, i removed the nand options.
-
OK been looking for the magic answer. What is the standard partition size for a c1000 ??? Im moving from CACKO lite with a 19MB partition
-
I would suggest just doing a NAND restore from TriSoft and not worrying about it.
-
Cheers, ended up doing just that.
Ta
-
now you know the partition sizes, can you post them, so that others can, maybe, avoid the same problem, thanks!
-
I believe
fdisk -l /dev/mtdblk0
or some similar device should give the info we're looking for.
-
Outputs are:
Disk /dev/mtdblock0: 7MB 7012352 bytes
255 heads 63 sectors/track 0 cylinders
Units= cylinders of 16065 * 512 = 8225283 bytes
Disk /dev/mtdblock1: 7MB 7340032 bytes
255 heads 63 sectors/track 0 cylinders
Units= cylinders of 16065 * 512 = 8225283 bytes
Disk /dev/mtdblock2: 60MB 60817408 bytes
255 heads 63 sectors/track 7 cylinders
Units= cylinders of 16065 * 512 = 8225283 bytes
Disk /dev/mtdblock3: 63MB 66060288 bytes
255 heads 63 sectors/track 8 cylinders
Units= cylinders of 16065 * 512 = 8225283 bytes
Cheers