Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-seo-pack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the unlimited-elements-for-elementor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the essential-addons-for-elementor-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-analytics-for-wordpress domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the happy-elementor-addons domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the premium-addons-for-elementor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/vivektan/pratiyogitavijay.com/wp-includes/functions.php on line 6121
महालवाड़ी व्यवस्था - Pratiyogita Vijay

महालवाड़ी व्यवस्था

‘महाकाव्य के अंतर्गत गाँव के मुखिया से धरकार का लगान वसूली का समझी होता था जिसे ‘महावी
व्यवस्था का जनक हॉल्ट 1610 के अपने प्रतिवेदन में महालवाड़ी व्यवस्था का सूत किया, जिसे सर्वप्रथम 1822 में कानूनी रूप से लागू किया ग 1833 में मार्टिन बर्ड तथा अपने सबसे बेहतर रूप में सामने आई। .
. यह व्यवस्था मध्य प्रांत, उत्तर प्रदेश एवं पंजाब में लागू की गई तथा इस व्यवस्था के अंतर्गत ब्रिटिश भारत की भूमि का 30% भाग था।
. इस व्यवस्था के अंतर्गत भू-राजस्व का निर्धारण समूचे ग्राम के उत्पादन के आधार पर किया जाता था तथा महाल के समस्त पू-स्वामियों के भू-राजस्व का रूप था। इससे गाँव के लोग अपने मुखिया प्रतिनिधियों के एक समय-सीमा के अंदर की को अपने ऊपर से लेते थे।
महालवाड़ी व्यवस्था का सबसे प्रमुख दोष यह था कि इस केको अत्यधिक शक्तिशाली बना दिया। किसानों को भूमि से करने देने के अधिकार उनकी अत्यधिक बढ़ गई। इस व्यवस्था का दूसरा दोष यह था कि इससे सरकार एवं किसानों के प्रत्यक्ष संबंध समाप्त हो गए।
इस पद्धति के अंतर्गत लगान का निर्धारण अनुमान पर आधारित था और इसकी विसंगतियों का लाभ उठाकर कंपनी के अधिकारी अपनी स्वार्थ सिद्धि में कंपनी को लगान वसूली पर अधिक खर्च करना पड़ा। परिणामस्वरूप वह व्यवस्था बुरी रही।
निष्कर्ष
ब्रिटिश भू-राजनीतियों का अधिकतम को प्रति करता था। फलतः ऐसी स्थिति में भूटान को जो भी पद्धति लागू की किसानों का अत्यधिक में हता था और भारत की बहु कृषी अतः किन हुए। पर भू- गतियों से जो अद्वेष उपजा उसे समय-समय पर होने वाले किसान एवं जनवरिवोह के रूप में देखा जा सकता है।

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top