hfs-user

hfs-user@lists.mars.org

183 discussions

Fw: [hfs-user] Curious about the current interest in HFS ...
by Entwicklung 24 Feb '02

24 Feb '02

----- Original Message ----- From: "Abuse at Microsoft" <abuse(a)microsoft.com> To: "Entwicklung" <entwicklung(a)whengenibk.de> Sent: Sunday, February 24, 2002 1:51 PM Subject: Re: [hfs-user] Curious about the current interest in HFS ... Hello, Thank you for contacting Microsoft. We appreciate the information you have provided thus far. Though you may have provided some of this information already, we will need more information to create a case. Please assist us in further processing your support request by providing the following information in an e-mail message to Msupport(a)microsoft.com: * Product name, version and Product Identification Number (PID) * Operating system and version (For example: Windows XP) * Browser type and version * Memory (RAM) * CPU type and speed * Complete error messages * Specifics of the problem * All Contact Information (Name, e-mail address, and telephone number) For help locating the Product Identification Number (PID), go to: http://support.microsoft.com/support/webresponse/pid/pidfind.asp If you have any additional questions, please let us know by replying to this message. Thank you, Justin Microsoft Online Customer Representative ------------------------ From: entwicklung(a)whengenibk.de Received: 2/24/02 4:14 AM To: Abuse at Microsoft Subject: Re: [hfs-user] Curious about the current interest in HFS ... Original Message Follows: ------------------------- I'm a student working part-time on a filesystems project and was just given an outline of the project requirements to start off. I enrolled myself as part of the student-dev and darwin-development mailing lists but the topics discussed there are not really relevant to my requirements... besides I end up getting more than a 100 mails from these which I can't really use purposefully. I'm glad that people have slowly started responding on this list and that a healthy discussion of issues seems to have begun.... as compared to the other apple mailing-lists I had begun to assume that this list was pretty much in hibernation :) > May be my assumption is a bit naive, but especially for writing CDs for > Macs on non-Mac platforms, creating a Rock Ridge/Joliet CD is much easier > than an HFS or HFS hybrid CD ... I'm not too sure but do older Macs support Roc Ridge/Joliet too? I'm sure there aren't too many people using older Macs but maybe this has to to do with making things easier for them (?) > P.S. does anyone else that posts to this list get a reply from > "<abuse(a)microsoft.com>" ... Aargh!...don't tell me they're mailing you too!....I don't intend to contact Microsoft (by no means!) but their mails always begin with a 'Thank you for contacting Microsoft...." ...maybe they don't know they're part of this list ? Besides if they're offering constructive suggestions we should be hearing from 'support' not 'abuse' I think. I wrote to them about this once and it doesn't seem to have made any difference. Regards, Nandini

1 0

Desktop Database
by Entwicklung 23 Feb '02

23 Feb '02

Hi, Could someone tell me where exactly to find some documentation on the desktop DB for an external HFS volume? I came across some interesting info on Thomas Tempelmann's developer's site and it said that one would have to request Apple for further technical info (?!) but the website didn't really furnish the kind of details I need. I basically need info. as to how and where exactly (in the image) this file has to be present and what its exact contents (structure) are...links to any sample code, open sources or headers related to this would be greatly appreciated. The technical notes for HFS+ and the related documentation for HFS volumes (part of Inside Macintosh) don't seem to contain elaborate info on this either. Regards, Nandini Hengen PS. Thanks to everybody who replied to my previous mail on 'embedded volumes'.... I've come to the conclusion I'll need one after all.....at least at a later stage (once I start dealing with HFS+) to ensure that my CD-RW HFS+ volumes don't get erased on earlier Macs...

4 4

Embedded volume..
by Entwicklung 23 Feb '02

23 Feb '02

Hi, what exactly does the term embedded volume mean? I've noticed that the HFS MDB has some fields related to this but the HFS+ volume header doesn't seem to. I'm not really using these fields but I'd like to know what they're used for in any case. So if anyone could enlighten me I'd appreciate it. Regards, Nandini Hengen

4 7

HFS under DOS
by Simon Bazley 22 Feb '02

22 Feb '02

There is a standard layout that a mac uses on a DOS floppy, so that it can support all the AppleDouble files and all the rest. Can someone tell me where its documented. I want to know how HFS+ should look when its mounted on a system that doesn't support forks. Simon

2 1

Re: [hfs-user] Embedded volume..
by Entwicklung 22 Feb '02

22 Feb '02

