Re: [Cooker] 9.2 - disaster already?
Ron Stodden [EMAIL PROTECTED] writes: A workaround is to launch update-menus as root. 1. Do an initial install with hd.img of 9.2, selecting everything except servers. Include nfs client. 2. Then use software install to install all the kde* RPMs which were not installed. 3. Note all the missing kicker panel big K menu items. 4. Running update-menus has no apparent effect. 5. Installing the Mandrake Updates solves the problem. Passing the information to fredl, thanks. I hope this is a *reproductible* scenario, not just that you had this one? :) We'll try that. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] 9.2 - disaster already?
Rolf Pedersen [EMAIL PROTECTED] writes: # urpmi --bug bug djbsupport installing /contrib/i586/./djbsupport-1.0-5mdk.noarch.rpm Preparing... ## 1:djbsupport ## added medium qmail urpmi database locked error: %post(djbsupport-1.0-5mdk) scriptlet failed, exit status 7 djbsupport is bad, it should not try to modify a database being currently used, if this is *really* needed, a perl script should be used using directly the urpm library and avoiding to explicitely to lock the urpmi db (so that no error will occur), this script is simple but may depend upon newer interface of urpmi (so it need a require on major version of urpmi to be safe). François.
Re: [Cooker] 9.2 - disaster already?
François Pons wrote: Rolf Pedersen [EMAIL PROTECTED] writes: # urpmi --bug bug djbsupport installing /contrib/i586/./djbsupport-1.0-5mdk.noarch.rpm Preparing... ## 1:djbsupport ## added medium qmail urpmi database locked error: %post(djbsupport-1.0-5mdk) scriptlet failed, exit status 7 djbsupport is bad, it should not try to modify a database being currently used, if this is *really* needed, a perl script should be used using directly the urpm library and avoiding to explicitely to lock the urpmi db (so that no error will occur), this script is simple but may depend upon newer interface of urpmi (so it need a require on major version of urpmi to be safe). François. OK. I was able to install djbdns by adding a source from http://rpmhelp.net/ Thanks. Rolf
Re: [Cooker] 9.2 - disaster already?
Vincent Danen wrote: On Tue Oct 21, 2003 at 08:04:19AM -0700, Rolf Pedersen wrote: # urpmi --bug bug djbsupport installing /contrib/i586/./djbsupport-1.0-5mdk.noarch.rpm Preparing... ## 1:djbsupport ## added medium qmail urpmi database locked error: %post(djbsupport-1.0-5mdk) scriptlet failed, exit status 7 djbsupport is bad, it should not try to modify a database being currently used, if this is *really* needed, a perl script should be used using directly the urpm library and avoiding to explicitely to lock the urpmi db (so that no error will occur), this script is simple but may depend upon newer interface of urpmi (so it need a require on major version of urpmi to be safe). François. OK. I was able to install djbdns by adding a source from http://rpmhelp.net/ Thanks. IIRC, djbsupport should no longer be in contribs. I think it may still be up for the older mdk versions, but I don't believe I made one for 9.2 thinking it's just too bloody easy to add a new source so I never bothered. Actually, I was able to urpmi djbsupport from my mirror of 9.2/contrib/, e.g: ftp://ftp.sunet.se/pub/Linux/distributions/mandrake/9.2/contrib/i586/djbsupport-1.0-5mdk.noarch.rpm Rolf
Re: [Cooker] 9.2 - disaster already?
On Tue Oct 21, 2003 at 08:04:19AM -0700, Rolf Pedersen wrote:
# urpmi --bug bug djbsupport
installing /contrib/i586/./djbsupport-1.0-5mdk.noarch.rpm
Preparing... ##
1:djbsupport ##
added medium qmail
urpmi database locked
error: %post(djbsupport-1.0-5mdk) scriptlet failed, exit status 7
djbsupport is bad, it should not try to modify a database being currently
used,
if this is *really* needed, a perl script should be used using directly
the urpm
library and avoiding to explicitely to lock the urpmi db (so that no error
will
occur), this script is simple but may depend upon newer interface of urpmi
(so
it need a require on major version of urpmi to be safe).
François.
OK. I was able to install djbdns by adding a source from
http://rpmhelp.net/ Thanks.
IIRC, djbsupport should no longer be in contribs. I think it may still be
up for the older mdk versions, but I don't believe I made one for 9.2
thinking it's just too bloody easy to add a new source so I never bothered.
--
MandrakeSoft Security; http://www.mandrakesecure.net/
Online Security Resource Book; http://linsec.ca/
lynx -source http://linsec.ca/vdanen.asc | gpg --import
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
pgp0.pgp
Description: PGP signature
Re: [Cooker] 9.2 - disaster already?
On Tue Oct 21, 2003 at 08:42:57AM -0700, Rolf Pedersen wrote:
OK. I was able to install djbdns by adding a source from
http://rpmhelp.net/ Thanks.
IIRC, djbsupport should no longer be in contribs. I think it may still be
up for the older mdk versions, but I don't believe I made one for 9.2
thinking it's just too bloody easy to add a new source so I never bothered.
Actually, I was able to urpmi djbsupport from my mirror of 9.2/contrib/,
e.g:
ftp://ftp.sunet.se/pub/Linux/distributions/mandrake/9.2/contrib/i586/djbsupport-1.0-5mdk.noarch.rpm
G... that was supposed to be removed months ago. =(
--
MandrakeSoft Security; http://www.mandrakesecure.net/
Online Security Resource Book; http://linsec.ca/
lynx -source http://linsec.ca/vdanen.asc | gpg --import
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
pgp0.pgp
Description: PGP signature
Re: [Cooker] 9.2 - disaster already?
Guillaume Cottenceau wrote: Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug. A workaround is to launch update-menus as root. This looks to me like it might be related: # urpmi --bug bug djbsupport installing /contrib/i586/./djbsupport-1.0-5mdk.noarch.rpm Preparing... ## 1:djbsupport ## added medium qmail urpmi database locked error: %post(djbsupport-1.0-5mdk) scriptlet failed, exit status 7 This is reproducible in two attempts, when installing with urpmi, first, then adding the --bug option to urpmi after urpme djbsupport. There is not a qmail source added to urpmi sources: # urpmi.update the entry to update is missing (one of CD1, CD2, CD3, CD4, club.comm_i586_9.2, contrib, plf, update_source) There is a compressed archive of bug/ here: http://home.mindspring.com/~rolfpedersen/bug.tgz Rolf
Re: [Cooker] 9.2 - disaster already?
On Thursday 16 October 2003 11:37 am, Guillaume Cottenceau wrote: Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug. A workaround is to launch update-menus as root. Do any of you that have this problem have fluxbox installed? -- /g Outside of a dog, a man's best friend is a book, inside a dog it's too dark to read -Groucho Marx
Re: [Cooker] 9.2 - disaster already?
On Thursday 16 October 2003 11:37 am, Guillaume Cottenceau wrote: Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug. A workaround is to launch update-menus as root. Do you guys that are having this problem have fluxbox installed? -- /g Outside of a dog, a man's best friend is a book, inside a dog it's too dark to read -Groucho Marx
Re: [Cooker] 9.2 - disaster already?
Guillaume Cottenceau wrote: Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug. A workaround is to launch update-menus as root. 1. Do an initial install with hd.img of 9.2, selecting everything except servers. Include nfs client. 2. Then use software install to install all the kde* RPMs which were not installed. 3. Note all the missing kicker panel big K menu items. 4. Running update-menus has no apparent effect. 5. Installing the Mandrake Updates solves the problem. -- Ron. [Melbourne, Australia] If you keep a green bough in your heart, the singing bird will come Get Fastest Mandrake downloader, English-only, from: http://members.optusnet.com.au/ronst/ Click all ye faithful!
Re: [Cooker] 9.2 - disaster already?
Greg Meyer wrote: On Thursday 16 October 2003 11:37 am, Guillaume Cottenceau wrote: Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug. A workaround is to launch update-menus as root. Do you guys that are having this problem have fluxbox installed? No, not me. -- Ron. [Melbourne, Australia] If you keep a green bough in your heart, the singing bird will come Get Fastest Mandrake downloader, English-only, from: http://members.optusnet.com.au/ronst/ Click all ye faithful!
Re: [Cooker] 9.2 - disaster already?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron Stodden wrote: Guillaume Cottenceau wrote: Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug. A workaround is to launch update-menus as root. 1. Do an initial install with hd.img of 9.2, selecting everything except servers. Include nfs client. 2. Then use software install to install all the kde* RPMs which were not installed. 3. Note all the missing kicker panel big K menu items. 4. Running update-menus has no apparent effect. 5. Installing the Mandrake Updates solves the problem. OK, so your reproducible case is that when you install some packages, the menus get broken, and when you install some other packages, they don't. Very reproducible. Not. - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/j7nGrJK6UGDSBKcRAnR+AJ9FcSdi5mECoHM6X4frP6cGJtStYQCgvU8P jJ7lVax1m/f4r1wPt7pliOs= =IvCP -END PGP SIGNATURE-
Re: [Cooker] 9.2 - disaster already?
Buchan Milne wrote: OK, so your reproducible case is that when you install some packages, the menus get broken, and when you install some other packages, they don't. Very reproducible. Not. Exactly and precisely reproducible as described, YES! Have you tried it? -- Ron. [Melbourne, Australia] If you keep a green bough in your heart, the singing bird will come Get Fastest Mandrake downloader, English-only, from: http://members.optusnet.com.au/ronst/ Click all ye faithful!
[Cooker] 9.2 - disaster already?
9.2 - disaster already? After an hd.img install of everything except servers, I immediately see that most of the kde RPMs were not installed with no installer error indication. After manually installing them and trying uselessly to run World Clock the amusement menu is rendered useless and cut back to only Arcade containing only frozen bubble and Chromium. The RPMs are still installed, which indicates some major conflictual screwup in the way they handle installing menu items. From this point user konqueror will not load from the menu. When tried manually: [EMAIL PROTECTED] ron]$ kfmclient openProfile filemanagement ERROR: Couldn't start konqueror from konqueror.desktop: Could not find service 'konqueror.desktop'. [EMAIL PROTECTED] ron]$ /usr/share/applink/konqueror.desktop is present. root konqueror will load and run from the kicker panel. Useful work-around: If the kicker root login dialog is ignored then user konqueror will load and run. konqueror will load and run if you click on (either as root or user) /usr/bin/konqueror. Confirmation and plan to fix before release at end of October, please. -- Ron. [Melbourne, Australia] If you keep a green bough in your heart, the singing bird will come Get Fastest Mandrake downloader, English-only, from: http://members.optusnet.com.au/ronst/ Click all ye faithful!
Re: [Cooker] 9.2 - disaster already?
torsdagen den 16 oktober 2003 08.08 skrev Ron Stodden: 9.2 - disaster already? After an hd.img install of everything except servers, I immediately see that most of the kde RPMs were not installed with no installer error indication. After manually installing them and trying uselessly to run World Clock the amusement menu is rendered useless and cut back to only Arcade containing only frozen bubble and Chromium. The RPMs are still installed, which indicates some major conflictual screwup in the way they handle installing menu items. I did a manual installation of everything KDE during installation and to me the Wold Clock is up and running in my desktop 8. To check your report I did a log out and reboot to view the results. And my last desktop to be 're-written' is desktop 4 with Kmail and there I got another functioning World Clock. I think that Mdk who uses Gtk and the Debian menu system and their own Mdk system of parting the KDE files is loosing some of the original sync because of c++ and c mis-match. Personally I prefere to have a full KDE installation and to be able to use Kappfinder in the original KDE way to add everything I install. I don't give very much for the Gnome way of hiding away certain programs, that is to say that they should know better than me what I should use. Pathetic way of non personal structure to my finding. regards guran -- Mandrake Linux 9.2 kernel-2.4.22.10mdk-1-1mdk Only in a society that has 'a priori' defined what is the truth can the result of the evolution of life be defined false.
Re: [Cooker] 9.2 - disaster already?
Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). Ron Stodden wrote: 9.2 - disaster already? After an hd.img install of everything except servers, I immediately see that most of the kde RPMs were not installed with no installer error indication. After manually installing them and trying uselessly to run World Clock the amusement menu is rendered useless and cut back to only Arcade containing only frozen bubble and Chromium. The RPMs are still installed, which indicates some major conflictual screwup in the way they handle installing menu items. From this point user konqueror will not load from the menu. When tried manually: [EMAIL PROTECTED] ron]$ kfmclient openProfile filemanagement ERROR: Couldn't start konqueror from konqueror.desktop: Could not find service 'konqueror.desktop'. [EMAIL PROTECTED] ron]$ /usr/share/applink/konqueror.desktop is present. root konqueror will load and run from the kicker panel. Useful work-around: If the kicker root login dialog is ignored then user konqueror will load and run. konqueror will load and run if you click on (either as root or user) /usr/bin/konqueror. Confirmation and plan to fix before release at end of October, please. -- Ron. [Melbourne, Australia] If you keep a green bough in your heart, the singing bird will come Get Fastest Mandrake downloader, English-only, from: http://members.optusnet.com.au/ronst/ Click all ye faithful!
Re: [Cooker] 9.2 - disaster already?
Fresh 9.2 install on a fresh harddrive. Everything went smooth and the machine rebooted and worked fine. Started Mandrake update and it downloaded/installed a couple of files successfully. After reboot almost the whole menu tree is empty and all application launcher items on the Kicker panel dissapeared. Ran update-menus and that brought back most (if not all) menu entries, but it didn't bring back any of the kicker application shortcuts. Had to start adding them manually again. Now I am almost afraid after reading some similar comments to install any new software or updates. Serge On Thursday 16 October 2003 04:20, Ron Stodden wrote: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). Ron Stodden wrote: 9.2 - disaster already? After an hd.img install of everything except servers, I immediately see that most of the kde RPMs were not installed with no installer error indication. After manually installing them and trying uselessly to run World Clock the amusement menu is rendered useless and cut back to only Arcade containing only frozen bubble and Chromium. The RPMs are still installed, which indicates some major conflictual screwup in the way they handle installing menu items. From this point user konqueror will not load from the menu. When tried manually: [EMAIL PROTECTED] ron]$ kfmclient openProfile filemanagement ERROR: Couldn't start konqueror from konqueror.desktop: Could not find service 'konqueror.desktop'. [EMAIL PROTECTED] ron]$ /usr/share/applink/konqueror.desktop is present. root konqueror will load and run from the kicker panel. Useful work-around: If the kicker root login dialog is ignored then user konqueror will load and run. konqueror will load and run if you click on (either as root or user) /usr/bin/konqueror. Confirmation and plan to fix before release at end of October, please.
Re: [Cooker] 9.2 - disaster already?
This is probably simply the update-menus that is running. It may take some time (30 seconds) You just have to wait or log off/log in. Eric
Re: [Cooker] 9.2 - disaster already?
On Thursday 16 October 2003 06:51 am, Serge Plüss wrote: Fresh 9.2 install on a fresh harddrive. Everything went smooth and the machine rebooted and worked fine. Started Mandrake update and it downloaded/installed a couple of files successfully. After reboot almost the whole menu tree is empty and all application launcher items on the Kicker panel dissapeared. Ran update-menus and that brought back most (if not all) menu entries, but it didn't bring back any of the kicker application shortcuts. Had to start adding them manually again. Now I am almost afraid after reading some similar comments to install any new software or updates. Serge same here but hey look at it this way we may get kde 3.1.4 as an update to fix this. Probably not though. -- -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- Brook Humphrey Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107 http://www.webmedic.net, [EMAIL PROTECTED], [EMAIL PROTECTED] Holiness unto the Lord -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
Re: [Cooker] 9.2 - disaster already?
Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug. A workaround is to launch update-menus as root. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] 9.2 - disaster already? Older server scsi problems
On Thursday 16 October 2003 08:37 am, Guillaume Cottenceau wrote: Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug. A workaround is to launch update-menus as root. I'll see what I can do maybe you guys dont use kde. but in at least 3 or 4 fresh installs when ever you install any package with a menu for kde this happens. It does fine if you get them all during install but if you install any kde apps after the os is installed this happens as well as all the icons missing off kicker. It is rather annoying. On a side not my trusty dec prioris 6000/4 can no longer install mandrake due to the fact that the installer bombs out on the scsi card. I have tried multiple times now. I have even tried with different scsi drives just to make shure it was not the drives. this also happens on my compaq 650 I think it is with a scsi controler and also a dec prioris mx 6200 the thing they all have in common is that they are all Multi procesor pentium pro prioris 6000/4 (4 cpus) prioris mx (2 cpus) compaq (2 cpus) and scsi but the prioris servers use adaptec ultra wide scsi and the compaq uses symbios I think. The install in all cases bombs out trying to format the drives. On a side note I have had mandrake 9.0 on the prioris 6000 and the compaq for a year or so with no issues. Me think I smell a nasty kernel driver issue. -- -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- Brook Humphrey Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107 http://www.webmedic.net, [EMAIL PROTECTED], [EMAIL PROTECTED] Holiness unto the Lord -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
Re: [Cooker] 9.2 - disaster already?
Le jeu 16/10/2003 à 15:37, Guillaume Cottenceau a écrit : Ron Stodden [EMAIL PROTECTED] writes: Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved). There seems there is still an odd locking problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, rpm -qa), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/. If only you could use triggers in the rpm db ... imagine, you install a rpm package, this starts the corresponding triggers ( a call to a function in update-menu library that update the menu accordingly ). This could allow faster operation and some really interesting things ... --- Je chante les heros dont Esope est le pere, Troupe de qui l'histoire, encor que mensongere, Contient des verites qui servent de lecons -- Jean de La Fontaine
