Commentary on Joshua - Keil & Delitzsch - David Cox

Commentary on Joshua - Keil & Delitzsch - David Cox Commentary on Joshua - Keil & Delitzsch - David Cox

davidcox.com.mx
from davidcox.com.mx More from this publisher
22.08.2013 Views

Keil and Delitzsch ong>Commentaryong> on the Old Testament Lake Huleh. There are still many oaks in that neighbourhood ( Rob. Bibl. Res. p. 386); and on the south of Bint Jebail Robinson crossed a low mountain-range which was covered with small oak trees (Pal. iii. p. 372). Adami hannekeb , i.e., Adami of the pass ( Nekeb , judging from the analogy of the Arabic, signifying foramen, via inter montes ), is supposed by Knobel to be Deir-el-ahmar , i.e., red cloister, a place which is still inhabited, three hours to the north-west of Baalbek, on the pass from the cedars to Baalbek ( Seetzen , i. pp. 181, 185; Burckhardt , Syr. p. 60; and Ritter , Erdk. xvii. p. 150), so called from the reddish colour of the soil in the neighbourhood, which would explain the name Adami. Knobel also connects Jabneel with the lake Jemun, Jemuni , or Jammune , some hours to the north-west of Baalbek, on the eastern side of the western Lebanon range ( Rob. Bibl. Res. p. 548; Ritter , xvii. pp. 304ff.), where there are still considerable ruins of a very early date to be found, especially the ruins of an ancient temple and a celebrated place of pilgrimage, with which the name "god's building" agrees. And lastly, he associates Lakkum with the mountains of Lokham , as the northern part of Lebanon on the Syrian mountains, from the latitude of Laodicea to that of Antioch on the western side of the Orontes, is called by the Arabian geographers Isztachri, Abulfeda , and others. So far as the names are concerned, these combinations seem appropriate enough, but they are hardly tenable. The resemblance between the names Lakkum and Lokham is only in appearance, as the Hebrew name is written with q and the Arabic with k . Moreover, the mountains of Lokham are much too far north for the name to be adduced as an explanation of Lakkum. The interpretation of Adami Nekeb and Jabneel is also irreconcilable with the circumstance that the http://207.44.232.113/~bible/comment/ot/k&d/josh/jos121.html (2 of 2) [13/08/2004 01:19:10 p.m.]

Keil and Delitzsch ong>Commentaryong> on the Old Testament lake Jamun was two hours to the west of the red convent, so that the boundary, which starts from the west, and is drawn first of all towards the north, and then to the northeast and east, must have run last of all from the red convent, and not from the Jamun lake to the Jordan. As Jabneel is mentioned after Adami Nekeb , it must be sought for to the east of Adami Nekeb, whereas the Jamun lake lies in the very opposite direction, namely, directly to the west of the red convent. The three places mentioned, therefore, cannot be precisely determined at present. The Jordan, where the boundary of Asher terminated, was no doubt the upper Jordan, or rather the Nahr Hasbany , one of the sources of the Jordan, which formed, together with the Huleh lake and the Jordan itself, between Lake Huleh and the Sea of Tiberias, and down to the point where it issues from the latter, the eastern boundary of Asher. Verse 34. From the Jordan below the Lake of Tiberias, or speaking more exactly, from the point at which the Wady Bessum enters the Jordan, "the boundary (of Asher) turned westwards to Asnoth-tabor, and went thence out to Hukkok." This boundary, i.e., the southern boundary of Asher, probably followed the course of the Wady Bessum from the Jordan, which wady was the boundary of Issachar on the north-east, and then ran most likely from Kefr Sabt (see at v. 22) to Asnoth-tabor , i.e., according to the Onom. ( s. v. Azanoth ), a vicus ad regionem Diocaesareae pertinens in campestribus , probably on the south-east of Diocaesarea , i.e., Sepphoris , not far from Tabor, to which the boundary of Issachar extended (v. 22). Hukkok has not yet been traced. Robinson (Bibl. Res. p. 82) and Van de Velde (Mem. p. 322) are inclined to follow Rabbi Parchi of the fourteenth century, and identify this place with the village of Yakûk , on the north-west of the Lake of Gennesareth; but this village is too far to the north-east to have formed the terminal point of the southern boundary of Naphtali, as it ran westwards from the Jordan. After this Naphtali touched "Zebulun on the south, Asher on the west, and Judah by the Jordan toward the sun-rising or east." "The Jordan" is in apposition to "Judah," in the sense of "Judah of the Jordan," like "Jordan of Jericho" in Num 22:1; 26:3, etc. The Masoretic pointing, which separates these two words, was founded upon some false notion respecting this definition of the boundary, and caused the commentators http://207.44.232.113/~bible/comment/ot/k&d/josh/jos122.html (1 of 2) [13/08/2004 01:19:11 p.m.]

