[Voyage-linux] rolling my own install image

[Voy User]

I did diff between the image from which we burn to flash & what gets burnt
on to the flash.

These are the differences I found
- a grub directory (I burnt with the grub option) and files get added to the /boot directory
- The timestamp of /etc/dnsmasq.more.conf get updated to current date/time, but not changes
to the file itself.
- The following files get regenerated (but the only things changed in the flash in the regenerated
file is the date/time which is one of the lines in the file.
    - usr/local/sbin/.voyage-install.conf
    - usr/local/sbin/test.conf
    - etc/modules
- a /lost+found directory gets added to the flash
- etc/inittab gets modified to comment out some lines & uncomment other lines.
 (I assume this is related to whether one choses the serial or console option while burning)


So essentially, if one adopts the method Stephane suggests, then while updating from
the flash to the base image, one has to
1) rm -rf boot/grub
2) restore the original etc/inittab to the base image.

Does this sound right?


 
> ----- Original Message -----
> From: Voy User
> Sent: 01/18/11 11:11 AM
> To: voyage-linux at voyage.hk
> Subject: Re: [Voyage-linux] rolling my own install image
> 
> On 01/07/2011 08:14 AM, Jeff Ramin wrote:
> >
> >>    On 01/07/2011 01:57 AM, Stéphane Acounis wrote:
> >>
> >>        Le Thu, 06 Jan 2011 13:46:44 -0600
> >>        Jeff Ramin<jeff.ra... at singlewire.com>  a écrit:
> >>>
> >>>
> >>>            Hi folks.
> >>>
> >>>            Quick question - is there a HOWTO or FAQ regarding creating my own
> >>>            voyage installation image? I need to install voyage on many machines
> >>>            and don't want some of the stuff that comes in the vanilla image,
> >>>            such as asterisk.
> >>>
> >>>            Thanks.
> >>>
> >>>
> >>>        Hi Jeff,
> >>>
> >>>        This is very simple. Here is how I do:
> >>>
> >>>        * install the stock Voyage.
> >>>        * trim it to your needs: remove unwanted packages, add new ones,
> >>>           configure network, add users, etc...
> >>>        * once you're happy with it, take the CF card and plug it into a card
> >>>           reader
> >>>        * make a copy with tar or rsync to a directory (rsync
> >>>           -av /mount/cf/ destdir)
> >>>        * use this directory as the source install of Voyage ( cd
> >>>           destdir ; /usr/local/sbin/voyage.update)
> >>>
> >>        you can use the command line options of the installer and use a script
> >>        file to automatically format the new CF and install your version of
> >>        Voyage.
> >>
> >    Is there a list of files I would need to "reset" after doing this? I can think of some issues, such as the sshd key being created after the first >    boot. Or does the voyage.update script take care of things like that?
> 
> 
> Hi - I am also interested in knowing the answer to this. 
> 
> Basically, when we burn the image to the flash, does voyage.update do any changes to image or does it just to a copy.
> If it just does a copy, then the above method would work - however, if it does some changes before or after copying, then
> the above method would need some changes.