Roy Schestowitz <newsgroups@xxxxxxxxxxxxxxx> wrote:
> __/ [ yttrx ] on Wednesday 31 January 2007 13:12 \__
>
>> wjbell <wjbell@xxxxxxxx> wrote:
>>> What a sad troll attempt.. but I'll oblige.. answers below.
>>>
>>> Tom Wiley wrote:
>>>> Our school machines are only P3 800mhz but they have been upgraded to 256
>>>> meg of memory. Heck, I run a DHCP/DNS server on a 32 meg 300mhz clunker.
>>>
>>> So you're some sort of IT guy for a school? Interesting that you come
>>> to an advocacy group for technical info... especially when you shouldn't
>>> need it, being the IT guy and all...
>>>
>>>> So 256 meg should run just about anything out there. Right?
>>>
>>> What do you think, Columbo?
>>>
>>>> Ok, ok. The above is just a little manure for the trolls.
>>>
>>> Sounds more like a little trolling.
>>>
>>>> But, seriously, anybody know if installing software on Vista is still a
>>>> stroll through reboot hell? After last summer's helping install new
>>>> network clients, office, sql, classroom stuff and antivirus on our
>>>> school's brand new XP machines, I almost have feelings back in my fingers
>>>> after twenty thousand logins. ...and reboot, login, reboot, login,
>>>> reboot, barf.
>>>
>>> OK, so you are the school comp guy... but you're not smart enough to
>>> temporarily automate logins for install purposes? You're complaining
>>> about having to type a username and password? God I hope you're not
>>> thinking of running linux....
>>>
>>>>
>>>> If they haven't fixed that obvious leftover from Win3.1, I may go fishing
>>>> this summer and let someone else earn part time money.
>>>
>>> You're fishing now. No need to wait for summer.
>>>
>>>>
>>>> TW
>>>>
>>>> *** And surely they have dumped that wonderous single point of failure -
>>>> the registry!!
>>>
>>> Of course they didn't... but you knew that. Now run along, Jr.
>>
>> What wjbell is trying to say (and I concur, having done it many times)
>> that yes, and install of Vista is still, after all these years, a stroll
>> through reboot hell.
>
> The 'problem' of reboots is greatly exaggerated to be honest. Unless you run
> a server, there's no serious penalty. Installations of S/W and patches,
> however, are rather frequent. If you run a busy environment with dozens of
> applications in many virtual desktops then rebooting has a high productivity
> cost. For that reason, I find that very few Windows users develop the
> healthy habit of having busy desktops that are augmented over months of
> persistent use. At the end of each day (or at times of a forced 'coffee
> break', e.g. patches arrive), everything just gets 'flushed'. To add insult
> to injury, KDE actually restores sessions in a sophisticated way, so it
> saves a lot of work for the users who prefer to reboot Linux.
>
Or, as has happened much more often in my experience, if you're controlling
the desktops of a thousand employees and there's an emergency windows update
that the big boss wants implemented immediately and "pushed" by the DC to
all those machines, EACH AND EVERY ONE OF THEM NEEDS TO REBOOT TO MAKE THE
UPDATE WORK.
Now, that may be fine for some people, but if 50 of those people are
developers waiting for a build to finish over the course of four days,
or a complex DB query to come back, there could be a lot of trouble and
possibly mountains of lost revenue.
Its a stupid system, and its a serious problem.
-----yttrx
--
http://www.yttrx.net
|
|
