ELKANAH WAS AN EPHRATHITE FROM RAMAH OF BENJAMIN

Note to Readers: This was an article of mine recently published in Bibliotheca Sacra  182 (April-June 2025), 163-77. It’s more technical than most of my articles on this blog, but feel free to have a read! (All footnotes have been included here as Endnotes. I’ve also noticed that the footnote notations have not appeared. Sorry for that inconvenience.)

ELKANAH WAS AN EPHRATHITE FROM RAMAH OF BENJAMIN

ABSTRACT

Much disagreement exists in the scholarly literature concerning the identity and home of Elkanah. The problem concerns the meaning of the phrase “hill country of Ephraim” and the word אֶפְרָתִי in 1 Samuel 1:1. Also of key importance is the uncertainty over the geographical location of Ramathaim and Ramah (and whether they are different locales or one and the same), the Land of Zuph (1 Sam. 1:1; 9:5), and the burial place of Rachel (1 Sam. 10:2; cf. Gen. 35:16, 19: 48:7). 

This paper seeks to demonstrate that: 1) The “hill country of Ephraim,” includes the tribal territory of Benjamin; 2) Ramathaim and Ramah are the same town located in the tribe of Benjamin (probably modern er-Ram); 3) The grave of Rachel should be located in the tribal territory of Benjamin near Ramah; and, 4) The context of 1 Samuel 1:1 suggests אֶפְרָתִי is best understood as “Ephrathite.” If true, these four conclusions remove any contradictions and demonstrate the consistency of the Samuel narrative regarding the hometown of Elkanah and Samuel.

PROBLEM: THE IDENTITY AND HOME OF ELKANAH

The introduction of Elkanah in 1 Samuel 1:1 provides background information regarding his ancestry and place of residence. The problem, at least for the modern reader, is that several geographical details and names are open to more than one interpretation. For example, the phrase, “hill country of Ephraim,” and the word אֶפְרָתִי, can suggest that Elkanah is a member of the tribe of Ephraim. However, אֶפְרָתִי can also refer to someone who is an Ephrathite (cf., 1 Sam. 17:12). Other biblical passages also provide evidence that “the hill country of Ephraim,” encompassed more than just the tribal territory of Ephraim (e.g., Judg. 4:5). Furthermore the name of Elkanah’s hometown, Ramathaim, is found only here. Elsewhere he (and his son Samuel) are said to be from Ramah (e.g., 1 Sam. 2:11). Do two different names for Elkanah’s (and Samuel’s) hometown suggest two different places? This question is important, for if Elkanah’s home of Ramathaim is in Ephraim, it is equally clear from passages in 1 Samuel that Samuel’s hometown of Ramah is in Benjamin (e.g., 1 Sam. 7:16-17). How then, is this to be explained? 

A related problem concerns Saul’s initial encounter with Samuel in the land of Zuph (1 Sam. 9:5ff.). Is the land of Zuph in the tribal territory of Ephraim, as possibly suggested by 1 Samuel 1:1 and Saul’s travels in 1 Samuel 9, or does Saul’s encounter take place in Ramah of Benjamin? The text’s testimony regarding the home and identity of Elkanah concerns the question of whether it presents a mixed, and thus confused, geographical picture, or one that is accurate and coherent. This paper seeks to address this question. 

Miller has pointed to four contributing factors related to potential geographical confusion over biblical sites: 1) Biblical writers assume the readers are familiar with the geography of Benjamin, and, therefore, do not provide much detail; 2) A number of Benjaminite names are appellative names that would be duplicated from site to site. For example, Ramah means “the height,” and was a name given to various sites; 3) Modern development in the area of what was ancient Benjamin has made it more difficult to envision what the topography was like in ancient times; and, 4) Literary-critical analysis, which Miller believes has led to the widest divergence of opinion among scholars. Miller’s own view is that biblical stories “. . . provide authentic memory of ancient Benjaminite toponymy. [However], During the process of transmission from ancient times to the present . . . this memory has been skewed in places.” 

Each of these factors present challenges, to the modern scholar and should be given due consideration when reaching any conclusions. It is important to remain open to alternative explanations, and to the possibility of new discoveries which may clarify some issues of interpretation or geography. With that in mind, this paper will suggest the biblical data regarding Elkanah’s identity and home can be reconciled without contradiction, while certain aspects must remain tentative (e.g., the exact location of Ramah, or Rachel’s tomb). What follows is an investigation of each of the key words and phrases describing Elkanah’s identity and geographical location.

WHAT GEOGRAPHICAL AREA IS MEANT BY “THE HILL COUNTRY OF EPHRAIM?”

When reading the phrase, “the hill country of Ephraim,” it seems natural that a modern reader would interpret this to mean the hill country contained within the tribal territory of Ephraim. It appears that some scholars have come to a similar conclusion. If one makes this assumption, then it is natural to conclude that 1 Samuel 1:1 is stating that Elkanah’s hometown of Ramathaim, and the land of Zuph, must be in Ephraimite territory. Later passages that suggest that Elkanah’s (and Samuel’s) home is in Ramah of Benjamin would, then, be understood to be in conflict with 1 Samuel 1:1. Kyle McCarter draws this conclusion. He writes,

Apparently there is confusion in the tradition itself. The older narrative recorded Samuel’s home as Ramathaim of the land of Zuph in the Ephraimite hills. In the course of the transmission of the story, the name became associated with the much more familiar Benjaminite Ramah. The result is a mixed picture. In the present episode there is no barrier to maintaining the assumption that Ephraimite Ramathaim is intended.

Miller comes to a similar conclusion:

Note . . . the apparent confusion concerning the identity and location of Samuel’s family home. 1 Samuel 1:19; 2:11; and 7:17 associate Samuel and his father Elkanah with Ramah. Yet the story in 1 Samuel 9–10, Saul’s search for the Donkeys, associates Samuel with the “land of Zuph,” while 1 Samuel 1:1 identifies Elkanah as an Ephraimite from Ramathaim-zophim. This confusion, in my opinion, . . . is to be explained on literary-critical grounds.

Other scholars also conclude that 1 Samuel 1:1 is stating that Elkanah’s home is in the tribal territory of Ephraim, but that other texts place his home in Ramah of Benjamin. 

There are texts, however, that suggest the hill country of Ephraim encompasses a wider geographical area. Judges 4:5 informs us that Deborah held court under a palm tree between Bethel and Ramah “in the hill country of Ephraim.” This is clearly Benjamite territory and illustrates that the hill country of Ephraim has a wider geographical reference than the tribal territory of Ephraim. Another passage which may identify the tribe of Benjamin with the hill country of Ephraim is 2 Samuel 20 concerning the rebellion of Sheba ben Bichri. Sheba is identified as a Benjamite (2 Sam. 20:1) who was from the hill country of Ephraim (2 Sam. 20:21). Rainey and Notley rightly state, “The ‘hill country of Ephraim’ is a generic geographical term for the entire block of hills that included the territory of Benjamin, Ephraim and Manasseh.” The tribe of Ephraim’s prominence appears to be the explanation for this designation. The hill country further south, though still part of the same range, became designated as “the hill country of Judah” (Josh. 21:11), due to the prominence of the tribe of Judah. Similarly, the hill country further north was designated as “the hill country of Naphtali” (Josh. 20:7).

A further example of a geographical feature named for the tribe of Ephraim, but not within the tribal boundary is the “forest of Ephraim,” where David’s men battled Absalom (2 Sam. 18:6). This battle most likely took place on the other side of the Jordan in the area of Gilead, not within the tribal border of Ephraim (2 Sam. 17:24).  

That the hill country of Ephraim also includes the tribe of Benjamin has been noted by several recent scholars. Context is therefore important when deciding what is meant by the “hill country of Ephraim.” Just because Elkanah lived in the hill country of Ephraim, does not automatically rule out that he lived within the tribal territory of Benjamin, nor does it mean that he must be an Ephraimite. The misidentification of Elkanah’s home with the tribe of Ephraim has ramifications for other related texts which we will examine below.

