Saltfire Distribution Status

My private GNU/Linux distribution project is primarily for servers, and does not yet contain a windowing system.  I plan to eventually integrate the primary system perhaps using some form of text windowing with ncurses.  I plan to add some version of X or maybe something a bit less massive – as part of the end user environment. Someday, I may release it, but a lot of cleaning up, and multi-platform porting would need to be done.  At this point, I have no plans to port the system off the X686 architecture.  One primary target is a system which can be built onto a remote boot disk, perhaps over a network.  At this point it is too large to fit on CD-/-DVD-/-ROM.

After upgrading to 2.6.24 significant stuff refused to work, and more stuff refused to compile. I reverted and ran several massive rebuilds, however I am still running a slightly old kernel, just to get builds completely working again.  This effectively holds building the distribution, while a new baseline is made and tested. The problem seems to involve changes to kernel headers, which have propagated to glibc, and gcc issues, which then propagates most everywhere. This is complicated by new releases of various packages which seem to be more or less inherently broken. It also brings to light an old set of software problems, perhaps new to Linux, which the “community” needs to solve.

This ongoing project has involved significant time and lots of Perl code, which has become my current language of choice. It is more C like than REXX, and seems to work better on a small machine, however it is rather heavy for bootstrapping a system.  I still love PL/1, but no one seems to use it anymore, and I don’t have time or incentive to write a Linux compiler for it. Besides, I suspect a syntactically constrained version of Perl6 – if it ever arrives – will be functionally equivalent, maybe syntactically similar, to the PL/1++ that never was. I don’t plan to go down either rabbit trail, because I believe human readable and coded computer software, itself will soon enough become a relic of the past.  One goal is to support a development platform to accomplish this.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: