From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-kernel@vger.kernel.org
Cc: Daniel Phillips <lkml@phunq.net>
Subject: Re: Tux3 report: New news for the new year
Date: Tue, 1 Jan 2013 15:37:08 +0100 [thread overview]
Message-ID: <201301011537.08466.Martin@lichtvoll.de> (raw)
In-Reply-To: <1492866.3ugQ2fqrP0@mars>
Am Dienstag, 1. Januar 2013 schrieb Daniel Phillips:
> On Tuesday, January 01, 2013 02:06:19 PM Martin Steigerwald wrote:
> > Sounds all good and nice and interesting to test, but where to grab the
> > source?
> >
> > I found no obvious URL.
>
> Hi Martin,
>
> Sorry about that, I knew I forgot something:
>
> git://github.com/OGAWAHirofumi/tux3.git
>
> Warning: the recent work is on branch temp-atomic-commit and tends to get
> refactored changeset-wise on a regular basis. This will be merged to
> master pretty soon, and settle down there.
Thanks.
I can compile and mkfs it with:
dd if=/dev/zero of=tux3.img bs=1M count=100
./tux3 mkfs tux3.img
Writing a file with
./tux3 write tux3.img /etc/fstab
also seemed to work, but I gave up holding down the enter key at:
delta_get: delta 448, refcount 2
tuxio: write 1 bytes at 4484, isize = 0x1184
delta_put: delta 448, refcount 1
/etc/fstab is 1714 bytes long.
No tux3fuse, but then, I lacked libfuse-dev, after installing, compiling
worked:
martin@merkaba:~[…]> make tux3fuse
gcc -MF ./.deps/tux3fuse.d -MP -MMD -m64 -std=gnu99 -Wall -g -rdynamic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -
I/home/martin/Linux/Dateisysteme/tux3/tux3/user -Wall -Wextra -Werror -Wundef -Wstrict-prototypes -Werror-implicit-
function-declaration -Wno-unused-parameter -Wno-sign-compare -Wno-missing-field-initializers -D_FORTIFY_SOURCE=2 -
DLOCK_DEBUG=1 -DROLLUP_DEBUG=1 -DDISABLE_ASYNC_BACKEND=1 $(pkg-config --cflags fuse) tux3fuse.c -lfuse -o
tux3fuse libtux3.a libklib/libklib.a
Then I could use it:
martin@merkaba:~[…]> ./tux3 mkfs tux3.img
__setup_sb: blocksize 4096, blockbits 12, blockmask 00000fff
__setup_sb: volblocks 25600, freeblocks 25600, freeinodes 281474976710656, nextalloc 0
__setup_sb: atom_dictsize 0, freeatom 0, atomgen 1
__setup_sb: logchain 0, logcount 0
make tux3 filesystem on tux3.img (0x6400000 bytes)
[…]
martin@merkaba:~[…]> sudo ./tux3fuse tux3.img /mnt/zeit
[sudo] password for martin:
martin@merkaba:~[…]> mount | grep fuse
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tux3.img on /mnt/zeit type fuse.tux3.img (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
But I am stuck with accessing it:
martin@merkaba:~[…]> LANG=C ls -l /mnt/zeit
ls: cannot access /mnt/zeit: Permission denied
martin@merkaba:~[…]> LANG=C sudo chown martin:martin /mnt/zeit
chown: cannot access '/mnt/zeit': Transport endpoint is not connected
martin@merkaba:~[…]> LANG=C sudo ls -l /mnt/zeit
ls: cannot access /mnt/zeit: Transport endpoint is not connected
martin@merkaba:~[…]>
Unmounting it again worked nicely.
I keep it at that for now until I may take time to take a closer look.
I think its better to continue this on tux3 mailing list, which I have
subscribed to. But I thought I post this here, to give others some starting
point for own experiments as I did not any documentation about this
in the git repo.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-01-01 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 11:52 Tux3 report: New news for the new year Daniel Phillips
2013-01-01 13:06 ` Martin Steigerwald
2013-01-01 13:28 ` Daniel Phillips
2013-01-01 14:37 ` Martin Steigerwald [this message]
2013-01-01 21:49 ` Daniel Phillips
2013-01-02 6:58 ` Shentino
2013-01-02 6:58 ` Shentino
2013-01-02 11:03 ` Daniel Phillips
2013-01-02 9:45 ` Tero Roponen
2013-01-02 11:15 ` Daniel Phillips
2013-01-04 10:04 ` OGAWA Hirofumi
2013-01-05 9:35 ` Shentino
-- strict thread matches above, loose matches on Subject: below --
2013-01-01 10:55 Daniel Phillips
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=201301011537.08466.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@phunq.net \
/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.