On Tue, 18 Jul 2000, arachne-digest wrote:
> SVGAlib returns me to a proper text console after running Arachne.
>
> The key (for me) lay in forcing use of the VESA driver by
> uncommenting the appropriate line in the /etc/vga/libvga.config file.
> I also uncommented "VesaText" and "VesaSave" and changed the default
> value of "14" to "1" (15 causes Arachne to run mono and does not
> reset the console to text; 0 causes Arachne to fail to run).
libvga.config is very cryptical.. but SVGAlib version 1.4 actually worked
for me immediately, in desired resolution, and returned to text mode
correctly...
> I hope this info helps someone. I'm surprised at how little comment
> there is on the Linux version. Is nobody using it or is nobody
> having any trouble? Just curious.
I think nobody is using it :(
> By the way, to obtain the effect of a RAM disk, I added a few lines
> to the /usr/bin/arachne startup bash script to delete cookies from
> a previous session and to delete the cached files from a previous
> session. Then I add the cache files for my hotlist sites from
why not...
> another directory. That's a technique that could also be used
> in the DOS version if you don't have a RAM disk and don't want to
> wait for the loading of your hotlist sites, since loading from disk
> is usually faster.
Yes, some people were asking me to do it, and I think to keep some
>>initial cache image<< is one option how to get this effect... but I
perefere to get up-to date versions of dynamicaly generated sites...
