FW: [suse-autoinstall] SLES9 + SP1 network install directory structure
To put a twist on Egan's question; I have reviewed the attached sp3Tree file and found it helpful. It appears to be a structure on a Linux server. How do I manually integrate SP1 into an http installation on a non-linux source machine? Here is my current linuxrc.config for reference. Because I am using a Windows server for an installation source, I can not create the symbolic links as stated in the sp3Tree file (or can I?). I could copy the linked items to the root, any other ideas? KernelPCMCIA: 1 UseUSBSCSI: 1 Product: SUSE LINUX Enterprise Server 9 UpdateDir: /linux/suse/i386-sles9 MemLoadImage: 163840 MinMemory: 256 MemYaST: 64000 MemYaSTText: 64000 Language: english Display: Color Keytable: us Install: http://192.59.213.61/SUSE/SLES/9/x86/1/ DHCP: 1 HostIP: Netmask: 255.255.255.0 Server: 192.59.213.61 Serverdir: /SUSE/SLES/9/x86/1/ Netdevice: eth0 insmod: 3c59x insmod: mii insmod: e100 AutoYaST: http://192.59.213.61/SUSE/SLES/9/x86/1/profiles/ Thanks in advance for your time. Bridgette -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, February 02, 2005 10:06 PM To: egan@sense.net Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] SLES9 + SP1 network install directory structure Hi, attached is a file with the structure. In general, it is similar to SLES8. Anas Egan Ford wrote:
I need to setup SLES9 + SP1 for network install, however the NFS server is not SLES9. The notes recommend using yast to set this up. How do I setup it up manually?
Thanks.
. |-- SUSE-CORE-Version-9 | |-- CD1 | | |-- ARCHIVES.gz | | |-- ChangeLog | | |-- INDEX.gz | | |-- content | | |-- directory.yast | | |-- ls-lR.gz | | |-- media.1 | | `-- suse | |-- CD2 | | |-- INDEX.gz | | |-- content | | |-- ls-lR.gz | | |-- media.2 | | `-- suse | `-- CD3 | |-- INDEX.gz | |-- content | |-- ls-lR.gz | |-- media.3 | `-- suse |-- SUSE-SLES-9-Service-Pack-Version-1 | |-- CD1 | | |-- ARCHIVES.gz | | |-- COPYING | | |-- COPYING.de | | |-- COPYRIGHT | | |-- COPYRIGHT.de | | |-- ChangeLog | | |-- INDEX.gz | | |-- Notes | | |-- README | | |-- README.de | | |-- README.es | | |-- README.fr | | |-- README.it | | |-- README.ja_JP | | |-- README.ko | | |-- README.pt_BR | | |-- README.zh_CN | | |-- README.zh_TW | | |-- SuSEgo.ico | | |-- autorun.inf | | |-- boot | | |-- content | | |-- directory.yast | | |-- docu | | |-- driverupdate | | |-- gpg-pubkey-3d25d3d9-36e12d04.asc | | |-- gpg-pubkey-9c800aca-40d8063e.asc | | |-- i386 | | |-- index.html | | |-- linux | | |-- ls-lR.gz | | |-- media.1 | | |-- pubring.gpg | | |-- rr_moved | | |-- servicepack.tar.gz | | `-- suse | `-- CD2 | |-- COPYING | |-- COPYRIGHT | |-- INDEX.gz | |-- SuSEgo.ico | |-- autorun.inf | |-- boot | |-- content | |-- directory.yast | |-- gpg-pubkey-3d25d3d9-36e12d04.asc | |-- gpg-pubkey-9c800aca-40d8063e.asc | |-- i386 | |-- ls-lR.gz | |-- media.2 | `-- suse |-- SUSE-SLES-Version-9 | `-- CD1 | |-- ARCHIVES.gz | |-- COPYING | |-- COPYING.de | |-- COPYRIGHT | |-- COPYRIGHT.de | |-- ChangeLog | |-- INDEX.gz | |-- LICENSE.TXT | |-- README | |-- README.DOS | |-- SLES-LICENSE | |-- SuSEgo.ico | |-- autorun.inf | |-- boot | |-- content | |-- control.xml | |-- directory.yast | |-- docu | |-- dosutils | |-- gpg-pubkey-3d25d3d9-36e12d04.asc | |-- gpg-pubkey-9c800aca-39eef481.asc | |-- ls-lR.gz | |-- media.1 | |-- pubring.gpg | |-- suse | `-- yast |-- boot -> SUSE-SLES-Version-9/CD1/boot |-- content -> SUSE-SLES-Version-9/CD1/content |-- control.xml -> SUSE-SLES-Version-9/CD1/control.xml |-- driverupdate -> SUSE-SLES-9-Service-Pack-Version-1/CD1/driverupdate |-- linux -> SUSE-SLES-9-Service-Pack-Version-1/CD1/linux |-- media.1 -> SUSE-SLES-Version-9/CD1/media.1 `-- yast |-- instorder `-- order 37 directories, 75 files # cat yast/instorder /SUSE-SLES-9-Service-Pack-Version-1/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 ( entries here are tab delimited) # cat yast/order /SUSE-SLES-9-Service-Pack-Version-1/CD1 /SUSE-SLES-9-Service-Pack-Version-1/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1
Am Donnerstag, 10. Februar 2005 22:48 schrieb Radzai, Bridgette A.:
To put a twist on Egan's question; I have reviewed the attached sp3Tree file and found it helpful. It appears to be a structure on a Linux server. How do I manually integrate SP1 into an http installation on a non-linux source machine? Here is my current linuxrc.config for reference. Because I am using a Windows server for an installation source, I can not create the symbolic links as stated in the sp3Tree file (or can I?). I could copy the linked items to the root, any other ideas?
Windows (2000 and up) knows about hard and softlinks. Softlinks are called junction or reparse points. Get the "junction" command from "http://www.wininternals.com/" to set or delete them. Windows itself has a tool: "fsutil.exe": fsutil hardlink create <neuer Dateinname> <vorhandener Dateiname> fsutil reparsepoint query <dateiname> fsutil reparsepoint delete <dateiname> But this tool does not permit to create a reparse point. You have to fetch "junction" from wininternals to create them. A better alternative: install cygwin coreutils. There is a command called "link" ("ln" is there too). It behaves as "link" ("ln") does with Linux. And --- it gives you a more or less "Linux" environment, most scripts used with Linux running in, without need to change anything. If you prefer setting reparse points and hardlinks with your mouse, have a look at "NTFS Link"-Tool. Installing it adds context menu entries for both types of links. -- Thomas
participants (2)
-
Radzai, Bridgette A.
-
Thomas Schweikle