Hi. 
I’m doing custom minimal OpenSUSE installation and trying to export detailed list of chosen software in yast on USB (FAT32) drive, but cannot locate the drive itself. It definitely is recognized by SUSE, since i can see it in partitioning section, but after that i just can’t find it in yast (mnt, media,…).
Is there any other way to mount/recognize the drive, because i just don’t have any other idea how to backup that chosen software list?
Thank you. 
Hmmm - suggest you retitle the post, since what you really need is to mount your FAT32 USB drive.
Could be a number of issues, but, if I recall correctly, start with CLI (as user) “fdisk -l” to list drive devices. Then create a mount point (an empty directory), check the permissions, and mount.
Other possibilities: might need to plug back into Windows and correctly remove hardware to release the file system. Might need to reformat and recreate the filesystem. That’s all the simple answers I can think of.
By the way if you need help with commands like mount do this from the command line.
info command
and/or
help command
and/or
man command
where command is the command you want help on
example
info mount
this will list all the options for mount
Hm, i’m not sure how to invoke CLI in regular installation procedure. Tried to do it from yast (CTRL+SHIFT+F1, CTRL+F1, CTRL+SHIFT+F1, and all sort of variations) but nothing helped. What am i doing wrong?
Unfortunately, neither suggestion helped. Maybe i’m wrong, but it seems to be mounted since the partition wizard lists it every single time… :\
Btw, how can i edit the thread title? :shame:
Hi there,
From your description I believe you are trying to get out to the command prompt from within the running yast installer during and actual install.
You should be able to do so by accessing the virtual terminals - you do so with ctrl+alt+F2 or F3, etc. I think you may be using only F1, which is the installer itself. Try using the other function keys and you will see other screens, including standard out, install messages, and a command line.
However, that being said, if you goal is to export a list of packages chosen at install time, you might want to consider just completing the install and generating an AutoYast configuration file. This will contain all the setup options you used on your install (partitioning, package selection, locale, etc.) which you can then feed to the installer in the future. It will let you easily replicate your installs. You can install the AutoYast Packages which will add the icon into Yast. For more information see Network Install HOWTO: SuSE Client Install
Cheers,
LewsTherin
Thanks. This is a great advice. I want to use this configuration file on multiple machines, because without it, it would be very time consuming to specify every single package in yast manually over and over again.
But how to feed it to installer in the future, since the USB obviously doesn’t work (which is weird), and i don’t own a floppy for years now? Is there a way to implement it into ISO directly?
Hi there,
While you could integrate the autoyast file into the iso, that would be a real pain to maintain. The best way to go is to just put the file on a web server, and then feed a kernel boot option when you run the installer and point it to the http address where the autoyast file is. The installer will then pull this in when it runs. It is a wonderful way to go.
See Autoyast installation using a network installation source - openSUSE for more info. There are some other, more extensive, pages out there on autoyast as well. You might want to see Chapter*5.*Network Based Installation too.
For example, if your config file were called suse11.2, and was in the web root of the system on 192.168.1.1, you could add this option to kernel line of the installer:
autoyast=http://192.168.1.1/suse11.2
This is definitely the way to go for replicating installs.
Note that you can also use a local device (USB) rather than http:// as well as NFS://, etc. So you could have the config on a USB stick too, etc.
If you are going to be doing lots of installs, I highly recommend Cobbler as a network install server deployment tool which helps to pull all this together. When you are installing dozens of servers, and want to use different config templates, etc. it is the only way to fly. https://fedorahosted.org/cobbler/
LewsTherin
Pericaa - so are you getting to where you need to? Are things working now?
I finally found some time to manage this issue, since i’ve been very busy lately.
And it finally worked! I entered the CLI using LewsTherinTelemon’s advice (CTRL+ALT+Fx ;)), and then followed this](http://www.novell.com/coolsolutions/feature/11637.html) guide step by step, mounted the disk and saved the .xml file. I’ll check the settings tomorrow on another installation, but it should work with import feature.
Thank you all for your replyes. You’ve been very helpful.