Finally time to start migration to Linux....

[Walter Vaughan]

Bill Campbell wrote:

>I have python scripts that handle this pretty easily, and they
>can handle things like moving $HOME directories from places like
>/usr/$LOGNAME or /u/usr/... to /home where they belong.  It's
>probably a good idea to assign new uid and gids that are in sync
>with the Linux standards.  SCO tends to use low numeric uids
>below the range considered standard in Linux.  Group gids are
>also a bit different.  The standard CentOS user admin commands,
>like Red Hats, like to assign unique groups for each user.
>
Danger Danger Will Robinson.
EVERY stupid record in filePro will then have invalid @CB @UB info

Most filePro installs should have user ids starting at 200 for the 
filePro user.
RHEL/Centos seems to want to reserve up to 499.
Don't have /etc/passwd at my fingertips for that OS to verify.

What's most important is maintaining your data. I don't care if you get 
everyone to
sign in blood that they don't care, eventually you will take the blame.

Find a currently supported Linux OS that does not want to create system
users that will interfere with your current user id's. Do not do 
anything till
you solve that problem (me, I use freeBSD with filepro and the highest
system user is 80, so this is not a problem).

Your not installing filepro so you can run an OS, find the OS that
supports filePro the best.

The other solution will be to update the binary header info on all your 
data.
If there was some sort of magical utility that would work that would be 
cool.
You would think someone would have written a general utility to convert
filepro user id's by now.