The UberJS Website

UberJS Standard
UberJS Server

Important Changes to UberJS NetInit

NetInit is the network initialization code that is the backbone of UberJS and UberJS Server. The changes in the new version, to be detailed below, should not break anything in your current builds. What is included is some bug fixes and additional features to make your life easier.

Due to a recent influx of inquiry, a run of new development has started and a whole bunch of new features are already in place and more are coming.

03/04/04 - After much testing, this release seems pretty stable and you should have good luck working with it. In a few days I will reversion it to 4.0.2 (from 4.0.1a).

A list of features and bugfixes:

  • Default router bug fix
  • New touchfiles in /tmp/uberjs enable and disable functions to save you time
  • As part of the above, some major improvements in the way of determining interfaces, skipping interfaces, and using specific and/or primary interfaces
  • A separate fix to UberJS Server code resolves a bug on machines with no OBP devalias for cdrom and causing an incorrect boot to the SBC code
  • Another fix for UberJS server resolves a non-existant default route bug on the server booted client.
Detailed description of changes:

Default route:
The route command on solaris does not support the gw tag, simply removed it so the executed command is 'route add default'. This may have has a minor effect on UberJS Server's functionality since it uses rarp.

New touchfiles:
There are four new types of touchfiles you may create in /tmp/uberjs (.tmp_proto/uberjs)

/tmp/uberjs/nodhcp: forces skipping of dhcp for interfaces not specified as DHCP in ipethers, saves waiting 60 seconds when no dhcp server is available. Essentially skips the installer right to a manual entry prompt if the machine is not in ipethers.

/tmp/uberjs/noautoroute: forces skipping of automatic route detection after manually configuring the interface. The installer will be prompted for a default gateway every time.

/tmp/uberjs/useonly-{interface}: allows you to specify primary interface only, or a specific interface name such as hme0. Acceptable options are any valid interface name or 'primary'. Examples: /tmp/uberjs/useonly-primary, /tmp/uberjs/useonly-fcip0, /tmp/uberjs/useonly-le0, or /tmp/uberjs/useonly-hme0. You may create more than one useonly to essentially supply a list of valid interfaces that may be used. It is also ok to have a useonly-primary as well as useonly-hme0 for example.

/tmp/uberjs/ignore-{interface}: allows you to specify one or several interfaces to never use, such as /tmp/uberjs/ignore-fcip0 to always ignore the fibre interface. Note: ignores take precedence over useonly's, ie useonly-primary when the primary interface is fcip0 used with ignore-fcip0 will result in that interface being skipped.

UberJS Server:
Some machines when booting from the UberJS Server CD thought they were server booted clients. This was due to some architectures needing to check for / being mounted from a scsi device. Fixed by adding an additional check.
Some machines when booting from an UberJS Server as a Server Booted Client encountered build errors at the sysidcfg phase due to a missing default router. Some machines when boot net runs get a default router, others get only a route to the UberJS Server machine. Fix this by putting in automatic route detection and prompting as a fallback.

Upcoming changes and updates:
  • Better text interface, testing use of gnu Dialog currently.
  • Possibly an X based interface as well

Home UberJS Standard UberJS Server Links

 For problems or questions regarding this Web site contact
Last updated: 03/04/04.