From: Daniel Phillips <phillips@phunq.net>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, tux3@tux3.org
Subject: Tux3 report: A Golden Copy
Date: Tue, 30 Dec 2008 19:35:48 -0800 [thread overview]
Message-ID: <200812301935.49303.phillips@phunq.net> (raw)
All versions of Tux3 are special, we think, but this one is a little
more special than all the rest: for the first time, it survives
repeated fsx-linux runs. That is mainly due to a burst of amazingly
accurate work by Hirofumi, and finishing up the SMP lock coverage.
Here is the HowTo again, lightly updated to install the first official
Tux3 Golden Copy:
# Get a kernel tree:
wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.5.tar.bz2
tar -xjf linux-2.6.26.5.tar.bz2
cd linux-2.6.26.5
# Get the Christmas tux3 patch and patch the kernel:
wget http://tux3.org/patches/tux3-2.6.26.5-4
patch <tux3-2.6.26.5-4 -p1
# Build linux with tux3:
make defconfig
make CONFIG_TUX3=y
sudo make install
# Get the Christmas tux3 userspace snapshot:
wget http://tux3.org/downloads/snapshots/tux3-20081230.tar.gz
tar -xzf tux3-20081230.tar.gz
cd tux3/user
make
# make a tux3 filesystem
sudo ./tux3 mkfs /dev/<testpartition>
Boot and mount!
cat /proc/filesystems | grep tux3 && mount /dev/<testpartition> /mnt
Recovery after crash or unexpected shutdown is easy:
tux3 mkfs <volname>
In other words, do not expect Tux3 to survive this kind of treatment
just yet. Atomic commit is on the way, and is the last major change
planned before starting review.
Caveats are the same as before:
http://kerneltrap.org/mailarchive/linux-fsdevel/2008/12/26/4493214
"Tux3 for Christmas"
And finally the usual offer: If you drop by to lend a hand we will
treat you with respect and admiration for showing such courage, and we
will make you even more famous than you already are, by carving your
name in the Tux3 Hall of Fame:
http://tux3.org/about.html
Regards,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-12-31 3:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 3:35 Daniel Phillips [this message]
2008-12-31 7:34 ` Tux3 report: A Golden Copy sniper
2008-12-31 8:00 ` [Tux3] " Daniel Phillips
2008-12-31 8:14 ` Justin P. Mattock
2008-12-31 10:09 ` Martin Steigerwald
2008-12-31 17:41 ` Justin P. Mattock
2009-01-02 20:17 ` [Tux3] " Martin Steigerwald
2009-01-02 20:36 ` Justin P. Mattock
2009-01-02 22:45 ` [Tux3] " Daniel Phillips
2009-01-02 23:11 ` Justin P. Mattock
2009-01-03 1:19 ` Daniel Phillips
2009-01-03 1:32 ` Justin P. Mattock
2009-01-03 3:03 ` [Tux3] " Daniel Phillips
2009-01-03 3:39 ` Justin P. Mattock
2009-01-04 3:17 ` Jamie Lokier
2009-01-04 4:15 ` Daniel Phillips
2009-01-04 4:29 ` Justin P. Mattock
2009-01-04 13:04 ` Theodore Tso
2009-01-05 1:10 ` Daniel Phillips
2009-01-05 2:13 ` Jamie Lokier
2009-01-08 2:50 ` Daniel Phillips
2009-01-08 4:38 ` Evgeniy Polyakov
2008-12-31 8:16 ` sniper
2008-12-31 8:31 ` Dave Chinner
2008-12-31 9:40 ` Daniel Phillips
2008-12-31 14:26 ` Andi Kleen
2008-12-31 18:14 ` sniper
2008-12-31 18:18 ` sniper
2009-01-01 9:56 ` [Tux3] " Daniel Phillips
2009-01-01 14:46 ` Daniel Phillips
2009-01-01 23:58 ` Dave Chinner
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=200812301935.49303.phillips@phunq.net \
--to=phillips@phunq.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tux3@tux3.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).