[Voyage-linux] Comments about 0.6.2 and /rw /ro replacement by aufs a good idea? I don't think so ...

[Beat Meier]

Hi Punky

Has past very long time :-)

>
> The workaround is to reinstall tzdata (apt-get install --reinstall 
> tzdata).

I have done this already as many other things :-)

>> Now the worst thing (at least for me :-)):
>> I've noticed (and read in changelog) that /rw /ro was replaced by 
>> /var/log and /var/tmp with aufs
>> and that /rw and /ro are no more in use.
>
> It's not aufs as of 0.6.2.  It is tmpfs as 0.6.2 default.

Ok

>> I think this is a very bad idea.
>> To replace /var/log /var/tmp is a good idea BUT you should leave the 
>> conecpt of /ro and /rw
>> For example there are a lot of packages which needs rw access at 
>> runtime in other places
>> of /var like
>>  pdnsd : /var/cache/pdnsd
>>  dhcp3-server : /var/lib/dhcp3
>>  mrtg: /var/lib/mrtg
>> and may more.
>
> See release announcement 0.6.2.  http://linux.voyage.hk/?q=node/41
> You can define these rw directories to VOYAGE_SYNC_DIRS in 
> /etc/default/voyage-util.
> The problem with ro/ rw/ is that when you install new packages, the 
> new files created somewhere under /var/ is lost after reboot, and you 
> need to carefully and manually create the symlink in /ro to /rw

Yes but if you install packages in an ro fs you needs to know what to do ...
I have installed a lot of additional packages everytime I upgrade and 
had never problem...
Of course you must have a look at each package but now too (see below)

>> as also the whole home dir of users which you want for example save 
>> the .ssh keys
>> while the machine is up ...
>> I now you can link to /var/tmp but I think this is not the right way
>> I must say I don't know aufs well.
>> I can add dirs in voyage-sync but thats not the solution to the above 
>> problem, or is it?
>
> You can add $HOME/.ssh to VOYAGE_SYNC_DIRS.  The only deficiency is 
> that it does not work for a single file.


>>
>> If the /rw /ro stuff really will be disabled please post a not how 
>> the users can enable this if it want.
>> Of what is the solution to the above problem with aufs.
>
> /rw and /ro was removed since 0.6.0, and there is no plan to bring 
> this back.  If the above solution does not work for you, please let me 
> know what situations need voyage linux to support.  The /ro and /rw 
> replacement has been discussed in the list during the course of VL 0.6 
> developement.

That's the problem if you are out town for a long time :-(
0.5.2 has been a long time active until I could install it finally and 
now 0.6.2 so I didn't hace noticed the discussion.
But was is the solution to the /rw /ro problem?
There are a lot of packages which need write access on some var file OR 
others and of course in an embedded system which can die
at every time you don't want your / system to be writeable and die in 
the worst moment.
So how can I enable write to some files?
That's the only problem I have. I don't not even need synchronizing this 
files but I want a copy.
Until today I could install the packages I wanted and move over the need 
stuff to /ro and create a link for that /var/XX/YY dir or file to /rw
and even files I wanted that they do not change (like .ssh/kown_hosts) I 
had my template which was fix in /ro and new hosts
were added to the /rw file but lost in case of reboot which was just 
what I wanted, of course this is my case ...
For example I need the following packages to run on voyage 0.6.2 as 
noted already above:
 pdnsd : /var/cache/pdnsd
 dhcp3-server : /var/lib/dhcp3
 mrtg: /var/lib/mrtg
How can I do that with 0.6.2??

If you have to add about 10-20 dirs to VOYAGE_SYNC_DIRS for packages you 
install you have to unterstand also
what the packages needs and we are own the same as befor tmpfs BUT I 
think this is not the idea behind tmps
to have for every package an own tmpfs. Of course the right solution to 
this problem would be to but the WHOLE
/var (as is the idea behind /var to be writtable) to VOYAGE_SYNC_DIRS 
but than you have other problems.

What I don't understand in the whole process. Does nobody install 
addtitional packages and need this requirement?

Why not leave the /rw /ro issue as it was?
If there is nothing in /ro there will be nothing in /rw
And of course if it is there nobody will bothered UNTIL you link the 
stuff from /var to /rw ...

Greetings

Beat

>>
>> Thanks a lot and Greetings
>>
>> Beat
>>
>> PS: Voyage homepage is down at the moment so I can not search for 
>> more infos ...
>
> Yes, there was a in the cable modem, it was fixed.
>