Deprecated, a newer release is available.
=== July 22, 2010: Alt-F-0.1B3 released
-What's new:
-Kernel, libraries and apps compiled for execution speed instead of
space saving (as a result, and because of lack of flash memory space,
uShare and Transmission are now packages)
-kernel 2.6.33.6
-Filesystem Maintenance web page
-Disk Partition/RAID creation web page
-improved DHCP support
-improved fun_plug for ffp users
-improved Alt-F packages installation and administration
-Available packages:
-end-user packages with web administration page:
-Transmission, Fuppes, MediaTomb, miniDLNA, uShare, Firefly,
cups, hplip, samba-doc,
-command-line tools:
-dev-bundle, file, lsof, make, strace, nano, usbutils, unrar
-mplayer, lame, ffmpeg, sane
-networking:
-avahi, netatalk (both untested)
-filesystems:
-ntfsprogs
-databases:
-sqlite, bdb, gdbm,
-support libraries and tools:
flac, expat, libdaemon, libdlna, libexif, libfuse, libid3tag, libmad,
libogg, libpng, libtheora, libupnp, libusb, libvorbis, libxml2,
readline, taglib, tiff, pcre
-Known Issues:
-Rev-A1 and rev-C1 hardware boards not yet supported
-network link auto-negotiation doesn't work. As result Alt-F
only works when the box is connected to Gbit switches/routers
or network cards. 100/10Mbps switch or routers won't work.
-ghostscrip/hplip can fail with an "Unable to get scanline 0/1" error,
and cups does not notices it, sending the print job to the printer,
which prints a black page, wasting all your cartridge ink.
After configure the printer in cups, DISCONNECT THE PRINTER and print
a test page. If in the State column of cups jobs web page, or using
"lpstat -p" you see a "Unable to get scanline 0/1" message,
CANCEL THE PRINT JOB AND DON'T USE THAT PRINT CONFIGURATION.
-big MTU (~>3712 bytes) cause a lot of "page allocation failure" error,
which impairs network performance (NFS at least)
-nfs generates a lot of "received packet spanning multiple descriptors"
errors when MTU is not the same on both hosts!
-partition sizes are not uniformly reported. Sometimes are binary based,
others decimal based.
-component RAID disks hotpluging/ejecting might not do the right thing,
specially for raid0, JBD.
-some web pages go back in browser history when an error is detected,
instead of reloading the previous page. The user must refresh the page
-The Disk Partitioning web page is not able to re-partition disks whose
partitions that are not in increasing partition-start order, as the
vendor's partition table are when configured for "standard disks".
This only happens if the user whish to keep some partition in the
middle of the disk unaltered. The solution is to re-partition the whole
disk, loosing all it data.
