Puppy Linux Discussion Forum

@ Geek3579, about the ydrv. Yes, you can rename it adrv. But I like reserving adrv for applications which need to be updated frequently, e.g. web-browsers*. So what I did was:

(1) mount the ydrv and copy its contents to a folder I named ydrv.
(2) Right-Clicked the folder and selected dir2pet.
(3) installed the ydrv.pet
(4) Right-Clicked the ydrv.sfs and renamed it 0ydrv.sfs -- just in case something went wrong & I had to revert.
(5) rebooted.
(6) Used nicOS-Utitlity-Suite's Remaster* Alternative, https://www.forum.puppylinux.com/viewto ... 983#p12983 to create a new base.sfs. [I think radky/rockedge now include the Suite. Look at the Utilities Sub-Menu].

That enables me to include applications I want to add and don't expect to change to a ydrv and those which change frequently to an adrv.

But I didn't realize initrd will now use bdrv. So rockedge's solution might be better.

* Neither PPM>Uninstall nor Menu>Setup>Remove Builtins can be used to remove applications in adrv, bdrv or ydrv. Removing, updating applications within them can be complicated. Before the remaster I removed the Builtin web-browser otherwise my system would have web-browsers in both the base and the adrv wasting space and resources. With the Suite in the base.sfs I can temporarily boot without the ydrv and use Save2SFS to update web-browsers.

Null_ID wrote: ↑Sun Feb 19, 2023 11:50 pm

So thanks again for another great release...

Thank you Null_ID !

A few more fixes are underway before the final release.

oldaolgeezer wrote: ↑Sun Feb 19, 2023 11:48 pm

I installed the latest Calibre (version 6.13) via the F96-CE_1
quickpet fossa Office feature.

When I attempted to view a converted ebook, nothing happened.

After trying a few things, I noticed that there was an error message while
trying just the Calibre version 6.13 ebook-viewer utility:

to see the error message, I ran Calibre's ebook-viewer in a terminal:

# /opt/calibre/ebook-viewer
...
Running as root without --no-sandbox is not supported.

