primary,extended,logic有什么区别?

本文介绍了硬盘分区的基本概念,包括主分区、扩展分区和逻辑分区的区别与联系。详细解释了每种分区的作用及其如何帮助实现更灵活的硬盘空间管理。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

primary ---主分区,最多不能超过四个。在主分区中,不允许再建立其他逻辑分区

extended----扩展分区,不可引导的分区称之为扩展分区。例如有一个40GB的硬盘,那么若只建了一个10GB的主分区,还剩30GB就无法进行管理了,所以要建立扩展分区。


logic----逻辑分区,需要从扩展分区中分逻辑分区,在Redhat9中的fdisk最多分(IDE硬盘16个,SCSI硬盘15个)

 

================================================================================================

早期应为硬盘小实际上没有主分区,扩展分区,逻辑分区的概念。一个硬盘只能分配4个分区,后来硬盘越来越大,4个分区明显不够用才发展出了主分区,扩展分区,逻辑分区的概念。

扩展分区的出现是因为主分区只能分4个,所以如果要分超过4个分区的话就不可以了,所以把其中一个主分区在分区表中的位置用来保存扩展分区分区的信息,这样就可以分配超过4个分区了。所谓扩展,就是说通过这个分区可以脱破分区个数的限制,将分区个数扩展到4个以上。

逻辑分区则是在扩展分区里再分区出来的,逻辑分区没有个数限制(不确定,这个得自己查资料确定一下)。

扩展分区一个硬盘只能有一个。

主分区,如果已经分配了一个扩展分区一个硬盘就只能有3个主分区了。

### UML Use Case Diagram Extend Relationship Meaning and Usage In UML use case diagrams, the `Extend` relationship indicates that one use case can add behavior to another base use case under certain conditions. This allows for extending functionality without modifying existing use cases directly. The extend relationship is depicted by a dashed line from the extension use case (the one adding new behavior) pointing towards the extended use case (base). An open arrowhead points toward the extended use case, labeled as «extend» near the connection point[^1]. When applying this concept: - **Base Use Case**: Represents core functionalities. - **Extension Point(s)**: Specific places within the base where additional behaviors may be inserted through extensions. - **Extended Use Case**: Provides supplementary actions triggered conditionally during execution of the base scenario. For instance, consider an online shopping application with "Place Order" being the primary process. If special offers apply only when users have loyalty membership status, then "Apply Special Offer" could represent an optional activity linked via an extend link back into "Place Order". ```mermaid %% Example Mermaid code showing extend relation in UML use-case diagram graph TD; A[<<usecase>> Place Order] -->|include| B[<<usecase>> Select Items]; C[<<usecase>> Apply Special Offers] -.-> |«extend»,if user has loyalty card| A; ``` This graphical representation highlights how conditional logic influences overall flow while keeping main paths clear and uncluttered. --related questions-- 1. How does dependency differ from association in UML? 2. What role do generalizations play in structuring object-oriented systems? 3. Can you provide examples illustrating extensibility mechanisms beyond just 'extend' relations? 4. In what scenarios would it make sense to prefer composition over aggregation in defining relationships between classes?
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值