Porteus

check this topic and see if there is any relavence : OpenBox and keyboard/font/codepage bug

updated to version 20200620
accommodated new naming convention eg. 2.83.0 , 2.90.0
stripped some python bits (hopefully not used)

Does pman works for you? I'm having troubles pinging to the router resulting in: seems to be ok here.. Also, does pkg2xzm manage new *.zst packages? yeah, no.. because arch's build of file doesn't handle -z(uncompress) option with zstd archives, which is kind of stupid since they've adopted zstd fo...

2020-05-23
base modules updated to latest packages..
notes:
added srt and vmaf: new ffmpeg deps

try: this will fetch the package from slackware and convert it to a module..

from: https://the.earth.li/~sgtatham/putty/0.73/htmldoc/AppendixA.html#faq-howto A.6.6 How do I copy and paste between PuTTY and other Windows applications? Copy and paste works similarly to the X Window System. You use the left mouse button to select text in the PuTTY window. The act of selection a...

http://dl.porteus.org/i586/Porteus-v4.0/ for 32 bit isos (or similar folder on one the mirrors mentioned)

looks to be tricky, but possible : https://askubuntu.com/questions/935657/how-to-install-ubuntu-on-miix-320 https://esc.sh/blog/linux-on-lenovo-miix-320/ nomodeset kernel parameter comes up a bit(goes on the APPEND line), probably try that first.. but since you're freezing at the boot screen, i'd b...

So just to be clear, cliexec=haveged~start and cliexec="haveged start" are the same and either format will work in the APPEND statement? no. cliexec=haveged~start is for the APPEND statement and haveged start is what you use in a terminal. basicly the cliexec= cheat does not take spaces(same with g...

Ed_P wrote: ↑

06 May 2020, 05:19

BTW in the cliexec=haveged~start command mentioned above is the ~start part to be taken literally? Usually parms are preceeded by a - or /.

for cliexec the ~ denotes a space.. so the real command is "haveged start" ..

somehow i don't think this is an entropy problem in this case, since the lag happens after the DE(kde in this case) loads .. might be worth trying noauto cheatcode to stop internal drives from mounting at boot time to eliminate (something going on with that) from the equation.. tend to think of balo...

But if i start system with copy2ram it dont save the last changes, or ? i can see where the confusion is: there's a boot entry "copy2ram" .. but copy2ram is also just a cheatcode you can add to the APPEND line of any boot entry.. eg. LABEL GRAPHICAL MENU LABEL Graphics mode KERNEL /boot/syslinux/vm...

you can use changes=EXIT: <pathORuuid> with ext format too.. for the best of both worlds(POSIX and no journalling) try ext2 : don't need a .dat container and less wear on the flash drive.. changes=EXIT: might make shutdown a bit slower.. another thing for general speedup is copy2ram cheatcode if you...

Is it what you need ? perfect :) .. so your booting device where porteus is frugally installed is sdd1 install 5.1.5-porteus not sure about this? the kernel version? anyway, your sdd1 install should look similar to this: $ tree -L 2 sdb1 sdb1 ├── EFI │   └── boot ├── USB_INSTALLATION.txt ├── boot │...

none of this is making any sense :D and saved in the /modules folder which is added to the APPEND line with the extramod= cheatcode. nope.. any modules in the <usb>/porteus/modules folder are loaded automatically, no extramod= cheatcode is needed. When you are booted to the USB drive the drive is sd...