Yes. This is an excellent idea. I've been working in *NIX training for more than a decade and have often suggested this sort of feedback in *NIX tools. It would also be worthwhile to suggest applicable man pages withing such feedback.

JAY VOLLMER TEXT REFS DOUBLEPLUSUNGOOD SELFTHINK VERGING CRIMETHINK IGNORE FULLWISE

Great ! opened a new feature-request: https://bugzilla.novell.com/show_bug.cgi?id=412933 Feel free to add comments. -- -Alexey Eromenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 July 2008 11:51:42 am Jide Ogunmekan wrote:

Alexey Eremenko wrote:

...

...

Yes. This is an excellent idea. I've been working in *NIX training for more than a decade and have often suggested this sort of feedback in *NIX tools. It would also be ... Great ! opened a new feature-request: https://bugzilla.novell.com/show_bug.cgi?id=412933

Feel free to add comments.

This would be a fantastic idea! I would really love to be of help any which way as I have personally benefited from the YAST tool when I first started using Linux some years back SuSE 6.4 I believe.

If one wants to see what is gong on in background, than look at logs in realtime. There is console (Konsole) and command tail. Run as root: tail -f /var/log/YaST2/y2log and then start YaST and play with. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 July 2008 04:30:21 pm Kermit Mei wrote:

...

If one wants to see what is gong on in background, than look at logs in realtime. There is console (Konsole) and command tail. Run as root:

tail -f /var/log/YaST2/y2log

and then start YaST and play with.

Hi,I don't think so.

What makes you not to think so?

What y2log shows is just some log, we want to see the shell commands which Yast2 runned.

You can see all commands that YaST is running. Excerpt from Software Manager start: ------------------------------------------------------------------------------- 2008-07-29 16:39:12 <1> linux(3722) [zypp] Sysconfig.cc(read):71 done reading '/etc/sysconfig/proxy' * zypp runs Sysconfig.cc reading /etc/sysconfig/proxy ------------------------------------------------------------------------------- 2008-07-29 16:39:12 <1> linux(3722) [zypp] MediaHandler.cc(attach):653 Attached: http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSU... attached; localRoot "/var/adm/mount/AP_0x00000001" * zypp runs MediaHandler.cc attaching KDE4 Factory to mount point /var/adm/mount/AP_0x00000001 ------------------------------------------------------------------------------- 2008-07-29 16:39:12 <1> linux(3722) [zypp] PathInfo.cc(assert_dir):354 mkdir /var/adm/mount/AP_0x00000001/repodata 00755 * zypp runs PathInfo.cc making directory /var/adm/mount/AP_0x00000001/repodata with permission 00755 ------------------------------------------------------------------------------- 2008-07-29 16:39:12 <1> linux(3722) [YCP] PackageCallbacks.ycp:1859 Downloading http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSU... to /var/adm/mount/AP_0x00000001/repodata/repomd.xml * YCP runs PackageCallbacks.ycp downloading repomd.xml to just created directory /var/adm/mount/AP_0x00000001/repodata/ ------------------------------------------------------------------------------- 2008-07-29 16:39:12 <1> linux(3722) [YCP] Progress.ycp:578 Resetting the subprogressbar... * YCP runs Progress.ycp resetting the subprogressbar (I guess the bottom one) -------------------------------------------------------------------------------- And it goes on and on. Not many shell commands there. The only I can see is mkdir, but even that can be just part of message string. Those logs are not created for people that need text "make a directory" instead of mkdir to understand what is done. As you can see I didn't need much effort to read the log. Once you get used to format it looks almost as plain text. To actually understand what is going on you have to read source code of programs. I hope that you understand that program code (source) is not only good for compilation, but it is also pretty compressed expression of what CPU will do. Writing explanation what each piece of code will do requires much more text to be written. I'm sure that if you or anybody else want to understand what particular function is doing, and ask for help, for instance, on opensuse-programming@opensuse.org mail list than people will help you, but you and everybody else should learn how to read programs. It is a bit easier than writing them. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 July 2008 16:43:09 Dave Howorth wrote:

Alexey Eremenko wrote:

...

Hi All !

I Have very good new idea: converting Yast into a Linux learning tool.

This is very simple to achieve: Yast must show the commands it executes and files it modifies, in a nice GUI dialog.

There was a previous discussion about this. IIRC it seems it's not as simple as it appears. Sorry, I can't remember when or what the thread was called.

Cheers, Dave

I think it's this email from November last year that you're referring to: http://lists.opensuse.org/opensuse/2007-11/msg03058.html Stanislav's reply indicates that its a much bigger change than I had naively assumed. I've managed to work some things out using the /var/log/YaST2 directory contents, but there's a lot of info in there for even the slightest task and a lot isn't relevant. Still, it would be nice to have. Cheers Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org