Edit: Done, everything went well! As usual, contact if something is not working the way it should.

Someone will check what is going on in a few hours.

Edit: Good, the filer managed to finally reboot itself, we are back online!

Among other things, we are going to replace all storage disks, and we will also take this opportunity to migrate from ext3 to ext4 as well as starting from fresh new filesystems, which suffered a little bit corruption from storage issues we had several years ago.

Of course, this is going to take... hours... so be prepared for a week-end with hours of downtime! :)

Edit Saturday, April 7th, 15:26 UTC: Workforce successfully delivered at destination, work begin.

Edit Sunday, April 8th, 11:58 UTC: Work almost done, everything should be back.

Edit Monday, April 9th, 08:19 UTC: Workforce sent back to origin, on the road again ;-)

This is probably either a power outage or a dead Ethernet switch.

But, the secondary services (ns2 and mx2) are up and running, mails are kept in a safe place ;)

Please bear with us.

Edit: As planned, our main Ethernet switch died, leaving everything in the middle of nowhere :-). It was replaced successfully in a record time with our spare switch by our generous houser !

Edit: This one was of course not an April fool joke... or the Ethernet switch enjoyed the April 1st as well, doing a joke in its own way :-)

One of our beloved hosted wrote a server implementing the Gopher protocol. Because of that, we had to try on TuxFamily and we managed to make it run on the TuxFamily website as well as on the download service.

For all common browsers, the overbite plugin allows you to browse the gopherspace, so there is no technical difficulty to use Gopher.

Now convinced that Gopher is far more simpler and faster than anything running over HTTP, we are going to switch to Gopher all services that are currently running over HTTP.

However, in order to let you smoothly migrate to Gopher, we designed some simple milestones that should give you enough time to prepare the migration of your websites. Here are the key dates:

• In a few days : Gopher service added to VHFFS, you'll be able to create gopherspaces along with your current HTTP Web areas.
• 1st May 2012 : All TuxFamily "internal" services moved to Gopher, like the TuxFamily Website, the FAQ, the VHFFS Panel, and so on...
• 1st Jun 2012 : HTTP, FTP, RSYNC removed from download repositories.
• 1st July 2012 : Planned shutdown of the web area service.

As usual, feel free to contact us if necessary.

The TuxFamily.org team

Edit: Of course it was our yearly April fool joke ;-)

Your website may be impacted if by chance it reads data from your download repository through the /data/repository directory (note this practice should be avoided as much as possible).

The server will be back as soon as possible.

Edit: The server is back, everything is working again.

Of course, as TuxFamily follows almost day-to-day the VHFFS trunk, we are already running it !

Enjoy!, and please report any bug found!