OS2World OLD-STATIC-BACKUP Forum

WebSite Information => Article Discussions => Topic started by: ff4 on 2012.02.19, 15:44:15

Title: pxeos4l released: overview & configuration
Post by: ff4 on 2012.02.19, 15:44:15
As current implementation of PXE miroFSDs are not fully compatible
with the OS/4 kernel the new pxeos4l microFSD was created to enable the
boot of the OS/4 kernel over the network.


A. Overview

The pxeos4l module is a part of the OS/4 project. The OS/4 project "phoenix" is
run by a team of talented developers.
This will be a small howto to quickly setup all correctly. Prequisites for this
test are a OS/2 alike install on HDD (MCP/ACP/eCS) that are capable to run
the new OS/4 kernel together with the new os2ldr - the client. The initial boot process
will be started from the network and then to be continued from HDD. For the
network part its required to have another OS/2 machine on the network that
will provide the files and services for the network boot, the client machine
requires an ethernet network adapter with PXE support, its not required to
have a working OS/2 NDIS driver for this adapter.

Summary of requirements:

 - OS/2 client machine with a build of OS/4 kernel & loader dated 23.1.2012 or
   newer (recommended to use revision 3636) + network adapter with PXE support
   http://ftp.Linking to this site is not permitted on our forums/os2krnlSVN3636_unoff.zip
 - OS/2 'server' machine for the network boot services
 - pxeos4 module ftp.Linking to this site is not permitted on our forums/moveton/pxeos4-1.120128.zip
 - TFTP-Server ftp.Linking to this site is not permitted on our forums/moveton/vgtftpd-1.0.zip
 - DHCP-Server http://www.os2site.com/sw/internet/dns/dhcp-3.1-esv-os2.zip


B. Configuration
   
Extract the tftpd and dhcp files to any place you like. Create an emty TFTP
directory that will hold the boot files, e.g. G:\TFTP then create the
subdir \OS4 and \pxeos4l.cfg
Place the following files from the OS/4 kernel package in the \OS4 subdir:

G:\TFTP\OS4\os2ldr.ini
G:\TFTP\OS4\os2krnl.os4
G:\TFTP\OS4\OS2LDR.os4
G:\TFTP\OS4\os4krnl.ini

from the working OS/2 client machine add

G:\TFTP\OS4\OS2LDR.MSG
G:\TFTP\OS4\OS2BOOT

from the pxeos4 package add

G:\TFTP\OS4\pxeos4l.0

create a config file for the client by using the mac address of the
network adapter in the client machine, this file will be placed in the
pxeos4l.cfg dir e.g.

G:\TFTP\OS4\pxeos4l.cfg\2C-41-38-AE-06-31.cfg

The settings of the config will include the name of the base files and
the boot device.

content of 2C-41-38-AE-06-31.cfg


========== 2C-41-38-AE-06-31.cfg =================================

# config for pxeos4l
device-id=128 # first HDD
device-part=1 # 0 - non partitioned, 1-4 - primary, 5+ - extended
drive=C # boot drive letter

# TFTP dir for files requested by os4ldr.
system-root=os4

# initial files to be loaded by microFSD
os4ldr=os2ldr.os4
os4boot=OS2BOOT

========== 2C-41-38-AE-06-31.cfg =================================

After we have finished the configuration for the client we can create the
configuration for the DHCP server. The files for the configuration are all
stored in the root of the dhcp server files, e.g. G:\DHCPD. Create an emty
file named dhcpd.leases

G:\DHCPD\dhcpd.leases

Then create the main dhcp.conf

G:\DHCPD\dhcpd.conf

The boot server has the ip address of 192.168.0.122 assigned. The complete
dhcp.conf will look like this:

========== dhcp.conf =============================================
# OS2 ISC DHCPD config file

option domain-name-servers 192.168.0.122;
authoritative;
ddns-update-style none;
default-lease-time 6400;
allow booting;
allow bootp;
class "pxeclients" {
   match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
   next-server 192.168.0.122;
   filename = "/os4/pxeos4l.0";
}

shared-network OS4DevCentral {
    subnet 192.168.0.0 netmask 255.255.255.0 {
    range 192.168.0.200 192.168.0.220;
    option routers 192.168.0.20;
  }
}
========== dhcp.conf =============================================

The setup is now ready, we start the TFTP service with the following command

vgtftpd.exe -root G:\TFTP

then the dhcp server

dhcpd.exe -f -d -cf G:\DHCPD\dhcpd.conf -lf G:\DHCPD\dhcpd.leases lan0

