Hi Joachim! On Thu, 06 Nov 2008 19:27:39 +0100, Joachim Breitner wrote: > Am Donnerstag, den 06.11.2008, 19:03 +0100 schrieb Luca Capello: >> - /etc/X11/xorg.conf >> >> It requires a specific configuration for both the touchscreen and >> the graphic driver (fbdev), in both cases it should be done >> automatically, since X.Org can already be used without that file > > this would require some serious X.Org hacking, I assume – don’t expect > that too soon.
I think the same for the tslib driver, but the fbdev one should work out of the box already, which AFAIK is not the case. I will investigate it a bit more in the future. Another thing: if we provide an option to install Xglamo instead, this file is not strictly necessary, but I will create it anyway to provide a better experience when people will install X.Org instead. >> - /etc/inittab >> >> This is modified to disable all tty* but tty1 to save memory. Back >> at DebConf8 I experienced some problem starting X11 with >> xinit/startx but without specifying the desired vt, which obviously >> needs to be not already in use. We need to investigate a bit more >> into this issue, since the vt for X11 is now hardcoded into the >> nodm init script, which is obviously not the desired behavior > > gdm checks for an unused vt, starting from vt 7. Maybe we should change > nodm’s vt setting to 7 as well, that will increase the likelihood that > it will work. Perfect, this goes into the ToDo list for nodm, which already includes the debconf question as explained at http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2008-October/000157.html >> - /etc/modules [...] > With some modules (g_ether, I guess), there is no automatic way of > deciding whether to load it or not (as it’s not a device driver, but > functionality). So I don’t think we can get rid of that. Fully agree :-) >> - /etc/default/rcS >> >> By default we enable fsck at boot, is this a good thing? I am >> thinking especially about very big (>= 4GB) microSD, where a >> complete fsck can take quite a lot of time > > By default we make fsck fix any error automatically, instead of asking > the user (which won’t work without an keyboard). I don’t think disabling > the fsck completely is a good idea. We could adjust the mount and > time-limit, though. The major problem I found with this setting is that when the FR runs out of power, as soon as you plug in the cable (being it the USB or the wall charger one) Debian starts and then fsck fires up, which results in the FR running again out of power. The only solution I am aware of is to switch on the distribution installed on the internal flash memory. Thx, bye, Gismo / Luca
pgpJc8kPuPDeW.pgp
Description: PGP signature
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
