YaST Development June 2007

yast-devel@lists.opensuse.org

32 participants
24 discussions

[yast-devel] y2makepot
by Ken Millett 12 Jun '07

12 Jun '07

y2makepot is using all of my src files except for my helps.ycp file. Is it supposed to include helps.hcp? I think it used to, but I'm not sure. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 2

[yast-devel] changes in yast2 lan
by Michal Zugec 07 Jun '07

07 Jun '07

Hi all, I want to make some changes with internal data structures in lan module (maybe later in other modules). Status now: - there are about 4 lists/maps (hwinfo, network configuration, hwcfg configuration, table items description) + some informations read from /sys filesystem - there are more places when these items are "matched" and there was some bugs that sometimes with different results ;-) Idea: - create one list of maps and match them just once - also I want to put there information from udev rules Example: list<map> lan_configuration = [ $[ "id":0, "hwcfg" : ... "ifcfg" : ... "hwinfo" : ... "table_descr" : ... "udev" : ... ], $[ "id":1, ... ] ] Not detected devices will have "nil" for hwcfg and not configured will have nil for ifcfg ... What do you think? Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 5

[yast-devel] Fw: Fwd: Mockups pre kdump
by Maneesh Soni 05 Jun '07

05 Jun '07

Hi Bernhard, We have the following observations & suggestions about the mock-up screenshots. Sorry about the long mail and taking some time in replying. We would also like to suggest changes in the kdump user scripts (kdump initrd) and based on that the yast kdump configuration screens will need changes. ************************************************************** 1) General Settings =================== We liked the three way enable/disable settings and they are at the right place, but the other portions like kernel command line or kdump commandline should be part of the expert settings as generally user should be provided with default set of kernel command line options and rarely one has to change them. Instead of command line settings, it would be useful to have the setting related to reserving memory for kdump kernel. The tool can have display like ---------------------------------------------------------------------------- Total system Memory (MB): 4096 (just informative) kdump Memory (MB): (A list box with a minimum memory value like 128, and option to increase should be there) Usable Memory (MB): 3968 (this is also informative) ---------------------------------------------------------------------------- 2) Dump Settings ================ This should capture the settings about dump target and other misc settings about daump saving. Apart from this, "the dump filtering" options for the "makedumpfile" utility can also be integrated here. So, Dump Target ----------- (a radio button to select either of the three targets like o Local filesystem - here we can have a list box with list of valid disk partitions with supported filesystems - path location o Network - This is for possible future extention of dump saving mechanism using which we can save the dump over network ie over NFS or scp, through the kdump initrd. For this we will need following settings - a radio button for selecting NFS or SCP - IP address of the server - path (exported path for NFS or target path for scp) o Raw disk - here we can have list of available paritions without any filesystem on them Default dump path (ie relative to the dump target) ----------------- [ /var/log/dump ] (select directory button) Dump filtering options ----------------------- - This should capture settings for options for using the dump fitering tool "makedumpfile". I am not sure right now if we need a separte screen for this or "Dump settings" is ok. 3) Expert Settings ================== - kdump kenrel command line options [ ] - path to custom kdump kernel [ /boot/vmlinuz-my-kdump-kernel ] - path to custom kdump kernel initrd [ /boot/initrd-my-kdump.img ] - Note: The current approach is to provide user a distro built kdump kernel. But some users would like to use their own kernel to minimize the reserve memory requirement. Also. the kdump initrd might be different if the user is trying to save dump thruough initrd in soe unsual envirnment like multipath IO etc. ************************************************************************* These might be confusing but please let me know if I can elaborate more. The kdump initrd related changes I was taking about are probably not the right stuff for this mailing list but please bear it here.. so that we can have the right context for discussions 1. The current approach in of using a _dedicated_ disk partition somewhat defeats the purpose of kdump flexibility. This mandates that use has to have a separte disk parition allocated just for kdump. The alternative is to have initrd based solution. In past we have done a prototype for such approach http://lse.sf.net/kdump/patches/automation/sles9-sp2-mkinitrd-1.2-27.9-auto… Here using initrd we copy the dump directly to the disk filesystem and avoid the intermediate step of copying to a raw partition and then to target path. This approach does make initrd somewhat bigger in size but it doesn't need user to have a dedicated disk partition just for kdump. 2. As of now there is no support for saving the dump over network using NFS or scp. The network dump can also be done using the kdump initrd once the user has specified right config parameters. So, overall kdump initrd should be able to copy the dump to all possible targets depending upon the user settings. 3. As of now the dump filtering tool is not integrated with kdump user scripts so we can get that also integrated in the initrd and have smaller size dumps based on options given to "makedumpfile" tool. Thanks Maneesh ----- Forwarded message from Bernhard Walle <bwalle(a)novell.com> ----- Date: Thu, 12 Apr 2007 00:32:22 +0200 From: Bernhard Walle <bwalle(a)novell.com> To: Maneesh Soni <maneesh(a)in.ibm.com> Cc: tiwai(a)suse.de Subject: Fwd: Mockups pre kdump Hello, as you may remember you wanted some discussion about the new kdump YaST module. Here I got some early screenshots. I think we should continue the discussion about on the yast-devel(a)opensuse.org mailing list. See http://en.opensuse.org/Communicate how to subscribe. Thanks, Bernhard -- SUSE LINUX Products GmbH Tel. +49 (911) 74053-0 Maxfeldstr. 5 GF: Markus Rex 90409 Nürnberg, Germany HRB 16746 (AG Nürnberg) OpenPGP DDAF6454: F61F 34CC 09CA FB82 C9F6 BA4B 8865 3696 DDAF 6454 From: Jiri Srain <jsrain(a)suse.cz> To: bwalle(a)novell.com, tiwai(a)novell.com Subject: Mockups pre kdump Date: Wed, 11 Apr 2007 15:23:41 +0200 Hi Bernard and Takashi! I already have some mockups for the YaST dialogs for kdump, find them attached to this mail. I hope that the desired functionality of the module is obvious form them, even though some of the widgets may need better labels. Please, comment on them, also feel free to forward them to IBM. Jiri BTW: How should the module be called? Is yast2-kdump OK with you? -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz ----- End forwarded message ----- -- Maneesh Soni Linux Technology Center, IBM India Systems and Technology Lab, Bangalore, India

