• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

pxeos4l released: overview & configuration

Started by ff4, 2012.02.19, 15:44:15

Previous topic - Next topic

ff4

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/

ff4

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

CDRWSel


IBManners

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
I am the computer, it is me.

ivan

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

David McKenna

#5
Maybe because of this: http://www.abuse.ch/

RobertM

Quote from: 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


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


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


IBManners

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
I am the computer, it is me.

valerius

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

ff4

Quote from: RobertM on 2012.02.20, 03:32:37

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

RobertM

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)


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


RobertM

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.


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


valerius

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?

RobertM

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.


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


valerius

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 :(