Re: [cobalt-users] Virtual Sites-Moving and Preserving Paths

[Jan Tietze <jptietze@xxxxxxxxxxx>]

baltimoremd@xxxxxxxxxxxxxxx wrote:

> On Sun, 14 Jan 2001, Tony wrote:
>
> > This is something that the Cobalt Migration tool doesn't
> > even mention in it's documentation.
>
> Why am I not surprized?

I agree this should be mentioned in the docs. But...

> > Did'nt pay attention
> > until after using it and found out that it pretty much
> > broke all the sites cgi's after the migration. All hard
> > coded /home/sites/siteX/ cgi paths need to be corrected to
> > the new site number after migration.
>
> Ah, I was hoping...but thanks for confirming the nightmare.

I must add that assuming there would be a software that would correct
hard-coded paths in applications, whether they be C-, PERL-, shell-based
CGIs, PHP scripts or whatnot is a bit much. There is no software
available today that can correct hard-coded paths without potentially
corrupting binaries or even regular code. For text-based languages, this
could be done, but since there are so many different ways of "hard
coding" filesystem paths (thinking of partially building paths through
concatenation etc.), it would be impractical even then.

So, THIS TIME, Cobalt is more or less innocent, although I must say -
and cannot stress this point enough - their support severely lacks
quality, they obviously have incompetent staff and inappropriate
procedures almost everywhere, and I am not buying or recommending their
boxes again.

Jan