[haiku-development] Re: BFS and UUID
- From: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 27 Oct 2011 14:39:26 +0200
On 27.10.2011 13:52, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 22.07.2009 11:25, Axel Dörfler wrote:
>>> Getting attributes isn't difficult but may need the module to be a
>>> bit
>>> bigger but difficult to say without actualy implementing.
>>> In short if haiku creates a volume_id I'll be happy to implement it
>> It might be a bit much for a boot loader implementation. I'll give it
>> some thought; the advantage of the attribute solution is that there is
>> already an API for retrieving it. OTOH this does not cover the UUIDs of
>> other file systems, so a generic solution sounds like the best option.
>>
> Was something decided or done on this?
>
Judging from:
phcoder@xxxxxxxxxxxxxxxxx:~/repos$ find haiku/haiku/ -exec grep -H -n
be:volume_id {} \;
haiku/haiku/src/add-ons/kernel/file_systems/googlefs/.svn/text-base/attrs.c.svn-base:364:{
"be:volume_id", B_UINT64_TYPE, sizeof(root_folder_attrs_2),
&root_folder_attrs_2 },
haiku/haiku/src/add-ons/kernel/file_systems/googlefs/attrs.c:364:{
"be:volume_id", B_UINT64_TYPE, sizeof(root_folder_attrs_2),
&root_folder_attrs_2 },
it wasn't. Could at least mkfs be modified to add random be:volume_id on
new filesystems? Also I'd recommend modifying fs drivers to add random
be:volume_id on any filesystem mounted read-write which doesn't already
have it
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
Other related posts:
