OT: redhat

[Bill Vermillion]

On Sat, Nov 06 21:39  GCC Consulting said 'Who you talkin' to? You talkin'
to GCC Consulting?  I didn't do nuttin'.  I said: 


> > When I installed my FreeBSD system here, I looked at the
> > default sizes that came up with an automatic allocation, and
> > doubled them all.

> > Every couple of years it seems that I have to double the
> > amount of space I allocate for the ``/'' file system on Linux
> > systems.

> > ...
> > >With journaling to avoid fsck's, and good backup policies, 
> > is it even 
> > >as much of an issue these days, that a large single / really 
> > -needs- to 
> > >be avoided?

> > As a rule, if a file system gets nuked, it's ``/'', and I 
> > really like to have all my critical data in another file 
> > system.  I've also found that when a journaling file system 
> > goes bad, it goes *REALLY* bad.

> Windows based computers:

> My biggest complaint with PC manufacturers is that they set up
> only one large partition on the system s they deliver. On a
> Sony Vaio, the drives was partitioned into a C and D.

And they so often assume that HD's never fail and the OS is
installed on a hidden partition so you can reinstall from the HD.
Woe be unto the user who doesn't get CD's or doesn't know they can
order them [at an additional cost].  Back when OSes were smaller
at least some manufacturers told you how to back up to emergency
install disks.

....

> One thing I try to remember to do is create a text file, in
> the program folder, with any key & serial # information for
> installing a program. Since they are on a separate drive, I can
> reinstall any programs even if the original disks are missing
> or have been removed from their original packaging.

> I would love a utility for XP that would search the drive(s)
> and install the necessary settings in the registry so the
> programs don't have to be reinstalled after a crash requiring
> an OS reinstall.

That's one design feature that I think is wrong.  Having everything
depend on the registry is the 'put all you eggs in one basket'.

That's why I like most of the Unix apps approach.  A great nummber
of the programs have their own subdirectores and libraries so if
something goes astray you don't lose the rest.  That could easily
help when some program installs a modified DLL that causes other
programs to break.

> Most clients don't bother to backup workstations.

That's why you have to teach them how to backup the critical files
to the Samba server so they get backup up with all the Unix files
:-)

Has anyone looked into the cron on SFU [services for Unix] on NT
to see if you could automate backups that way.  I just thought of
that this moment.

Bill
-- 
Bill Vermillion - bv @ wjv . com