Oh well, sorry I was partly wrong: - you still need a /tmp/ filesystem - wherever the config file is located, elisa will attempt to write to $HOME/.elisa-0.5/ so you need to be logged. Otherwise you can edit the source code and change the line instructing elisa where to write files (elisa/core/application.py somewhere at the beginning)
Philippe Le mercredi 29 octobre 2008 à 18:54 +0100, Philippe Normand a écrit : > Hi Stephan, > > You need to setup a /tmp filesystem, elisa sometimes writes files there > (errors and some files sporadically needed by some plugins). Elisa will > attempt to create directories and other files in the directory where > your elisa.conf file is. So if you launch elisa with elisa > -c /foo/elisa.conf then elisa will need write-access to /foo/ directory. > > Philippe > > Le mercredi 29 octobre 2008 à 18:22 +0100, [EMAIL PROTECTED] a > écrit : > > Hello, > > > > I plan to create an embedded Linux distribution based on uClibc and > > Busybox (no login) what Elisa starts automatically and is small as > > possible and fast. I am as far as the Elisa test, I just want to start > > so I have some problems. The filesystem is completely write-protected, > > as it is a SquashFS filesystem. Only /etc and /var are RamFs > > filesystems. /root /tmp and /mnt are symlinks to /var/root /var/tmp > > and /var/mnt. Which directories must be writable by Elisa to start? If > > I run elisa -c /etc/elisa.conf only an empty /etc/elisa.conf will be > > created. Where is the elisa.log tried to write when I have no home > > directory and I did not login as an user (I think /elisa.log)? Can I > > configure Elisa by variables that Elisa writes everything in a given > > directory? > > > > Stephan > > -------------------------------------------------------------------------------- > > visit http://www.openelec.tv
