LINQ is more of an abstraction over query-like operations than a database adapter. It's very good for writing expressive code that can be optimised at runtime by the underlying provider.
If you're looking to implement a proper Data Access Layer, I suggest looking at NHibernate, which has MySQL support and a LINQ provider. It will also let you map specific operations to Stored Procedures.
I wouldn't touch DataObjects with a 10-foot pole. It's an odd little proprietary thing without much of a user base. You should evaluate NHibernate and Entity Framework 4 to see which suits you best; you'll be able to get help with either of those on StackOverflow.
If you've got some money to spend, I recommend looking at LLBLGen to make your life easier.
Ah, thanks for the warning. I've already seen plenty of NHibernate posts on Stack Overflow, I can see how that is going to be a useful resource. Thanks for the help- I'll recommend we pick up LLBLGen. One of the reasons I was looking outside of NHibernate was the idea of the XML configuration files. A GUI will go a long way to avoiding that problem...
EDIT: Just seen Fluent NHibernate, too. Interesting.