Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Could Minix use separate segments for stack and data?

Data minix segments separate stack
0
Posted

Could Minix use separate segments for stack and data?

0

Minix uses the Intel i386 protection mechanisms to define code, data, and stack segments. Executable instructions in the code segment are read-only, and it is impossible for data in the data or stack areas to be treated as executable code. However, Minix, in the tradition of other Unix-like systems, does not distinguish between data and stack areas — although data and stack use separate segment descriptors and could be protected from each other by the hardware, Minix initializes the data and stack descriptors to point to the same area of memory. A question was asked on the comp.os.minix newsgroup as to whether separate data and stack areas could be used, and what would be the advantages and disadvantages of doing it either way. David Given wrote this reply (newsgroup headers appear at end of this page): Assuming you’re using a traditional 8086 implementation with normal-sized pointers, then having separate stack and data segments means that you can’t address structure

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.