In case all services are running we can start the OS/2 client machine with
enabled PXE boot rom, change the boot order or use the boot menu of the BIOS
to try the boot from the network. In case everything is fine the PXE Boot client will
get the dhcp address from the boot server and then transfer the base files
for the boot from the tftp server then the boot will use the files of the os2
install on the HDD.
In case you run into troubles check the readme of the pxeos4l package, when
it comes to bugs of pxeos4l contact the author whose name can be also found in
the readme.

http://www.Linking to this site is not permitted on our forums/
Title: Re: pxeos4l released: overview & configuration
Post by: ff4 on 2012.02.19, 17:12:11
In case somebody may wonder but some urls were removed by replacing it with 'Linking to this site is not permitted on our forums', this seems to be made by an automatic script or manual change. Theres no reason todo so, we are not linking to strange content, like anywhere else - use on your own risk. People with interest can simply find the right urls using google. Thats a pretty nice way to 'help' new developments. Cheers
Title: Re: pxeos4l released: overview & configuration
Post by: CDRWSel on 2012.02.19, 17:56:46
What is it? ...
Title: Re: pxeos4l released: overview & configuration
Post by: IBManners on 2012.02.19, 18:02:02
The website or the software  ;D

I cant reach the website anyway, haven't been able to for over a week now.

I don't know if my network and the Primus network have been banned from the server end, or its on the Australian Censorship list.

Yes, Australia has a 'Voluntary' Censorship list, honest, no one has to use it but if an ISP doesn't use it they risk losing government listing or something.

Cheers
Ian
Title: Re: pxeos4l released: overview & configuration
Post by: ivan on 2012.02.19, 18:52:58
Ian, you aren't the only one blocked, or at least, have the OS4 site unavailable.  It just gives a timeout here in Europe.

@ff4. 
Is it possible to use another server that doesn't get blocked?

ivan
Title: Re: pxeos4l released: overview & configuration
Post by: David McKenna on 2012.02.19, 22:51:50
Maybe because of this: http://www.abuse.ch/ (http://www.abuse.ch/)
Title: Re: pxeos4l released: overview & configuration
Post by: RobertM on 2012.02.20, 03:32:37
In case somebody may wonder but some urls were removed by replacing it with 'Linking to this site is not permitted on our forums', this seems to be made by an automatic script or manual change. Theres no reason todo so, we are not linking to strange content, like anywhere else - use on your own risk. People with interest can simply find the right urls using google. Thats a pretty nice way to 'help' new developments. Cheers


Could it be

Just curious. Let us know.

Robert
Title: Re: pxeos4l released: overview & configuration
Post by: IBManners on 2012.02.20, 04:50:50
Hi Robert,

In ff4's case I think only No. 1 applies, he should however find another host, ---.su domain is badly tainted because its on half os.ru

Not saying that's it's right, just stating facts.

Cheers
Ian
Title: Re: pxeos4l released: overview & configuration
Post by: valerius on 2012.02.20, 18:44:56
2IBManners: Not sure if ff4 is Codex, Linking to this site is not permitted on our forums admin (more likely, he is not, I think). But in fact, the former Linking to this site is not permitted on our forums admin, Konstantin Okounkov agreed to pass him the site maintenance. It is still available as http://old.Linking to this site is not permitted on our forums, though, he attempts to create a new site with new content So, he has some legal rights to own the domain name..

Regarding the http://Linking to this site is not permitted on our forums -- in fact, there are some problems with DNS. So, probably, it is not related to ban list etc.

2all: Please, don't flame OS/4 team for pEracy and likewise. They work hardly. The only thing they need is feedback, but not bare word accusations in pEracy. Or you just repeat after e-co? E-co's claims about pEracy are not proven and are bare word. So, is it good to declare a team of programmers to be pErates and put a spoke in their wheel?  It is common now to put labels on everybody, and the worst label is pErate. Indeed this is just cunning manipulation.

ff4 posted news here about the project progress. Is that prohibited to post news about OS/2-related projects? There is a new PXE microfsd created, this is in fact a great news. So, let's discuss technical problems here, and test it, not to put labels on somebody

WBR,
valery
Title: Re: pxeos4l released: overview & configuration
Post by: ff4 on 2012.02.20, 19:38:07

Could it be
  • because you are releasing intellectual property that is not yours, and included in your works or as your own works?
  • because you are collecting license keys to products that are not yours?
  • because your site supports piracy of OS/2 related products?

