[K12OSN] K12ltsp V 4.1.1 & new(er) kernels problem

[Julius Szelagiewicz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> On Sun, 2005-03-06 at 15:55, "Terrell Prudé, Jr." wrote:
>> I'm
>> assuming a "clean install" of K12LTSP here, which is the only way I
>> really trust.
>
> You can do a 'mostly clean' install if you have /home on a separate
> partition.   Just don't reformat /home, and patch up your
> passwd/shadow/group/gshadow files to include all the old users
> above uid 500.  There can still be some problems with things
> that expect a new dotfile format in home directories.
>
>> For those who have implemented LDAP authentication
>> infrastructures, use K12LTSP only for running apps (no file/printer
>> serving, etc., /home is NFS-mounted on a dedicated server), and tell the
>> K12LTSP server to authenticate against LDAP, then upgrading an entire
>> K12LTSP system is not nearly as risky a proposition.  That's, BTW, why
>> I'm currently studying LDAP.  :-)  I need to be able to set that kind of
>> thing up.
>
> Having this will also let you run a test system with the next version
> concurrently, accessing the same home directories so you'll know
> what to expect.
>
> --
>   Les Mikesell
Les, this is a receipe for disaster. The apps usually are backward
compatible but they sure are -not- forward compatible. after say,
evolution upgrade, the files may change so much, that accessing them with
the old version will really hose the user boxes. ditto for mozilla. I
know, I've learned the hard way :-)
The safe way to do it is to run tests of new software against separate
directories. julius

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFCLFx42LhlZOaj6vURAiXGAJ9cCJn1M/GuHi9SF5SUzOolbRTLuQCdGvzb
hXtEXti+eangnTMZjb+ZsgQ=
=4vgM
-----END PGP SIGNATURE-----