(04-23-2016, 03:48 PM)longsleep Wrote: I am a friend of pragmatic solutions, so here is a very simple one to handle current and future fixes required on Pine64 without having to provide packaging.

So there is now a script which can be run on any Pine64 (Linux) any time, multiple times. The script will fix whatever needs fixing. Thus the script is called "pine64_fix_whatever.sh". The idea is that whenever some issue comes up, a solution can be added to this script, run it again and be good.

Fixes (in the order as they have been added):

- Pulseaudio stuttering by disable timer-based audio scheduling


The script is part of my platform-scripts at https://github.com/longsleep/build-pine64-image/tree/master/simpleimage/platform-scripts.

You can simply run it like this on all Linux images (as root):

Code:

bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_fix_whatever.sh)

And reboot afterwards.

(04-23-2016, 06:55 PM)patrickhwood Wrote: I've wondered for a while now why some people favor this syntax over the simple, old-style pipe, e.g., 

(04-24-2016, 01:34 AM)longsleep Wrote:

(04-23-2016, 06:55 PM)patrickhwood Wrote: I've wondered for a while now why some people favor this syntax over the simple, old-style pipe, e.g., 

I do not know reasons for other people but my reasons are simple - people cannot type the | easily on many international keyboards. Also there are tons of articles which say that you should not pipe curl into bash with the | example and as this is an end user forum i chose not to irritate - After all these scripts are for users who do not care what actually is done.