Maybe I did not express myself clearly. Its seems to me that whatever the 
original value of pt_entry_t.status on the disk was,  encode part will 
always write 0x80 or 0x00, effectively clearing all the other bits.

Regards,
Jiri


---------- Původní zpráva ----------
Od: Dominik Taborsky <[email protected]>
Datum: 5. 5. 2013
Předmět: Re: [HelenOS-devel] libmbr & hdisk update

"Jiri,

one more thing. I'd like to discuss this:


>> It think if you read a label with libmbr, then make no changes and 
>> write it,
>> you should not get any changes on your disk. I don't think this is the 
>> case.
>> As an example, you will loose any partition flags besides 0x80. I think 
>> you
>> need to be really careful when messing with the label, which could be
>> created by other OSes and you don't have to understand all their 
>> features
>> and constraints.
>
> OK, will fix that.

I said I would fix it, since I found parted has some flags. But I tried 
applying almost all flags to MBR partition and none of them made any 
difference regarding the status byte. What I mean is this:
http://www.gnu.org/software/parted/manual/html_chapter/parted_2.html#SEC28

None of those flags apart from 'boot' change the status field. And I 
couldn't find any other source that would say there are any other flags in 
use.

I get your point of saving previous data, but I just want to know if you 
have any more info on this. I could incorporate that into the library.

By the way, to save the status byte I will need at least another byte in 
the mbr_part_t structure. Just FYI.


Dominik

_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel";
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel

Reply via email to