Small Web Browser?

[Gerald Combs]

Leo J Mauler wrote:
> 
> On Sun, 23 Nov 2003 15:28:30 -0600 (CST) Gerald Combs 
> <gerald at ethereal.com <mailto:gerald at ethereal.com>> writes:
>> On Sun, 23 Nov 2003, Jonathan Hutchins wrote:
>> 
>>> On Sunday 23 November 2003 01:03 pm, Gerald Combs wrote:
>>> 
>>>> Links (version 2) has a graphics mode.  You can invoke it with
>> "-device x"
>>>> from X.  It also supports JavaScript:
>>> 
>>>> 
>> http://atrey.karlin.mff.cuni.cz/~clock/twibright/links/features.html
>> 
>>> 
>>> Ok, you're missing the point here:  What if you DON'T have or
>>> want
>> XWindows?
>> 
>> 
>> And you didn't read the feature page above, or you skipped bullet 
>> item #2. It says:
>> 
>> "Links runs in graphics mode (mouse required) on X Window System 
>> (UN*X, Cygwin), SVGAlib, Linux Framebuffer, OS/2 PMShell, AtheOS
>> GUI"
>> 
>> bam:/home/gerald> links -help links [options] URL Options are:
>> 
>> -g Run in graphics mode.
>> 
>> -no-g Run in text mode (overrides previous -g).
>> 
>> -driver <driver name> Graphics driver to use. Drivers are: x,
>> svgalib, fb, directfb, pmshell, atheos. Available drivers depend on
>> your operating system and available libraries.
>> 
>> -mode <graphics mode> Graphics mode. For SVGALIB it is in format
>> COLUMNSxROWSxCOLORS -- for example 640x480x256, 800x600x64k,
>> 1024x768x16M32
>> 
>> [ ... ]
> Okay, tried Links with the options:
> 
> links -g -driver svgalib -mode 800x600x256
> 
> and
> 
> links -g -driver svgalib -mode 640x480x256
> 
> Each time the system responds with:
> 
> svgalib: Cannot get I/O permissions.  (which file should I chmod 
> permissions?)
> 
> If I try to run the same commands as root, I get:
> 
> Segmentation fault.

 From reading the documentation available on www.svgalib.org, it looks
like applications that use svgalib must be running as root or at least
be suid root.  I'm not sure what's causing the segfault here.  If you're
feeling adventurous and you have gdb installed you could:

  - Allow core dumps ("ulimit -c unlimited" for Bourne-style shells and
    "limit coredumpsize unlimited" for C-style shells)

  - Re-run links as root to create a dump.

  - Run "gdb /path/to/links ./core"

  - Inside gdb, run 'bt' and see what made the application crash.

If you're feeling less adventurous you might want to make sure your
kernel is compiled with a framebuffer device (/dev/fb<x>), set its
permissions accordingly, and tell links to use the "fb" driver instead.

> Typing
> 
> links
> 
> by itself with no command line arguments results with a blank screen
> and a single flashing cursor near the top of the screen.  If I press
> Ctrl-C I can get out of the blank screen and back to a shell prompt.

AFAIK if links doesn't have a home page configured it will print a blank
screen.  Try hitting "g" to go to a URL or "F10" to bring up the menu.