small problem seting up jumpstart



I have a central jumpstart server delivering Solaris 8 , 9 & 10 to the engineering workshop. Its recently been upgraded from an Ultra 2 to a V20z running Solaris 10 x86.

A colleague came over a problem with the Solaris 8 add_install_client, producing adb errors. On closer observation the add_install_client incorrectly parses output from the ifconfig command, but only when zones are running. ifconfig list which zone owns the interface and this what Solaris 8 add_install_client script fails to cope with.

Workaround, make the following changes in blue at line number 1939 to add_install_client
read inet ipaddr netmask mask broadcast broadaddr
if [ "${ifname}" = "lo0:" ]; then
 continue;
 fi
 if [ "$inet" = "zone" ]; then
 # Found an interface dedicated to a local zone.
 # Read in the real "inet" line and continue.
 read inet ipaddr netmask mask broadcast broadaddr
 continue;
 fi

    Comments

    Post a Comment

    Popular posts from this blog

    Solaris 11 Locale en_GB.UTF-8 / en_GB.ISO8859-1 / en_GB.ISO8859-15

    When you install Solaris 11/11 from standard text installer cdrom, the en_GB-UTF-8 locales are not installed, even if you select British locales on install. EDIT 4th FEB 2018 - Still valid for Solaris 11.4 Beta.  To make sure packages are have the correct localisation, IPS uses facet as a localisation personality. $ pkg facet FACETS VALUE facet.locale.pt_BR True facet.locale.es_ES True facet.locale.en_US True facet.locale.zh_TW True facet.locale.zh_CN True facet.locale.de_DE True facet.locale.fr_FR True facet.locale.it_IT True facet.locale.ko_* True facet.locale.ja_* True facet.locale.es True facet.locale.de True facet.locale.zh True facet.locale.ko True facet.locale.it True facet.locale.pt True facet.locale.fr True facet.locale.en True facet.locale.ja True facet.locale.* False As you can see no en_GB is described and " facet.locale.* False " is a deny everything else rule. So let change this. I'm assuming you have a Solaris 11 repository already configured
    Read more

    Scheduled network capture on Windows using Wireshark (tshark.exe)

    A customer had an iSCSI issue and was required to capture network packets at a specific time on a Windows 2008 server. I came up with simple method using Wireshark's tshark.exe and Windows scheduler "AT". at cmd /c c:\capture.bat type c:\capture.bat rem Capture WireShark example rem Andy Paton rem WTL rem use AT to run batch rem example at 01:50 cmd /c c:\capture.bat rem debug at issues rem example at 09:50 /interactive cmd /k c:\capture.bat rem -a duration:1200 in seconds rem -B Buffer Size - default is 1Mb rem -i Interface number - use "tshark.exe -D" to list interface numbers rem -n don't resolve IP addresses rem -q Quiet output rem -w output file rem capture filter "host " c:\"Program Files"\Wireshark\tshark -a duration:1200 -B 2 -i 4 -n -q -w c:\network.out host 192.168.1.1
    Read more

    [Linux] X-server ScreenShots from the CLI "ImageMagick"

    Build some documentation for a customer and required some screenshots, KDE has Ksnaphot . But I wanted many screen shots and need a simple cli command to capture various screens. ImageMagik provides the " import " command which does just the job from the command line. To capture the whole desktop as a JPEG use the following. $ import -window root screen.jpg To save in a diffrent grapics format change the extention of the output file. (gif,pnm,pmm,tiff etc..) To capture single window ie firefox You need to find the window name, two methods of getting the "window name" 1. use xwininfo, which will then ask you to click target window and display information. 2. xlsclients -l display list of windows Note you can use a window title or the DECIMAL window ID, xwininfo and xlsclients output in HEX. $ import -window < WINDOW ID DECIMAL > screen1.jpg $ import -window "< WINDOWS TITLE >" screen2.jpg
    Read more