04-16-2009
I have been using Opera for many years since 6.x and except occasional page rendering issues (normally due to IE-centric coding on many sites), it has been my favourite because it is stable and fast. However, there is no doubt that Mozilla/SeaMonkey/Firefox is strong with a wide range of plugins available (that you previously mentioned).
Opera is still my favourite on Linux, although occasionally keyboard will be locked up probably due to some windowing toolkit issue (i.e. Qt).
Google Chrome also loads fast on my system. Often lighter compared with Opera so I tend to use it more often on Windows these days.
4 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
I have just seen someone using the OPERA browser - it looks quite good and seems to have a friendly GUI.
Can I get this for UNIX(Solaris 8 is my OS)??? Does anyone have this installed on their UNIX workstation?? How is it performing??
All comments and advice is welcome!! (1 Reply)
Discussion started by: Kanu77
1 Replies
2. AIX
On AIX 5.3 host, the lvm_queryvg call does not work properly and results in a sudden memory rise. This is happening on one particular host and the call works fine on another host.
Is this a known issue and is there any patch available for this? (0 Replies)
Discussion started by: sandiworld
0 Replies
3. Solaris
Has anyone gotten Opera 9.5 to work? I'm using Solaris Sparc 5.10. The browser is unusable. It crashes even when viewing Opera's Desktop Team blog. I've asked Opera about this, but no reply. I've never been able to get the 9.5 betas to work either. From one Opera user's blog, I don't see any... (0 Replies)
Discussion started by: cooldude
0 Replies
4. Solaris
Hi,
There is a abrupt memory rise observed for a process on solaris.
When the process is started the memory is around 268 MB and is stable for a day. Then suddenly the memory increased to 4364 MB.
Below is the pmap -xs output for the process (only for heap)
Address Kbytes ... (1 Reply)
Discussion started by: Nidds
1 Replies
LEARN ABOUT DEBIAN
vlock-plugins
VLOCK-PLUGINS(5) Linux Programmer's Manual VLOCK-PLUGINS(5)
NAME
vlock-plugins - plugin support for vlock
DESCRIPTION
If vlock-main(8) is compiled with plugin support its default features are very limited: it can only lock the current session and ask for
authenticiaton. However it is possible to extend this functions through plugins. These plugins are loaded when vlock-main starts and can
provide hooks that are called at certain points during the lifetime of the vlock-main process.
DEFAULT PLUGINS
The following plugins are provided when installing vlock with default options:
all
This plugin locks all sessions by disabling console switching. It is also loaded when giving the -a,--all option to vlock(1).
new
This plugin switches to a new virtual console before disabling console switching through the "all" plugin. It is also loaded when
giving the -n,--new option to vlock(1).
nosysrq
Linux only. This plugin disables the Linux SysRQ mechanism before the console switching is locked by the "all" plugin. It is also
loaded when giving the -s,--disable-sysrq option to vlock(1).
ADDITIONAL PLUGINS
The following plugins are only available if explicitely selected at build time:
caca
This plugin runs a random libcaca screensaver when the screen is locked.
WRITING PLUGINS
For information about writing plugins see the PLUGINS file in the vlock source distribution.
SEE ALSO
vlock(1), vlock-main(8)
AUTHORS
Frank Benkstein <frank-vlock@benkstein.net>
Linux 10 November 2007 VLOCK-PLUGINS(5)