udf.ko writes grokked most quickly how
Subsystems (2)
Hi I'm now taking on the impossibly steep learning curve of explaining why udf.ko can't append nonzero to two or more files in round robin sequence.
1) I glance thru Documentation/filesystems/udf.txt
2) I start browsing http://lxr.linux.no/source/fs/udf/?v=2.6.0-test7
3) I notice udf_debug in super.c, I see we ship with that on by default via #define UDFFS_DEBUG in udf_fs.h. I conclude already in dmesg I have all available info, I will have to add my own printk's.
4) Maybe next I try grep write ...
Please reply to direct me past all the usual newbie pitfalls.
Pat LaVarre
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".
102150diffs.pdf 201250diffs.pdf udf102.pdf udf200.pdf udf250.pdf 150200diffs.pdf dcn200.pdf udf150er.pdf udf201er.pdf 200201diffs.pdf dcn201.pdf udf150.pdf udf201.pdf
we get from the Web trail:
Documentation/filesystems/udf.txt
Specs UDF
http://www.osta.org/specs/index.htm
///////////////////////////////////////////////
Ecma-167.pdf
third edition only, we get from the web trail:
Documentation/filesystems/udf.txt
script setTimeout window.location.replace:
http://www.ecma-international.org/
standards
http://www.ecma-international.org/publications/standards/Standard.htm
Ecma-167
http://www.ecma-international.org/publications/standards/Ecma-167.htm
///////////////////////////////////////////////
Pat LaVarre
PATCH 1/1 udf.txt link rot
Ben F:
Quoted 6 lines
Subject: Re: udf.ko writes grokked most quickly how
...Documentation/filesystems/udf.txt
http://www.ecma.ch/
script setTimeout window.location.replace:
http://www.ecma-international.org/
To swim against the tide of link rot, I propose:
Documentation/filesystems/udf.txt +1 -1
@@ -56,6 +56,6 @@ Documentation on UDF and ECMA 167 is available FREE from: http://www.osta.org/ - http://www.ecma.ch/ + http://www.ecma-international.org/ Ben Fennema <[email protected]>
http://www.google.com/search?q=udf+ecma-167+revision+2
yields:
http://www.dvdforum.gr.jp/Japan%20Conf.%202001-PDF/WG3-2001.PDF
(144,424 bytes) which includes graphical overviews of versions of udf format.
Pat LaVarre
Kindly offline another linux-fsdevel newbie suggests reviewing:
A Linux CD-ROM Standard ...
12 March 1999 ...
fetched via:
$ cd Documentation/cdrom $ cp -ip cdrom-standard.tex ~ $ cd $ latex cdrom-standard.tex ... $
Red Hat --> Graphics --> DVI Viewer
Pat LaVarre
P.S. When tried at my desk,
cd linux-2.6.0-test9/Documentation/cdrom
make
accomplishes something similar, launching an X viewer of a slightly different cdrom-standard.dvi file, seemingly with help from gv and gs`.