- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: INIT disk/DIRECTORIES=n
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2014 09:44 AM
09-03-2014 09:44 AM
I'm back to trying to understand this INIT option, which I've never understood.
This is clear: INIT disk/HEADERS=n directly effects the size of the INDEXF.SYS file, which I've just reconfirmed in some quick tests (I understand what HEADERS are so this was just a sanity check).
But, I've never understood what the /DIRECTORIES=n switch does. The HELP text is unclear, I couldn't find more info with a web search, and in some quick testing, using N=16 (the default) or N=16000 (the max allowed) seems to make no difference in the sizes of the files created by the INIT operation.
Would someone explain what this switch does and how I should consider using it? TIA
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2014 12:06 PM
09-03-2014 12:06 PM
SolutionAre you conflating the index file INDEXF.SYS and the 000000.DIR Master File Directory (MFD)?
The INITIALIZE /DIRECTORIES qualifier pre-allocates the 000000.DIR master file directory directory file, and is not particularly useful for most cases. Not unless you're going to immediately fill 000000.DIR with a gazillion files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2014 12:34 PM
09-03-2014 12:34 PM
Re: INIT disk/DIRECTORIES=n
Ah yes, that simple. I was expecting something more complicated. Thank you