RAMATHAIM AND RAMAH: TWO CITIES, OR TWO DESIGNATIONS FOR THE SAME CITY?

The name Ramathaim has puzzled many scholars. 1 Samuel 1:1 is its only occurrence. Elsewhere, both Elkanah (1 Sam. 1:19; 2:11) and Samuel (1 Sam. 7:17; 15:34) are said to have lived in Ramah. Two names and seemingly, two different locations (one in Ephraim, one in Benjamin), have led to the confusion. For example, while convinced that 1 Samuel associates Samuel with Ramah of Benjamin (er-Ram), Klein notes that, based on the identification by Eusebius and Jerome, modern scholars associate Ramathaim with Rentis about 16 miles east of Tel Aviv. Klein further asserts that “Ramathaim is the same as Arimathea in the NT (Matt 27:57).” This leads him to conclude that, “. . . the first verse of the book—and possibly v 19 and 2:11—represent an alternate, Ephraimite tradition.” This conclusion, however, is based on two assumptions. First, that the “hill country of Ephraim,” must refer to a person living within the tribal boundary of Ephraim. Second, that the Hebrew term אֶפְרָתִי, refers to a person living in Ephraim. If these assumptions are removed, then it becomes possible to view Ramathaim and Ramah as two names for the same place as several scholars posit.

The dual form in the name Ramathaim should not automatically be interpreted as referring to a town other than Ramah of Benjamin. Other towns and cities in ancient Israel display the same phenomenon. The most famous of these, as noted by Driver, is Jerusalem (yerushalayim). No one would suggest that the singular and dual spellings of Jerusalem refers to two distinct cities. Another example of this phenomenon is Gittaim of Benjamin (2 Sam. 4:3; Neh. 11:33) which appears in the singular form Gath in 1 Chronicles 7:21 and 8:13. Other examples of cities using a dual form include Kiriathaim (Gen. 14:5), Shaaraim, Adithaim, and Gederothaim (Josh. 15:36), to name a few. 

Demsky notes that, “Scholars have explained this linguistic form either semantically or morphologically.”  The semantic approach interprets the dual forms literally. For example, Shaaraim (1 Sam. 17:52) means “two gates,” Naharaim (Judg. 3:8, 10) means “two rivers,” etc. Using this approach, Ramathaim would mean “two hills,” an interpretation which is frequently put forward by many commentators. Demsky, rightly in my opinion, dismisses this approach, for the most part, stating, “In general, these semantic explanations are too simplistic and somewhat fanciful, and are unable to explain most of the names in the dual form either topographically or historically.” The morphological explanation, first put forward by J. Barth, contends, “that this dual ending is an expanded long ām ending with the special meaning of a locative.”  For example, Rainey and Notley conclude, “Ramathaim is the town of Ramah in Benjamin, here with an adverbial locative or directive suffix (homophonous with the dual suffix).” Demsky also rejects the morphological explanation, maintaining that the dual ending in topographical names, “was actually an alternate form of a more common nominal ending.” For our purpose, it is not necessary to choose between Barth’s and Demsky’s explanations. It is enough to note that the use of a dual ending for towns and cities is not an unusual occurrence in ancient Israel. There are several possible explanations for this phenomenon none of which necessitate that the use of the dual form must refer to a different site. The context in Samuel clearly presumes that the Ramathaim of 1 Samuel 1:1 was the same as Elkanah’s home in Ramah (1 Sam. 1:19; 2:11).

EPHRATHITES AND EPHRAIMITES: THE MEANING OF אֶפְרָתִי

Jan Joosten writes, “In Biblical Hebrew, gentilic adjectives can be derived from proper nouns designating a putative ancestor, a clan, a city, an area or a country.”

In the context of 1 Samuel 1:1, אֶפְרָתִי seems to designate an area that Elkanah’s ancestors came from, although a reference to a clan should not be ruled out. Area, or clan, are possible, given the four-generation genealogy in 1 Samuel 1:1. אֶפְרָתִי is an ambiguous term that may refer to someone from the tribe of Ephraim (Judg. 12:5). However, it may also refer to someone from the clan of Ephrath (1 Chron. 2:50-54; 4:4ff.). This clan settled in the northern region of Judah and gave its name to the area, especially the area associated with Bethlehem (e.g., Ruth 1:2; 1 Sam. 17:12). Context is therefore important in determining its meaning. Elkanah, and his ancestors, are designated as אֶפְרָתִי in 1 Samuel 1:1. The mention of the hill country of Ephraim earlier in the verse causes many to assume that Elkanah must be an Ephraimite. Driver’s comments are representative of many when he writes, “This word appears to represent Elqanah not merely as resident in Ephraim (מהר אפרים), but as an Ephraimite.” 

Again, when these assumptions are suspended and one posits that Elkanah’s home was in the tribal territory of Benjamin (which is a part of the hill country of Ephraim), אֶפְרָתִי naturally takes on the meaning Ephrathite (i.e., a person from the district of, and/or descended from the clan of, Ephrath). Other scholars also recognize Ephrathite as the correct rendering in 1 Samuel 1:1. 

There are even scholars who equate the hill country of Ephraim with the tribal territory of Ephraim but maintain that אֶפְרָתִי could be rendered as “Ephrathite” in 1 Samuel 1:1. Tsumura, notes that “. . . the gentilic ’eprātî denotes either a member of the tribe of Ephraim (Judg. 12:5; 1 K. 11:26) or an inhabitant of Bethlehem (1 Sam. 17:12; Ruth 1:2). Elkanah might have been of Bethlehemite stock rather than being an ‘Ephraimite,’ even though he dwelt in the hill country of Ephraim.” 

Again, while supposing that Elkanah lived within the tribal territory of Ephraim, Leuchter makes the following observation: “The verse tells us that Samuel’s father Elkanah has settled in the hill country of Ephraim; the appearance of אפרתי as a reference to Ephraim in the same verse would be redundant.” He continues, 

Other traditions point to sacral figures hailing from Bethlehem and later taking up posts in the Ephraimite hinterland (Judg 17:7–8); Elkanah as an Ephratite sojourning in Ephraim is not an anomaly. We thus have grounds to retain the term אפרתי in 1 Sam 1:1 without emendation, suggesting a strong connection between the religious circles of Ephratah-Bethlehem in Judah and the Shilonites of the Ephraimite hinterland.

While this writer contends it is incorrect to locate Elkanah’s home in Ephraim, the above comments demonstrate that even scholars who do, recognize that אֶפְרָתִי should be read as “Ephrathite.” One reason, similar to Leuchter’s argument above, is that it strengthens the literary tie between the end of the Book of Judges (which ends with two stories about Levites who have connections with Bethlehem and the hill country of Ephraim) and the beginning of 1 Samuel. An Ephrathite origin could also hint at Elkanah’s levitical lineage (along with his descent from Zuph, cf. 1 Chron. 6:33-38), thus, justifying Samuel’s service in the tabernacle and later acting as priest. Furthermore, if Ramathaim is the same as Ramah and is to be located in Benjamin, as is being argued here, then אֶפְרָתִי must be read as “Ephrathite” because Ephraimite would make little sense in the context.

An important related question is, “What exactly is an Ephrathite and does this designation denote someone from Bethlehem?” 1 Chronicles 2:19, 50-54 gives a genealogy of a certain Caleb the son of Hezron of the tribe of Judah (1 Chron. 2:18). After the death of his first wife, Caleb married a woman named Ephrath. Ephrath became the matriarch of a clan that bore her name. Ephrath’s descendants are listed in both 1 Chronicles 2:50-54 and 4:1-10. Ephrath gave birth to various sons who became the ancestors of those who lived in various towns in northern Judah. These towns included Bethlehem, Kirjath Jearim, and Tekoa, among others. According to Demsky’s detailed study of this genealogy, 

