Fatdog64-800RC [13 Feb 2019] [CLOSED]

[mavrothal]

Other than that nothing major besides the remaining spot/Downloads on fat/vfat media that is still useless and makes running the browser as spot annoying at least.

I thought we've fixed this. Let me check again.

No, you are right. I had updated the beta savefile . Is ok on a new one.
Though now spot has access in the entire device not just the Downloads folder. I guess is a trade off.

A bit latter: It would appear that the keyboard issues are not mac-specific. In an oldish i5 samsung (NP350) the Fn modifier is recognized only for F1, 6, 7 and 8 but not F2, 3, 4, 5, 11 and 12. In this cage neither showkey (-s) nor hexdump -C nor xev return any code as if they are dead. For reference "big" distributions have no issue with either mbp nor samsung function keys and modifiers.

[jamesbond]

No, you are right. I had updated the beta savefile . Is ok on a new one.
Though now spot has access in the entire device not just the Downloads folder. I guess is a trade off.

It is indeed a trade-off. It's the only way to do it if you're using FAT. Using any other filesystem (including ntfs), spot will not have access to the partition.

If you don't move the Downloads folder, the easiest way to lock down spot when you have savefile in FAT is to pass the boot param SAVEDEVICE_MODE_STRICT=yes. (Don't use this if you move the Downloads folder otherwise spot can't access it).

A bit latter: It would appear that the keyboard issues are not mac-specific. In an oldish i5 samsung (NP350) the Fn modifier is recognized only for F1, 6, 7 and 8 but not F2, 3, 4, 5, 11 and 12. In this cage neither showkey (-s) nor hexdump -C nor xev return any code as if they are dead. For reference "big" distributions have no issue with either mbp nor samsung function keys and modifiers.

Yeah, this is quite confusing. udev changed the way the handle keyboard; but that was a couple years ago (many of the points remain valid however). That being said, we have the full eudev in FD; with complete rules and hwdb for keyboards, so it should work. Except that it doesn't. I installed 800alpha on samsung laptop (not accessible to me at the moment) and I still had to use the compatibility "udev-keymap" to program the special keys. Perhaps those big distros have something else going that I'm not aware off. I'd look at that but it probably won't get resolved in Final. Nevertheless, I have added the mbp special xmodmap codes; so at least we're covered for the mbp case

[mavrothal]

Perhaps those big distros have something else going that I'm not aware off.

As far as I can see now keymaps are kernel modules, kernel kbd and X xkb are unified, and systemd (:shock: ...) takes care of the rest.
I do not know if building the kernel with the keymaps modules in will make scancodes recognizable or not but might worth trying.
In the mean time I went around the lame-way, got scancodes from kernel errors and made the relevant setkeycode entries in rc.local (no messing with udev rules)

[jamesbond]

[mavrothal]

I've just rebuild eudev

Is this in the repo (to test)?

[stemsee]

bluez package no longer has bt-audio, it seems.

I have not examined the difference between this package and the one in fatdog-721, but maybe audio connection is now through 'bluealsa', but my bluetooth app you referenced in the first post does not connect audio service in 800RC.

Also using 'prt sc' to capture areas of the screen places the image in /root. So that when trying to upload to forum using seamonkey, images are not accessible by spot ... they then need to be copied into spot /root directory.

EDIT: bluetoothctl is installed: it wasnt in 721. This maybe useful.
https://stackoverflow.com/questions/218 ... t-commands

[jamesbond]

bluez package no longer has bt-audio, it seems.

This was provided by bluez-tools package in 721. In 800, bluez-tools no longer provides this as the same functionality can now be done using bt-connect.

I have not examined the difference between this package and the one in fatdog-721, but maybe audio connection is now through 'bluealsa', but my bluetooth app you referenced in the first post does not connect audio service in 800RC.

Oops. I was under the impression you did this for the 800 series and therefore has taken into account the changes in 800.

The change is basically because we use bluez-5.x. Bluez-5 is a major change, they drop a lot of the tools and change the way things work behind the scenes. Bluez-tools also removed a lot of their tools because bluez-5 no longer provides the API to work with it.

Also using 'prt sc' to capture areas of the screen places the image in /root. So that when trying to upload to forum using seamonkey, images are not accessible by spot ... they then need to be copied into spot /root directory.

Yes. This is by design. This is to prevent you accidentally take an embarassing screenshot which is accidentally shared with the rest of the world ....

But if you really want screenshots to be saved to /home/spot automatically, just edit /etc/xdg/Startup/xscreenshot and add the parameter "-p /home/spot/xscreenshot" to the "exec" line you see there. Then logout and login again.

EDIT: bluetoothctl is installed: it wasnt in 721. This maybe useful.
https://stackoverflow.com/questions/218 ... t-commands

bluetoothctl is the "new" CLI tool from bluez.

[stemsee]

Excellent stuff. I will rewrite the script to take advantage of the bluetoothctl and anything else I can find. But I already connected a speaker using bluetoothctl interactive mode. Yes, it is much easier and more reliable. I also found how to pipe to bluetoothctl so both options will be available if useful.

I will also simply link to fd bluetooth tether in the command section. If the mac address can be piped to the script.

[don570]

Suggestion...

When 'Reboot' is selected from menu there is a warning message...
however it should remind user to save open documents.
_________________________________________________

[stemsee]

This was provided by bluez-tools package in 721. In 800, bluez-tools no longer provides this as the same functionality can now be done using bt-connect.

err bt-connect is not in bluez5 but bluetoothctl connect.

Actually to connect a bluetooth audio device is like this

Code: Select all

bluetoothctl
bluetoothctl#scan on
bluetoothctl#devices
bluetoothctl#pair $mac
bluetoothctl#trust $mac
bluetoothctl#connect $mac

