[yast-devel] 3 questions about yast....
OK. First some background: My customer has written a sles9->sles10 live update installation script. I just ran it via ssh. It uses autoyast (the sles10 version) and it installs onto a clean partition (i.e., a partition that isn't running sles9). It works, but they've had to mess with some of the ycp files. Note this script is specialized to their nodes because they only ship 2-3 type of nodes. It's not a general purpose script. Here are the 3 questions they have (for sles10 version): 1) After yast completes installation (i.e., post-install), the fstab is created. What yast module makes this call? It has to be in yast2-installation, but I can't find the connection between the installation and yast2-storage where WriteFstab() lives. 2) How does yast determine what the source partition to mount is? 3) bootloader_finish.ycp breaks the install at the end. They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do? Thanks -robert -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Wednesday 29 August 2007 19:48, Roberto Angelino wrote:
My customer has written a sles9->sles10 live update installation script. I just ran it via ssh. It uses autoyast (the sles10 version) and it installs onto a clean partition (i.e., a partition that isn't running sles9). It works, but they've had to mess with some of the ycp files. Note this script is specialized to their nodes because they only ship 2-3 type of nodes. It's not a general purpose script.
Here are the 3 questions they have (for sles10 version):
1) After yast completes installation (i.e., post-install), the fstab is created.
the fstab is created immediately after the (/) partition is formated and mounted and before the first RPM gets installed and not during post-install. Post-install would be too late (a lot too late actually because post-install in autoyast terms means after the first reboot).
What yast module makes this call?
libstorage as part of yast2-storage is doing that Thomas Fehr can tell you more about that
2) How does yast determine what the source partition to mount is?
I dont understand the question What is the "source partition"?
3) bootloader_finish.ycp breaks the install at the end.
in which way? Logs? Error message?
They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do?
Stefan Fent and Olaf Dabrunz can tell you more. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug now playing mind.in.a.box - Walking -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Here are the 3 questions they have (for sles10 version):
1) After yast completes installation (i.e., post- install), the fstab is created.
the fstab is created immediately after the (/) partition is formated and mounted and before the first RPM gets installed and not during post- install. Post- install would be too late (a lot too late actually because post- install in autoyast terms means after the first reboot).
OK, so the scenario is the user has selected his software pkgs and tells yast "make it so". Yast formats the target partition, creates the File system and creates the /etc/fstab? Is this correct?
What yast module makes this call?
libstorage as part of yast2- storage is doing that Thomas Fehr can tell you more about that
Cool.
2) How does yast determine what the source partition to mount is?
I dont understand the question What is the "source partition"?
The source partition (or the source of the installation maybe a better term) in this case is the partition that contains the distribution.
3) bootloader_finish.ycp breaks the install at the end.
in which way? Logs? Error message?
I looked at the bootloader code a couple of weeks ago. I'm not a yast expert, but I think yast wants to install the mbr and stuff like that to get the machine ready to boot without CD assistance.
They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do?
Stefan Fent and Olaf Dabrunz can tell you more.
OK. BTW, you guys have to see this thing run. While sles9 is runnning, the system upgrades itself to sles10. Of course you need a partition that's not being used for it to work. ---- Roberto Angelino Dedicated Partner Engineer (310) 529-3527 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 11-Sep-07, Roberto Angelino wrote:
3) bootloader_finish.ycp breaks the install at the end.
in which way? Logs? Error message?
I looked at the bootloader code a couple of weeks ago. I'm not a yast expert, but I think yast wants to install the mbr and stuff like that to get the machine ready to boot without CD assistance.
Correct. But we really need error messages to help you solve any problems.
They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do?
Stefan Fent and Olaf Dabrunz can tell you more.
bootload_finish.ycp writes the bootloader configuration to the installed target system and then calls the bootloader to install the "boot code" (aka "stage1") to the selected disk block (MBR, at the beginning of a partition, etc.). It is the last stage before the reboot during a fresh installation or an update. -- Olaf Dabrunz (od/odabrunz), SUSE Linux Products GmbH, Nürnberg -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Tue, Sep 11, 2007 at 09:58:30AM -0600, Roberto Angelino wrote:
2) How does yast determine what the source partition to mount is?
I dont understand the question What is the "source partition"?
The source partition (or the source of the installation maybe a better term) in this case is the partition that contains the distribution.
Hi Roberto, You seem to mix two concepts: the installation source(s) and the installation target(s) The source(s), recently renamed to "repositories", are where the RPMs come from. By default it is the boot CD/DVD, or whatever you specify in the boot menu or as the install=URL parameter. The source can also reside on a hard disk partition (which you'd better not format during the instalation...) The target(s) are the partitions to install the RPMs to. AFAIK there is some magic in the partitioner module to propose the root partition. In case of a distro upgrade, you get to select which of the many SUSE Linuxes on your computer you want to upgrade. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
The source partition (or the source of the installation maybe a better term) in this case is the partition that contains the distribution.
Hi Roberto,
You seem to mix two concepts: the installation source(s) and the installation target(s)
Yes. I now realize I am mixing the terminology.
The source(s), recently renamed to "repositories", are where the RPMs come from. By default it is the boot CD/DVD, or whatever you specify in the boot menu or as the install=URL parameter. The source can also reside on a hard disk partition (which you'd better not format during the instalation...)
Yes. This is what he was asking about---the mount point that contains all RPMs to install... Thanks ---- Roberto Angelino Dedicated Partner Engineer (310) 529-3527 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
3) bootloader_finish.ycp breaks the install at the end.
in which way? Logs? Error message?
They don't actually get an error msg (I'm attaching the end of the log file). It just stops and goes back to the shell prompt. ---- Roberto Angelino Dedicated Partner Engineer (310) 529-3527
On 11-Sep-07, Roberto Angelino wrote:
3) bootloader_finish.ycp breaks the install at the end.
in which way? Logs? Error message?
They don't actually get an error msg (I'm attaching the end of the log file). It just stops and goes back to the shell prompt.
Thanks for the attached log. The attached log stops in the middle of the proposal, with no apparent error condition. Most probably there were other logs in /var/log/YaST2. As this is probably a bug or an L3 case, could you please open a bug for it and attach the complete logs (save_y2logs). Thanks a lot, -- Olaf Dabrunz (od/odabrunz), SUSE Linux Products GmbH, Nürnberg -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Yast Developers, I have a customer who is stuck debugging where the string SUSE Linux Enterprise Server 10 SP1 is read from? Is it created? If so where? Is it read? If so what file is it reading it from? Thanks ---- Roberto Angelino Dedicated Partner Engineer Developer Support (310) 529-3527 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Roberto Angelino wrote:
Yast Developers, I have a customer who is stuck debugging where the string
SUSE Linux Enterprise Server 10 SP1
is read from? Is it created? If so where? Is it read? If so what file is it reading it from?
Thanks
May be other YaST folks could confirm it. IIRC if you are seeing that in the UI, it is $product variable in sidebar texts, which come from YaST UI productName() which is read from libzypp target first installed product, which libzypp reads from installed database in /var/lib/zypp/db/products. Cheers Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On st 27. února 2008, Roberto Angelino wrote:
Yast Developers, I have a customer who is stuck debugging where the string
SUSE Linux Enterprise Server 10 SP1
is read from? Is it created? If so where? Is it read? If so what file is it reading it from?
If the read call is really SCR::Read(.content.LABEL) , than it refers to the file 'content' that could be found in the root directory of the installation media. See http://en.opensuse.org/Libzypp/Metadata/YaST/content_syntax#The_content_file and e.g. http://ftp5.gwdg.de/pub/opensuse/distribution/10.3/repo/oss/content as an example. Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (6)
-
Duncan Mac-Vicar P. -
Jiří Suchomel -
Martin Vidner -
Olaf Dabrunz -
Roberto Angelino -
Uwe Gansert