Just curious. Let us know.

Robert

There are dns problems yes but there is nothing connected to spam or trojan horses on the site or inside the zip files in our case. What is interesting in the case of removing the links, one was simly pointing to the project site - a simple news page. What others already said - I posted the news along with a howto to quickly try and see if it works to get the feedback for the developers. There never was any piracy. keygens or whatever - all related to pxeos4l is new developed software. I would like to see somebody standing up here to explain exactly what it is about - removing simple links is censorship. We are in a free world and people can decide if they want to click on a link that *doesn't* point to any os2world related content - thats the base mechanism of the Internet. Simply annoying that we now talk about the access but not about the subject itself.

@ivan
makes no sense to post any other address here that will quickly get removed again, theres always another way..., but uploading the files to another server is not the aim right now.

Cheers
Title: Re: pxeos4l released: overview & configuration
Post by: RobertM on 2012.02.20, 19:38:43
Valery,

The site contains software that uses code they are not licensed to use in such a fashion. The site contains releases of software that has code in it that is not theirs, and that they do not have the right to.

As long as that is the case, linking to that site is prohibited on our forums and website. That is nothing personal. We are simply following the requirements our own rules and the laws that govern us require.

Thus, any good and legally unencumbered efforts there will also suffer, as linking there will remain prohibited until the situation is rectified.

Two additional notes:
(1) the eCo team are not the complaintants in this matter
(2) you have failed to address whether these releases (and others accessible via the prohibited links) contain code that is owned by or licensed to others (thus i cannot help you)
Title: Re: pxeos4l released: overview & configuration
Post by: RobertM on 2012.02.20, 19:46:42
ff4 you have not addressed the key issue. Are the other OS4 projects that contain others' code still hosted there? If so, then things will not change here.

This is not censorship. This is a privately owned web service where (a) there is no freedom of speech guarantee and  (b) we do not support linking to sites that contain code that the site owners do not have the legal rights to distribute.

We have asked for clarification of all of this via email, but you have not provided such - thus we cannot help you, and the sites will remain in the filter.
Title: Re: pxeos4l released: overview & configuration
Post by: valerius on 2012.02.20, 20:11:07
2all: BTW, just now -- I talked to e-co on his channel and he has threatened to me -- he insisted me to remove the mention of his name. When I rejected his claim, he *banned me from his channel* :) -- Just for all to know. The same way he threatens to admins of all sites and writes letters to ISP's of admins if they don't agree. He shut down almost all ftp sites in exUSSR in fact.

PS: WTF, does he thinks his name is Unnamable? Is he megalomaniac?
Title: Re: pxeos4l released: overview & configuration
Post by: RobertM on 2012.02.20, 20:30:38
Valery, that is in no way related to the issue at hand. Sorry we cant help you with THIS issue, but no one seems willing to address the issues presented.
Title: Re: pxeos4l released: overview & configuration
Post by: valerius on 2012.02.20, 20:59:37
2RobertM: The issue was that this post was about technical problems, and somebody just turned the conversation to pEracy. My previous post was just an illustration of methods of 'pErate fighters'. I will not advocate pErates but Codex's site does not contain public warez area. Do you see warez under anonymous login? OS/4 downloads are hosted at anonymous ftp area where no warez nearby. And it has no relation with 'warez' or pEracy. As I told, it's only label.

PS: It's seems OS/4 people doesn't care of this thread, So, I'll stop advocating it then :(
Title: Re: pxeos4l released: overview & configuration
Post by: RobertM on 2012.02.20, 21:06:53
those of us who have checked do see "warez" (some of the issues i mentioned) - btw, dont assume we are limited to the anon login.

 As apparently you arent authorized to act on their behalf, i appreciate your willingness to bow out of this conversation.
Title: Re: pxeos4l released: overview & configuration
Post by: miturbide on 2012.02.21, 21:14:13
Hi

1) My recommendation to the OS/4 team is that publish their files on public sites like hobbes (http://hobbes.nmsu.edu/), sourceforge, etc, etc... and make the announcement of their progress via OS2World.com or the other OS/2 news sites. I will be happy to post their progress as news.

2) My other recommendation to the OS/4 team is to open source their software under any OSI approved open source license. If the source code is available and the use license is defined and clear there will be no doubt about their work and many other people will be interested on supporting him. Otherwise we will be always on the doubt about how to use the files they produce.

About the "xxxx" server, it had been blacklisted on this forum because it contains copyrighted files on a Warp 4 boot image contained there for public download (BootFlash512.7z).