or non interactively

Code: Select all

echo -e "scan on" | bluetoothctl
echo -e "devices" | bluetoothctl
echo -e "pair $mac" | bluetoothctl
echo -e "trust $mac" | bluetoothctl
echo -e "connect $mac" | bluetoothctl

or

Code: Select all

bluetoothctl scan on
bluetoothctl scan off
bluetoothctl devices
bluetoothctl pair $mac
bluetoothctl trust $mac
bluetoothctl connect $mac

Audio Services available seem to be auto-found.

[quirkian2new]

I usually run Fatdog64 in RAM without any save file, the existing remind message on reboot or shutdown seems OK to me and i have already got used to it . Thanks

[quirkian2new]

Running 800RC now, Clicking on a jpeg file in ROX-Filer cannot open the jpeg file, and nothing happens.

[quirkian2new]

in 800 alpha/beta, there is the numlock light issue :

http://www.murga-linux.com/puppy/viewto ... 9&start=45

the numlock light issue seems still remains in 800RC. Thanks

[jamesbond]

Thanks for the report.

@don570: I will change tthe message a bit.

RE: JPEG issue - foxpup found that too, with the fixes: http://murga-linux.com/puppy/viewtopic. ... 95#1018595/ We have already fixed it for Final.

RE: numlock issue: Does this fix it?
a) Open COntrol Panel, navigate to Desktop tab
b) Then open "Manage desktop startup programs", then click the "System startup program"
c) Scroll down and you will see "numlock off" or "numlock on". Choose one of them, and then click "enable"

Let me know if that solves your issue.

[stemsee]

Hi all

The remastering function is slightly flawed in the case where there is enough room to do the remaster, but not enough room also for the iso image. What happens then is a partly made iso remains and all 'usefully complete' remaster objects get deleted.

Ideally the calculation to take into account the size of system + basesfs + iso. And/or make a further calculation before creating the iso and leaving said objects if not enough room available. Or after creating the basesfs and initrd delete the copied system, and then proceed with the iso creation.

stemsee

[foxpup]

I had the numlock issue in xenial64pup, also with the shiftlock.
Adding

Code: Select all

modprobe input-leds

to /etc/rc.d/rc.local solved it for me then.

[jamesbond]

@foxpup: On my desktop I found that input_leds is already loaded (by udev). That being said there is a possibility that Xorg starts up before udev finish loading this module, so the problem. In this case, the solution is to add "input_leds" to /etc/modules (so it gets loaded much earlier, before udev is even started). I don't want to do this by default because not everybody is having the same problem and I'm not sure of the hazard of loading this module for systems that don't need it.

Of course, modprobe-in it via /etc/rc.d/rc.local works too. Many ways to skin the cat

EDIT:

@stemsee - The size estimation is based on how big is the uncompressed filesystem. We're estimating that we can compress at least half of this (this will be the size of the SFS), and then the ISO will be about the same size as the SFS; thus we expect that the total size of temporary files + ISO will be about as big as the uncompressed filesystem. Of course how true / correct is this, depends on:
a) how compressible is the content, and
b) compression method (lz4

I can compensate for (b) by multiplying the required size by a fudge factor based on the compression method chose; but I cannot compensate for (a) other than adding a safety factor.

[stemsee]

So, seems to me, the best option, avoiding arbitrary guess work, would be to make a calculation just before creating the iso, if not enough room stop the remaster leaving created objects.

Because in my personal scenario 99% of my remasters is just to update the basesfs with a few script edits and then replace the basesfs on a frugal install. (basesfs update) maybe another function to add, combining an update sfs to the basesfs.

[jamesbond]

So, seems to me, the best option, avoiding arbitrary guess work, would be to make a calculation just before creating the iso, if not enough room stop the remaster leaving created objects.

Not a bad idea. We'll still do an estimation at the beginning but if the save location can't hold the ISO we'll bail out rather than producing incomplete ISO.

[WB7ODYFred]

Joplin Note taking application

https://joplin.cozic.net
https://electronjs.org/apps/joplin

wget to download and install to a Linux from a terminal window.

Code: Select all

wget -O - https://raw.githubusercontent.com/laurent22/joplin/master/Joplin_install_and_update.sh | bash

or Download from here on github:

https://github.com/laurent22/joplin

Other URL articles about Joplin Notes application operation and useage
https://opensource.com/article/17/12/jo ... lternative
https://www.linuxuprising.com/2018/08/j ... -note.html

As an American using an Android phone Motorola Moto E5 model, I found it amazing to install and Use Joplin from Google Play. Make a note by clicking, but instead of hunting and pecking on the virtual keyboard, I choose to click the little microphone on the upper right hand side of the keyboard and then speak my note into existence! Wow!
Then from Debian 9 Q4OS using Joplin, I could print my notes into a PDF file for sharing or printing or emailing. The Todo check boxes for a ToDo list was a good addition.

I tried installing on Fatdog64 800 Beta and got an error in trying to execute Joplin. I don't have the error information handy to share here now, just my feeble memory :>).
The Joplin Electron app does work in LinuxMint 19.1 Teresa without errors and in http://Q4OS.org Debian 9 Sid version.
I wanted to note this here now before RC is released. I will test soon on my 800RC installation and report back here my errors in a future edit. Welcome comments and other error reports. Yes, I believe the 800RC is great and that the included apps work well together. I just want to support Electron apps and/or AppImages that others might use in the future. Here, Joplin is just a test case. Yes, you can't have everything included because the base size gets too large.

Thanks James Bond, and other developers for a wonderful FatDog64 experience with a small linux package.

Fred

Here is my pastebin copy of the Joplin install on Linux Mint 19.1

https://pastebin.com/e3jekczW