problem solved (Re: new OLPC slackware 13.37 released (fwd)

supat at supat at
Tue May 31 07:36:50 EDT 2011

Thank you much for your kind information.
Two major reasons why I never put how to at Wiki are:

1. I don't think I have authority to do so.
2. I am very busy on teaching in my university.

Are you sure I have authority to write at Wiki? I say so because even in 
this news group I don't have authority but it was you who FWD it in.

I plan to write short easy mini how to make slakware to work in OLPC in 3 
manners :

1. after they put any thing they want to USB then I made USB to boot under 

2.  a small minimal Slackware that work on OLPC and then they can add any 
packages they want.

3. optimal slackware OLPC ready to be used.


On Tue, 31 May 2011, James Cameron wrote:

> On Mon, May 30, 2011 at 09:07:59PM +0700, supat at wrote:
>> On Mon, 30 May 2011, mokurai at wrote:
>>> Have you added this download to the Wiki?
>> No. I never did so.
>> Please let me know why I have to do so?
> It is not mandatory, but it is optional, and helpful.
> Documentation in the Wiki is beneficial to future users, or current
> users who may wish to try Slackware on their OLPC XO.  Many of these
> users are not on this e-mail list.
> It is really your choice whether to publish on the Wiki, but if you do
> not do it someone else may do it, and the message they write may not be
> to your liking.  Have some faith in the value of your work, don't just
> abandon it like a stray pet.
> For instance, for the Tiny Core Linux builds, we have a Wiki page on
> OLPC Wiki
> And we have a general "Minimal Linux Distributions" page at
> which mentions four
> Slackware based distributions that are not known to be available for the
> And we have a "Sugar on Slackware" page at
> which says nothing useful,
> yet points to the Sugar Labs Wiki which has nothing useful on Slackware.
> Anyone reading the Wiki now, looking for Slackware information, would
> naturally conclude there is nothing available.
> If your work is not for general use, then fine, keep it silent.
> Your work does seem opaque ... you have not shown *how* you made the
> build, and therefore it is not publically reproducible ... and the sum
> of knowledge has not increased markedly.  But the same can be said for
> some other builds, yet they are of use.
> -- 
> James Cameron

More information about the Devel mailing list