just noticed this same problem myself after updating the mysql on debian testing... don't know if it's a mysql issue or a slimserver issue.
Most likely a combination of the two - I've just opened a Debian bug (no number yet) against mysql-server-5.0 on the Debian BTS in case more people run into the problem, but I don't expect the maintainer to do much if this affects only slimserver. Is anyone else able to reproduce this? C. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