Oops ...sorry! the second field was meant to be drEmbedExtent... wrote that in a hurry! -Nandini ----- Original Message ----- From: "Entwicklung" <Entwicklung(a)WHengenIBK.de> To: "Simon Bazley" <sibaz(a)sibaz.com> Cc: <hfs-user(a)lists.mars.org> Sent: Friday, February 22, 2002 3:05 PM Subject: Re: [hfs-user] Embedded volume.. > Hello, > Thanks for replying... was hoping that someone would respond! > > I was referring to the fields: > UInt16 drEmbedSigWord ;//embedded volume signature - formerly drVCSize > and HFSExtentDescriptor drEmbedSigWord ;//embedded volume location and > size - formerly drVBMCSize and drCtlCSize > > I think what you mentioned about Wrappers is relevant to what I wanted to > know though I don't see the purpose of having a HFS+ partition embedded in a > HFS volume (?). Why would anyone want an embedded partition when all data > could be stored in the original HFS partition? I've just set these fields to > 0 right now and I fail to see a situation where I (a third-party HFS-volume > developer) would ever need these. > Any tips? > > Regards, > Nandini Hengen > > ----- Original Message ----- > From: "Simon Bazley" <sibaz(a)sibaz.com> > To: "Entwicklung" <entwicklung(a)whengenibk.de> > Cc: <hfs-user(a)lists.mars.org> > Sent: Friday, February 22, 2002 2:51 PM > Subject: Re: [hfs-user] Embedded volume.. > > > > I'm not sure exactly what you're referring to, but heres a few pointers. > > > > The volume is the thing that you mount on your computer which provides > > files. It represents the single mount point which appears as a disk on > > your computer. > > The HFS Wrapper is a HFS partition consisting of a massive consecutive > > bad block file, which happens to be a HFS+ partition thats embedded in > > the HFS volume. > > The important difference between HFS+ and HFS is that wheras in HFS > > certain files (Device Drivers, Boot System Files, Allocation Bitmap) > > exist at various physical disk locations (sector 0, sector, sector 4 > > etc) and the MDB only gives the location to the Catalog and Extent > > files. Also there are 2 different address spaces, physical (in > > sectors), and logical (in blocks, starting at 0, after the end of the > > volume bitmap, at the location described in the MDB as the start of free > > space). HFS+ has very little (if any) system files at fixed locations, > > and everything is referred to in the volume descriptor (replaces the > > MDB), in the way the Catalog and Extent files was before. > > > > Hope that explains everything, if not give me the names of the variable > > in the HFS and HFS+ volume descriptors and I'll explain what they mean. > > > > Simon > > > > Entwicklung wrote: > > > > > Hi, what exactly does the term embedded volume mean? I've noticed > > > that the HFS MDB has some fields related to this but the HFS+ volume > > > header doesn't seem to. I'm not really using these fields but I'd like > > > to know what they're used for in any case. So if anyone could > > > enlighten me I'd appreciate it. Regards,Nandini Hengen > > >

2 1

Re: Mac-OS Dates
by Entwicklung 11 Feb '02

11 Feb '02

> > I think they actually used 1900 there, to make matters even more confusing... > > Just I think so too.. I just landed up with a timespan of 101 years for the date of a file I had created a few months back. This wouldn't make sense if it were 1904. Regards, Nandini Hengen > _______________________________________________ > carbon-development mailing list | carbon-development(a)lists.apple.com > Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/carbon-development > Do not post admin requests to the list. They will be ignored.

1 0

Index nodes of a catalog B-Tree
by Entwicklung 11 Feb '02

11 Feb '02

> Simon Bazley, > Thanks for replying ! > I managed to figure out what the problem was- I had mentioned this in my > previous email to the list. > I have a question to which maybe you or someone from the list knows the > answer - > At the moment I'm wondering how to determine the number of index nodes > needed for a catalog tree. I have determined the number of catalog nodes > needed and my question is : Does every leaf node in the catalog-tree have to > be referenced in the index-nodes? > In a broadly logical sense I would say that it has to ...since a leaf > without an index in a 'real' tree would probably be like a leaf falling off > a branch in autumn :). The HFS reference (Inside Macintosh) has this figure > of a sample B-Tree where a reference to every leaf-node is maintained in the > index nodes. > But I came across a sample HFS-image (which is readable on my Mac) which > shattered all my illusions since the root-node (the only index node in this > image) doesn't maintain references to all leaf nodes, only to a few of them. > > Does anyone from Apple (or others) maybe know how the index nodes are to > built up i.e. to which leaf-nodes (if not to all) a reference has to > necessarily be maintained ? I guess a Mac internally should be doing some > kind of optimization to reduce the search-time in finding a leaf-record.... > but all I need to know is what I should take into account while constructing > my index-nodes to make the job easier for the Mac when an external > HFS-volume is mounted. > > Would be grateful for any tips. > > Regards, > Nandini Hengen > > > > ----- Original Message ----- > From: "Simon Bazley <sibaz(a)sibaz.com>" <simon(a)sibaz.com> > To: "Entwicklung" <entwicklung(a)whengenibk.de> > Cc: <hfs-user(a)lists.mars.org> > Sent: Monday, February 11, 2002 2:41 AM > Subject: Re: [hfs-user] Volume-Names in HFS > > > > Have you checked Inside Macintosh Files to see what it says about the MDB > > record (assuming its an HFS volume) or the equivalent in the HFS+ Technote > > (assuming its HFS+). My understanding was that volume name was pretty > > bullet proof. > > > > Simon > > > > On Thu, 7 Feb 2002, Entwicklung wrote: > > > > > Hello, > > > My HFS-Volume seems to be recognized if I give the Volume a name > with an odd no. of characters say "NEW" but fails to be recognized if the > name is say "NAND_HFS". Does anybody know of a possible reason why this is > happening ? > > > > > > I think this had something to do with the key length field. In my case - > if the volume name is even hence implying that the associated key does not > end on an even byte boundary (where applicable), i byte is added for padding > but the key-length and name length fields are maintained as before. In those > keys which have to be of size=maximum key length the padding with zeroes is > done in any case. > > > Does anybody know if something else needs to be changed ? > > > > > > TIA, > > > Nandini Hengen > > > > > >