Bethlehem . . . was the primary city of the Ephrathites, whose area of settlement extended at first along the mountain range from Kiriath-jearim to Gedor. Secondary expansion went to proximate villages to the west – Manahath, Hushah and probably Bether and Giloh – and to the east around Tekoa. Tertiary expansion moved down to the Shephelah, to sites such as Zorah, Eshtaol and perhaps Sha’araim. Bethlehem was therefore the epicentre for the larger territory of Ephrath.

Ephrath was, therefore, a large area which encompassed a number of cities, but chief among them was Bethlehem. Identifying Elkanah as an Ephrathite could mean that his ancestors came from any area within the Ephrathite domain. The connection with the stories at the end of Judges suggests that Bethlehem might be in mind. Furthermore, there are only two occurrences of אֶפְרָתִי in the books of Samuel and there is no doubt that it should be rendered as “Ephrathite” in the second passage. In 1 Samuel 17:12 David is described as the son of Jesse “that Ephrathite from Bethlehem.” The fact that the only other occurrence of אֶפְרָתִי is in 1 Samuel 1:1 suggests these two passages should be compared. The use of the word to describe only these two individuals (and their families), suggests a possible link between the two. This is borne out literarily. Elkanah parallels Jesse, as both are fathers of sons who will bring deliverance to Israel. Samuel and David are not only parallel as deliverers, but are directly connected through Samuel’s anointing of David as king.  

THE LAND OF ZUPH AND THE TOMB OF RACHEL: LOCATION, LOCATION, LOCATION!

Two other passages that bear on the location of Samuel’s Ramah occur in the introductory story of Saul. When Saul went looking for his father’s lost donkeys, he traveled through the hill country of Ephraim, eventually coming to the land of Zuph and the city of Samuel (1 Sam. 9:4-6). Following his anointing by Samuel, he was given three signs to confirm his anointing. One of those signs involved going by the tomb of Rachel which is described as being “in the territory of Benjamin at Zelzah” (ESV, 1 Sam. 10:2). The mention of the “land of Zuph” automatically recalls 1 Samuel 1:1. Understanding the land of Zuph to be in the tribal territory of Ephraim has led some scholars to suggest a contradiction with 1 Samuel 9:4-5 which places Zuph in the territory of Benjamin. 

Similarly, certain passages in Genesis (35:16-20; 48:7) may be interpreted as locating Rachel’s tomb near Bethlehem (which aligns with the current tradition in Israel). These call into question 1 Samuel 10:2, which places Rachel’s tomb in the territory of Benjamin, near Ramah. In this section these passages will be examined and it will be demonstrated that Ramah of Benjamin is once again the best choice when all the data is considered. If it is allowed that ancient Israelite authors knew their history and geography well, then a solution that solves any apparent contradictions should be considered superior to an interpretation that suggests irreconcilable differences.

The Location of the Land of Zuph. One of the challenges in understanding Saul’s journey in looking for his father’s lost donkeys is that several of the place names have not been confidently identified geographically. As Gilmour notes, “Many scholars have attempted to locate these place names but no consensus has yet been reached.” Diana Edelman has also observed that, 

1 Sam. 9:1-10:16 has been the subject of many diverse investigations over the past 135 years. No single route and series of identifications has gained acceptance, however, and some scholars have despaired that it is impossible to reconstruct the journey on the basis of the scanty evidence available.” 

The mention of “the hill country of Ephraim,” leads many scholars to assume that Saul’s search carried him into the tribe of Ephraim. This seems doubtful for, as already noted, the hill country of Ephraim can apply to the tribe of Benjamin as well. In reading the passage it seems that “the hill country of Ephraim” is a summary statement of the area traversed by Saul and his servant. 

Equating the hill country of Ephraim with the tribal territory of Ephraim leads Edelman to suggest that Saul began his search outside of the tribe of Benjamin.  The basis of this contention is that the text does not name his hometown and therefore the point of his departure is unknown. While true, the most natural reading of the context suggests that Saul left from his family home and that after three days he was concerned to return there knowing his father would be worried about him (1 Sam. 9:3, 5). It makes little sense for Saul’s search to have begun in Ephraim, rather than starting near his home. As McCarter notes, “Saul began his search, as we might expect, ‘in his own backyard.’” 

If Saul began his search from Gibeah of Benjamin, then the lands of Shalishah, Shaalim, Yamin, and finally, Zuph would suggest an ever-widening search for the donkeys in these districts. Cogan and Tadmor state that these names represent family districts in the territory of Benjamin. This certainly fits the designation of the land of Zuph which echoes the ancestral area Elkanah is from (1 Sam. 1:1). It is in the land of Zuph that Saul encountered Samuel at Ramah. This appears to be the northern limit of his search. After three days of wandering all over the territory between Gibeah and Ramah (cf. 1 Sam. 9:20), Saul was ready to return home. 

A three day journey, or period of time, is very common in Scripture (e.g., Gen. 22:4; 30:36; Exod. 5:3; 15:22; Num. 33:8; Josh. 1:11; 1 Sam. 20:19; 2 Sam. 20:4; 1Kgs. 12:5; 2 Kgs. 2:17; 1 Chron. 12:39; Jonah 1:17; 3:3). “In the biblical world, three days was a typical period of preparation for something important.” This observation is appropriate to the context here where Saul’s three-day search for the donkeys ended with a sacred meal (1 Sam. 9:19-24) and his anointing by Samuel (1 Sam. 10:1). Context appears to determine whether the three days represents a short or long period of time. For example, the description of Nineveh being a city that takes three days to traverse, suggests a very large city (Jonah 3:3). However, Moses’s request to Pharaoh that the Israelites make a three-day journey into the wilderness to sacrifice to Yahweh, suggests a short journey (Exod. 5:3).

While it is not impossible, it seems a stretch to suggest, as a number of scholars do, that Saul’s search encompassed an area of sixty miles in these three days. This sixty-mile distance is based on the assumption that Saul’s journey took him into the tribal territory of Ephraim. While identification of the geographical regions remains in doubt, it seems that such an area is too large for a three-day search. It is more realistic to suppose that the donkeys would not have wandered that far away and that a thorough search of the area between Gibeah and Ramah would easily take three (or parts of three) days. We are not talking a search in a direct line between Gibeah (modern Tel el-Ful) and Ramah (modern er-Ram), only a distance of about 2 miles or 3 kilometers, but a slow, methodical, ever widening search, traversing east and west in mountainous terrain between these two cities. It also makes more sense for Saul’s father to be worried about him being gone three days if the distance was short, than if a wider area had been canvassed. One would assume that a search of sixty miles would take some significant time, whereas a search in the vicinity of one’s home should be concluded more quickly. Based on the report by the men at Rachel’s tomb (if the tomb is near Ramah), it does appear that the donkeys did not wander far. Therefore, unless further geographical evidence is produced in the future that proves otherwise, nothing suggests that Saul’s search took him beyond the tribal limits of Benjamin.

The Location of Rachel’s Tomb. Another geographical uncertainty of the early chapters of 1 Samuel is the location of Rachel’s tomb. Although 1 Samuel 10:2 and Jeremiah 31:15, firmly locate it in the territory of Benjamin, other scholars point to Genesis 35:16-20 and 48:7 which mention Ephrath, further identifying the area as near Bethlehem. To complicate matters a traditional tomb located near Bethlehem today is identified as Rachel’s tomb. While most scholars maintain that the original site of Rachel’s tomb is in Benjamin, there are a few who prefer the Bethlehem location. 

Na’aman has presented the most thorough case for defending the Bethlehem location. He argues that the Bethlehem tradition is older, going back to the Ephrathites who moved into the area from the tribe of Ephraim. Na’aman also believes that the tradition of Rachel’s tomb in Benjamin goes back to a wrong identification which equates the tomb of Deborah (Rachel’s nurse) with Rachel’s tomb (see Gen. 35:8). 

