Well, this is beyond my current knowledge... but basically /etc/init.d is where you make things happen at startup, and with the numbers leading filenames there (take a look...) you can have control when your script will be executed. I'd suggest take a look into those scripts and try to insert your script, and google runlevels if you want to be sure when your script would be executed. I suppose basically everything in /etc/int.d goes off before anything (normally) happens to your home directory.<br>
<br>Andras<br><br><div class="gmail_quote">On Sat, Jun 12, 2010 at 5:48 PM, Ingo Scherzinger <span dir="ltr"><<a href="mailto:ingo@miamiwave.com">ingo@miamiwave.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Andreas,<br>
<br>
Sounds like a good idea to put the entire "/home/user" folder into a tmpfs<br>
but I have no idea how to get my data copied into this tmpfs prior to the<br>
system wanting to use it.<br>
Any idea?<br>
<font color="#888888"><br>
Ingo<br>
</font><div><div></div><div class="h5"><br>
> >On Fri, Jun 11, 2010 at 11:03 AM, Ingo Scherzinger<br>
<<a href="mailto:ingo@miamiwave.com">ingo@miamiwave.com</a>>wrote:<br>
> ><br>
> >If the file's contents have to be preserved between sessions, it's<br>
> > breaking<br>
> >the "read only system" paradigm. (You may still be able to use an usb<br>
> > drive<br>
> >for this purpose?)<br>
> ><br>
> > It's actually working fine writing edited data to the rw sda3<br>
> > partition where some folders have been linked to.<br>
> ><br>
> >If the file can be recreated with the same content at each startup,<br>
> >i'd think about how to trick it to be on a temporary writable<br>
> >filesystem. I suppose we cannot change the default path for this<br>
> >file, and i'm not sure<br>
> > if<br>
> >you can a have link in your read only filesystem (/home/ingo)<br>
> >pointing to<br>
> > a<br>
> >yet-to-be-created file on a temporary filesystem, but given the<br>
> >annoyance factor of the problem, it may make sense to trick your<br>
> >whole /home/ingo<br>
> > onto<br>
> >a temporary filesystem (from where of course you will be free to<br>
> >create links to directories that reside on the read-only filesystem).<br>
> ><br>
> >Andras<br>
> ><br>
> > I tried that already. I was mounting the entire /home/ingo folder to a<br>
> > tmpfs.<br>
> > That way I didn't have all files I needed available. All system<br>
> > settings seemd to be gone.<br>
> > After getting the data partition to auto mount -rw I made a link to<br>
> > the .ICEauthority file. Didn't help. Maybe mounting drives comes later<br>
> > in the upstart order. I should check that out.<br>
> ><br>
> > Ingo<br>
> ><br>
<br>
>Well, when you mount your whole home to a tmpfs you have to copy all those<br>
>needed files and system settings on it, and if you can, you have to save<br>
them back >to permanent storage before shutdown.<br>
>Automounting drives from fstab may happen sooner or later during startup,<br>
but the >system is surely capable of mounting and temp-filesystems from the<br>
moment the >kernel is alive, and you can make things happen at a given<br>
moment in the boot >order by adding it to the right place in /etc/init.d/<br>
><br>
>Andras<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Muranyi Andras<br>