<strong>Keil</strong> and <strong>Delitzsch</strong> <str<strong>on</strong>g>Commentary</str<strong>on</strong>g> <strong>on</strong> the Old Testament<br />

<br />

lake Jamun was two hours to the west of the red c<strong>on</strong>vent, so that the boundary, which<br />

starts from the west, and is drawn first of all towards the north, and then to the northeast<br />

and east, must have run last of all from the red c<strong>on</strong>vent, and not from the Jamun<br />

lake to the Jordan. As Jabneel is menti<strong>on</strong>ed after Adami Nekeb , it must be sought for<br />

to the east of Adami Nekeb, whereas the Jamun lake lies in the very opposite<br />

directi<strong>on</strong>, namely, directly to the west of the red c<strong>on</strong>vent. The three places menti<strong>on</strong>ed,<br />

therefore, cannot be precisely determined at present. The Jordan, where the boundary<br />

of Asher terminated, was no doubt the upper Jordan, or rather the Nahr Hasbany , <strong>on</strong>e<br />

of the sources of the Jordan, which formed, together with the Huleh lake and the<br />

Jordan itself, between Lake Huleh and the Sea of Tiberias, and down to the point<br />

where it issues from the latter, the eastern boundary of Asher.<br />

Verse 34. From the Jordan below the Lake of Tiberias, or speaking more exactly,<br />

from the point at which the Wady Bessum enters the Jordan, "the boundary (of<br />

Asher) turned westwards to Asnoth-tabor, and went thence out to Hukkok." This<br />

boundary, i.e., the southern boundary of Asher, probably followed the course of the<br />

Wady Bessum from the Jordan, which wady was the boundary of Issachar <strong>on</strong> the<br />

north-east, and then ran most likely from Kefr Sabt (see at v. 22) to Asnoth-tabor ,<br />

i.e., according to the Onom. ( s. v. Azanoth ), a vicus ad regi<strong>on</strong>em Diocaesareae<br />

pertinens in campestribus , probably <strong>on</strong> the south-east of Diocaesarea , i.e.,<br />

Sepphoris , not far from Tabor, to which the boundary of Issachar extended (v. 22).<br />

Hukkok has not yet been traced. Robins<strong>on</strong> (Bibl. Res. p. 82) and Van de Velde (Mem.<br />

p. 322) are inclined to follow Rabbi Parchi of the fourteenth century, and identify<br />

this place with the village of Yakûk , <strong>on</strong> the north-west of the Lake of Gennesareth;<br />

but this village is too far to the north-east to have formed the terminal point of the<br />

southern boundary of Naphtali, as it ran westwards from the Jordan. After this<br />

Naphtali touched "Zebulun <strong>on</strong> the south, Asher <strong>on</strong> the west, and Judah by the Jordan<br />

toward the sun-rising or east." "The Jordan" is in appositi<strong>on</strong> to "Judah," in the sense<br />

of "Judah of the Jordan," like "Jordan of Jericho" in Num 22:1; 26:3, etc.<br />

The Masoretic pointing, which separates these two words, was founded up<strong>on</strong> some<br />

false noti<strong>on</strong> respecting this definiti<strong>on</strong> of the boundary, and caused the commentators<br />

http://207.44.232.113/~bible/comment/ot/k&d/josh/jos122.html (1 of 2) [13/08/2004 01:19:11 p.m.]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!