Puppy Linux Discussion Forum

Even with that the first command fails because /bin/sh is denied to spot. I'm honestly not certain what is wrong here as all the executable bits are set for the owner, group, and world...

Seems like a bug with the frontend that puppy uses to generate icons on the go for partitions.

Still a fail unfortunately...

I'm rather curious as to what happens if you attempt mounting one of these created device nodes. This will mount as read-only in the terminal.

mount -o ro /dev/device

Regarding accessing files off a frugal install (savefile) you'll need to inform the mount utility via terminal to use a loop device. This is only needed if your file manager cannot do this. This is how puppy is capable of reading and using a file.

mount -o loop path/to/filesystem/file mount/point

Can confirm updating again then rebooting doesn't solve the problem. Although its not credential issues.

VLC should have a log option, what do you see in there when attempting to read off it? (Generally sensitivity level to warning is good enough, but if you want debug you can set that too)

I already did this booting into RAM. The homepage displays fine, as well as nothing amiss in the logs given by cups. However navigating to any other function requiring execv of a .cgi file fails due to permissions.

I am preferably trying to run-as-spot for a given program, such as firefox or palemoon. But run-as-spot does not work either. /bin/ash: Permission denied
As well, reading the README.txt reveals I should be able to issue su spot; cd ~

Can you show us what's in dmesg? (If it nothing related doesn't show up you'll need to get it from /var/log/messages then).
Also are the card contacts clean enough? As well as the reader?
I'm fairly certain ATA devices are not SD cards. But I may be wrong.

I have now booted via pfix=ram and setting up via loginmanager still doesn't work. Permissions still being denied. I've tried chown spot:root and that fails too.

If at all possible reset to factory default. As well issue rfkill list all If it reports hard blocked as a yes, then its a BIOS issue/keyboard set the wifi card off.

You may need firmware to get it to work.
Which puppy are you using? As well, give the kernel version being used here. You can get that via dmesg | head. Also you may need to click the refresh button instead.

@Fletch
Could you provide a quick snippet of grub.cfg/menu.lst? Which ever one contains menu entries for puppy. Providing a directory listing of how its configured on the USB can also help. Also confirm that vmlinuz exists at the base folder of the USB.

We need you to write in English, or if needed look at the Board Index for the relevant language.
Firefox needs to be updated, along with openssl/ssl possibly.

Well it works on the same puppy that my sister uses. So I'm not certain what I'm doing wrong here.

The order suggested does not work unfortunately.

There is possibly an rc.bluetooth in system services under Startup Manager. That starts the bluetooth daemon. But I'm quite certain that does not stop it from being powered. Neither WI-FI cards.