Repository pattern: One repository class for each entity?

Question

Say you have the following entities defined in a LINQ class:

Product
Customer
Category

Should I have one repository class for all:

Answer 1

Basically there will be one repository per aggregate root object. There are some interesting points about DDD and aggregate root object and how we should design repository classes in the book ASP.NET MVC 2 in Action, look at it if you want to know more.