… kei­ne Ahnung, wie groß das Vor­wis­sen beim The­ma Musik-Pro­gram­mie­rung ist
Ich stol­pe­re da öfter mal drü­ber und finds echt fas­zi­nie­rend + den­ke dass das live auch sehr #nois is/sein kann …

Hier etwas Inspiration:

  1. Stich­wort: Stru­del
  2. 3mins simp­ler Ein­stieg mit etwas Acid von „Switch Angel“
  3. und hier 25mins Stru­del mit Switch Angel

Ich ver­ste­he nat. so musi­ka­lisch wie­der nix – iwie fehlt mir da die musi­ka­li­sche Grund­spra­che, die Wor­te mit Musik (Töne, Melo­dien, Har­mo­nien, … – über­setzt #any­way

Viel Freu­de!

Was ich habe, will ich nicht ver­lie­ren, aber
wo ich bin, will ich nicht blei­ben, aber
die ich lie­be, will ich nicht ver­las­sen, aber
die ich ken­ne, will ich nicht mehr sehen aber
wo ich lebe, da will ich nicht ster­ben, aber
wo ich ster­be, da will ich nicht hin:
Blei­ben will ich, wo ich nie gewe­sen bin

aus: Tho­mas Brasch: Kar­go. Suhr­kamp Ver­lag, Frank­furt a.M. 1977.

#hppyb­dy + #dan­ke! @Thomas

Old but not bus­ted … – Die­ser Inhalt wur­de vor mehr als 3 Jah­ren publi­ziert. Die Kor­rekt­heit und Ver­füg­bar­keit von Links kön­nen lei­der nicht gewähr­leis­tet werden.

Sin­ce 2020 I use a Nord (EU ver­si­on) as my dai­ly dri­ver. I’ve never put Lineage (#wha­te­ver) on it, for reasons … But I’ve roo­ted it with Magisk, use Nova, a fire­wall (AFWall+), an ad-blo­cker (AdA­way), … – I’d say it’s very good cus­to­mi­sed. Upgrading Oxy­ge­nOS by the OTA and always patching the new ver­si­on after instal­la­ti­on by Magisk befo­re the reboot work­ed very well.

Until today …
I saw the noti­fi­ca­ti­on for a new OOS ver­si­on and touch­ed the but­ton, as alway. But this time my Nord straight went black and reboo­ted. After start­ing up neither AFWall+, nor AdA­way came up and the (still instal­led) Magisk app say­ed: #nope I’m not instal­led (any­mo­re).

Long sto­ry short: I lost root (by Magisk) on my Nord after upgrading (wit­hout patching the new instal­led image/version with Magisk befo­re the reboot) to Oxy­ge­nOS ver­si­on AC2003_11.F.13.

Here is my quick fix (after rese­ar­ching a lot about the who­le stuff, like every time ;-)) for you and also as my notebook.

The ori­gi­nal gui­de from XDA ‘How to root the One­Plus Nord with Magisk’ is very good and clean. #thanks! It also appli­es to this cur­rent situa­ti­on. You can skip the first part ‘Pre­pa­ring your One­Plus Nord’ becau­se all this steps are still done, from your pre-upgrade process.

Start­ing at the second part ‘Roo­ting your One­Plus Nord‘ you can skip some steps or parts of them. I think steps 2 (2.1 you can skip) and 3 are essen­ti­al. But plea­se read all the stuff and under­stand what you are doing.
For the link to the cur­rent boot image (EU ver­si­on) at 2.2 I found one at XDA: thanks a lot @TheSSJ for his fast rep­ly and work. #usa­ved­my­day! (And may­be this link will also end in the offi­ci­al list of repos of OOS builds …)

Fol­lo­wing the rest of the steps left me with a re-roo­ted Nord. 🙂

Old but not bus­ted … – Die­ser Inhalt wur­de vor mehr als 5 Jah­ren publi­ziert. Die Kor­rekt­heit und Ver­füg­bar­keit von Links kön­nen lei­der nicht gewähr­leis­tet werden.

Housten, I have a problem …

At work I have to use a VPN con­nec­tion. Curr­ent­ly the­re is set up a (so cal­led) SSH jump-host, that only accepts con­nec­tions from out­side the internal/VPN network.

Pro­blem with that: If the VPN con­nec­tion is up it’s not pos­si­ble to SSH to the jump-host any­mo­re, becau­se my local machi­ne (with the VPN con­nec­tion) has an inter­nal IP address and is not allo­wed to con­nect to the jump-host.

Solution

I crea­ted a udev rule for the VPN inter­face tun0.
That rules worke like this: Crea­te a new rou­te (to the jump-host) over my default net­work inter­face if the VPN con­nec­tion is up and dele­te that rule if tun0 wents down.

And here are this udev rules for you – and myself … 🙂

  1. Crea­te the file with/for both udev rules as root (you can free­ly name the file as you want): /etc/udev/rules.d/99-tun0.rules
  2. Insert the fol­lo­wing two lines/rules, replace 
    • 2.2.2.2 with the jump-host IP
    • 1.1.1.1 your local gate­way IP
    • default_interface with your local/default net­work inter­face (for me it’s wlp2s0; you can use ip addr to see all interfaces)
  3. Restart (as root) the udev ser­vice: systemctl status udev
KERNEL=="tun0", ACTION=="add", RUN+="/sbin/ip route add 2.2.2.2 via 1.1.1.1 dev default_interface"
KERNEL=="tun0", ACTION=="remove", RUN+="/sbin/ip route delete 2.2.2.2 via 1.1.1.1 dev default_interface"

Housten, the problem is fixed …

Thanks (for hints and inspi­ra­ti­on) to