General Comment.
I have already made the point in relation to 8GB sticks that all such sticks are not equal and many are not the full shilling. The same applies to 4GB sticks.
The whole point in V3 of reducing the image to 4GB but continuing to target 8GB sticks or greater was to surmount that issue and so achieve the desirable 99% deployment reliability.
Will V3 fit on a 4GB stick? – Yes, if the stick is the full shilling. If it is not, the build will fail.
Is it advisable to put it on 4GB stick? – No. Not if you want some certainty that it will work. It would also invalidate testing which is intended to take place on larger sticks.
Can I try it anyway? – Of course you can but at your own risk of failure and not as part of any testing. It would run the risk of re-introducing one of the problems that V3
is intended to solve.
@ 8-bit,
Your news of success is most welcome. Syslinux.cfg has changed in V3 and now reads as follows:
Code: Select all
# Boot Blue Pup ETP 25th March 2014
default /vmlinuz root=/dev/sdb2 rootwait rw
@ Volhout,
You are correct but for the purposes of testing lets keep it simple and just follow the instructions:
NOTES: (For testing V3 - The target is an 8GB or larger stick)
1. Unplug any other cards or sticks before attempting to boot V3.
2. Use a port rather than a USB hub if possible as there is an underlying problem with QT.
3. Linux install commands for V3:
Code:
# xz --decompress --stdout blue_pup_v3_4gb.img.xz > /dev/sdx
# sync
(replace the x at the end with your target device letter)