Does anyone know if it is possible to use the 'dirinstall' from the command
For instance i would like to be able to do something like:
# yast dirinstall -d /someroot -s mypackages.sel
If i do yast -h it says:
"Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]"
But is there a way to find out what 'module specific parameters' are available
for a specific module?
i am trying to move a Suse Installation CD to a USB-Stick so i can use
the USB Stick for installation.
The suse installation has the wonderfull option that you can add on a
command line additional parameters to the kernel .
-> Select Installation
-> On the command line add:
At the moment i am able to boot from the USB-Stick with grub and can
select 'Installation' from the grub menu.
But how do i add additional parameter to grub without the need to
modify the menu.lst ? Like the isolinux.cfg when booting from cd/dvd
Extract from the menu.lst
kernel /boot/loader/linux root=dev/sda1 vga=791
UNIX Systems Engineer
Am Kavalleriesand, 31
64295, Darmstadt, Germany
Tel : +49 6151 807-7307
-----BEGIN PGP SIGNED MESSAGE-----
Is there a good searchable site for the archives? Right now, the best
I've found is http://lists.suse.com/archive/suse-autoinstall/
and not very useful... Perhaps a FAQ on this topic would be
appropriate at this point, if anybody @ Novell is reading this.. Since
it comes up so often.
On Oct 18, 2005, at 4:03 PM, Michael Marion wrote:
> On 18 Oct, Michael T. Halligan wrote:
>> I have two dilemmas with AutoYast I'm sure somebody here will be able
>> to help me solve. They're
>> really the same issue, and that is adding external rpms.
> Both of what you want to do can be easily solved using a custom
> path with
> custom RPMS.
> Look in the archives for the subject:
> Additional Package & Silent install
> One message of which also talks about 2 other threads with more in-
> depth info.
> Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
> Frasier: "...we know for whom the bell tolls."
> [A bell dinging is heard, everyone looks around a little confused]
> Martin: "Anybody else hear that?"
> Daphne: "Oh! The biscuits!" --Fraiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
-----END PGP SIGNATURE-----
after I just finished my first succesful autoinstall (yeah!) :-) I am
left with a couple of questions as to how to improve it further.
One thing I need to do is to automatically install more than one
language - basically like you do under YaST2 in the "language" module
with adding "Secondary Languages". I have seached through
http://www.suse.de/~ug/autoyast_doc/ as well as through the archive of
this list http://marc.theaimsgroup.com/?l=suse-autoinstall&r=1&w=2 but
came up empty. Is there an easy way to accomplish this? If not, I can
think of only two alternatives:
- Manually add all language related packages for the languages I need to
the package list (brrrrr...)
- Try to do some script-wizardry in post-install or init? I have yet to
figure out whether I can convince YaST2 to add the secondary languages
from the commandline - if not, I'm down to the first option...
Any hints (including docs I might have missed...) are welcome!
I have two problems:
1) CD Creator doesn't respect SP2
2) ncompress package is not installed
I use a custom CD to install all our servers. I create the CD with SuSE
Yast CD Creator. With SLES9 SP1 everything was fine. With SP2 I noticed
that not all files on the CD are up to date. The driverupdate file comes
from the SP1 CDs. The /boot comes even from the original SLES9 CDs.
I fixed this by copying the SP2 files into the directory and
the ISO image by hand, but I think this is the job of CD Creator.
I need /usr/bin/uncompress to install one of our enterprise tools. In
this was in the sharutils package. With SP2 it moved to the ncompress
package. Though, I added the ncompress package to my XML file and
recreated the ISO image.
When I install a machine with this new CD, the GUI tells me that the
ncompress package is being installed. The Yast logfiles, tell me that
installation of ncompress was successful. But if I do a rpm –q ncompress
it tells me that ncompress is not installed and I can't find the
/usr/bin/uncompress on disk.
If I do rpm –ihv /media/cdrom/suse/*/ncompress*.rpm it installs cleanly.
I also installed the machine with an install-server using the same XML
files. The result is the same. The logfiles tell me that ncompress was
successfully installed, but the files are not on disk.
Any idea what's happening here ?
Kaikki RPM:t eivät aina asennu.
From: Christian Goetze <cg(a)sensage.com>
Date: Fri, 28 Oct 2005 11:58:37 -0700
Subject: [suse-autoinstall] Warum ist SLES9 "Full-Installation" nicht full installation?
Wieso werden nicht alle *-devel rpms installiert wenn ich "Full
Im Moment muss ich eine Menge extra *-devel RPMs explizit angeben...
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
if you want to put an "info" file into the SuSE 10.0 initrd,
e.g. for creating an autoinstall-CD, you can do it in the
============= 8< ============
echo info | cpio -o -H newc -A -F initrd
gzip -9 initrd
============= 8< ============
It took me a while to notice the necessary "-H newc" option.
Greetings, I presently have an autoyast set up to deliver Novell OES1
(SLES9 i386 based). I wish to build some servers with just the SLES9
x64 distribution and was hoping to use the same rules.xml file to kick
things off. Here is the rules.xml that is presently working for OES1:
<!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd">
if [ -n "`grep build= /proc/cmdline`" ]
echo -n `cat /proc/cmdline | sed -e 's/.*build=\(.*\)/\1/' -e
echo -n "hse9-32"
The SLES9 x64 autoyast attempts using the same rules.xml file but seems
to not match any of the rules and prompts for the location of a proper
rules file. On inspecting the /var/log/YaST2/y2log file, it appears
that the bit of shell scripting being kicked off to compare the
product/mac strings to the * character are failing and returning 1
instead of 0 as they do with the OES1 installation. ie the scripts are
treating the wildcard (*) character literally. Does the SLES9 x64
autoyast support the use of wildcards in the match? If not, what can I
Thanks for any help...
when i get the menu, there is a spot for the
server name, which i put in as:
download.opensuse.org/ choosing http and :
the directory on server, then i get an error,
(which by the way, is unintelligble(?)
anyone know what i'm doing wrong and interpet
the error message?
Edward M Dunagin
4646 Glenwood Drive
Bozeman, MT 59718
Skype-phone +1 406 322 2566
Yahoo! Mail - PC Magazine Editors' Choice 2005