[Voyage-linux] 'ro' changes in version .5 onwards

Voy User (spam-protected)
Wed Jan 5 14:31:57 HKT 2011


Thank you.
Few more questions.

In 0.3.1 image,
there were several files in /etc/ like /etc/adjtime /etc/issue
which were softlinks to /rw/etc/adjtime /rw/etc/issue.
In 0.6.5, these are actual files.

Also, /var/log was a soft link to /rw/var/log
In 0.6.5, this is an actual dir.

/var/lib/logrotate was a link to /rw/var/lib/logrotate
In 0.6.5, this is a link to /lib/init/rw/var/lib/logrotate

Can someone explain these changes?
Asking because in my customisation of 0.3.1, I had several files/directories
which were links to corresponding files/dirs in /rw

Now I am confused whether I should do the same thing i.e. (links to files in /rw)
or should I make it an actual file or link to files in /lib/init/rw?

Please help.



> ----- Original Message -----
> From: Punky Tse
> Sent: 12/27/10 02:55 PM
> To: Voy User
> Subject: Re: [Voyage-linux] 'ro' changes in version .5 onwards
> 
> It is in /etc/init.d/voyage-sync.
> 
> 
> On 24/12/2010 19:09, Voy User wrote:
> > This is what I am trying to understand.
> >
> > As per my understanding this is how stuff used to work in 0.3
> > - Whatever you needed writable was stored in the image itself in
> > /ro. For eg a config file you needed which was supposed to be in
> > /etc/prod/prod.conf - the base version was stored in /ro/etc/prod/prod.conf
> > - /rw was empty in the image
> > - the actual /etc/prod was a soft link to /rw/etc/prod
> > - At boot time, /etc/init.d/mountall.sh has line
> > tar -C /ro -cf - . tar -C /rw -xf -
> > So at booting everying in /ro was copied to the empty /rw
> > directory.
> >
> > Let me know if I am mistaken in my above understanding.
> >
> > In 0.6.5, there isn't any /ro directory in the image.
> > There is an empty /rw.
> >
> > There is no tar line in mountall.sh
> >
> > So how will this work in 0.6.5?
> >
> >





More information about the Voyage-linux mailing list