When read carefully, however, the Genesis texts do not locate Rachel’s tomb near Bethlehem. Genesis 35:16 states that Rachel gave birth after leaving Bethel while “still some distance from Ephrath” (ESV, NASB). Genesis 35:19 similarly states that Rachel was buried “on the way to Ephrath” (ESV, NASB). When Jacob retells the story (Gen. 48:7), he uses the same expressions found in Genesis 35:16 and 19. Demsky writes, 

The idea that Rachel dies near Ephrat (or Bethlehem), just before they got there, is based on a misunderstanding of the phase דרך ‘the road to’ or לבוא ‘the way of/approaching.’ In the Bible, and in general, a road is named after the destination, so it is called ‘the way of Ephrat’ because that is where they were going, but it does not mean they were anywhere near there.” 

Sarna points out that a Bethlehem location for Rachel’s tomb is unlikely because Genesis 35:21 states that after burying Rachel, Jacob moved on to Migdal Eder which is identified with a section of Jerusalem (cf. Mic. 4:8). If Rachel was buried near Bethlehem, Jacob would have had to reverse his direction. Instead, Sarna supports Kiriath Jearim as the most likely place for Rachel’s tomb (it being on the Benjamin/Judah border in an area identified with Ephrath). Sarna is not alone in this conclusion. However, there is no ancient or modern tradition connecting Rachel’s tomb with Keriath Jearim. Based on the biblical texts, Ramah of Benjamin remains the best option. 

One objection to Ramah as the site of Rachel’s tomb is that Jeremiah 31:15 does not use the Hebrew article he (ה). Normally, when referencing the city of Samuel, Ramah does include the Hebrew article. Thus, some suggest that Jeremiah 31:15 is using the word in its natural Hebrew meaning of “height.” However, Jeremiah 40:1 makes it clear that Ramah was the place from which the exiles were carried away to Babylon and Jeremiah 31:15 is referring to this same event. 

Based on a study by Ernst Vogt, Wenham notes that the Hebrew word כִּבְרַת (used in Gen. 35:16; 48:7, and translated as “still some distance”) “. . . equates Hebrew ברה with Akk. bēru, the distance traveled in two hours, roughly eleven kilometers or seven miles.” The distance from Ramah (er-Ram) to Bethlehem is slightly farther, being ten miles or 16 kilometers. If כִּבְרַת is being used in an approximate way, as seems likely from the context in Genesis, then a location near Ramah is reasonable. In fact, Vogt states that the distance communicated by כִּבְרַת is not exact but depends on the time and the gait of a person. Based on the Genesis texts (and 1 Samuel 10:2), Vogt argues that the distance being specified by כִּבְרַת is the distance between Rachel’s tomb (near Ramah) and Ephrath. Thus, there is no need to conclude that a discrepancy exists between the Genesis accounts of Rachel’s tomb and the accounts in 1 Samuel 10:2 and Jeremiah 31:15.

SUMMARY AND CONCLUSION

It has been demonstrated that the “hill country of Ephraim,” also encompasses the tribal territory of Benjamin and that Ramathaim is another name for Ramah, the dual form being a characteristic of other ancient city names. If then, Ramah of Benjamin is the location of Elkanah’s hometown, אֶפְרָתִי in 1 Samuel 1:1 should be understood as “Ephrathite.” The connection with the end of the Book of Judges (Judg. 17:7-8; 19:1) as well as the connection with Jesse the father of David (1 Sam. 17:12), further strengthens this interpretation. 

We have also noted that Saul’s search for his father’s lost donkeys need not have taken him beyond the border of Benjamin. In fact, it seems more likely that his search was in a relatively smaller area (between Gibeah and Ramah) than what some scholars suggest, given the three-day time frame of his search and what is realistically known about the complexities and time element involved in such a search. Thus, when Saul met Samuel in 1 Samuel 9:10-14, the city was Ramah of Benjamin and not a Ramah or Ramathaim in the tribal territory of Ephraim as some assert. 

We have also demonstrated that there is no conflict between the texts in Genesis and 1 Samuel 10:2. The Genesis texts are more vague in their location of Rachel’s tomb, giving only the general area, which plausibly includes the southern part of the tribal territory of Benjamin. In contrast, 1 Samuel 10:2 and Jeremiah 31:15 clearly locate Rachel’s tomb in Ramah of Benjamin. Vogt, followed by Wenham, has argued that the word כִּבְרַת can reasonably refer to the distance between Ramah and Ephrath.

All scholars are in agreement that the text of 1 Samuel locates the home of Samuel in Ramah of Benjamin (most concluding it is the modern er-Ram). When all of the evidence is considered, it is not only clear that Samuel lived in Ramah of Benjamin, but that his father Elkanah and mother Hannah did as well and that there is no contradiction between the statements of 1 Samuel 1:1, 9:4-5; 10:2, or any other passages in 1 Samuel relating to the identification of his hometown. Thus, the proper understanding of 1 Samuel 1:1 is that Elkanah was an Ephrathite from Ramah of Benjamin.

End Note

  1. All Scripture quotations are from the ESV unless otherwise noted

2 Max Miller, Notes on Benjaminite Place Names,” JNSL 25.1 (1999): 61–62.

3 Miller, 62.

4 P. Kyle McCarter Jr., 1 Samuel, AB 8 (Doubleday, 1980), 61–62.

5 Miller, “Benjaminite Place Names,” 63.

6 For example, Henry Preserved Smith states, “The genealogy given seems to leave no doubt that Elkanah was an Ephraimite by blood.” A Critical and Exegetical Commentary on the Books of Samuel, ICC (T&T Clark, 1992), 5. See also, Tony W. Cartledge, 1 and 2 Samuel, SHBC (Smyth & Helwys, 2001), 27; and A. Graeme Auld, 1 and 2 Samuel: A Commentary, OTL (Westminster John Knox, 2011), 27.

7 C. F. Keil and F. Delitzsch, The Pentateuch, trans. James Martin, vol. 2 of Commentary on the Old Testament (Hendrickson, 1996), 372–73. Conversely, Miller contends that the Benjaminites were southern Ephraim clans that settled in the southern hill country of Ephraim. He believes that Benjamin’s tribal status was a literary rather than a historical development. “Benjaminite Place Names,” 62. While there is no solid evidence for this conjecture, Miller’s theory does not negate the suggestion that the hill country of Ephraim encompassed the tribe of Benjamin.

8 Anson F. Rainey and R. Steven Notley, The Sacred Bridge: Carta’s Atlas of the Biblical World, 2nd ed. (Carta, 2014), 137.

9 For a fuller discussion, see Henry O. Thompson, “Ephraim, Forest of,” in ABD, ed. David Noel Freedman (Doubleday, 1992), 2:557.

10 Jack M. Sasson, Judges 1–12, AB 6D (Yale University Press, 2014), 188; and Mark S. Smith and Elizabeth Bloch-Smith, Judges 1: A Commentary on Judges 1:1–10:5, Hermeneia (Fortress, 2021), 259–60.

11 According to Diana Edelman, “Ramathaim of the Zuphites should not be equated with Ramah of Benjamin, which almost certainly is to be identified with er-Rām. The latter lay within Benjamin, just south of the probable geographical border between the central Ephraimite land masse and the territory of Benjamin.” “Saul’s Journey Through Mt. Ephraim and Samuel’s Ramah (1 Sam. 9:4–5; 10:2–5),” ZDPV 104 (1988): 56. Edelman’s statement illustrates that er-Ram is the presumed site of many scholars were it not for the assumption that the Ramathaim of 1 Samuel 1:1 must be located in Ephraim.

12 Ralph W. Klein, 1 Samuel, WBC 10 (Word, 1983), 5.