OS2World.com site can not afford problems related to linking illegal files, since we don't have resources to solve any legal problem that may appear in the future. I prefer to blacklist a site than have the risk to shut down OS2World.com.

valerius, I personally envy you... I still don't know how to get banned from him ;)
Title: Re: pxeos4l released: overview & configuration
Post by: valerius on 2012.02.22, 15:46:35
2Martin: Was very surprised that my personal projects 'Flash512' and 'BootCD' also got blacklisted. Their purpose is demonstrate the new OS/2 booting technology I invented. (Flash512 is a 512 Mb bootable flash with OS/2, BootCD is a newer boot disk using the new method of booting from 'ramfs.ifs' RAMdisk). I specially removed things like ACPI or Panorama from the disk, but as you understand, could not remove Warp4 files as then there will be nothing to boot. Yes, so, OS/2 community must remain  without the Live CD/flash again, and nobody cares. Somebody cares about IBM's copyrights though IBM doesn't care about OS/2 for a long time...

Yes, I had an idea to make something like PE builder, but for OS/2, but I have no time for that. So, then I'll remove my boot disks from public area, if you insist. Then those interested in my boot disk will need to ask me to give them 'hands to hands'.

PS: These files are not related to OS/4 (the boot disks contain only OS/4 loader and kernel, together with IBM ones)
Title: Re: pxeos4l released: overview & configuration
Post by: IBManners on 2012.02.22, 17:33:40
Hi valerius,

That's the way copyright works, using a little bit of something that's copyright protected is just as bad as pinching the lot. Think of it as you are saying its a little bit dead, so that's not as bad as completely dead - the end results the same :D

You also need to remember its not just IBM but Microsoft that is involved in OS/2 code copyright, if it was just IBM involved I suspect they probably would open source OS/2 code as no one in IBM really cares but because Microsoft AND others were involved, its a different ball game. Bending the law is not better than breaking the law in US, UK, and AU, the penalties are often the same  :(

Everything on your server needs to be clean, the same applies to OS4 code, you cant take what someone else has produced and modify it, to be legally correct it needs to be done in a 'clean room' environment with no 'dirty' (read copyrighted) code involved.

In relation to your Flash512 and BootCD you could provide a howto.txt text file, and all the other non copyright files, leaving it up to the user to add the copyright files themselves. By doing it this way you are in effect 'keeping your hands clean'.

My understanding re the kernels you provide is that you could provide a patch file only, once more leaving it up to the user to provide the kernel themselves as well as a quick readme.txt file explaining the simple patch process. I could be wrong here but as you are not providing someone else's code, or altered code, only the means of altering what the user already has, this then becomes legal.

Cheers
Ian
Title: Re: pxeos4l released: overview & configuration
Post by: abwillis on 2012.02.22, 17:42:56
You also need to remember its not just IBM but Microsoft that is involved in OS/2 code copyright, if it was just IBM involved I suspect they probably would open source OS/2 code as no one in IBM really cares but because Microsoft AND others were involved, its a different ball game.
Actually, Microsoft already told IBM they didn't care if it was Open Sourced... IBM chose not to do the Open Source of OS/2 due to the expense.  IBM will Open Source if it either doesn't cost them much or even if the cost is high if there will be a return on the investment.  They did not see any return on the investment if they were to Open Source OS/2.
Title: Re: pxeos4l released: overview & configuration
Post by: miturbide on 2012.02.22, 18:26:04
...Microsoft already told IBM they didn't care if it was Open Sourced...

I personally do not trust that kind of statements from Microsoft. I remember that on the OOXML fight they promise ODF support on Office 2010. At the end they put a mediocre ODF support that breaks the ODS file formulas as "values".

If it is not signed, I can not trust Microsoft. They may even twist the statement as saying "...Yes, we say we don't care, but that doesn't mean we can not charge a license fee" ;)
Title: Re: pxeos4l released: overview & configuration
Post by: valerius on 2012.02.22, 18:43:18
2Yan: Yes, I already thought about a HOWTO or a tool like PE builder which could be supplied together with my own files... But the problems are 1) the lack of time 2) the distributions of  OS/2 files is a carefully chosen collection of files, so versions does matter very much. For example, IBM's versions of os2ldr hang on many machines when booting from flash disk, so I worked with OS/4 team for their os2ldr to be fixed. And much drivers must have definite versions too. So, I must pass all such problems to user's shoulders. And, as it was noticed, many users will stop using it because of the problems. So I see no good exit from this situation :(

PS: The os2 dot ru is not my site and my files were only hosting there. I am also have no relation with OS/4 project (I can participate here only as a tester, not more).
Title: Re: pxeos4l released: overview & configuration
Post by: IBManners on 2012.02.22, 19:05:49
Hi AB,

Doesn't matter what Microsoft say, IBM's not even willing to get the legal departments talking because of both the $ involved, and distrust of Microsoft, so yes you could say certainly no ROI for IBM to open source OS/2 according to the accountants, the initial hurdles cost to much, and not much of OS/2 can be used elsewhere anyway. It's in the to hard basket and there I'm sure it will stay.

Cheers
Ian
Title: Re: pxeos4l released: overview & configuration
Post by: RobertM on 2012.02.22, 23:21:49
You also need to remember its not just IBM but Microsoft that is involved in OS/2 code copyright, if it was just IBM involved I suspect they probably would open source OS/2 code as no one in IBM really cares but because Microsoft AND others were involved, its a different ball game.
Actually, Microsoft already told IBM they didn't care if it was Open Sourced... IBM chose not to do the Open Source of OS/2 due to the expense.  IBM will Open Source if it either doesn't cost them much or even if the cost is high if there will be a return on the investment.  They did not see any return on the investment if they were to Open Source OS/2.

Well, it was more than just getting Microsoft to clear things. There are many dozens of other companies that contributed code to OS/2, licensed to IBM, for which IBM would need to get clearance from. Some of those companies exist in name only now (or as a different entity of the same name), making things even more difficult. One such company was Commodore.

Then there's technology that is still in part used by other companies (who I am sure would not want it open sourced), such as supposedly Apple.
Title: Re: pxeos4l released: overview & configuration
Post by: RobertM on 2012.02.22, 23:23:53
Side note: last I heard, tracking down all of the sources for much of OS/2 would be near to impossible. Are the relevant sections available? Not a clue - but not something I think we'd get an answer to anyway. As it is, most of the people who worked on various subsystems have "disappeared".
Title: Re: pxeos4l released: overview & configuration
Post by: valerius on 2012.02.23, 02:02:02
2Ian Manners: An interesting thought has come... If this is not a secret -- everybody knows that your site contains many OS/2 kernels and fixes. But aren't they OS/2 binaries (which cannot be redistributed without IBM's permission)? So, do you have a special permission given by IBM? Could you open a secret to other sites' admins -- how is it possible to distribute OS/2 files when even eCS Demo CD is not permitted to redistribute? I'm just curious -- I am do not sell my CD/flash too, get no profit/just for fun, but it's illegal. So, maybe, I just could ask you to host it on your site (if you agree, and maybe, OS/4 files too?).