I had found the same issue when testing fossapup64-9.5 and
made a little workaround script: no-sandbox-ebook-viewer.sh, (for
dragging my ebook .azw, .mobi, .azw3 or .epub file to my Calibre's ebook-viewer startup script):
viewtopic.php?p=6415#p6415

(and later 666philb (fossapup64's developer) made a much more sophisticated
repair by using /etc/profile.d which installed via his Quickpet >>> fossapup updates
for Calibre's ebook-viewer utility.)

Might we need 666philb's /etc/profile.d Calibre's ebook-viewer code in F96-CE_1 ?

Thanks for any help

@oldaolgeezer

The bugfix feature of the original F95 "quickpet fossa" is now disabled since some of the older updates will break the current F96 release. Unfortunately, @rockedge does not have access to the quickpet files at the ibiblio server, so it is no longer possible to update or modify the original quickpet resources.

However, the pet below contains 666philb's original F95 update for the Calibre's ebook-viewer. In time, this update and others if necessary, could be made available in a more accessible forum location such as an update or bugfix thread for F96.

Thanks for the report.

rockedge wrote: ↑Mon Feb 20, 2023 1:45 pm

Geek3579 wrote:

Is it possible to install these Desktop environments in other ways, eg in the package manager ??

Yes I think it is possible by renaming the yfrv to adrv or in some cases bdrv and then inserting the desktop eniviroment as the ydrv.

Some juggling might be needed to find the right combination when it comes to the layering order.

Thanks, I will give that a try later in the week.

Maybe it´s just a side question.
Can Firefox-ESR Portable (included in F96-CE_1) be run as spot?
Its checkbox (to run as spot) doesn´t seem to be available in the login manager.
Thanks.

EDIT:
@mikeslr , thanks for your tutorial (5 posts down) for running firefox_esr portable as spot. I edited the LAUNCH script in /opt/FirefoxESR-portable64 exactly as instructed. Then running "run-as-spot firefox_esr" in the terminal returns 2 messages in the sense of "...no such file or directory". Maybe I'm making a mistake somewhere. But nevermind, I was just wondering if a common user could easily achieve this.

F96-CE_1 is looking good! I just replaced F96-CE_stable with this one. Runs really snappy.

@Feek Because it is a portable application is the reason I think that run-as-spot script is not working in the case of ->
in a terminal : run-as-spot firefox_esr
which may have to do with it's failure to start and run as user spot.

rockedge wrote: ↑Tue Feb 21, 2023 3:33 pm

@Feek Because it is a portable application is the reason I think that run-as-spot script is not working in the case of ->
in a terminal : run-as-spot firefox_esr
which may have to do with it's failure to start and run as user spot.

I don't have much experience with portable browsers, so thanks for the clarification.
I did a quick test. I downloaded the latest 64-bit chromium (.sfs) from peebee, put it in /mnt/home, then loaded it on-the-fly. Then I went to Menu --> System --> Login and Security Manager --> Configure apps to run as spot. I checked Chromium here and confirmed. Then I successfully started Chromium and found in htop that it was running as spot.
So there are definitely solutions.

rockedge wrote: ↑Mon Feb 20, 2023 1:45 pm

Geek3579 wrote:

Is it possible to install these Desktop environments in other ways, eg in the package manager ??

Yes I think it is possible by renaming the yfrv to adrv or in some cases bdrv and then inserting the desktop eniviroment as the ydrv.

Some juggling might be needed to find the right combination when it comes to the layering order.

Yes I simply changed the ydrv to adrv (and anther one as well...I forget) then added in the slightly name-changed ydrv with the LXQt built for Fossapup64.

Has worked flawlessly so far, although PCMANFM still does not show all the drives, or shows them as empty.. One can work around that by putting a link on the dektop to /mnt and pre-mounting the drives one wants to use regularly via Pmount.

But I do like the Pulseaudio feature and the Bluetooth manager works well so far. These two features make Puppy a bit more friendly wrt audio control which has been lacking IF you start to compare it with the common Linux distros vying for one's attention.

@ Feek: run firefox-esr portable as spot

This is pre-first cup of coffee. So I may be confused. But:

In the firefoxESR-portable64 folder there's a bash script named LAUNCH.

In it you'll find 2 lines which read:

LD_LIBRARY_PATH=$HERE/:$HERE/extralibs${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} "$HERE/firefox64/firefox" "$@" -profile "$HERE/profile"

Above them below the line which reads
mkdir "$HERE/profile" 2> /dev/null

add the following lines:

chown -R spot:spot "$HERE/firefox64"
chown -R spot:spot "$HERE/extralibs"
chown -R spot:spot "$HERE/profile/spot"

Then edit the two lines to read:

LD_LIBRARY_PATH=$HERE/:$HERE/extralibs${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} run-as-spot "$HERE/firefox64/firefox" "$@" -profile "$HERE/profile"

blue for emphasis only.

Don't forget to configure your settings for Downloads to use a folder also chowned spot.

@ MikeWalsh: Have I got that right?

Request for @rockedge - @radky to evaluate this ability for this PUP.

It adds the simple ability for all smb machines/devices/units to be discoverable by their hostname.

@Sofiya was extremely helpful...it is here

I assume this could be built via WoofCE when the next F96CE update is produced

It looks like F96 is missing another important fix in woof-CE, from December: https://github.com/puppylinux-woof-CE/w ... 24555ddc53.

This change adds a dummy apulse that doesn't do anything, in woof-CE builds that use PulseAudio or PipeWire. This makes old packages built for Fossapup64 (and older), which expect ALSA and try to use apulse as a workaround, work out of the box.

@dimkr That does make sense, I've experimented with a dummy apulse but never implemented it. Good idea to do that now.

rockedge wrote: ↑Thu Feb 23, 2023 2:47 pm

@dimkr That does make sense, I've experimented with a dummy apulse but never implemented it. Good idea to do that now.

It's a good idea and even works. I'm no longer getting complaints about browsers that don't start or don't have working audio since December. People still use browser packages floating around the forums, which run browser x using apulse x.

dimkr wrote: ↑Thu Feb 23, 2023 2:41 pm

It looks like F96 is missing another important fix in woof-CE, from December: https://github.com/puppylinux-woof-CE/w ... 24555ddc53.

This change adds a dummy apulse that doesn't do anything, in woof-CE builds that use PulseAudio or PipeWire. This makes old packages built for Fossapup64 (and older), which expect ALSA and try to use apulse as a workaround, work out of the box.

Hm. I see. In-ter-esting....

Useful info, Dima. I may have to try this out at some point.

Cheers.

Mike.

RETRACTION: My REQUEST above has issues and is not ready for prime time.

The following does NOT address ALL units on the LAN, but for those that are SMB servers, this terminal command will list the NAMES of those SAMBA/Windows/MAC/ChromeOS/etc that are sharing folders in your home network:

# findsmb

To access those listed server units, you can

1. copy-add the IP address-hostname combination to your /etc/hosts file (discard the pc1-3 entries while you're there).

2. after-which you can immediately access those resources, by their hostnames, in programs on your PC; for example to access a samba resource from another LAN PC your command might look like this

   Code: Select all

   # mount //some-hostname/resource-name /mnt/mountpoint

I agree that a utility to allow the system to access LAN units by name is one that has been called for, in the Linux world, for decades. ... with varied approaches.

The best solution is a router solution, but, excepting for a few, most consumer routers dont provide that in its DHCP features

exFAT issue in this modern PUP.

dimkr wrote: ↑Thu Feb 23, 2023 2:41 pm

It looks like F96 is missing another important fix in woof-CE, from December: https://github.com/puppylinux-woof-CE/w ... 24555ddc53.

This change adds a dummy apulse that doesn't do anything, in woof-CE builds that use PulseAudio or PipeWire. This makes old packages built for Fossapup64 (and older), which expect ALSA and try to use apulse as a workaround, work out of the box.

Is this something we can try with some manual creation of the required files?

@mow9902 Yes it is. Just create the script /usr/bin/apulse manually. That should work just as well.

rockedge wrote: ↑Fri Feb 24, 2023 2:02 am

@mow9902 Yes it is. Just create the script /usr/bin/apulse manually. That should work just as well.

I created an empty file called apulse ie. /usr/bin/apulse and set the properties for write and exec to owner, group, world
Not sure if this is what you meant....but anyway, did not make a difference in my case.
Did I misunderstand?

@mow9902 This bit of code must go in the the /usr/bin/apulse file. I should have specified better! my fault.

#!/bin/ash
exec "$@"

UPDATE: fixed an error in syntax

@rockedge @mow9902 Without the \

For .mkv video files changing the open with from:

defaultvideoplayer "s@"

to:

defaultmediaplayer "s@"

starts the player when clicking on the .mkv file.

Jinx wrote: ↑Sat Feb 25, 2023 4:50 am

For .mkv video files changing the open with from:

defaultvideoplayer "s@"

to:

defaultmediaplayer "s@"

starts the player when clicking on the .mkv file.

Fixed, thanks @Jinx

Thanks @Jinx, pushed https://github.com/puppylinux-woof-CE/woof-CE/pull/3945 into woof-CE.

rockedge wrote: ↑Sun Feb 19, 2023 3:52 pm

@Overdrive5
looks like the ip6tables support is lacking something. The firewall looks secure for ipv4 but can't resolve ipv6.

Maybe a kernel swap/upgrade/downgrade might fix this..... or reexamine the support installed for ip6tables to work. We'll have to go in and look under the hood.

Checking into this further, I modprobed ipv6 and that shrunk the error message quite a bit.
But there is still a few errors:

# ./rc.firewall restart
Loading kernel modules ...
net.ipv4.tcp_syncookies = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.all.secure_redirects = 1
net.ipv4.conf.all.log_martians = 1
Flushing Tables ...
ip6tables v1.8.4 (legacy): can't initialize ip6tables table `nat': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.4 (legacy): can't initialize ip6tables table `nat': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.4 (legacy): can't initialize ip6tables table `nat': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.4 (legacy): can't initialize ip6tables table `nat': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.4 (legacy): can't initialize ip6tables table `nat': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
Create and populate custom rule chains ...
Process INPUT chain ...
Process FORWARD chain ...
Process OUTPUT chain ...
Load rules for nat table ...
Load rules for mangle table ...
#

@Overdrive5 It's been fixed and will be in the next release of F96-CE

Overdrive5 wrote: ↑Sat Feb 25, 2023 2:58 pm

rockedge wrote: ↑Sun Feb 19, 2023 3:52 pm

@Overdrive5
looks like the ip6tables support is lacking something. The firewall looks secure for ipv4 but can't resolve ipv6.

Maybe a kernel swap/upgrade/downgrade might fix this..... or reexamine the support installed for ip6tables to work. We'll have to go in and look under the hood.

Checking into this further, I modprobed ipv6 and that shrunk the error message quite a bit.
But there is still a few errors:

...

@Overdrive5

The kernel issue with ipv6 is fixed in the upcoming F96-CE_2.

radky wrote:

The kernel issue with ipv6 is fixed in the upcoming F96-CE_2.

OK, Cool.

Still don't know if I actually need ipv6 or not.

But the error messages gave me some concern.

I found a issue with FP96 /usr/sbin/firewall_ng and tweaked the script for a possible fix.

Should I bring that up in this forum? Or somewhere else?