What's the difference between Linq2Sql and ADO.Net Entity Framework

Recently, I've been looking into using ADO.Net Entity Framework with my ASP.NET MVC talks. Primarily I wanted to understand how the Entity Framework differed from Linq2Sql so I could see which technology was a better fit for my project. Here's what I've been able to come up with:

Linq2Sql is SQL-Server specific and the generated object model bears a strong resemblance to the underlying tables. In other words, there is a 1-to-1 mapping of database tables, stored procedures, etc available in Microsoft SQL Server.

Entity Framework is database-vendor independent (although you need providers) that allows the object and relational models to be quite different. Because of this you can mix a variety of database objects  to create an aggregated and combined data model.

For me, it seems that Linq2Sql is the choice for quick data access to well designed SQL Server databases where Entity Framework is the choice when a variety of data sources and data models must be combined into a single model.