Part of Slepp's Projects — Pastebin — TURL — Imagebin — Filebin
Feedback -- English French German Japanese
Create Upload Newest Tools Donate
Sign In | Create Account

Paste Actions

Download Raw
Embed
Post to Twitter
Remove Paste

Paste Details

Raw format, 3 years 6 months old, and 128 hits.

Paste Description for server instl_boottab

/etc/opt/ignite/instl_boottab on server

server instl_boottab
Thursday, August 10th, 2006 at 3:13:21am MDT 

  1. # NOTE: This table is only for booting PA-RISC clients.  For booting IPF clients
  2. #       you have to edit /etc/bootptab.  Please see the example in
  3. #       /etc/bootptab for instruction how to add entries.
  4. #
  5. # /etc/opt/ignite/instl_boottab:  Used by /opt/ignite/lbin/instl_bootd(1M)
  6. #
  7. # This file contains a list of IP addresses to be reserved for booting
  8. # clients during an the HP-UX install process.  These addresses are
  9. # used only during the boot period and not at any other time, thus
  10. # they are temporary.
  11. #
  12. # A list of (one or more) IP addresses should be entered below, one
  13. # per line, beginning in the first column.  The IP addresses will be
  14. # cycled through for each consecutive client that boots.  If many
  15. # clients are booting at the same time, it may be necessary for you to
  16. # enter several addresses to keep the server from denying any client
  17. # access.
  18. #
  19. # When instl_bootd allocates an IP address to a client, it will
  20. # change the line to include the clients network hardware address and
  21. # the date/time that it booted (fields 2 and 3).  This data is for use
  22. # by instl_bootd when determining which address to use next time.
  23. #
  24. # File Syntax:
  25. #
  26. #    - Comments can be included as appropriate.  They are denoted
  27. #      by the '#' character and end-of-line.  They can appear at the
  28. #      end of an IP address line, or on a line by themselves.  Blank
  29. #      lines are also allowed.
  30. #
  31. #   Non-comment lines can contain 1 or 4 fields.  Fields are separated
  32. #   by the ":" (colon) character.  Each fields is described as follows:
  33. #
  34. #       Field 1: Must start in the first column, and contain an IP
  35. #                address in "dot" notation.  This field is not optional.
  36. #
  37. #       Field 2: Can be empty, or can specify the LAN hardware address
  38. #                of the system that last used the entry, or (depending
  39. #                on field 4), the only system that is allowed to use it.
  40. #                This field is updated automatically by instl_bootd.
  41. #
  42. #       Field 3: Can be empty, or can specify the date/time of the last
  43. #                time that the IP address was used.  This field is also
  44. #                updated by instl_bootd.  It should be left empty when
  45. #                adding new entries.
  46. #
  47. #       Field 4: Can be empty, or the keyword "reserve" can be
  48. #                specified to prevent an IP from being allocated to
  49. #                any client not matching the hardware address value in
  50. #                field 2.  If field 2 is empty ("::"), then when the
  51. #                entry is issued to a client, that entry/IP-Address
  52. #                will become reserved for that system and will not be
  53. #                allocated to any other systems.
  54. #
  55. # Example: (lines are intentionally commented out)
  56. # 15.1.54.125                             # IP address usable by any client
  57. # 15.1.54.126:080009123456:19960116132331 # Entry usable by all (used already)
  58. # 15.1.54.127:::reserve                   # Reserve this entry once used.
  59. # 15.1.54.138:080009123457::reserve       # Reserve an IP-Addr for specific host
  60. #
  61. 10.233.7.241:0x0013217C54EB:20060125174012:
  62. 10.233.7.240:::
  63. 10.233.7.75:::
  64. 10.233.16.60:::
  65. 10.233.16.61:::
  66. 10.233.16.62:::
  67. 10.233.16.63:::
  68. 10.233.16.64:::
  69. 10.233.16.65:::
  70. 10.233.16.66:::
  71. 10.233.16.67:::
  72. 10.233.16.68:::
  73. 10.233.16.69:::
  74. 10.233.16.70:::
  75. 10.233.16.71:::
  76. 10.233.16.72:::
  77. 10.233.16.73:::
  78. 10.233.16.74:::
  79. 10.233.16.75:::
  80. 10.233.16.76:::
  81. 10.233.16.77:::
  82. 10.233.16.78:::
  83. 10.233.16.79:::
  84. 10.233.16.80:::
  85. 10.233.16.81:::
  86. 10.233.16.82:::
  87. 10.233.16.83:::
  88. 10.233.16.84:::
  89. 10.233.16.85:::
  90. 10.233.16.86:::
  91. 10.233.16.87:::
  92. 10.233.16.88:::
  93. 10.233.16.89:::
  94. 10.233.16.89:::
  95. 10.233.16.90:::
  96. 10.233.16.91:::
  97. 10.233.16.92:::
  98. 10.233.16.93:::
  99. 10.233.16.94:::
  100. 10.233.16.95:::

advertising

Update the Post

Either update this post and resubmit it with changes, or make a new post.

You may also comment on this post.

update paste below
details of the post (optional)

Note: Only the paste content is required, though the following information can be useful to others.

Save name / title?

(space separated, optional)



Please note that information posted here will expire by default in one month. If you do not want it to expire, please set the expiry time above. If it is set to expire, web search engines will not be allowed to index it prior to it expiring. Items that are not marked to expire will be indexable by search engines. Be careful with your passwords. All illegal activities will be reported and any information will be handed over to the authorities, so be good.

worth-right