2 1

Algorithm of B* tree Implementation
by Biswaroop Banerjee 11 Feb '02

11 Feb '02

Hi All, Can anybody of you give me the algorithm of implementating a B* tree which is the prominent data structure in a HFS formatted volume. Waiting for your help. Regards Biswaroop Banerjee. The essence of Success lies in its Struggle -Bisban

4 6

Volume-Names in HFS
by Entwicklung 11 Feb '02

11 Feb '02

Hello, My HFS-Volume seems to be recognized if I give the Volume a name with an odd no. of characters say "NEW" but fails to be recognized if the name is say "NAND_HFS". Does anybody know of a possible reason why this is happening ? I think this had something to do with the key length field. In my case - if the volume name is even hence implying that the associated key does not end on an even byte boundary (where applicable), i byte is added for padding but the key-length and name length fields are maintained as before. In those keys which have to be of size=maximum key length the padding with zeroes is done in any case. Does anybody know if something else needs to be changed ? TIA, Nandini Hengen

2 1

RE: [hfs-user] Algorithm of B* tree Implementation
by Gordon Beatty 08 Feb '02

08 Feb '02

The technote number is 1150 but if you point your browser to http://developer.apple.com/techpubs/macos8/Files/FileManager/filemanager.htm l the links to the original HFS spec in "Inside Macintosh" and the HFS+ spec in TechNote 1150 are listed there (although the way OS X uses and interprets some of the fields in HFS+ does not seem completely reflected in the TechNote). Also, the technote refers to Robert Sedgewick's book 'Algorithms in C - Parts 1-4' -- and similarly 'Algorithms in C++ - Parts 1-4' -- which should prove a fairly clear reference for the purposes of understanding. The 'File Structures' book (previous or current version) by Michael Folk could help in this regard as well. At the end of the day though, a solid C implementation is certainly the best reference. Gord Beatty -----Original Message----- From: hfs-user-admin(a)lists.mars.org [mailto:hfs-user-admin@lists.mars.org]On Behalf Of Patrick Dirks Sent: Thursday, February 07, 2002 1:57 PM To: hfs-user(a)lists.mars.org Cc: Biswaroop Banerjee Subject: Re: [hfs-user] Algorithm of B* tree Implementation "The algorithm" is a bit hard to lay out in an e-mail message - it's wrapped up in a series of design and implementation aspects. Read up on B*-Trees and you should have a good idea what the data structure's supposed to look like at any given time. Read "Inside Macintosh" and you'll find a more detailed explanation of the exact details of the HFS/HFS+ B*-Tree structure. More helpful than "Inside Macintosh", perhaps, is the tech note that Apple's published on the subject - "must read" for anyone implementing a version of HFS/HFS+. I can't remember the tech note number offhand but it's freely available through Apple's web site - do a search there. Finally, note that the Darwin code, which Apple has open sourced, includes a complete "C" implementation of the B*-Tree code as part of a UNIX kernel. Sign up as a Darwin developer and check out a copy of the sources. It's in the "xnu" project in the "hfs" directory inside the "bsd" directory of "xnu". That's the ultimate answer right there. Hope that helps, -Pat Dirks. On Thursday, February 7, 2002, at 02:04 AM, Biswaroop Banerjee wrote: Hi All, Can anybody of you give me the algorithm of implementating a B* tree which is the prominent data structure in a HFS formatted volume. Waiting for your help. Regards Biswaroop Banerjee. The essence of Success lies in its Struggle -Bisban

2 1

← Newer
1
...
6
7
8
9
10
11
12
...
19
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

hfs-user