[Arm-netbook] SATA - ATAS

joem joem at martindale-electric.co.uk
Tue Sep 10 10:06:16 BST 2013


On Mon, 2013-09-09 at 11:33 -0500, Christopher Thomas wrote:

> 
> http://linux-sunxi.org/Building_on_Debian (although even following
> them on Wheezy, I had problems on two separate machines.) 
> 
> 
> I couldn't get the instructions
> at http://rhombus-tech.net/allwinner/a20/boot/  to work as is. 


I'm interested in what the solution looks like.

To make useful Sheevaplug images, I collected
instructions from various forums and web sites
and made a long crib sheet that that could be followed
blindly like a script and it 100% worked.

Want something similar.

The options are
Virtual Machines:
1. Create instructions to set up virtual machine(s) in different distros
   with the complete build environment for one or more tool chains.
   The build environment is created with a script.

2. Make reference virtual machines, compress and upload
   the base virtual machine(s) to take
   care of users who trip up on step 1 or don't want to do step 1
   themselves. If the build environment changes, 
   make updated virtual machines and upload them to replace the outdated
   build environment.

3. Make one script per distro that runs on
   reference virtual machine unattended
   that gives option to download the sources
   if not already done, download and apply patches or updates
   compiles it and creates the uSD images that
   can fit in a 1GB uSD card.
   The script then gives the option to dd the image
   to uSD card and expand the partition to fill their uSD card.

That should march projects to market as fast as possible
without tangling the average dabblers in specifics.

The second option involves no virtual machines
and end up with similar result with faster compile times.
Buy a few 64GB SSD because they are cheap, split it into
4 partitions, and put up to 4 distros
on it and the build environments for each distro.
Take dd image and distribute that for the build environment.

The work files and sources
will be a separate bin file that sits on a hard disk
or a 64GB ssd. The bin file can be mounted by
any of the distros as an ext4 partition and worked
on to create the uSD images as in step3 above.

The second option has the advantage of not being dependent
on virtual machines with their slow compile times.
But to join the club, you would need something like a dedicated netbook,
with a 64GB SSD, and spare SSDs, and the file sizes are a lot bigger
to transfer.

Option 3 - that is for anyone to suggest with better
ideas than above :)



More information about the arm-netbook mailing list