Puppy Linux Discussion Forum

[clarf]

Hi ttuuxxx,

There is nothing wrong with the jwm -exit option , but there´s a bug inside xwin using Xvesa . In Xvesa mode you can´t exit to prompt, reboot or shudown Puppy. I will explain the full problem and solution implemented:

1. When you call /usr/X11/wmpoweroff or wmreboot from menu, these scripts writes "poweroff" or "reboot" in /tmp/wmexitmode and then do a "killall X". At the end of X it returns control to xwin, which reads the file exitmode if this file is present with some of the previous words, xwin runs /sbin/poweroff or reboot. But xwin has a "exec xwin" code that prevented to read the value saved in exitmode, then it not executed the proper shutdown or reboot scripts and does a restart instead. So I had to move the code in xwin to fix the problem with reboot and shutdown.

2. The option "exit to prompt" (jwm -exit) kill the actual windows manager jwm, then xwin is called but it starts again the windows manager and you can´t exit to prompt. It´s a normal behavior because xwin needs to be restarted each time you choose a different video mode (resolution or depth color) and not exit to prompt. That´s the reason I had to change the "jwm -exit" call to wmexit, because wmexit writes a "exit" value to /tmp/wmexitmode as reboot or poweroff options do, if xwin finds that value then it will not restarts X.

With the fix you can change video modes in Xvesa without exit to promt, yet you can reboot, poweroff or Exit to Prompt when you want to.

About wmexit it only does a killall X so there´s no rela problems using it. Although it has a counter before kill actual windows manager (jwm), it counts up to 30 seconds waiting for process pup_event_front_end_d to be terminated before "Exit to Prompt", if that process is not in memory then it kill X immediately. I don´t find any other possible reason to have problems using wmexit, but that time could be shorted if you want. Also additional clean up code could be included in wmexit, to terminate some buggy app before Exit to prompt.

I hope that I expressed myself clear enough to explain the bug with Xvesa and Why I made those changes.

Any questions will be answered gladly.

Greetings, your friend

clarf

[Aitch]

ttuuxxx

I found this nice little mail gif [attached]

Any use to you?

Aitch

Edit: Icon??? It's a dynamic gif, ...try turning on java

You'll see a letter being scribed, then folded & put in an envelope

[ttuuxxx]

Nice icon Aitch and great response clarf as ever
ttuuxxx

[ttuuxxx]

Ok here a 25MB pet that I'm working and will be a sfs in the near future, its made for writers. I've read online that lyx is the best app for writers once you get used to it, I still have to get some plugins but its a start, I used an older version because of the different QT deps. Included are the following files
http://puppylinux.asia/tpp/ttuuxxx/2.14series/documents/Writers-Software-v1.pet
username:puppy
password:linux

aspell6-en-6.0-0
aspell-0.60.6
enchant-1.5.0
Python-2.5
lyx-1.4.1
QT-Theme-ttuuxx
scribus-1.3.3.13
stardict-3.0.1

ttuuxxx

As a addon is F4L is a Flash swf editor/creator, its only good with the above pet, it uses a large QT lib which is included.

[sullysat]

Very cool idea. Thanks ttuuxxx!

I write, so this will be very welcome

Sully

[ttuuxxx]

I also have to add some plugins/templates for lyx, maybe tomorrow I'll update it
ttuuxxx

[Colonel Panic]

Hi. I'm afraid I've had a few problems with this one. I downloaded a copy of the iso and burnt two copies to disk, and in each case when I tried to boot it up I got this message;

Loading isolinux: Disk error 00, AX=42A2, drive 9F

Boot failed...press a key to retry...

and I have therefore had to write them both off as duds.

Can anyone tell me what the problem is? I've downloaded and used four previous versions of Ttuuxxx's 2.14X series and whilst in my experience they're all prone to freezing up and necessitating a reboot, mostly when Firefox is running with several windows open, I've not had this problem so far with any of them.

In fact, just to prove the point I booted up Puppy 2.14X7, made a savefile from it and then used it to boot 2.14X4, which I'm posting from now - all with no problems whatsoever.

[Aitch]

[ttuuxxx]

[sinc]

thanks clarf, I read the thread and right away switched to 214X to download the fix. Thank you very much for your time and knowledge, you have been a HUGE contributor in applications and getting these hidden bugs out of 214X. Thank you again!!!

[ttuuxxx]

Hi Guys I've been thinking it would be nice if could finish this off and continue with puppy 2.20. Since its the smallest woof and we could keep that version going into the future.
With 2.20 I could use it for Living water, OLPC, and a main puppy retro release.
Right now I'm over extending myself with so many large projects and not enough hours in week.
So I'll let this release go for another week or two, then make a RC2 to test the changes and for Christmas I guess I could Release 2.14X-Final.
Meanwhile I'll get 2.20 going again
ttuuxxx

[James C]

ttuuxxx,

Sounds like a plan to me. It looks like most of the bugs have been squashed in 2.14 X and its basically down to polishing off the final few details.

Anyway, work and family need to come first.....but 2.14 has been a heck of a journey.....

[davesurrey]

Hi ttuuxxx and everyone,
Yes sounds a great plan ttuuxxx and a great Xmas present.

My only regret is that I can't use it on my asus eee 901 due to the lack of wifi drivers for this kernel. Needs rt2860sta.


Cheers
Dave

[ttuuxxx]

[davesurrey]

Ahhhh...my stupidity again. Just found a load of interesting stuff about this on this very thread. Sorry for wasting your time.
Off to try this now.
Dave