[QUOTE=subhanahmed2013;16819]I’m installing SLES 11 SP2 in a VMWare VM with autoyast configuration. I’ve gotten to the point where I’m prompted for the location of my CC files.
The formats accepted are url://, ftp:// and file:///. This VM has no internet connectivity, so I am attempting to provide the location as ‘file’. On physical machines we could do this by ALT+F2 to bring up a terminal, mount a USB device, and ALT+F2 to go back to the installation screen, but this does not seem to work in the VM. I can bring up a terminal but cannot dismiss it to continue (ALT+F2 does nothing). Giving the raw device name (as either file:///dev/sdXX or just file:///sdXX) doesn’t work.
I also tried utilizing a shared folder to do this, but no luck. I tried by file:////path, and by file:///mnt/hfgs//path based on this article, but in all cases I get:
cp: cannot stat '<path>': No such file or directory.
cp: missing destination file operand after <path>
FAILED: could not obtain file <path>
FAILED: please provide URI holding all CC files
Does anyone know of a workaround for this problem?[/QUOTE]
I’ve been wondering at first if “the CC files” refers to the C compiler (which would be part of the SDK add-on), but you seem to actually have the required files and are only looking for a way to make them accessible during install.
On physical machines we could do this by ALT+F2 […] but this does not seem to work in the VM.
manual intervention seems to contradict with an autoyast install But the problem with doing the same for the VM might be simply caused by your host’s window manager “catching” that special key code. If you’re using KDE, go into the VM window’s system menu (the outer left icon of the window, left of the window’s title bar), select “advanced” - “special window settings” - tab “appearance & fixes” - check “ignore global shortcuts”, change “do not affect” to “force” or “force temporarily” and check “yes”. Close the dialog with “OK”. Now “Alt-F2” would be sent to the VM, rather than intercepted by the host’s window manager. There might be some menu option in the VM’s window “to send special keys to the VM”, too.
Using shared folders might fail because the VMware Tools are not yet installed or running.
Who’s asking for the files, is it something you put in your autoyast’s or nodes or is it some RPM’s post-installation script? If the latter, you’d depend on what access methods are supported by that installer…
Depending on the stage of installation this is happening in, you might be able to provide a script that mounts some network resource to provide the files - or copy them in advance via entries in the “” node. You could create your own RPM and add that to the install - there are many ways to skip a cat and to me it is not yet clear what the actual requirements and dependencies are.