If I remember right, Light6 came shipped with one tiny GUI browser and one full GUI browser. A couple of good choices to fill these niches could be Midori and one of the Chromium offshoots(Iron or ChromePlus?). Since the Chromium browsers as well as Midori use webkit, possibly a default other than Midori could be considered?

Kazehakase is very light and runs either Gecko or Webkit renderers.

Dillo2 has been redesigned in 2008 to use FLTK instead of GTK and saw a memory footprint improvement of 50%. Wikipedia even has this to say about Dillo: "Dillo is, however, the browser of choice in several space-conscious Linux distributions, such as Damn Small Linux[34], Feather Linux[35], VectorLinux[36], antiX[31] and Mustang Linux[31]." I don't see any info on what Dillo uses for a rendering engine.

Dillo is pretty useless for anyone doing serious Web browsing. It doesn't do flash or multimedia and can't do various logins. It's okay for browsing mainly text Web sites but not much else. I think it should be left out and left up to the user to install if such minimal Web use is what they're happy with.

I'm personally wary of Chromium because I don't want to further Google's dominance of the online world.--GrannyGeek

Dillo 3 has been released. Will need FLTK 1.3 to build. Haven't looked at it. Wouldn't include a minimal browser unless it were highly capable and what it lacks could be filled in with other small apps. The idea is to have something ready-to-go out of the box, even if not exactly to taste.

A text-mode browser may be desirable or a necessity in some cases; but a graphical "minimal browser" alone, alongside a larger browser, is just a waste of space that could be used to add real functionality.

Dillo 3 works just fine. I could not imagining using the web without Dillo. One has to learn how to use it. 80 % of my browsing is done with it. And no silly ads disturbing my viewing. All my posting here is done with it.

In a pcmanfm file manager window, "open folder as root" works fine with out-of-the-box CD, but installing updates breaks it. IIRC, it worked OK after update 1, but not when update 2 was installed, not sure.

Greetings,Don't know how much help I can be, but as an end user I shall give my experince with the new Vector 7.

I am IMPRESSED with its speed!

I like to test candidates for my netbook Asus Eee 1015px as a Live CD on my main big box. It is my feeling that with the constraints imposed by a CD drive that a closer approxmation will be achieved in the performance of an install for the netbook using a Live CD.

1) Was not able to fully access the hard drive, limiting the ability to open the files within. I was able to get to items that were not within a folder. 2) Music: .wav and .mp3 played without errors!3) Pictures : .jpg, Yay! Outstanding, very quick!4) 401 KB File on desktop : was not able to open.Error creating mount point : no such file or directory5) USB stick 2G, Kingston, same error, no file or directory.5a) Used Gslapt to upgrade all. No change in the above error.5b) Downloaded USB View.Error : Can not open the file /proc/bus/usb/devices.6) Used Disk utility : Peripheral Devices, clicked USB, none shown.6a) Note, bottom left of panel scrolling to the bottom showed the Kingston stick and the 401 KB File.Error is the same for both when attempted to mount : Error monting volume while performing an operation the operation failed.7) Tried all the above as root.

Hope that helps! I am looking very much forward to this being ready for prime time! Go Vector!

Elinks fails to display several webpages. For example, google displays fine, but not duckduckgo. Many more like this. Probably something in the config.

edit - This occurs in STD RC 3.4 and apparently VL 64 too, so posted to 3.4 bug thread with a little more info.

I did notice that elinks honors most of the command line options from lynx. I have several scripts which use lynx, but if it's just a matter of applying sed s/lynx/elinks/g to the scripts in ~/bin, no problem. Need it to work, though.

On package dependencies:Many or most of the packages recently released for testing will fail due to unmet dependencies. This is due to version differences between the STD version the packages are being built on -- usually the most recent RC -- and older test-releases like 7 Light Live A5. This should clear up when STD goes final and the others are updated to reference STD's newly stable buildbase.

Ignoring dependencies and installing anyway often works, but be careful.

I ignored a version dependency (had a slightly older version installed) to upgrade Firefox to 7.0.1, and that seems to work.