Shinobar's 'firstrun' PET has the numlockx binary executable in it. Firstrun is used in many puppies, as it offers a nice X GUI localization interface instead of the first-boot text-mode dialog windows of the traditional Puppy.
I am considering using firstrun, maybe even merging it into Woof, however, the first step is to extract 'numlockx' as a separate PET. It is uploaded to the 'common' repo and usable by all builds (3KB):
Comments:Posted on 16 Oct 2011, 10:54 by jodylehigh
I have enjoyed Racy and Tiny very much, but I found the only way I could manage the resolution with them on my hardware was to add and then use firstrun. Enjoying the new Wary 5.2 at this writing. Thank You for all your great efforts!
2005 HP XP Media Center, Processor 2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+,
Posted on 16 Oct 2011, 14:39 by Sage
Surely you can leave any mention of numlock out altogether - there is a keyboard hard-wired switch. SW numlock was a curse of Mandrake/driva - those guys had an obsession with it. Had to switch it off in HW three times during boot-up to make sure it stayed OFF!
Posted on 16 Oct 2011, 18:30 by wowow
This a good news.
where can I download this firstrun PET, and Barry, do you compile the numlockx from source, thanks.
Posted on 16 Oct 2011, 22:01 by linuxcbon
I see my remarks are usefull, so I will continue testing, especially the scripts, which are too complex and buggy . By the way, very important, please simplify the download folders in ibiblio. I don't even understand why there are old versions or there is separate puppylinux and quirky accounts which make things hard to follow. Please unify simplify. And the versions, maybe one test version each month is easier to follow, and one final each 3 or 6 months...
Posted on 17 Oct 2011, 7:13 by disciple
Sage - certain other operating systems remember the numlock status between reboots. Most people have it on most or all of the time, and find it disconcerting that when they reboot it is turned off in Puppy. Why do you have a problem with giving people a choice to have it on by default?
Posted on 17 Oct 2011, 7:26 by disciple
1. Some users don't even understand about number lock, and get very confused if it is off. Mentioning it in firstrun will be educational for these people.
2. Every keyboard I have ever seen has big labels for the numbers, and tiny little ones for the arrows, which indicates that they are a secondary feature which can be accessed by using the shift key. It therefore makes more sense for numlock to be on by default... probably even more sense than remembering the status between boots.
Posted on 17 Oct 2011, 10:15 by broomdodger
on notebook computers the numlock keys are second function on letter keys.
having numlock on by default would be very confusing.
Posted on 17 Oct 2011, 13:26 by Sage
"Most people have it on most or all of the time, and find it disconcerting that when they reboot it is turned off in Puppy. Why do you have a problem with giving people a choice to have it on by default?"
You are mistaken. Most people want it OFF and never use it. It would save a lot of plastic(aka oil) and copper if the keypad were omitted from keyboards. For those who persist, is it too arduous to lift your finger to press 'NUM LOCK'? If you want a keypad, these can be purchased on a separate flying lead.
Just to claim 'more sense', 'everybody does it' doesn't make it true. It's like sex talk amongst early teens. Might have to revise that simile, though, this century...
Posted on 17 Oct 2011, 17:05 by 01micko
Sage said, "You are mistaken. Most people want it OFF and never use it. It would save a lot of plastic(aka oil) and copper if the keypad were omitted from keyboards. For those who persist, is it too arduous to lift your finger to press 'NUM LOCK'? If you want a keypad, these can be purchased on a separate flying lead."
I think that would upset many number crunchers :). As disciple said, and as you have seen in Slacko, it is a choice. No body ever said it would be on by default, in fact default is off and always will be.
Posted on 17 Oct 2011, 17:53 by Sage
"default is off and always will be. "
Thanks for that confirmation, mick - friend for life!
Posted on 17 Oct 2011, 19:14 by shinobar
For your information
Updated firstrun to v1.9.
Regarding the startup sequence, i hope you reconsider the delayedrun.
In my opinion, it must be more simple if the delayed run never be involved in the sequence.
I hope they are easy for the puplet maker to plug in and off, that is barking, launching welcome1stboot, installing flashplayer and launching bootmanager.
Posted on 17 Oct 2011, 20:11 by 01micko
I tend to agree with shinobar. /usr/sbin/delayedrun is a bit of a mess (in part due to me) and should be revised.
I think (shino, correct me please if wrong) shino refers to extra stuff that could be run from the ~/Startup dir. (yes, Startup apps are called by delayedrun, for onlookers)
Posted on 17 Oct 2011, 22:49 by Iguleder1
All stuff from .xinitrc should be moved to /root/Startup - if we already want stuff to run on startup, let's do it right and use only one method.
I overwrite ~/.xinitrc with "exec openbox" just to get rid of all the mess it causes on non-JWM/IceWM/etc' puplets.
Posted on 19 Oct 2011, 15:11 by Sage
Help at hand
A little old lady is coming to Perth today to help you with your computing problems. She is an ardent twitter, allegedly. Watch out for the sword, not wielded in anger, but don't nod in the wrong place.
Posted on 19 Oct 2011, 18:21 by BarryK
I'm still thinking about delayedrun, .xinitrc and /root/Startup ...need gestate for awhile.
One problem with /root/Startup is that I envisaged it as a place for end users to mess around in.
I don't really want to have things in it that are more relevant to developers.