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
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
Christian Zoz wrote / napísal(a):
> On Sun, May 27, Michal Zugec wrote:
>> 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
>
> Also here use ifcfg-<interface name> and provide udev rules in
> /etc/udev/rules.d/70-persistent-net.rules
exactly, also rule - don't write hwcfg if there is exactly one driver
detected by kernel comes here - but in next round, first I want test this
BTW - how can I handle persistent-by-busid in udev? There is sysfs
option address but busid I can know only by where shows device link
In short what should I use instead of SYSFS{address} rule?
M.
>
>> - 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
>
> ok
>
--
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
Hi all,
I need to set a value for a variable in a file during the install time. (need to replace FLAG="true" by FLAG="no" in /etc/someconf.conf file). I thought i can place the [replace -s 'FLAG="true"' 'FLAG="no"' -- /etc/someconf.conf] in my script which is called by yast GUI. But it seems replace command is missing in SLES. So i have planned to keep like
sed 's/FLAG="true"/FLAG="false"/g' /etc/someconf.conf > tmp && mv tmp /etc/someconf. It works fine in the post install. Will it work in the fresh install scenario? Creating the new file (tmp) will work during the fresh install? If there is a better solution please suggest me.
Thanks,
-Kalyan
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi We have a new mailinglists
<opensuse-softwaremgmt@xxxxxxxxxxxxxx>
This mailing list has one mission: bring the people involved in different
projects having to do with package management, together.
Like:
- ZYpp developers
- Autobuild & build service
- Updater applets and YaST modules.
- Community
in order to:
- define metadata formats, standarize, push upstream, create specifications
and centralize the knowledge.
- coordinate features in one componet to be used by other components.
- discuss ideas to make the user experience better (how to make downloading
metadata faster?)
- coordinate community projects in order to integrate them with other
components.
- Discuss having common codebase for tools like metadata generators,
validators, packaging tools, etc.
To subscribe to the lists, just send an email like this:
opensuse-softwaremgmt+subscribe@xxxxxxxxxxxx
For more information about the Mailinglists, please look at
http://en.opensuse.org/Mailing_Listshttp://en.opensuse.org/Communicate#Mailing_Lists
with kind regards,
--
Duncan Mac-Vicar Prett
Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi Jiri,
On Fri, 2007-05-18 at 10:39 +0200, Jiri Srain wrote:
> The YaST SVN repository (the primary source of YaST code) has just been moved
> from the internal server to svn.opensuse.org server. The old (internal)
> repository has been switched to read-only mode. The repository was moved at
> revision 38031.
This is great news :-)
Any chance we can get the 'gtk' module imported from:
forgesvn1.novell.com/svn/yast/trunk/gtk
There are ~no branches AFAIR, we do conditional compiles for different
yast2 versions.
Thanks,
Michael.
--
michael.meeks(a)novell.com <><, Pseudo Engineer, itinerant idiot
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
On 5/17/07, Justin Haygood <jhaygood(a)spsu.edu> wrote:
> It currently depends on kdebase? Will this dependency always be there,
> since it adds an unnecessary dependency for e.g. GNOME users (like
> myself)
What yast-package-manager package are you talking about? I don't have
one, and I can't see one in factory.
_
Benjamin Weber
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
It currently depends on kdebase? Will this dependency always be there,
since it adds an unnecessary dependency for e.g. GNOME users (like
myself)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We had our kickoff openSUSE Software Portal project meeting today.
The goals are to provide the best possible end-user experience with
regards to package installation/upgrading at large.
The idea is to provide several software components and services:
* a server backend that aggregates various kinds of information
* a web client, including one-click installation (yast2-mpp)
* a desktop client (GTK/Qt/YaST)
More information about the project:
http://en.opensuse.org/Software_Portalhttp://dev-loki.blogspot.com/2007/05/project-launch-opensuse-software-porta…
Basic infrastructure is set up, so if you want to join the effort (any
help is more than welcome), please subscribe to our mailing-list [1]
We're definitely looking for Java/Python/YCP developers, web designers,
artwork designers, and people with ideas, suggestions, and motivation.
[1]http://forge.novell.com/mailman/listinfo/appinstaller-devel
Please spread the word ;)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be>
_\_v The more things change, the more they stay insane.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFGRk9ur3NMWliFcXcRApeeAKCHM60BvwlPfhs08JWCaiCZX8NTygCcDeh7
E5AnXfaTK396NoB2HyVYsng=
=P8Ke
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org