Porteus

I've installed those two packages. SpaceFM didn't pick it up when I plugged the phone. So I tried to do something manually: root@porteus:~# mkdir /mnt/A root@porteus:~# jmtpfs /mnt/A Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). At this stage I was asked for additional permissio...

Thanks, ncmprhnsbl . SpaceFM indeed has an interesting script in >devices>settings>protocol handlers>mtp with the following comment: "To mount mtp:// you must install jmtpfs, simple-mtpfs, mtpfs, or go-mtpfs, or add a custom protocol handler." Perhaps I should try to install one of the "jmtpfs, simp...

Can't connect my Samsung Galaxy A3 2017 to Porteus 4.0: no new disk in the SpaceFM, and a long error message on the smartphone saying Attention The connected device is unable to access data on this device ... and so on mentioning Android File Transfer for Mac OS X. There is a Android File Transfer f...

Thank you, jssouza : I was unsuccessful in trying to convert the packages to the modules, complaining that some files were missing. I don't think it's worth instigating in light of the upcoming Porteus 5 that will have it natively. I'm likely to stay on OpenBox even in Porteus 5, so I'd be needing a...

@jssouza, Thank you for these Qt packages that has enabled my work for all this time. I wonder whether you could easily upgrade it to the next version. The reason for me is that I'd like to upgrade some of my apps which begin to rely on the newer Qt, for example, the next version of qpdfview, `qpdfv...

I can't find the script setting "TERM=xterm-256color" on my system. And it seems to break wine related programs (complains: 'xterm-256color': unknown terminal type.) Setting it back to TERM=xterm seems to solve it. I say "back to" because on my previous USB with LXDE it is indeed TERM=xterm -- I've ...

neko, what exactly should I do?

neko , I successfully boot after a few restarts always. This problem only happens on the new Dell computers with /dev/nvme host system disk drives which do not claim the names /dev/sda. So, /dev/sda become partitions of my USB drive. That's unusual. I'm used to seeing my USB disk to be sdb etc. I t...

francois , bootloader? You mean `porteus.cfg`? The relevant entry looks like this, and I think I only added login=root to APPEND: LABEL GRAPHICAL MENU LABEL Graphics mode KERNEL /boot/syslinux/vmlinuz INITRD /boot/syslinux/initrd.xz APPEND changes=/porteus login=root When successfully booted, the o...

In my case it's just a thumb drive: I reboot the whole computer and it (the porteus partition) gets eventually recognized. I'm thinking of trying a different USB brand, not SanDisk.

Neither of those worked.

also didn't work, complaining that from= cheatcode is incorrect, press enter for the list of devices or something.

Reboot and pray is my only solution so far

Thanks @Ed I've added literally without double quotes: from=UUID:04defda4-a423-4e51-8485-8b65e657213e and the boot didn't go through complaining about the "from" cheatcode and no such device It's always /dev/sda2 for me, so I'm going to try adding simply from=/dev/sda2 Will report tomorrow. Although...

I increased the SLEEP to 15 in two places where previously it specified 6 in `finit`, which made it even worse: couldn't go past the 15 sec wait at all no matter how many restarts -- had to fall back to the original `initrd.xz`

mbos , yes, Leafpad would crash on me too sometimes. The problem is upstream, or the way they work with GTK2. The solution is as follows: switch to the OpenBox porteus -- it's very similar to LXDE anyway, even better. Its native file manager (and desktop manager?) is SpaceFM. Now, very important: g...