Monday 15 April 2013

Eiruvin 38a, b

Although today's daf is quite complex, I am going to share the condensed version.

The rabbis use daf 38a and b to argue about Festivals that fall next to Shabbat.  They pose the question: can an eiruv be placed on one day to represent the need for an eruv for both holidays?  And if not, how do we go about establishing an eiruv twice at the same place over two days?

They touch on acquiring an eiruv with one's feet as opposed to food or drink.  They share information about speech versus silence (and even sleep) in establishing an eiruv.  The rabbis deliberate over when and how one might prepare food on a Festival for Shabbat, or on Shabbat for a Festival.  They also consider how far one might be able to travel in placing an eiruv on one day in one place and then on another day in another place.  

Interestingly, the rabbis themselves seem confused about which former esteemed rabbis held which opinions.  The ease with which they accept their lack of definitive answers is fascinating.  And, as an extension of this idea, it is amazing to me that the rabbis continually speak of amending baraitot.  Baraitot are the learnings that inform the Mishnah from outside of the Talmud altogether.  If the baraitot are used as prooftexts, how can they be so easily amended when the rabbis need a particular prooftext to strengthen their arguments?  Isn't the point of a prooftext the reference to something that is more definitive, not less?

As someone who did not grow up knowing any of the halacha of eruvin, the concept of an eiruv is almost entirely theoretical.  I wonder about the seemingly arbitrary nature of these debates and these halachot... lives can be made incredibly difficult through the use of this text.  And of course I'm sure that lives also are enriched for those who find the halacha useful.  Any action can become "spiritualized" with intention and with systemic support.  At least the laws of eiruvin are not tremendously invasive or potentially traumatizing.  As far as I know, anyhow.

No comments:

Post a Comment