Grench
Forum Addict!
- Joined
- Oct 3, 2008
- Messages
- 6,629
The short of it - treat the NAND as a recovery partition.
OK - so I've been booting off of an SD card since 4 days after I got my Pandora. Works fine - maybe even better than the internal NAND since user profile space isn't an issue. Reading through some of the HF6 threads, the size of the NAND is a limiter to what we can include for drivers and software with the image.
Here is my idea:
1. Start requiring that anyone who owns a Pandora also own an SD card to put in the left slot and leave there for the OS to ride on. A 2GB card is $6 and a 32GB card is $42. Not exactly a high barrier for someone buying a $500 device.
2. Have the OS image place the basics to boot to command line and a single huge compressed file in the NAND containing the OS image (which can be BIGGER than the one we're using now). I'm not encouraging code bloat, but having a bit of breathing room in the OS load would be refreshing.
3. If you boot from the NAND, have it automatically ask the following:
-This process will erase any data on the card in the left slot and load the Pandora Operating System to it. Continue (Yes,No)?
-How much of the card in the left slot would you like to assign to the OS (1000KB minimum, 32000KB maximum)? <- query the card and put in the card's size as maximum.
-How much of the card in the left slot would you like to assign to an optional swap partition (0KB minimum, 4000KB maximum)?
-Do you prefer the remainder of this card to be formatted as a FAT32 or EXT2 partition?
Please plug this Pandora into the AC adapter and go find something else to do for the next 30 minutes or so while the OS installs.
4. Then the OS installs to the SD/SDHC/SDXC card in the left slot. If that card ever dies, drop in another one, boot from NAND and have it back up and running in 30 or so minutes.
I don't see any drawbacks to this. So... why not?
OK - so I've been booting off of an SD card since 4 days after I got my Pandora. Works fine - maybe even better than the internal NAND since user profile space isn't an issue. Reading through some of the HF6 threads, the size of the NAND is a limiter to what we can include for drivers and software with the image.
Here is my idea:
1. Start requiring that anyone who owns a Pandora also own an SD card to put in the left slot and leave there for the OS to ride on. A 2GB card is $6 and a 32GB card is $42. Not exactly a high barrier for someone buying a $500 device.
2. Have the OS image place the basics to boot to command line and a single huge compressed file in the NAND containing the OS image (which can be BIGGER than the one we're using now). I'm not encouraging code bloat, but having a bit of breathing room in the OS load would be refreshing.
3. If you boot from the NAND, have it automatically ask the following:
-This process will erase any data on the card in the left slot and load the Pandora Operating System to it. Continue (Yes,No)?
-How much of the card in the left slot would you like to assign to the OS (1000KB minimum, 32000KB maximum)? <- query the card and put in the card's size as maximum.
-How much of the card in the left slot would you like to assign to an optional swap partition (0KB minimum, 4000KB maximum)?
-Do you prefer the remainder of this card to be formatted as a FAT32 or EXT2 partition?
Please plug this Pandora into the AC adapter and go find something else to do for the next 30 minutes or so while the OS installs.
4. Then the OS installs to the SD/SDHC/SDXC card in the left slot. If that card ever dies, drop in another one, boot from NAND and have it back up and running in 30 or so minutes.
I don't see any drawbacks to this. So... why not?