Re: Permanent static route in AIX 4.3

"Steve Greatbanks" <steve_greatbanks@xxxxxxxxxxx> wrote in
news:ds1mc7$30n8$1@xxxxxxxxxxxxxxxxxxxx:

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/
com.ibm.aix.doc/files/aixfiles/rc.net.htm Unsupported? Really?
It is supported, but it is a system file that can be overwritten by a PTF,
whereas changes to the inet0 ODM object tend to be kept. If a PTF zaps all
your changes to /etc/rc.net, IBM support will say: "Your problem. Use
inet0 or your own init file".

If you want to add your routes to a file instead of the ODM, just add your
own inittab entry, say /etc/rc.local .

And in the doco above, "traditional configuration method" could easily
be replaced
by "portable configuration method" :)
The problem with the theory of the "portable configuration method" is that
it clashes with system files. The ODM is a way of keeping data separated
from code(the scripts), so that you can update the code without having to
identify user changes and port them into the new scripts.

Heck, even linux is separating code from data.

One of the dangers with /etc/rc.net modifications is that IBM
reserves the right to overwrite or alter it during patching or OS
upgrades. They will leave ODM values alone, such as the chdev -l
inet0 approach.

This is a tricky area. I don't have insider information about what IBM
intends to deprecate and what will or won't be supported. My guess is
that rc.net is reasonably safe.

rc.net is safe, it's been there for over 15 years (and with minor
modifications along the way).

It's also not safe, since sometimes it gets trampled during version/release
migrations.

I'm sceptical that IBM would describe rc.net and the route command as
"unsupported".
It's supported but unsafe.


--
Doing AIX support was the most monty-pythonesque
activity available at the time.
Eagerly awaiting my thin chocolat mint.
.

Relevant Pages

  • Re: Windows Explorer application errors
    ... The system file c:\windows\system32\commdlg.dll could not be copied into the ... The specific error code is 0x00000000 [The operation completed ... This file is necessary to maintain system stability. ... see Help and Support Center at ...
    (microsoft.public.windows.server.general)
  • Re: Help PLs! Script Error trying to open Help and Support.
    ... Event Source: Windows File Protection ... Windows File Protection scan found that the system file ... see Help and Support Center at ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Windows Explorer application errors
    ... The system file c:\windows\system32\commdlg.dll could not be copied into the ... The specific error code is 0x00000000 [The operation completed ... This file is necessary to maintain system stability. ... see Help and Support Center at ...
    (microsoft.public.windows.server.general)
  • Re: Windows Explorer application errors
    ... The system file c:\windows\system32\commdlg.dll could not be copied ... The specific error code is 0x00000000 [The operation ... This file is necessary to maintain system stability. ... see Help and Support Center at ...
    (microsoft.public.windows.server.general)
Loading