From: Johannes Berg <johannes@sipsolutions.net>
To: Greg KH <gregkh@suse.de>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Joel Becker <Joel.Becker@oracle.com>,
Michael Buesch <mb@bu3sch.de>
Subject: Re: debugfs oddity
Date: Wed, 04 Oct 2006 10:23:19 +0200 [thread overview]
Message-ID: <1159950200.2817.34.camel@ux156> (raw)
In-Reply-To: <20061004081213.GA3477@suse.de>
On Wed, 2006-10-04 at 01:12 -0700, Greg KH wrote:
> I don't understand. Does ramfs have the same issues you feel debugfs
> has? Or does it work like a disk based file system?
It works like tmpfs and disk based filesystems and allows re-creating a
removed directory.
johannes
prev parent reply other threads:[~2006-10-04 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 9:25 debugfs oddity Johannes Berg
2006-10-03 5:28 ` Greg KH
2006-10-04 7:20 ` Johannes Berg
2006-10-04 8:12 ` Greg KH
2006-10-04 8:23 ` Johannes Berg [this message]
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=1159950200.2817.34.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=Joel.Becker@oracle.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=tiwai@suse.de \
/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