6 9

[yast-devel] installation & network
by Michal Zugec 04 Jun '07

04 Jun '07

Hi, I made some changes in network code for installation to make it easy to understand, no duplicate code, easy to debug, etc. I will document that changes in opensuse wiki (changes, current status and my plan to future) but not now and not here (after test that everything is ok). Here I want to describe package/file/root_file changes: ------------------------------------------------------------------------ yast2-installation: control/control.openSUSE.xml, control/control.xml - removed item "inst_netsetup", this file is removed from yast2-network network_finish.ycp, S07-medium - changes yast2-network : inst_netsetup.ycp - removed install.ycp - renamed to "save_network.ycp" this file should replace create_interface bash script NetworkStorage.ycp, Lan.ycp - changes inst-sys (root): - remove create_interface script - use save_network.ycp and NetworkStorage.ycp script in inst_sys - use changed control.xml (I hope that changes in svn are enought) ------------------------------------------------------------------------ Steffen, could you made that changes for inst-sys? I don't know if I should mark that files (and how)? yast2-network is not included in inst-sys, because is used for second stage, not first. But because of maintenance I would like to have that files in my package. Lukas - is that enough when I changed 2 xml files above, or do I need anythink else? Christian - all changes we talked before I will implement after this Thomas, Arvin, Uwe - I didn't checked autoinstallation because Storage is broken in autoyast (is it known bug or should I report this)? All changes are in subversion now, I will send them to autobuild probably after Tuesday's meeting and after your responses. Bye, Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 5

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development June 2007