All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: udf.ko writes grokked most quickly how
Date: 20 Nov 2003 09:53:11 -0700	[thread overview]
Message-ID: <1069347191.7211.7.camel@patrh9> (raw)

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



             reply	other threads:[~2003-11-20 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 16:53 Pat LaVarre [this message]
2003-11-20 17:13 ` udf.ko writes grokked most quickly how Pat LaVarre
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=1069347191.7211.7.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.