lkml.org 
[lkml]   [1998]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: beos-bootloader?
Date
Followup to:  <19980406193046.47068@cerebro.laendle>
By author: Marc Lehmann <pcg@goof.com>
In newsgroup: linux.dev.kernel
>
> I cannot imagine somebody confusing this with lilo. This is clearly kernel
> code. The question is wether (pseudocode) "ld boot-loader.o kernel-image.gz"
> is considered "linking". (at least they used the linker to do this).
>
> Again, there is no sign of lilo code in it. it's _kernel_ code.
>
> It might have surely been some dumb attempt at getting beos to boot with
> lilo or loadlin, but this is the beos kernel image, and it clearly contains
> linux code. Wether or not they give credits (to my knowledge, they didnt
> (renaming their bootloader from lilo to belo isn't exactly fine, either)),
> is another important question only somebody owning the commercial beos
> distribution can answer.
>
> In any case, I doubt they will have a notice saying "The beos kernel image
> was linked together with some linux code".
>

Actually, the decompression module is a hunk of standard code from the
gzip or info-zip distribution (not sure which) that is quite
explicitly declared public domain (not GPL, not LGPL, not BSD, but
without any copyright and hence restrictions, whatsoever.)

-hpa

--
PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74
See http://www.zytor.com/~hpa/ for web page and full PGP public key
I am Bahá'í -- ask me about it or see http://www.bahai.org/
"To love another person is to see the face of God." -- Les Misérables

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.627 / U:0.236 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site