From: Pavel Machek <pavel@ucw.cz>
To: andyliu <liudeyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH]a tar filesystem for 2.6.10-rc1-mm3
Date: Thu, 11 Nov 2004 00:42:03 +0100 [thread overview]
Message-ID: <20041110234203.GE1099@elf.ucw.cz> (raw)
In-Reply-To: <aad1205e04110621472123bf67@mail.gmail.com>
Hi!
> let's think about the way we access the file which contained in a tar file
> may we can untar the whole thing and we find the file we want to access
> or we can use the t option with tar to list all the files in the tar
> and then untar
> the only one file we want to access.
>
> but with the help of the tarfs,we can mount a tar file to some dir and access
> it easily and quickly.it's like the tarfs in mc.
>
> just mount -t tarfs tarfile.tar /dir/to/mnt -o loop
> then access the files easily.
>
> it was writen by Kazuto Miyoshi (kaz@earth.email.ne.jp) Hirokazu
> Takahashi (h-takaha@mub.biglobe.ne.jp) for linux 2.4.0
>
> and i make it work for linux 2.6.0. now a patch for linux
> 2.6.10-rc1-mm3
Hmm, at least it needs to be indented by tab, see
Documentation/CodingStyle. If it could do compressed tars... well I
could find a use for _that_...
Pavel
> +static int tarfs_readdir(struct file * filp,
> + void * dirent, filldir_t filldir)
> +{
> + struct inode *inode = filp->f_dentry->d_inode;
> + int err;
> + struct tarent *dir_tarent, *ent;
> + int dtype=0;
> + int count, stored;
> +
> + dir_tarent = TARENT(inode);
> +
> + message("tarfs: tarfs_readdir (dir_tarent %p, f_pos %ld)\n",
> + dir_tarent, (long)filp->f_pos);
> +
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-11-11 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 7:17 [PATCH]a tar filesystem for 2.6.10-rc1-mm3 andyliu
2004-11-07 5:47 ` andyliu
2004-11-10 23:42 ` Pavel Machek [this message]
2004-11-10 3:01 ` Rusty Russell
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=20041110234203.GE1099@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liudeyan@gmail.com \
/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