Xterm and .Xresources

[NKavanagh at psgroup.com (Niall Kavanagh)]

They've actually cut down on the number of reboots necessary for Win2000
(I'm running RC1 right now, and they *really* have!).

I've noticed that a lot of new Linux users reboot without thinking after
making changes - they don't realize it's not necessary! ;)

Most folks don't realize you can unregister, replace, and re-register DLLs
on the fly. The reason this STILL isn't up to par is that there's no way to
kill the windows GUI to do this - and most system DLLs are required to use
the GUI (so you can't replace without - you guessed it - a reboot).

Having the overhead and complexity of a GUI like the windows shell on a
dedicated server is *insane*, and it's about time they did something about
it. 

--
Niall Kavanagh    | Webmaster @  The Patricia Seybold Group
niall at psgroup.com | Corporate Site:  http://www.psgroup.com
P: 617.912.3168   | Customers.com: http://www.customers.com
 

> -----Original Message-----
> From: Jerry Feldman {75562} [mailto:gzf at gbr.msd.ray.com]
> Sent: Thursday, September 02, 1999 1:27 PM
> Cc: discuss at Blu.Org
> Subject: Re: Xterm and .Xresources
> 
> 
> Jerry A Clabaugh wrote:
> > 
> > This is one of the small points where Unix shines and NT falls
> > on its face: The library path and the regular path are the same
> > on NT, so applications have greater tendency to interfere with
> > one another.  Last week an NT machine I was using became unbootable
> > because I put another entry into the PATH, when I needed a library.
> > This new directory had something in it with the same name as
> > a program which was part of the NT login sequence - result: can't
> > login anymore!
> I think one of the worst problems in Windows9x+NT is the way DLLs are
> handled. In many cases, the installation of an application or 
> even changing
> something like a DNS address may require a complete reboot, 
> where most Unix
> and Linux systems rarely require a reboot. I have routinely 
> changed shared
> libraries in a running system. By shared libraries, I mean libc.so and
> libm.so. One needs to take care when doing this, but the 
> procedure works. 
> In the "official" patch procedure, we used to require a 
> reboot, but that was
> only because it's difficult to recover when one screws it up. 
> In Windows, it
> is difficult to install and important DLL on a running 
> system. Other than a
> kernel change, Linux rarely needs a reboot. Normally in the 
> worst case a
> shutdown to single user mode and then a switch back to 
> multi-user mode will
> do it. 
> 
> -- 
> Jerry Feldman (HP On-Site Consultant) http://gbrweb.msd.ray.com/~gzf/
> +-------------------------------------------------------+-----
> Note: ------+
> | Raytheon Electronic Systems  (W) (781)999-1837/1-1837 | My 
> views may not|
> | Mail Stop:  S3SG10           (F) (781)999-4030/1-4030 | 
> reflect the     |
> | 180 Hartwell Road            (W) gzf at gbr.msd.ray.com  | 
> views of my     |
> | Bedford, MA 01730-2498      (FWD:H+W) gaf at blu.org     | 
> employer.       |
> +-------------------------------------------------------+-----
------------+
> -
> Subcription/unsubscription/info requests: send e-mail with
> "subscribe", "unsubscribe", or "info" on the first line of the
> message body to discuss-request at blu.org (Subject line is ignored).
> 
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).