21 Mar
2012
21 Mar
'12
6:46 a.m.
RisaFrickenFrackenFudge!!!
The darn problem seemed to be in starttde with the
location of cache files
having changed and init hanging when it got to that point.
Somewhere around:
Yeah, the most common thing I do when troubleshooting or rebuilding a new package set is
to delete the profile cache files:
rm -f .trinity/cache-$HOSTNAME/ksycoca*
Recently we changed the names of the temp directory locations to avoid conflicts with
KDE4. Although the directory names used within the profile are sand boxed and safe, the
names of the external linked locations was the same for TDE, KDE3, KDE4. Not good.
So yes, the names changed.
I never experienced any problem after the change. Possibly because I routinely rm -f the
cache files in my testing. Still, I wonder whether the name changes will cause problems
for people who don't do that. I wonder whether we should add a snippet in startde to
look for the old names and rm -fr if they exist in order to force creation to the new
linked names.
Darrell