PS: If you have no IBM's permission to do so, what makes your site to be different from 'warez' ones, when you say other sites are?
 
Title: Re: pxeos4l released: overview & configuration
Post by: RobertM on 2012.02.23, 02:29:57
2Ian Manners: An interesting thought has come... If this is not a secret -- everybody knows that your site contains many OS/2 kernels and fixes. But aren't they OS/2 binaries (which cannot be redistributed without IBM's permission)? So, do you have a special permission given by IBM? Could you open a secret to other sites' admins -- how is it possible to distribute OS/2 files when even eCS Demo CD is not permitted to redistribute? I'm just curious -- I am do not sell my CD/flash too, get no profit/just for fun, but it's illegal. So, maybe, I just could ask you to host it on your site (if you agree, and maybe, OS/4 files too?).

PS: If you have no IBM's permission to do so, what makes your site to be different from 'warez' ones, when you say other sites are?

Stop wasting our time:
(1) we do not host kernel files here
(2) the kernel files you speak of are from IBM or Mensys, who own the code, or the rights to distribute the binaries
(3) the eCS Demo CD is released by Mensys, who has the rights to distribute it.
(4) You have no such rights to distribute such
(5) In the country OS/2 World is hosted in, selling (or making money) is not required for one to be violating intellectual property laws

Anyway, try Hobbes to host your files.

Rob
Title: Re: pxeos4l released: overview & configuration
Post by: valerius on 2012.02.23, 02:55:38
2RobertM: The question was directed to Ian, I don't asked os2world to host any files. And there was a bit of joke here, so do not treat it too seriously :) I want everybody to understand me correctly: I mean, os2site hosts many OS/2-related binaries, and nobody sues him. His site is very useful, I don't want to be shut it down. But I interested in his answer, what is the secret? Nothing personal for Ian, just want to have understood...

