PINE64

Full Version: Pine64 Linux fixup script
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
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-pine6...rm-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, 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-pine6...rm-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.

I've wondered for a while now why some people favor this syntax over the simple, old-style pipe, e.g., 


Code:
curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_fix_whatever.sh | bash
Functionally, they're the same, and connecting processes with a pipe "|" doesn't make the shell mess with named pipes; it also isn't whitespace sensitive, while <(...) is, leading to possible error and confusion.
(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 Smile - After all these scripts are for users who do not care what actually is done.
(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 Smile - After all these scripts are for users who do not care what actually is done.

I didn't think about the problems of finding | on some keyboards.  My ASCII-centric bias is showing through, I'm afraid.  I wonder how people write bash scripts if they don't have a $ key.  Maybe the Euro symbol works as a substitute Big Grin

I'm guessing the articles about piping curl into a shell you mention are of the "don't run random shell scripts off the internet" variety.  Not bad advice, actually, although this (and wget) shows up all over various official installation guides.  Here's one for installing Docker from docs.docker.com: curl -fsSL https://get.docker.com/ | sh