now fields that carry information about the boot disk and partition.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9956 a95241bf-73f2-0310-859d-f6bbb57e9c96
Renamed vm_area::lock to vm_area::protection to be less confusing - wiring
is still called wiring, though (might be renamed to lock later, as that's
how BeOS calls it).
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9858 a95241bf-73f2-0310-859d-f6bbb57e9c96
real time shared page (it contains the boot time offset and the system
time conversion factor for now).
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9850 a95241bf-73f2-0310-859d-f6bbb57e9c96
(it will be maintained by the system afterwards, though).
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9849 a95241bf-73f2-0310-859d-f6bbb57e9c96
We can't handle an allocation failure there (at least for now). Took the chance to stylize the code.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9782 a95241bf-73f2-0310-859d-f6bbb57e9c96
for temporary memory anymore, it's the store's responsibility to do that
correctly now, and that functionality is reached via the vm_cache using
vm_cache_set_minimal_commitment().
Therefore, the vm_store commit() function now returns a status instead of
the size that could be commited.
Replaced the max_commit mechanism with one that cares about the available
memory, stores can reserve and unreserve such memory. The anonymous_commit()
will now fail in case it could not reserve the needed amount of memory.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9777 a95241bf-73f2-0310-859d-f6bbb57e9c96
add_partitions_for(), though).
The partition now also tracks if it refers to a partitioning system or not.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9745 a95241bf-73f2-0310-859d-f6bbb57e9c96
- only one byte was being used for total data length in a data field
which had 'maxi' size data (total data > 255 bytes), rather than the
correct four bytes.
- Seem to have finally nailed the proper algorithm for calculating data
item padding (four size bytes + bytes of data, padded to 8-byte
boundary) in all places.
- Was passing the address of the padding string, rather than the string
itself, when writing out NULL padding bytes
- Was incorrectly clearing the MSG_FLAG_MINI_DATA bit when the number of
data items or the size of the largest data item exceeding 256 bytes.
Bit is now cleared when total size of all item data (including size
bytes and padding, if applicable) exceeds 256 bytes
- Modified SizePolicy::Padding(const T&) to use calc_padding() from
MessageUtils.h/.cpp
- Added SizePolicy::Padding(const Store&) to calculate padding for data
field's entire data store
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9743 a95241bf-73f2-0310-859d-f6bbb57e9c96
* Added resolve_mount_point_to_volume_root() which does what
resolve_volume_root_to_mount_point() did. IOW the latter one didn't
do what it advertised.
* Fixed dir_vnode_to_path(). Basically broken due to the broken
resolve_volume_root_to_mount_point(), but also compared potentially
unrelated vnode IDs (belonging to different volumes).
* Fixed get_dir_path_and_leaf(). It didn't deal correctly with paths
ending in '/' (including the root dir).
* fs_mount() does now accept a NULL fsName, getting the FS name from
the DDM in this case.
* fs_mount() now also supports mounting file images; it lets the DDM
create a file device for them.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@9629 a95241bf-73f2-0310-859d-f6bbb57e9c96