13 David Toshio Tsumura, The First Book of Samuel, NICOT (Eerdmans, 2006), 124–25; John B. Song, “Rathamin,” in The Lexham Bible Dictionary, ed. John D. Barry et al. (Lexham, 2016), ebook; and Brandon Ridley, “Ramah of Benjamin,” in Barry, Lexham Bible Dictionary, ebook.

14 S. R. Driver does not believe the dual forms of city names are original but reflect a later artificial expansion of the original. He points out that the Tel el-Amarna letters point to -im as being the original ending for Jerusalem. Notes on the Hebrew Text and the Topography of the Books of Samuel, 2nd ed. (Clarendon, 1913), 1–2.

15 Wesley I. Toews, “Gittaim,” in Freedman, ABD, 2:1030. This Gath should not be confused with the more famous Gath of Judah.

16 Aaron Demsky, “Hebrew Names in the Dual Form and the Toponym Yerushalayim,” in These Are the Names: Studies in Jewish Onomastics, ed. Aaron Demsky, vol. 3 (Bar-Ilan University Press, 2002), 11–20.

17 Demsky, 12.

18 Demsky, 12.

19 Rainey and Notley, Sacred Bridge, 143. See also Yohanan Aharoni, The Land of the Bible: A Historical Geography, 2nd ed., trans. and ed. A. F. Rainey (Westminster, 1979), 120.

20 Demsky, “Hebrew Names,” 13. Demsky’s reasons for his assertion are beyond the scope of this paper.

21 Jan Joosten, “Construct-Phrase Gentilics: A Distinctive Feature of Classical Biblical Hebrew,” Orientalia Suecana 73 (2024): 61.

22 Some scholars suggest that this is an etymological coincidence. John Mauchline, for example, states, “Ephrathah is derived from a Hebrew verb which means ‘to be fruitful’ (pārāh). Its use for more than one area is intelligible.” 1 and 2 Samuel, NCB (Oliphants, 1971), 42. See also, Lamontte M. Luker, “Ephrathah (Place),” in Freedman, ABD, 2:557-58. On the other hand, Nadav Na’aman contends that ephrati originally referred to Ephraimites who migrated southward into northern Judah, and the area of Ephrath received its name from these Ephraimite immigrants. “The Settlement of the Ephrathites in Bethlehem and the Location of Rachel’s Tomb,” RB 29–516 :)2014 (121.4)

23 Folker Willesen, however, argues that even in Judges 12 the word should be translated “Ephrathite.” “The יתרפא of the Shibboleth Incident,” VT 8.1 (1958): 97–98. Mark Leuchter also argues that the designation יִתָרְפֶא has a theopolitical importance “in presenting Jeroboam as a legitimate Davidic type.” “Jeroboam the Ephratite,” JBL 125.1 (2006): 60.

24 Hans Wilhelm Hertzberg states, “Elkanah . . . is described as an Ephrathite. Here the word is meant to indicate the Ephraimite descent of the family and not, as in Ruth 1:2 (cf. Micah 5:2), to describe a clan of Bethlehem.” 1 and 2 Samuel: A Commentary, trans. J. S. Bowden, OTL (Westminster, 1964), 22–23. Hertzberg’s differentiation appears to be based on his assumption that “the hill country of Ephraim” must mean the tribal territory of Ephraim.

25 Driver, Notes on the Hebrew Text, 4 (emphasis original).

26 David G. Firth, 1 and 2 Samuel, ApOTC 8 (InterVarsity Press, 2009), 49; and Harry A. Hoffner Jr., 1 and 2 Samuel, Evangelical Exegetical Commentary (Lexham, 2015), 1 Samuel 1:1, ebook.

27 Tsumura, First Book of Samuel, 107 (emphasis original).

28 Leuchter, “Jeroboam the Ephratite,” 60.

29 Leuchter, 61

30 Many scholars note the connection between the end of the Book of Judges and the beginning of 1 Samuel. For example, J. P. Fokkelman states, “In Hebrew narrative art a geographical name is often more than a neutral spatial co-ordinate. This phenomenon is well-illustrated by the end of Judges and the beginning of Samuel.”Vow and Desire, trans. L. Waaning-Wardle, vol. 4 of Narrative Art and Poetry in the Books of Samuel, SSN 31 (Van Gorcum, 1993), 6. See also Robert Polzin, 1 Samuel, part 2 of Samuel and the Deuteronomist: A Literary Study of the Deuteronomic History (Indiana University Press, 1989), 23–24, 29–30; and Johanna W. H. van Wijk-Bos, The Road to Kingship: 1–2 Samuel, A People and a Land 2 (Eerdmans, 2020), 16-17.

31 Hoffner makes a similar observation. 1 and 2 Samuel, 1 Sam 1:1, ebook.

32 Aaron Demsky demonstrates that there is a chiastic layout to these chapters, and he provides a helpful map detailing the area of the Ephrathites. The Clans of Ephrath: Their Territory and History,” TA 13.1 (1986): 46–59.

33 Demsky, 51 (emphasis suppressed)

34 McCarter, for example, takes exception with the reading of the Masoretic Text, since he is convinced that Zuph must be in Ephraim. He writes, “As generally agreed MT ʾere yĕmînî, “the land of Benjamin” (!), cannot be correct. Saul, who has been traveling for some time, is about to reach the land of Zuph. To assume that he has somehow doubled back to Benjamin leaves any reconstruction of the itinerary in shambles.” 1 Samuel, 174.

35 Not all will agree with this presupposition of course, but it seems more reasonable to trust the accuracy of the ancient authors (or redactors), who were closer to the events and geography, than to trust modern interpretations, which are farther removed. The fact that many modern interpreters equate “the hill country of Ephraim” with only the tribal territory of Ephraim is a case in point.

36 Rachelle Gilmour, “Suspense and Anticipation in 1 Samuel 9:1–14,” JHebS 9 (2009): 9, https://doi.org/10.5508/jhs.2009.v9.a10.

37 Edelman, “Saul’s Journey,” 44. For a detailed summary of the various itineraries suggested by scholars, see 44–48.

38 Edelman notes that K. Budde observed this in 1881. Because Edelman supposes that “the hill country of Ephraim,” must refer to Ephraimite territory, she contends that Budde contradicts himself because he locates the various areas mentioned in 1 Samuel 9:4 within the tribal territory of Benjamin (48).

39 Edelman, 50.

40 McCarter, 1 Samuel, 174.

41 Yamin is often translated as “Benjamin,” which is a possible meaning. Tsumura states, “The term seems to be a designation of a district like Shalishah and Shaalim rather than of the tribal group.” First Book of Samuel, 264n10.

42 Mordechai Cogan and Hayim Tadmor, 2 Kings, AB 11 (Yale University Press, 1988), 59.

43 Bruce K. Waltke, Genesis: A Commentary (Zondervan, 2001), 307.

44 Scholars can be found who support both positions. For example, D. E. Garland states, “ ‘The Third Day’ is a Semitic idiom referring to an unexpectedly short period of time.” “Third Day,” in ISBE, ed. Geoffrey W. Bromiley (Eerdmans, 1977–88), 4:840. On the other hand, Rhiannon Graybill, John Kaltner, and Steven L. McKenzie reference two earlier scholars (Bauer 1958; Eynikel 2005) when they maintain that “three days as a measure of time is frequently a topos for a relatively long period.” Jonah, AB 24H (Yale University Press, 2023), 224 (emphasis original)

45 McCarter, 1 Samuel, 163, has a map of Saul’s travels that suggests a wide area covered while looking for the lost donkeys. V. Philips Long states that if the areas mentioned in 1 Samuel 9:4 are in Ephraimite territory, then Saul’s search covered some sixty miles over its three-day duration. 1 Samuel,” in Zondervan Illustrated Bible Backgrounds Commentary, ed. John H. Walton (Zondervan, 2009), 2:312. Driver states that to cover this distance in three days “does not seem very probable.” Notes on the Hebrew Text, 70.

46 There is nearly unanimous agreement among scholars that modern Tel el-Ful should be equated with ancient Gibeah. For a summary of the evidence and various identifications of Gibeah, see S. Shalom Brooks, Gibeah, Geba,” in Dictionary of the Old Testament: Historical Books, ed. Bill T. Arnold and H. G. M. Williamson (Inter-Varsity Press, 2005), 330–32.

47 There is still some question as to the location of Ramah of Benjamin. Most scholars suggest modern er-Ram, which correlates well with the biblical data (e.g., Judg 19:13; Isa 10:29; Hos 5:8). See Patrick M. Arnold, “Ramah,” in Freedman, ABD, 5:613–14. The vicinity of present-day Ramallah is also suggested by some, such as Aaron Demsky, based on the assumption that 1 Samuel 1:1 locates Elkanah’s home near the border of Ephraim and Benjamin. “Where Was Rachel Buried?,” TheTorah.com, updated 2023, https://www.thetorah.com/article/where-was-rachel-buried.

48 The Manasseh Hill Country Survey begun by the late Adam Zertal in 1978 is still in process. The survey consists of a small team meeting each Friday and traversing the country on foot searching for ancient sites. This survey, a little farther north than where Saul and his servant would have been searching for the lost donkeys, illustrates what a painstaking task it is to search for something in the central hill country and the length of time involved in such a search. Serge Frolov, while assuming a larger search area, makes the same point: “All reconstructions of Saul’s journey, including my own . . . represent his route as a line. It is obvious, however, that simply pushing forward would be an ineffective way of looking for the lost animals. If Saul and his servant ever cared about finding their livestock, they had no other choice but to comb one area after another; this is why it took them three days (9.20) to reach the city of anointing that could hardly be more than a dozen miles away.” “The Semiotics of Covert Action in 1 Samuel 9–10,” JSOT 31.4 (2007): 435n10

49 The current structure dates to the Crusades. However, Matitiahu Tsevat points out that the location of Rachel’s tomb (whether in Benjamin or Judah) was already confusing rabbis in the early centuries AD. Studies in the Book of Samuel: Interpretation of 1 Samuel 10:2: Saul at Rachels Tomb,” HUCA 33 (1962): 107n1.

50 E.g., R. Riesner, “Archeology and Geography,” Dictionary of Jesus and the Gospels, ed. Joel B. Green and Scot McKnight (InterVarsity Press, 1992), 34.

51 Na’aman, “Settlement of the Ephrathites,” 516–29. See also, Serge Frolov and Vladimir E. Orel, A Nameless City,” JBQ 23.4 (1995): 252-56.

52 Demsky, “Where Was Rachel Buried?”

