public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Segin <segin2005@gmail.com>
To: � <vsazel@atlas.cz>
Cc: linux-8086@vger.kernel.org
Subject: Re:
Date: Wed, 26 Apr 2006 19:07:41 -0400	[thread overview]
Message-ID: <444FFD3D.4030000@gmail.com> (raw)
In-Reply-To: <444FFA9F.5010301@atlas.cz>

� wrote:

> Hi!
>
> I have subscribed to this mailing list 14 days ago. This is the first 
> message i've received.
> I would like to do the same. Is ELKS dead forever?
>
Who the hell knows. Now, on ELKS development, I have hacked together a 
"alternative" libm for ELKS. It consists of Minix 2 and OpenSolaris (no 
shit) code, and I am currently trying to find of libm functions that are 
nice to have, kk, let me pack my bowk..., much better. Now, the most 
important thing to remember here is licensing. ELKS is LGPL/GPL. Minix 2 
is BSD. OpenSolaris is CDDL. This provides us with a clash. Pot, the 
GPL, and the CDDL license, and you are concocting an illegal mess, GPL 
code cannot legally link against CDDL code. THC loves the GPL with the 
BSD license, so all's fair in love and war.

> With regards,
> Vojtech Sazel
>
> pfengland@mailshack.com napsal(a):
>
>> hi.
>> I know not a lot is being done on ELKS these days, but I would really 
>> like to use it and possibly do some development on it.  I'm having 
>> some trouble though
>> Date: Wed, 26 Apr 2006 16:30:49 -0500
>> From: pfengland@mailshack.com
>> Subject:
>> To: linux-8086@vger.kernel.org
>>
>> 1.) I can't access the archives of this list so that I don't ask 
>> questions which have already been answered.  I tried 
>> http://www.geocrawler.com/lists/3/Linux which redirected me to a 
>> sourceforge page saying it wasn't found.
>> I also tried http://www.geocrawler.com/lists/3/Linux/ which didn't 
>> work either.
>>
>> 2.) I can't check elks out from cvs, so I'm stuck using an older 
>> version:
>> $ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/elks login
>> Logging in to :pserver:anonymous@cvs.sourceforge.net:2401/cvsroot/elks
>> CVS password:
>> cvs login: authorization failed: server cvs.sourceforge.net rejected 
>> access to /cvsroot/elks for user anonymous
>>
>> Any help would be greatly appreciated.
>>
>> Forrest
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
>>
>>
>>
>>   
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-04-26 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060426223343.0E21590BB5@kelly.nerdshack.com>
2006-04-26 22:56 ` Vojtěch Sázel
2006-04-26 23:07   ` Segin [this message]
2006-04-27 10:58   ` Re: Hans
2006-04-27 15:44 Re: James Tabor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=444FFD3D.4030000@gmail.com \
    --to=segin2005@gmail.com \
    --cc=linux-8086@vger.kernel.org \
    --cc=vsazel@atlas.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox