Files from the Tunes project
All these files, as well as the whole Tunes project are
copyright (c) 1995,1996,1997
François-René "Faré" Rideau
and
the members of the TUNES project.
Read these
Warnings
if you haven't yet.
How to use this page
Everything is directly available from
here
You can get all the stuff with your ordinary Web Browser,
but I recommend you to use some utility like the perl-scripts
w3mir or
webget, or
GET (from the libwww-perl on CPAN).
This way, you can easily grab files through the WWW
from any shell script or command line,
download only files that changed,
and read everything calmly at home.
Please tell me if you know any better tool.
Inside brackets is the size in bytes or kilo-bytes (if a K is appended).
Until this server is finished being set up,
only the most essential files may be available for sure,
that is,
the latest released and
development
distributions in .tgz format.
Other stuff, advertised or not, in the same format or in other formats,
may be made available on demand.
Also, the Tunes project is looking for a new FTP site,
so if you have any suggestion, we're open to it.
Full Distributions
Roadmap of the distributed software
- The distribution is split in three parts,
because we feel that
people may want to download separately:
- The main/binary "bin" part
contains runnable binaries
(well, should, at some stage)
so people can test the system.
- The Tunes documentation "doc" part
contains the documentation for the system
(most of which is an archive of the WWW pages),
so people can learn about the system.
- The Tunes source "src" part
contains the original sources from which the
system is built,
so it can be rebuilt, modified, etc.
- Summary:
- make a directory $TUNES
- uncompress the "bin" part in $TUNES/
- uncompress the "doc" part in $TUNES/doc/
- uncompress the "src" part in $TUNES/src/
- Because Tunes is not yet bootstrapped,
it is being cross-developped from Linux,
and its distribution must follow the lame traditional
hierarchical-filesystem structuring
that it will replace by a reflective knowledge-base system.
- Project development requires a filesystem
with long filenames with case significance;
however, you should be able to uncompress the files
on a lame "8.3" filesystem, too, so you can view them.
- Every subdirectory should contain a file named README
that describes its contents.
Archive file format
- Currently, files come archived and compressed either in
.zip,
.tgz or
.tbz format.
- .zip is a standard format
that allows incremental file-based archiving and dearchiving,
but it's the least space-efficient.
- .tgz (a.k.a. .tar.gz) is also standard,
but does not allow easy incremental archiving and unarchiving;
it is 13% smaller compressed than .zip.
- .tbz (a.k.a. .tar.bz) is like .tgz,
with
bzip
replacing
gzip;
it 20% smaller than .tgz,
and 32% smaller than .zip,
saving more network bandwidth,
but is slower to run (network costs more anyway),
and not as standard and patent-less.
Archive Organization
- All "official" releases are available as .tbz, .tgz or .zip archives
- The release files of the project are available at locations of the form:
http://www.eleves.ens.fr:8080/home/rideau/Tunes/files/$EXT/tunes.$VERSION.$DIST.$EXT
where $VERSION is the x.y.z.tt version number,
where $DIST is bin, src, or doc,
and where $EXT is the extension corresponding to the
archiving/compression method used.
- $VERSION in any of
0.0.0.05, 0.0.0.07,
0.0.0.10 to 0.0.0.20,
and 0.0.0.25, 0.0.0.27 to 0.0.0.31.
- Older versions are only .zip, newer are only .tgz, or even only .tbz
Distribution Archive
- The latest is 0.0.0.31
- 0.0.0.31: [.tbz]
bin [19K],
doc [332K],
src [73K].
- 0.0.0.30: [.tgz]
bin [20K],
doc [385K],
src [75K].
- 0.0.0.29: [.tgz]
bin [20K],
doc [358K],
src [75K].
- 0.0.0.27: [.tgz]
bin [15K],
doc [322K],
src [44K].
- 0.0.0.25: [.tgz]
bin [15K],
doc [301K],
src [128K].
- 0.0.0.25: [.zip]
bin [16K],
doc [348K],
src [147K].
- 0.0.0.20: [.tgz]
bin [13K],
doc [255K],
src [97K].
- 0.0.0.20: [.zip]
bin [15K],
doc [299K],
src [110K].
- 0.0.0.19: [.zip]
bin [15K],
doc [295K],
src [93K].
- 0.0.0.18: [.zip]
bin [15K],
doc [309K],
src [91K].
- 0.0.0.17: [.zip]
bin [14K],
doc [297K],
src [97K].
- 0.0.0.16: [.zip]
bin [14K],
doc [284K],
src [97K].
- 0.0.0.15: [.zip]
bin [14K],
doc [280K],
src [75K].
- 0.0.0.14: [.zip]
bin [10K],
doc [304K],
src [125K].
- 0.0.0.13: [.zip]
bin [7K],
doc [298K],
src [61K].
- 0.0.0.12: [.zip]
bin [10K],
doc [297K],
src [56K].
- 0.0.0.11: [.zip]
bin [10K],
doc [292K],
src [103K].
- 0.0.0.10: [.zip]
bin [10K],
doc [280K],
src [96K].
- 0.0.0.07: [.zip]
bin [10K],
doc [252K],
src [71K].
- 0.0.0.05: [.zip]
bin [10K],
doc [245K],
src [71K].
Development code
- These may be more recent than the latest "official" release above.
- They reflect the current state of the WWW pages.
- development: [.tgz]
bin [20K],
doc [358K],
src [75K]
- development: [.zip]
bin [?],
doc [?],
src [?]
(may be currently unavailable;
ask if needed)
Patches
Patches are computed and applied from the main
$TUNES directory,
and assume the various packages have been installed as above.
To apply a patch from file patch.$OLD-$NEW.gz,
use command
"cd $TUNES ; zcat patch.$OLD-$NEW.gz | patch -p0 -E"
To make patches (if you participate heavily in our development),
you need put the latest official release in $OLDTUNES
(which default to ../OLDTUNES in the Makefile; edit it if needed)
(GNU cp with options -dpRx might come handy)
and from the $TUNES directory, use the command
"make patch", then send me your patch.
They are available as
http://www.eleves.ens.fr:8080/home/rideau/Tunes/files/patches/$OLD-$NEW.gz
where $OLD and $NEW are the x.y.z.tt
version numbers for Tunes.
0.0.0.05-0.0.0.06 [5K]
0.0.0.06-0.0.0.07 [36K]
0.0.0.07-0.0.0.08 [26K]
0.0.0.08-0.0.0.09 [40K]
0.0.0.09-0.0.0.10 [57K]
0.0.0.10-0.0.0.11 [46K]
0.0.0.11-0.0.0.12 [81K]
0.0.0.12-0.0.0.13 [46K]
0.0.0.13-0.0.0.14 [86K]
0.0.0.14-0.0.0.15 [57K]
0.0.0.15-0.0.0.16 [35K]
0.0.0.16-0.0.0.17 [30K]
0.0.0.17-0.0.0.18 [40K]
0.0.0.18-0.0.0.19 [52K]
0.0.0.19-0.0.0.20 [98K]
0.0.0.20-0.0.0.25 [244K]
0.0.0.25-0.0.0.27 [89K]
0.0.0.27-0.0.0.29 [144K]
0.0.0.29-0.0.0.30 [37K]
0.0.0.30-0.0.0.31 [120K]
Mail archive
The archive for the Tunes@ens.fr
as well as the Tunes-LLL@ens.fr
and MOOSE
mailing lists,
is available
here.
Find out more about this downloadable archive
here.
Other files
Eric Biederman
is an active member who just released some early experimental code
for the Tunes LLL here
Patrick Premont
is an active member who has got interesting
documents
and
files
(also
here)
A patch to the 1995.03.12 version of Bruce Evans' bcc C compiler
for the 8086/80386/6809
(which includes the 16/32 bit assembler "as86" typically used to
assemble 8086 code linux, including the kernel and LILO boot code,
dosemu real-mode code,
and old Tunes code between version 0.0.0.10 and 0.0.0.25)
is available
here.
To Do in the Files directory
- Have the FTP site
regularly mirror these files...
- Make all the files actually available.
- Add individual entries for every file.
- Add file size information everywhere.
- Update the page regularly.
- Perhaps stop this splitting the archive in three parts,
because when the system is bootstrapped,
the sources will be an essential part of it
(remember - it's reflective, so accesses its own source),
and the architecture-dependent binaries can be made tiny,
then self-bootstrapping from the sources,
available as an architecture-independent bootstrap image.
- Actually, Tunes could be distributed with simple inefficient but small
early layers of boot code for every architecture
(if using something like openboot,
let's count a few tens of kB for unportable code
per supported architecture),
so that a truely portable distribution be possible.
Surely, a first run of such a system will be slow,
and the system image would be bulked by the high-level code
for all the supported architectures.
But there could be other, less portable versions, too;
it's just that a portable distribution would be fun,
and easier to fit the backup archives than tens of
specific distributions.
The problem is that until we prove that correct,
we oughta test that bootstrap on all machines before
distributing. But we can make it modular enough so
that by booting just on one computer, we know that
the non-booting part is preserved for all architectures,
whereas if an architecture's booting part was unmodified,
then we're sure it'll still work.
Project Coordinator:
Faré