PS: And no desire to scandal, we've already got a productive dialog with Martin on #os2russian, so need to be more constructive and understand each other...

WBR,
valery
Title: Re: pxeos4l released: overview & configuration
Post by: IBManners on 2012.02.23, 08:34:02
Hi valery and anyone else interested,

os2site.com host some kernel TESTCASE files, and some kernel files that are in IBM publicly available legacy boot images mirrored in the 'boot' section.

I have not made changes to the intellectual property of IBM or other entities to any of the files hosted on os2site.com, all copyright and ownership information remains intact on/in all the files hosted on os2site.com.

I was given permission years ago (hmm, probably around 2000/2001) to keep copies of the testcase kernels on the proviso that I only keep a couple of the latest ones, I am not allowed to put the entire testcase archive online, which is why you will note that the latest/last IBM kernels are not there either.

Kernels that are a part of Fixpacks (ie, contained in the fixpacks) are also ok to mirror as long as they are ONLY the publically available fixpacks. This is also why the latest fixpacks are not available on os2site.com, or on hobbes for that matter.

For someone to commence legal action against me they have to first issue a takedown order, then I have to ignore it's directives within the time limit set, in theory, the reality is no one is now sure of what happens because American law enforcement appears to be able to request local Australian and NZ law enforcement to knock your door down and take all your stuff away before they issue a takedown order on their way out of the door..

Cheers
Ian
Title: Re: pxeos4l released: overview & configuration
Post by: valerius on 2012.02.23, 11:33:22
2Ian: Sorry for an incovenience, I really didn't thought that it is possible to get permission from a corporation like IBM to an individual like you -- thought that it was possible only for corporations like Mensys/Serenity. The reasons are its bureaucracy and money -- it is known how ended up the petitions to opensource OS/2, for example. So, if IBM allowed it to you, then it knew what it did, and it could not allow it to random people. So, you were appreciated by IBM for something. So, my big apologies, I only wanted some justice. I was mistaken, I'm sorry

P.S. also, I am, together with many OS/2 users, very thankful to you for your site support, because some files are hard to find on other sites, even they're missing sometimes on IBM's sites -- as IBM forgot about OS/2 and removed many files. So, I want it the long live. Also, I want to say that other sites are carefully collecting OS/2 files, so if we would persecute them as pirates, then only several 'legal' sites will remain, so if they suddenly became down, the community will be in danger. So, if to follow the law literally, we could destroy our community itself. So, it has benefit only for people like I named previously, these people blackmail the community sites and try to make FUD. Yes, they're formally right, but make that for their own profits.

WBR,
valery
Title: Re: pxeos4l released: overview & configuration
Post by: ff4 on 2012.07.17, 14:24:33
Stop wasting our time:

That's not a nice way to stop somebody to talk even when it was addressed to somebody else in this case. About the files, these are not provided by os2world and placing beta code on hobbes is not an option.
Title: Re: pxeos4l released: overview & configuration
Post by: miturbide on 2012.07.17, 14:51:42
Dear ff4.

I already talked to Valery about this subjet long time ago and he understand me. We chat on the #osfree channel from time to time.

OS2World can be closed for linking files that are copyrighted. Even if the files are not on our server.

The OS4 kernel is based on leaked IBM kernel source code, that's why it makes it ilegal to distribuite that files.
Also, distribuiting abandonware is consider by law a copyright infringement (http://en.wikipedia.org/wiki/Abandonware)

A solution to distribuite OS4 may be to release the files as a kernel patch or to completely replace the IBM code from the kernel.

We don't do this because we are in favor or not of the OS4 team/kernel, we do it because we don't want OS2World to be closed.

Thanks.
Title: Re: pxeos4l released: overview & configuration
Post by: WarpWorld on 2012.07.17, 17:58:49
Similar situation as some programmers had with BeOS Dan0. Code of Dan0 ''leaked'', Be Inc. closed, and some people made own distributions, based on Dan0's modifications. In that time c.holder was Palm Source and it was very indifference (like IBM now) very hard to say YES or NO in written form, and many interpreted as YES I can make freeware distribution, and someone had really permission from Palm Source but verbal, and in 2007 holder became ACCESS who clearly said NO YOU CAN'T. Unclearly still stayed what with unmodified version of Dan0 who received permission of Palm Source for educational purposes. Many said that deal is still current.

So people from OS/4 team, try permission from IBM for educational necessary modification of OS/2 kernel as OS/4 and other stuff to stayed under other valid licenses.