LINUX GUI CRASHPROOF?

LINUX GUI CRASHPROOF?

Post by Moses Milazz » Fri, 28 Jul 2000 04:00:00




> Christopher's explanation is a good discussion of the underlying
> mechanics of apps under GUIs on Linux, and I doubt I can improve
> on it. What I can do is give you my actual experience:

> The system I'm typing this on has been running now for 38 1/2 days
> without reboot. I use it for web surfing/email/news, business stuff
> (mostly spreadsheets at the moment), and development in C++ and
> Perl (I'm just learning Perl, so there are lots of errors). I
> run KDE almost exclusively for everything I do - if I do command
> line stuff, I do it in a KDE xterm. I have also installed at least
> half a dozen pieces of software over that period.

I've been running the Open Look Virtual Windows Manager (OLVWM)on
Slackware 7.0 for well over 100 days, with basically no problems at all.  I've
had
a couple applications crash on me, but that had nothing to do with the WM, and
didn't do anything to the WM.
Whenever there is a problem, I can kill off the offending program generally with
out touching the WM.  When I do have to touch the WM, it NEVER hurts the
rest of the system (yeah, I have to kill the apps that are running over the WM),
I
haven't rebooted the machine in about 120 days, and that last reboot was because
I upgraded the kernel.
I had KDE and Gnome running on this same machine running RedHat 6.1 for a while,
but it wasn't nearly stable enough for me, and I had to return to Slackware.
I use this machine for image processing, so I need something which is very
stable, and  on
which the Window Manager uses very little memory.  Slack's stable, and OLVWM is
the most stable, smallest memory hog I've used.

Cheers,
Moses

 
 
 

LINUX GUI CRASHPROOF?

Post by Anh L » Sat, 29 Jul 2000 04:00:00


well, i don't anything is crash proof...but for me, if it were to crash, i
would like it not to hang user input and it has to be viusally appealing.  my
pick: Enlligtenmet, ALONE...not with GNOME or KDE. they are curses.
if Enlightenment crashes...you fly to console, but that is very rare.  if you
code with vim, just make sure you have the backup option on if you are
paronoid of crashes of the gui.  or code in console =)
if you have a machine that isn't whimpy, and you like a fast and easy to
customize interface without that silly bar at the bottom of the screen, use E.
actually, E fanatics don't call E a windowmanager...we like to say "graphical
shell"  =)
and it has a nifty termincal called Eterm.  E is the MOST configurable
"graphical shell" and without a doubt Eterm is the most configurable terminal.
and if you want to brave Eterm out of CVS, it has even more f?atures like font
fx..emboss...drop shadow..some others i can't think of...

cheers!



>> Christopher's explanation is a good discussion of the underlying
>> mechanics of apps under GUIs on Linux, and I doubt I can improve
>> on it. What I can do is give you my actual experience:

>> The system I'm typing this on has been running now for 38 1/2 days
>> without reboot. I use it for web surfing/email/news, business stuff
>> (mostly spreadsheets at the moment), and development in C++ and
>> Perl (I'm just learning Perl, so there are lots of errors). I
>> run KDE almost exclusively for everything I do - if I do command
>> line stuff, I do it in a KDE xterm. I have also installed at least
>> half a dozen pieces of software over that period.

>I've been running the Open Look Virtual Windows Manager (OLVWM)on
>Slackware 7.0 for well over 100 days, with basically no problems at all.  I've
>had
>a couple applications crash on me, but that had nothing to do with the WM, and
>didn't do anything to the WM.
>Whenever there is a problem, I can kill off the offending program generally with
>out touching the WM.  When I do have to touch the WM, it NEVER hurts the
>rest of the system (yeah, I have to kill the apps that are running over the WM),
>I
>haven't rebooted the machine in about 120 days, and that last reboot was because
>I upgraded the kernel.
>I had KDE and Gnome running on this same machine running RedHat 6.1 for a while,
>but it wasn't nearly stable enough for me, and I had to return to Slackware.
>I use this machine for image processing, so I need something which is very
>stable, and  on
>which the Window Manager uses very little memory.  Slack's stable, and OLVWM is
>the most stable, smallest memory hog I've used.

>Cheers,
>Moses

--

University of Illinois at Urbana-Champaign
Student of Computer Engineering

   ~            yeah, i'm a Pimpin-Penguin
  'v'
 // \\
/(   )\
 ^`~'^

Linux, ain't it cool?

 
 
 

1. LINUX GUI CRASHPROOF?

[snip the rest of Christopher's explanation]

Christopher's explanation is a good discussion of the underlying
mechanics of apps under GUIs on Linux, and I doubt I can improve
on it. What I can do is give you my actual experience:

The system I'm typing this on has been running now for 38 1/2 days
without reboot. I use it for web surfing/email/news, business stuff
(mostly spreadsheets at the moment), and development in C++ and
Perl (I'm just learning Perl, so there are lots of errors). I
run KDE almost exclusively for everything I do - if I do command
line stuff, I do it in a KDE xterm. I have also installed at least
half a dozen pieces of software over that period.

In that 38 1/2 days, I have had two instances where I locked up
KDE - both while running Netscape. I'm in and out of Netscape at
least half a dozen times most days - you can calculate the failure
rate. In one case, I just killed X with a CTRL-ALT-BKSPC, in the
other I switched to a console, typed 'killall netscape' and went
back to KDE without restarting it. Other than that, I have had no
crashes - apps, KDE or kernel - other than bugs in the software
I'm developing, and those only killed the app.

I can think of only one thing I don't do which caused me trouble
under the KDE beta's (nearly a year ago) - I don't use KFM for
web browsing. That may even work now - I haven't tried it lately.
I have also had an xterm, 5 editor windows (under C-Forge), Netscape,
and StarOffice running simultaneously on a number of occasions, plus
all the usual daemons (NFS, NIS, qmail, etc). NS and SO both use a
lot of memory.

You can compare my experience to your Windows experience and decide
which is better. Of course, YMMV.

Arthur

Running Linux 2.0.35 (SuSE 5.3) and KDE 1.0

2. ftp line command

3. BogoMips = 400 ???

4. RedHat 6.1 as DHCP Server

5. Is NT crashproof at high hit no's?

6. how to upgrade from Redhat 6 to 7

7. Crashproof? I think not (major problems)

8. GUI->Text->GUI?

9. GUI GUI builders? (Was: Re: GTK builder?)

10. gui ftp program? (or gui frontend for ncftp?)

11. Toronto: Senior Java GUI Architect (up to 90K+options): Java w/GUI emphasis, OOA/OOD, Swing