53 Nahum M. Sarna, Genesis, JPS Torah Commentary (Jewish Publication Society, (1989), 408.

54 See e.g., Tsevat, “Studies in the Book of Samuel,” 112.

55 Victor P. Hamilton, The Book of Genesis: Chapters 18–50, NICOT (Eerdmans, (1995), 386.

56 Ernst Vogt, “Benjamin geboren ‘eine Meile’ von Ephrata,” Bib 56.1 (1975): 30–36.

57 Gordon J. Wenham, Genesis 16–50, WBC 2 (Word, 1994), 32

58 Vogt, “Benjamin geboren,” 34.

 

Logos 2026 Gold Researcher Library

Logos 2026 Gold Researcher Library

Logos 2026 Gold Researcher Library
Logos 2026 Gold Researcher Library

In my last post I announced Logos’s introduction of their new 2026 library and gave a general overview of some features. In this post, I want to focus on the Logos 2026 Gold Researcher Library which I currently own.

Help For Translators in Logos 2026 Gold Researcher Library

This series is included in the Logos 2026 Gold Researchers Library.
This series is included in the Logos 2026 Gold Researchers Library.

There are 171 commentaries included in the Logos 2026 Gold Researcher Library. One of the best series is the United Bible Society (UBS) Handbook series on both the OT and the NT. These volumes provide insight into the original languages, along with practical advice about how to translate into other modern languages.  Also included are 14 volumes of Classic commentaries on the Greek NT. Although these are a bit older, they include the insights of important scholars of the past such as B.F. Westcott and J.B. Lightfoot. The International Critical Commentary on the OT and NT is also a part of this collection. This series includes older and newer volumes. Although this is not my “go to” series, because of its Higher Criticism approach, it does include important scholarship and focuses on examining the original text.  One of the intriguing new commentary series offered here is the Illuminations Commentary. According to the description on Logos, “The Illuminations Commentary Series is an innovative resource for all who are interested in engaging the Bible in depth. The author of each volume employs the full range of biblical scholarship to illumine the text from a wide variety of perspectives, including the engagement and impact of the text through the centuries.” Currently only 3 volumes are available (Jonah, Micah, and Job 1-21). I look forward to exploring these volumes.

Hebrew and Greek Texts and Grammars in Logos 2026 Gold Researcher Library

Included in the Logos 2026 Gold Researchers Library
Included in the Logos 2026 Gold Researchers Library

For researchers, as well as translators and advanced students, the Logos 2026 Gold Researcher Library has a good number of Greek and Hebrew resources. The following description is just a sample of what is available. Texts include a copy of Codex Sinaiticus (!), as well as a few Greek New Testaments. For Old Testament study in Greek, Rahlfs Septuagint is also included.  For Hebrew OT studies, a copy of BHS is included, as well as an “Introduction to the Hebrew Bible,” by John J. Collins and “The Parallel Aligned Hebrew-Aramaic and Greek Texts of Hebrew Scripture,” by renowned textual scholar Emmanuel Tov. Various Greek grammars (e.g., Louw & Nida), Metzger’s “Textual Commentary on the Greek New Testament,” and 2 Theological Word Dictionaries (one being an abridged volume of TDNTA) are also included. There are 4 Hebrew grammars, as well as 3 Hebrew dictionaries. The final resource to mention in this category is the 11 volumes of the “Biblical and Ancient Greek Linguistics” Journal (issues from 2012-2023).

My Favorite Aspects of the Logos 2026 Gold Researcher Library

Several volumes of the LNTS are included in the Logos 2026 Gold Research Library.
Several volumes of the LNTS are included in the Logos 2026 Gold Research Library.

Although I am excited about the commentary and Greek and Hebrew resources, there are 2 other aspects of this library that are my favorite. The first is a collection of the “Studies in Scripture & Biblical Theology,” by Lexham Press. This includes OT and NT volumes. In the OT this includes such titles as “Evil in Genesis: A Contextual Analysis of Hebrew Lexemes for Evil in the Book of Genesis,” and “Reading the Psalms Theologically,” to name only two. The NT includes “The Word of God Has Not Failed: Paul’s Use of the Old Testament in Romans 9,” and others. Also included are a number of volumes in the LHBOTS (The Library of Hebrew Bible/Old Testament Studies), and the LNTS (Library of New Testament Studies). Clicking any of the links in this post will take you to the page where you can compare and contrast libraries if you interested in more of the specific selections. A second favorite aspect of this collection for me are the many resources related to the Second Temple Period (some refer to it as New Testament Backgrounds). There are a number of works related to the Jewish Apocrypha and Pseudepigrapha as well as an 8-volume work on the writings of Josephus.

Conclusion

If you are interested in building your Logos Library, now is a good time to do it. The sale lasts until February 15th. Gold is a good library to start with for those who are looking for more in-depth Bible study. It doesn’t matter whether you choose the Standard, a Denominational package, or the Researcher one I have chosen here. If your budget can’t quite handle the Gold package, or if you’re looking for a more general bible study experience, then certainly the Bronze or Silver packages can get you started. As you can tell by perusing my web site, I am a huge Logos fan and believe it is the best tool available today for in-depth bible studyCheck out the sale on the Logos 2026 libraries and receive an extra 20% off.

(Thanks to Logos who provided a copy of this library in exchange for an unbiased review).

 

Logos 2026 Libraries

Logos 2026 Libraries

Logos 2026 libraries
Click on the picture or the link here to check out the Logos 2026 libraries.

The New Year brings fresh starts and that’s also true for those who love Logos Bible Software. This year a Bible software program that just keeps getting better, is introducing the Logos 2026 libraries. Over the next few weeks these libraries are on sale for a 20% discount.  If you are new to Logos, the best way to build valuable resources is to purchase a library. You will receive more books at a reduced cost than you could ever pay for individually. Seasoned Logos users are well aware of the value of these libraries. This post will introduce readers to some of the various options available this year, while focusing on my review of the latest library I have obtained. Seasoned Logos users who are very familiar with Logos libraries may want to skip down to my review of the current 2026 library I am focusing on (see Logos 2026 library: Researches Gold below).

The Variety of Logos 2026 Libraries

Logos 2026 library for Learners

Over the years Logos has grown its libraries to include various specialties. The common library is known as the “Standard” library. This library includes a well-rounded selection of books including Bibles, commentaries, Old Testament and New Testament studies, biblical theology, maps and atlases, biblical languages, devotionals, journals, and counseling, to name a few. Libraries are based on size and begin with a Starter library and graduate to Bronze, Silver, Gold, Platinum, Diamond, Portfolio, and the granddaddy of them all, the Collector’s edition. If a user desires to have a more specialized collection they can browse the categories of Traditions (focused on various denominations such as Anglican, Lutheran, Baptist, etc.), Learner (great for students), Leader (for elders, bible study leaders, etc.), Preacher (needs no explanation), and Researcher (for the teacher or academic).

Logos 2026 Library: Researchers Gold

I have purchased a number of the Standard libraries over the years. Being a teacher at a Bible College, however, I have focused on the Research libraries the last couple of years. The Researchers Gold Library is a good starting point for Teachers and Academics. As with all libraries, cost varies depending on how many of the items you already own in your library. Researchers Gold comes with 16 Bibles, 171 commentaries, 2 Bible dictionaries, and 1 dictionary of theological terms, 25 OT studies and 24 NT studies, and 6 classified as Biblical studies resources. There is an emphasis on original language studies including 24 Greek resources (grammars, bibles, original texts) and 17 Hebrew resources. This library is not only helpful to the scholar, but includes valuable resources for those translating the original languages into modern foreign languages. In my next post, I will give a more detailed description of some of the resources available in this library.

Check out the sale on the Logos 2026 libraries and receive an extra 20% off.
Check out the sale on the Logos 2026 libraries and receive an extra 20% off.

(Thanks to Logos who provided a copy of this library in exchange for an unbiased review).

 

Logos 10: My Favorite New Features

Logos 10: My Favorite New Features

Logos 10 is Here!
Purchase Logos 10 and receive 15% off, or upgrade to Logos 10 and receive 30% off. Each off allows you to choose 5 free books out of a list of 30. Simply use the link here or anywhere on this website.

As some of you may be aware, Logos just launched the newest version of its popular Bible Study software program on 10/10/22. Logos 10 is here! As with every upgrade, Logos 10 adds new features to an already powerful way to study the Bible.  If you read on, I’ll list the newest features pointing out three of my favorites. The links on this page will also entitle new Logos users to a 15% discount off any package plus 5 free extra books out of a list of 30. If you’re already a Logos user then by using one of the links on this page you can receive a 30% discount on any upgrade, plus the same choice of 5 extra free books is also yours! (Offer good until Christmas 2022!) If Logos is brand new to you and you would like a general introduction to it see my article here.

The Newest Features Available on Logos 10

The slogan for Logos 10 is “Live in the Word.” The object is to keep Scripture at the center where it belongs. The new features include:

  1. Advanced Searching–one of the powerful uses of Logos has always been its search capabilities, whether in the Bible or other books in your library. The search feature is now even more powerful and simple to use.
  2. Searching your Print Books–now you can tell Logos what books you have in your physical library. If the book exists in Logos you can use Logos’s searching capabilities to locate something on a particular page.
  3. Expanded Timeline–the Timeline now has extra features including being able to focus on a particular individual, historical period, or theme.
  4. More pop ups with more information–Logos 10 has added 10s of millions of informational tags. Just hover over a word to bring up extra information!
  5. Translation–you can now choose a passage from a book that is in a language you don’t know and Logos will translate it for you!
  6. All your sermons in one spot–If your sermons are in a Word Document format, you can now add them to Logos and keep them in Sermon Manager.
  7. Finding Quotes–If you’re looking for a quote on a certain topic or idea, Logos now allows you to search from thousands of quotes. You don’t even have to have the book! Logos 10 will give you access to the quote, tell you who said it, and what resource it came from!
  8. Toolbar–the location of the Toolbar has changed in Logos 10. It is now on the left side. If you don’t like it there, it can be moved to the top (its more traditional position). The tool bar now has new icons such as the search feature, and the preferred Bible icon. The Toolbar can also be minimized so that more room is available on the screen to see the books you have opened.
  9. Speed!–Logos 10 is much faster than previous versions!
  10. Church History–This feature helps people to understand doctrines in their historical context. There are dozens of new pages in the FactBook tracing various themes.

Favorite Features of Mine

Everyone is going to like/use certain features in Logos 10 more than others. Below are 3 of my favorites.

The Translation Tool

Logos 10 screenshot of translationAs noted above, Logos now includes the ability to translate from and into various languages. For example, if your primary language is English you may want to read a paragraph that’s in German or Latin. It’s no problem now in Logos. Just enable the translator tool and you can scroll through the document getting a side by side translation, or you can highlight a given sentence or paragraph and get a translation of that portion of the text. In the screenshot above I have the English text of Genesis 18 on the left with a German translation on the right. All that’s necessary is to click on the box that says to open or close sidebar (see picture above), then choose the language you want.

Adding Previous Sermons to Sermon Manager

Logos 10 screenshot of Sermon ManagerIf you have sermons that you didn’t create in Logos, now they can be put into Logos. The only requirement necessary is that it be a Word doc. In the example above, I have opened Sermon Manager and added previous sermons of mine by clicking the “Add” button in the upper right (in blue), choosing the sermon and importing it into Logos.

Searching Print Books

Print library in Logos 10
This screen shot shows the print books I have added to my Logos library. In the filter column I chose “Print Library.” I can now search any or all of these resources.

One of the nice features of any version of Logos is being able to search any book you have in your Logos library and find what you’re looking for in an instant. Now in Logos 10 you can do the same with your print library! Instead of thumbing through a book on your bookshelf looking for that particular quote you know is in there somewhere, you can now do it with Logos even if the book isn’t in your Logos library. Just go to your library in Logos, add the book to your “Print books,” and then you can do a search to find the quote you’re looking for.

To see the original video by FaithLife announcing Logos 10 and reviewing its features, click here.

If you would like to take advantage of the Logos 10 sale click this link or the links above.

(Many thanks to Logos for a free upgrade to Logos 10 in exchange for this review. I was not required to give a positive review).

Was King Saul a Victim or a Sinner?

Was King Saul a Victim or a Sinner?

King Saul: Victim or Sinner?
Part of the modern debate concerning King Saul is whether he was a victim or a sinner.

The story of King Saul in the books of 1&2 Samuel is certainly tragic. When Saul dies on the battlefield against the Philistines (1 Sam. 31), it is hard not to feel that a life of great potential has been wasted. As a reader of Saul’s story, I do not celebrate his demise but feel a sense of sadness and grief. Interestingly, David is portrayed as having the same feelings in spite of Saul’s tireless pursuit to destroy him (2 Sam. 1). Some modern commentators have an even stronger reaction to Saul’s story, suggesting that the cards were stacked against him from the beginning. Saul becomes a victim of Yahweh, or Samuel, or the pro-Davidic author. Thus, a modern debate has emerged as to whether King Saul was a victim or a sinner? In other words, were the choices that Saul made responsible for his downfall, or was there a more sinister plan at work? Was there a divine plan that spelled doom for Saul from the very beginning no matter he did? Was he merely a pawn in the Divine game plan of kingship?

Saul Was a Victim: Gunn and Brueggemann

Gunn’s View

Saul as victimAlthough one can find ancient Rabbis who extolled Saul as one of Israel’s heroes, the modern debate was fueled by two scholars in particular. The first of these, David M. Gunn, published a work entitled: The fate of King Saul: An Interpretation of a Biblical Story in 1989, arguing for the victimization of Saul by Israel’s God. In examining the sin of Saul described in 1 Samuel 13 and 15, Gunn concludes: “. . . there is essentially no failure on Saul’s part to be accounted for, no failure, that is to say, for which he can be held seriously culpable” (p. 56). Furthermore, he states, “From the moment of his anointing the future is loaded against him (in the form of the fatally ambiguous instruction of 10:8) and from his establishment as king in chapter 11 it is as though fate has become his active antagonist, thwarting and twisting his every move” (p. 115). For Gunn, this stacking of the deck against Saul, must ultimately be blamed on Israel’s God, Yahweh. Gunn takes a very low view of God, or at least, as he sees how the story presents God. He writes, “Expressed in terms of a story of character and action, however, Saul falls victim to Yahweh’s resentment at an imagined insult (the “sin”) and becomes the pawn (or scapegoat) in a process (the “expiation”) whereby Yahweh vindicates his shift of attitude towards the monarchy and buttresses his shaken self-esteem” (p. 128). That’s about the nicest thing that Gunn has to say about Yahweh’s portrayal in the books of Samuel. He goes further when he writes, “Yahweh manipulates Saul mercilessly, and he does so for what, on most people’s terms, must count as less than honourable motives. He is insulted, feels jealous, is anxious to justify himself. It is tempting to say that this is the human face of God—but to say that would be perhaps to denigrate humankind, which is not something this Old Testament story does; rather we might say that here we see the dark side of God” (p. 129). Gunn’s Star Wars terminology (theology?) is found again in the final lines of his book where he notes that while the David story does show a “light side” to God, when it comes to Saul, the story shows that “God does have a dark side” (author’s emphasis, p. 131).

Brueggemann’s View

Saul was a victimA year following the appearance of Gunn’s work, Walter Brueggemann produced a commentary in the Interpretation series on First and Second Samuel (Brueggemann, W. (1990). First and Second Samuel. Louisville, KY: John Knox Press). Brueggemann also argued that Saul’s fate was predetermined. Although the responsibility for this ultimately must be laid at God’s feet, Brueggemann spends a lot of time villainizing the prophet Samuel. Regarding Samuel’s rebuke of Saul in 1 Samuel 13 he writes, “On all these grounds it appears that Samuel plays a daring, brutal game with Saul’s faith, Saul’s career, and eventually Saul’s sanity. We do not know if Samuel had the oracle in hand and withheld it from Saul or if there never was in fact such a promise. Is the statement only a fabrication designed to torture Saul? We do not know” (p. 101). Brueggemann suggests that Samuel’s antagonistic nature toward Saul might be partially responsible for Saul’s later instability. Brueggemann also casts blame on both the inspired author and God when he states, “If so, Saul’s argument and justification were irrelevant and he never had a chance—because the narrative has stacked the cards in the favor of David; because Samuel is so partisan; because the literature is deeply committed to David, even before David explicitly appears in the literature; because Yahweh had committed to David before the literature was ever cast” (p. 101). Once again Saul is cast as a victim, which leads Brueggemann to conclude: “The outcome is that Saul is defeated by the combination of Yahweh-Samuel-David before he ever joins the struggle” (pp. 101-102).

Saul Was Not a Victim, He was a Sinner

Saul was not a victimMost evangelical commentators take the more traditional interpretation that Saul was rejected because of his own disobedient choices. Robert Vannoy notes the controversy over whether Saul was victim or sinner and states, “While it is clear that Saul faced great difficulties in assuming the responsibilities of his office, it is not so clear that his behavior is properly understood as that of a pawn moved about on the chessboard of life by a malevolent deity” (Vannoy, J. R. (2009). Cornerstone Biblical Commentarya: 1-2 Samuel (Vol. 4, p. 94). Tyndale House Publishers). In a recent commentary, V. Philips Long summarizes Saul’s problem this way: “The heart of his failure is his neglect of the word of Yahweh. Saul obeys up to a point, but that is the problem. He obeys only up to the point at which other concerns begin to carry more weight” (Long, V. P. (2020). 1 and 2 Samuel: An Introduction and Commentary (D. G. Firth, Ed.; Vol. 8, p. 168). IVP Academic: An Imprint of InterVarsity Press.).

Conclusion: Victim or Sinner?

Saul was not a victimThe words “victim” and “sinner” are laden with emotion in today’s society. One is a popular term used to derive pity (and at times to manipulate!), while the other is an unpopular, seemingly judgmental term rarely used. Vannoy notes the power of the term “victim” when he writes, “This approach {i.e., Gunn’s and Brueggemann’s] agrees not only with the opinion that Saul had of himself but also with the contemporary tendency to account for many human failures by appealing to victimization” (p. 94). In spite of the popular “victim mentality,” so prevalent in western society, there are a number of good reasons why 1&2 Samuel picture Saul as a sinner, not a victim.

  1. One of the primary messages of 1&2 Samuel is first enunciated in 1 Samuel 2:30 when God states, “Those who honor me, I will honor, and those who despise me shall be lightly esteemed.” This statement explains the basis on which God raises up some and brings down others (see my article on the theology of Samuel). V. Philips Long  notes this as well (p. 168).
  2. In the Hebrew canon, the books of Samuel fall among the division known as The Prophets. Specifically, 1&2 Samuel are among the Former Prophets (Joshua-2 Kings). Each of these books highlight the importance of the prophetic word. As such, Saul’s continual violation of God’s word demonstrates a disobedient nature. As king, Saul is God’s representative. Therefore, when Saul continues to misrepresent God through his disobedience, his kingship is terminated. The importance of this truth is emphasized in Samuel’s speech in 1 Samuel 12:14-15, 24-25), which immediately precedes the accounts of Saul’s disobedience.
  3. The narrative goes to great lengths to demonstrate that God does everything in his power to set Saul on the right path toward godly kingship. A) God gives Saul 3 confirming signs through Samuel that he has been chosen as king (1 Sam. 10:1-7); B) God changes Saul’s heart (1 Sam. 10:9); C) God fills Saul with his Spirit, Saul prophesies, and people who know Saul are amazed at the change in him (1 Sam. 10:10-13); D) God touches the hearts of valiant men to join Saul and support his kingdom (1 Sam. 10:26); E) God gives prophetic guidance to Saul through Samuel; F) God gives Saul multiple opportunities to demonstrate his obedience.

When all of the above factors are taken into consideration, it becomes apparent that 1&2 Samuel are demonstrating that Saul’s rejection is his own fault. In spite of God’s (and Samuel’s) best efforts, Saul willfully disobeys. Thus, Saul is not a victim; he is a sinner.

I do not mean to minimize the circumstances of those who truly are victims today. There are some, through no fault of their own, who are victimized by evil people. We can even find this in Scripture (e.g., the Levite’s concubine in Judges 19). Saul, however, is not a victim. His story stands as an example for those who choose the path of disobedience and experience its consequences. As unpopular as the term today might be, Saul is a sinner and sin and sinner are words we would do well to add back into our modern vocabulary. Today many are considered victims and few are considered sinners. In reality, however, it is most likely the other way around.