Porteus

Here is a relatively simplistic example of how I would ultimately like this to work.
https://github.com/Sitwon/Byzantium/com ... 02b69238a7

Currently it only handles SBo-style packages, I need to finish writing support for Pat's and Ponce's trees as well.

Another Humble Bundle with five cross-platform (including Linux) games. Time is limited, grab 'em while they're hot.
http://www.humblebundle.com/

My squashfs-tools SlackBuild was accepted at SBo. I suggest future releases use this.

http://slackbuilds.org/repository/13.37 ... hfs-tools/

JFS is pretty efficient with large files.

Hamza wrote:If it works, please say it is NOT an official channel.

In that case, we can just continue using ##porteus and ignore #porteus.

It seems that #porteus has already been registered by the user XDS2010. I have registered ##porteus for us.

Freenode will allow us to reclaim #porteus if the primary contact for the project registers the group.
http://freenode.net/group_registration.shtml

http://happypenguin.org/ Lots of games are native on Linux as well. Some of the best known are Wesnoth and OpenArena. There's also the UT series (with the exception of UT3) and all the various Humble Indie Bundle games. And for Porteus, any of these should be easy to pull in. http://slackbuilds.org...

Worse yet, in this site (http://forum.porteus.org/viewtopic.php?f=53&t=640) you [Fanthom] ask your contributors for binary modules, which could easily conceal malware! Wouldn't it be better for everybody if contributors just uploaded the code -which procedence can be easily confirmed- and a script ...

What you describe sounds pretty much what i use for my own setup (minus the makefile). As i mentioned earlier i was playing around with an SVN for Porteus and in the end, it is just much easier to offer the ISO. The end user has to download much more than 300Mb otherwise. I still think it should be...

I would recommend having an IRC channel instead of the mini-chat. Most Free/OpenSource projects use IRC (often irc.freenode.net). I would suggest #porteus on freenode. In place of the mini-chat you could use an embedded IRC client such as qwebirc. http://www.qwebirc.org/ As an example, Hak5 uses qwe...

So what I'd like to propose is that under the base/ directory there would be a directory for each module. 000-kernel/ 001-core/ 002-xorg/ ... and so on Within each module directory you would have build/ - The module's root directory. Files that aren't coming from packages should be placed in here an...

@fantom & brokenman First of all, thanks a lot for publishing your development trees. It's a great help having that to look at as a resource. Unfortunately, there still seem to be a few gaps. https://github.com/Sitwon/Porteus/tree/master/base As you can see I have extracted lists of packages for eac...

Here is full Porteus 64bit tree: http://ponce.cc/porteus/x86_64/current/extras/Porteus-1.0-x86_64-Tree_including_updates_to_01.07.11.tar.bz2 The tree contains all loose files which are not listed in /var/log/packages/* files (slackware/custom packages). Tarball includes all updates and fixes merged...

There's a mailing list?

What kind of WiFi dongle is it? Do you know the chipset?