Path_to_install

Hi all
what is the purpose of /etc/path_to_inst in network?

While I agree that checking manual pages and doing web searches before asking questions on the forum is a good idea, I can see how somebody not familiar with Solaris may find the path_to_inst manaul page hard to understand. So I'll answer you question.
The simplest statement with this file is "do not mess with it". Don't edit it, don't delete it, etc. It is a file maintained by the system and you shouldn't mess with it directly unless you know a lot more about the system that I do.
I'll try to describe the file as simply as possible. When you add a device to the system it will be assigned two identifiers. A device node in the /devices tree in the filesystem and an internal identifier associated with the relevant driver in the kernel. This file is simply a mapping of two representations. It is important because it makes the mapping permanent so that the device assignments don't change when the hardware configuration of the system changes.

Similar Messages

  • Can't boot with zfs root - Solaris 10 u6

    Having installed Solaris 10 u6 on one disk with native ufs and made this work by adding the the following entries
    /etc/driver_aliases
    glm pci1000,f
    /etc/path_to_inst
    <lang pci string for my scsi controller> glm
    which are needed since the driver selected by default are the ncsr scsi controller driver that do not work in 64 bit.
    Now I would like to create a new boot env. on a second disk on the same scsi controller, but use zfs instead.
    Using Live Upgrade to create a new boot env on the second disk with zfs as file system worked fine.
    But when trying to boot of it I get the following error
    spa_import_rootpool: error 22
    panic[cpu0]/thread=fffffffffbc26ba0: cannot mount root path /pci@0,0-pci1002,4384@14,4/pci1000@1000@5/sd@1,0:a
    Well that's the same error I got with ufs before making the above mentioned changes /etc/driver_aliases and path_to_install
    But that seems not to be enough when using zfs.
    What am I missing ??

    Hmm I dropped the live upgrade from ufs to zfs because I was not 100% sure it worked.
    Then I did a reinstall selecting to use zfs during the install and made the changes to driver_aliases and path_to_inst before the 1'st reboot.
    The system came up fine on the 1'st reboot and did use the glm scsi driver and running in 64bit.
    But that was it. When the system then was rebooted (where it made a new boot-archive) it stopped working. Same error as before.
    I have managed to get it to boot in 32bit mode but still the same error (thats independent of what scsi driver used.)
    In all cases it does pop the SunOS Relase banner and it do load the driver (ncrs or glm) and detects the disks in the correct path and numbering.
    But it fails to load the file system.
    So basically the current status are no-go if you need to use the ncrs/glm scsi driver to access the disks with your zfs root pool.
    File-Safe works and can mount the zfs root pool, but that's no fun as server OS :(

  • JNLP and Eclipse Birt Runtime Engine

    The Birt report engine requires a path to the jar files that are downloaded. Is there a way to get the install location so that path can be used to setBirtHome(path_to_install).
    Dennis

    Is there a way to get the install location ...Sure, or rather, use an installer to put the Jar's
    in a specific place, then store where that specific
    place is, in your 'env. variable' or whatever.
    (Note that I, as an end user, can change the
    location of the class cache any time I like, so
    it is not advisable to try and get the 'path' to it
    for any reason.)

  • Mknod error when pkgadd of SUNWqfed - device is not created

    I am trying to install a second quad FE card in a sparcstation 20. There is a quad ethernet card in there right now, which is live.
    I ran the pkgadd command to install the SUNWqfed and SUNWqfedu packages. When the SUNWqfed package was being installed I noticed an error
    Executing postinstall script
    Usage: mknod name [b/c major/minor] [p] failed Postinstall script did not complete successfully.
    I uninstalled the package and tried it again but it still failed, and I tried another downloaded copy of the packages with the same error. I also saw that the path_to_install file did not have the entries for the qfe card.
    Any idea how I can fix this and install the card?
    Thank you
    Edited by: HCCS on Feb 7, 2008 1:32 PM

    I already have a quad ethernet card in this system and it is the live interface. I tried to physically remove it before installing the package, with the same results.
    Also, I was looking at the SUNWqfed postinstall script that was
    indicated as where it was failing and the link in points to nothing. There is no clone@0:qfe file to link to.
    ln -s ../devices/pseudo/clone@0:qfe ${BASEDIR}/dev/qfe id=`grep "^qfe " ${NAMEMAJOR} | awk '{printf("%s", $2)}'`
    mknod ${BASEDIR}/devices/pseudo/clone@0:qfe c 11 $id
    The path_to_install file only has entries for the qe interface, nothing for the qfe.
    Thanks for your help.

  • Network card problems

    I have a sbus quad ethernet card in a sparcstation 20 running 2.5.1. I just also put in a FE quad card, and at the OK prompt the system see the card if I issue show-devs. After boot -r or /reconfigure and boot but the drivers are not loading. My path_to_install never gets updated with the 2nd card and the link in /dev points to nothing. I know it could be an issue that the prom version of the machine is 2.1 when 2.9 is what indicates is supported, but I would thnk that it wouldn't see the card at the OK prompt.
    Any suggestions?
    # ls -al | grep qfe
    lrwxrwxrwx 1 root other 29 Dec 21 09:11 qfe -> ../devices/pseudo/clone@0:qfe
    sysdef -d | grep qfe
    Node 'SUNW,qfe', unit #-1 (no driver)
    Node 'SUNW,qfe', unit #-1 (no driver)
    Node 'SUNW,qfe', unit #-1 (no driver)
    Node 'SUNW,qfe', unit #-1 (no driver)
    patsy# sysdef -d | grep qe
    Node 'qec', unit #0
    Node 'qe', unit #0
    Node 'qe', unit #1
    Node 'qe', unit #2
    Node 'qe', unit #3

    try this one I DL it text file says v 7.2.17.101
    http://www.allpcdrivers.com/drivers/laptop-drivers/ibm/14183_thinkpad_t42_t42p_intel_pro_10_100_1000...
    Thinkpad R61 7733-1GU
    Thinkpad X61T 7762-54U
    Thinkpad X60T 6363-4GU
    Did a member help you today? Thank them with a Kudo!
    If a post answers your question, please mark it as an "Accepted Solution"!
    Regards,
    GMAC

  • Ultra 20 workstation NIC driver install

    hi friends,
    I have brand new Sun Ultra 20 WS installed.
    It was preinstalled with Solaris 10 6/06 system,
    in ifconfig -a command only loop back intervace is showing.
    and
    */etc/path_to_install* also not able to find the interface name.
    my questions are:
    1. Is there any command to get only interface name.
    2. Do i have to install driver for my NIC if so how.
    I also nead the URL path of the driver to download.
    Please help me ASAP.......

    Never mind. I think the drivers for this workstation can be found in this ISO file download available on SUN's web site.
    http://www.sun.com/desktop/workstation/ultra20/downloads.html
    Hope it helps all who may or may not be installing Windows on this workstation.
    - SG

  • [Forum FAQ]Tips on Upgrading Windows 10 Technical Preview from Build 9841 to 9860

    The new Build 9860 for Windows 10 Technical Preview has been released recently. Here, I would like to share some experience on upgrading Windows 10 Technical Preview from Build 9841 to 9860.
    Tip 1: How to use Refresh option to upgrade.
    Scenario
    In order to upgrade to Build 9860, the new preview build should be downloaded firstly:
    PC settings-> Upgrade and recovery->
    Preview builds, which is as shown below.
    If there are multiples PCs which are running Windows 10 Technical Preview Build 9841 need to be upgraded, you may just want to use one copy of downloaded preview build to upgrade all of them instead of downloading the new build on each PC.
    Solution
    If you have upgraded one PC from Windows 10 Technical Preview Build 9841 to 9860, the downloaded preview build (install.esd) can be used to upgrade other PCs. Here we can use install.esd to export the install.wim, then this intall.wim can be used as a recovery
    image.
    Step 1: Understand the basic information about install.esd.
    Install.esd file is located at C:\ $WINDOWS.~BT\sources folder at first. When the upgrade is finished, it would be copied to
    C:\RecoveryImage folder. Here is the information in setupact.log which contains information about setup actions during installation:
    2014-10-28 19:03:38, Info SP Moving file D:\$Windows.~BT\Sources\Install.esd to D:\RecoveryImage\Install.esd
    What’s more, the command Dism /Get-Wiminfo /Wimfile:<path_to_install.esd> is used to display the information about the file install.esd:
    Step 2: Export the file install.wim.
    The following command is used to export Windows 10 Technical Preview Build 9860 image:
    Dism /Export-Image /SourceImageFile:<path_to_install.esd>
    /SourceIndex:4 /DestinationImageFile:<path_to_install.wim> /Compress:recovery
    Step 3: Copy exported install.wim to other Windows 10 Technical Preview Build 9841 computers, and set the recovery image.
    For example, the install.wim has been copied to C:\image folder, the following command is used to set the recovery image:
    Reagentc /setosimage /path C:\image /index 1 /target C:\Windows.
    Step 4: Use Refresh option to upgrade your PC.
    Go to
    Update and recovery setting under PC settings, choose
    Refresh your PC without affecting your files:
    Note:
    Applications needed to be reinstalled.
    System would use the exported install.wim to refresh Windows 10 Technical Preview from Build 9841 to 9860:
    Note: If you use install.esd to refresh directly, just need point the index location as 4:
    Reagentc /setosimage /path C:\image /index 4 /target C:\Windows. However, install.wim is easier for deployment, such as creating bootable USB, WDS and SCCM deployment.
    Tip 2: Workground to upgrade native boot VHD.
    Scenario
    Many users use the method native boot into VHD to test Windows 10 Technical Preview. However, there is a limitation on native boot when using VHDs:
    If you boot from a VHD, you cannot upgrade the Windows version in the VHD to a newer version. This article describes how to upgrade VHD system Windows 10 Technical Preview from Build 9841 to 9860.
    Solution
    Step 1: Upgrade in Hyper-V.
    Use Hyper-v to create a new virtual machine, and use your native boot VHD
    as an existing virtual hard disk:
    If booting from this virtual disk directly, it would fail to start due to lacking of boot files. You can use Windows 10 Technical Preview Build 9841 ISO file to repair the startup issue:     
    You can boot intosystem successfully in Hyper-v, then the upgrade process would be supported.
    Step 2: Create Native Boot to VHD.
    When the upgrade is finished, shut down the virtual machine, use the same way to create Native Boot to VHD:
    Mount the 9860 native boot VHD file.
    Use the following command to create boot entry for VHD system: Bcdboot
    v:\windows (v: represents the mounted virtual disk drive letter).
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi Arman mohseni,
    From my observation, if I click download now, it would create a BITS task:
    We can use following command to check:
    Import-module bitstransfer
    Get-bitstransfer –allusers
    From the output, we can see the system account created a BITS job for transferring, under the C:\Windows\Software Distribution\download, we can get the temporary downloaded file, which is approximately about 2.5G.
    After we restart, and go to C:\Windows\Software Distribution\download, the temporary file is gone.
    If I click the download again, the BITS would create a new task, a new temporary file, if we compare the JobIds of the two times downloading, they are totally different.
    On the other hand, if we download a windows update, the JobId would be kept, and the temporary files would be kept, too.
    Alex Zhao
    TechNet Community Support

Maybe you are looking for