From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: Re: udf.ko writes grokked most quickly how
Date: 20 Nov 2003 10:13:53 -0700 [thread overview]
Message-ID: <1069348432.7511.2.camel@patrh9> (raw)
In-Reply-To: <1069347191.7211.7.camel@patrh9>
cd linux-2.6.0-test9/fs/udf
vi *.h
// ecma_167.h
linux/types.h may be giving us uint8_t, uint16_t etc.
VSD_STD_ID_BEA01 is the "BEA01" string of mkudffs hexdump.
// osta_udf.h
UDF_ID_DEVELOPER "*Linux UDFFS" maybe distinguishes our volumes from
others.
UDF_ID_MAC_RESOURCE "*UDF Mac ResourceFork" etc. acknowledges Mac
exists.
UDF_ID_NON_ALLOC includes the "Non-Allocatable Space" string of some
Windows views of udf discs.
Many of UDF_OS_ID_* are 0x00U but have the same suffix as distinct
UDF_OS_CLASS.
// udfdecl.h
UDF_NAME_LEN of 255, UDF_PATH_LEN of 1023, enough forever, right.
# (UDF_I_USE(inode) ... Ouch a form of C I'm too ignorant to immediately
understand.
#define UDF_PATH_LEN 1023 redundant ok why I wonder.
Here be our extern's.
// udfend.h
Prefix le maybe means little-endian.
Why endian.h is not enough I do not yet know.
// udf_i.h
// udf_sb.h
UDF_SUPER_MAGIC 0x15013346 ... hmmm ... bash of $'\x55\x41\x33\x46' is
"UA3F".
next prev parent reply other threads:[~2003-11-20 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 16:53 udf.ko writes grokked most quickly how Pat LaVarre
2003-11-20 17:13 ` Pat LaVarre [this message]
2003-11-20 18:01 ` Pat LaVarre
2003-11-20 18:08 ` [PATCH] udf.txt link rot Pat LaVarre
2003-11-20 18:18 ` udf.ko writes grokked most quickly how Pat LaVarre
2003-11-24 19:19 ` Pat LaVarre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1069348432.7511.2.camel@patrh9 \
--to=p.lavarre@ieee.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox