Thanks watchdog, the information you provided has been very helpful. I think I fixed this... https://github.com/puppylinux-woof-CE/w ... 986b0627a9watchdog wrote:@jlst
I think there is a problem in the first shutdown procedure with my configuration (ext4 partition). The lightencrypted slackosave saved does not work but if I use a renamed slackosave from wary after replacing its content with a slackosave folder it works.
You're right, that's the right way to do it. I do use locale-gen... or used to use it, locale.gen and locale-gen are deleted in the woof process. i'll fix this, and rewrite the locale stuff.. soon..anikin wrote:...
Hello jlst.jlst wrote:You're right, that's the right way to do it. I do use locale-gen... or used to use it, locale.gen and locale-gen are deleted in the woof process. i'll fix this, and rewrite the locale stuff.. soon..anikin wrote:...
Puppy is a bit more rational now, it doesn't connect to icanhazip (by default) or pings google or duckduckgo [deleted references] (i think there is still a script that pings duckduckgo, but you have to call it manually)... with the xorg_base_new pkg template people can use any app to configure the keyboard layout.. in theory..
I want to make it very C.L.E.A.R.musher0 wrote:Concerning the development of Puppy Linux itself , this looks like we're
undoing a solution found many years ago -- and that works well.
"If it works, don't fix it," I'd say. Puppy doesn't need to chase its tail like
this.
BFN
peebee wrote:Hi riedzig....I'm pleased to report that the Keyboard Handler panel plugin is now working in LxPupSc-17.01.21.....riedzig wrote:Hi Peebee
I'm still using your excellent LXpup as No. 1 among all distros, but I am also trying to get through some bugs (not found in forums). One of them is the Keyboard Layout switcher/handler), which won't show in any LXPup the appropriate flags in the panel (shows only a blank frame). Do you please know a solution?
It works! However there is a warning when mounting the lightencrypted savefile after writing the password to load it at e2fsck about the "date in the future" of the superblock probably due to hardware clock not correctly set. My clock is correctly set, I think.jlst wrote:I think I fixed this... https://github.com/puppylinux-woof-CE/w ... 986b0627a9watchdog wrote:@jlst
I think there is a problem in the first shutdown procedure with my configuration (ext4 partition). The lightencrypted slackosave saved does not work but if I use a renamed slackosave from wary after replacing its content with a slackosave folder it works.
I attach a adrv for you to test and report is this fix works for you...
Sorry, jlst.jlst wrote:I want to make it very C.L.E.A.R.musher0 wrote:Concerning the development of Puppy Linux itself , this looks like we're
undoing a solution found many years ago -- and that works well.
"If it works, don't fix it," I'd say. Puppy doesn't need to chase its tail like
this.
BFN
The issue was that the /usr/lib/locale [already fixed] directory was missing. In slacko the app that initializes the default locale needs that directory to be present (it only happens in slacko, other puppies start ok).
In a previous post i attached a adrv_slacko_6.9.6.4.sfs file, which also fixes the locale issue. everyone wanting a quick fix may want to add that file to their slacko 6.9.6.4 frugall install dir and start again.
Looking at the lxpup thread, the change in xorg template made the lxde keyboard handler work. The woofce 'native' keyboard handler also works as expected.
peebee wrote:Hi riedzig....I'm pleased to report that the Keyboard Handler panel plugin is now working in LxPupSc-17.01.21.....riedzig wrote:Hi Peebee
I'm still using your excellent LXpup as No. 1 among all distros, but I am also trying to get through some bugs (not found in forums). One of them is the Keyboard Layout switcher/handler), which won't show in any LXPup the appropriate flags in the panel (shows only a blank frame). Do you please know a solution?
Respectfully.[/mnt/+mnt+ho....9.6.4.sfs]>tree
.
└── usr
├── lib
│ └── locale
└── sbin
└── shutdownconfig
4 directories, 1 file
Sometimes I see this when starting with pfix=fsck, it's a just warning and it only once i think. so it's ok to ignore it.watchdog wrote:It works! However there is a warning when mounting the lightencrypted savefile after writing the password to load it at e2fsck about the "date in the future" of the superblock probably due to hardware clock not correctly set. My clock is correctly set, I think.
I was not aware of that, i'll fix it. And please don't talk about animosity ... there's always animosity in the way you talk. You make fun of others, but it's an insult when they play your game.musher0 wrote:jlst.
As you can see from the attached diff report, the only keyboard missing
from your new list is the qc keyboard, the one I use.
Do you have animosity against me? If not, who shall I give a mouthful to?
Perhaps I'm the only Puppyist using that keyboard, but one cannot forget
just like that the millions of French-Canadians who use that keyboard daily
on other OS's.
Respectfully.
Sorry about the tone.jlst wrote:I was not aware of that, i'll fix it. And please don't talk about animosity ... there's always animosity in the way you talk. You make fun of others, but it's an insult when they play your game.musher0 wrote:jlst.
As you can see from the attached diff report, the only keyboard missing
from your new list is the qc keyboard, the one I use.
Do you have animosity against me? If not, who shall I give a mouthful to?
Perhaps I'm the only Puppyist using that keyboard, but one cannot forget
just like that the millions of French-Canadians who use that keyboard daily
on other OS's.
Respectfully.
Thanks for the reply, jlst.jlst wrote:I looked in ubuntu and slackware packages, the reason qc is not there is because that kb is long gone. Even precise (2011) doesn't have that kb.
http://packages.ubuntu.com/precise/all/ ... a/filelist
The template uses what's available in the distro.
Hi musher - I think it is unreasonable to consider people "bulldozers" just because they speak the languages spoken by the majority. It is a form of terrorism to try to enforce acceptance of the minority behaviour.musher0 wrote:I'm quite surprised at this "reflex": were the authors of this edit brought up in an unilingual environment absolutely unaware that other languages were spoken in the world?
Sorry for being so frank, but that's what it looks like viewed from French-
Canada. This also means that members of minority cultures generally
(not just cf or qc) must continue to be vigilant against bulldozer languages
such as English, Russian and Mandarin.
