Re: DO NOT UPGRADE TO POTATO. MENU UPLOAD ON OCT 2 KILLS SYSTEMS
In <[EMAIL PROTECTED]>, on 10/06/99 at 06:28 PM, Hamish Moffatt <[EMAIL PROTECTED]> said: >On Tue, Oct 05, 1999 at 08:13:41PM -0400, Terry Katz wrote: >> 2.1.3-2 is one that does it ... >Seems to behave itself here. But then I only have fvwm2 installed, none of >these fancy new wms. I had individual ones start up on menu's invocation with some upgraded packages. First olvwm, then wmaker, then I finally got the thread killed (thought I had it the first time, but another was somehow spawned). Menu's been removed now. My upgrade came before the warning... yech. And I had the usual (?) assortment of wm's. That's now been trimmed. Kenward -- --- [EMAIL PROTECTED] ---
Re: DO NOT UPGRADE TO POTATO. MENU UPLOAD ON OCT 2 KILLS SYSTEMS
On Tue, Oct 05, 1999 at 08:13:41PM -0400, Terry Katz wrote: > 2.1.3-2 is one that does it ... Seems to behave itself here. But then I only have fvwm2 installed, none of these fancy new wms. hamish -- Hamish Moffatt VK3SB. CCs of replies on mailing lists are welcome.
RE: DO NOT UPGRADE TO POTATO. MENU UPLOAD ON OCT 2 KILLS SYSTEMS
> It doesn't totally kill the system .. It seems to start up the various wm's, > and they run at about 95% cpu and 88%+ memory for about 2-5 mins (each), but > they do die (or finish?) and everything is fine (my worst case, I saw > gnome-panel running at 95% for about 3 mins, then wmaker running at that for > 3 mins.. (in console mode))... Its an annoyance, but it doesn't kill the > system .. (at least on 3 of mine it didn't) Could we have a potato mailing lists? It would be really nice to e-mail fellow potato users and check for the latest bugs, features, etc. Also... someone commented to me about how unstable debian is. After some clarifications... I realized that he was talking about the potato debian release which was always discussed on the debian-user mailing lists. regards, = == Andre M. Varon - Technical Head = = == Lasaltech, Inc. - http://andre.lasaltech.com = === = = = = If I cannot bend Heaven, I shall move Hell. = = -- Publius Vergilius Maro (Virgil)
RE: DO NOT UPGRADE TO POTATO. MENU UPLOAD ON OCT 2 KILLS SYSTEMS
2.1.3-2 is one that does it ... It doesn't totally kill the system .. It seems to start up the various wm's, and they run at about 95% cpu and 88%+ memory for about 2-5 mins (each), but they do die (or finish?) and everything is fine (my worst case, I saw gnome-panel running at 95% for about 3 mins, then wmaker running at that for 3 mins.. (in console mode))... Its an annoyance, but it doesn't kill the system .. (at least on 3 of mine it didn't) Terry > > > "Adam" == Adam Heath <[EMAIL PROTECTED]> writes: > > Adam> I just did an upgrade. The menu pkg ate memory like no > Adam> tomorrow. > [...] > Adam> Cease and desist at all costs. > > Adam> I have just been informed on irc that a fixed menu is in > Adam> incoming. So, it should all be fixed tomorrow. > [...] > > Adam, thanks. What are the menu package versions (broken and fixed)? > Thanks. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] >
Re: DO NOT UPGRADE TO POTATO. MENU UPLOAD ON OCT 2 KILLS SYSTEMS
> "Adam" == Adam Heath <[EMAIL PROTECTED]> writes: Adam> I just did an upgrade. The menu pkg ate memory like no Adam> tomorrow. [...] Adam> Cease and desist at all costs. Adam> I have just been informed on irc that a fixed menu is in Adam> incoming. So, it should all be fixed tomorrow. [...] Adam, thanks. What are the menu package versions (broken and fixed)? Thanks.
Re: DO NOT UPGRADE TO POTATO. MENU UPLOAD ON OCT 2 KILLS SYSTEMS
On Tue, Oct 05, 1999 at 03:58:10PM -0500, Adam Heath wrote: > I just did an upgrade. The menu pkg ate memory like no tomorrow. I have a > dual-330, 256m ram, 384m swap. Update-menus calls install-menu, and I saw > that eating 280m of memory. Just don't install the new menu package. It's fscked up anyway. It didn't integrate with ANY of my window managers.
