¡ɹǝpun uʍop ɯoɹɟ ʎɐppᴉפ

  • 7 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle


  • I find Joplin perfect for my needs. Markdown, embedding images, links etc. I sync to my selfhosted nextcloud.

    I like tags, I would like them to add a “directory tree” type of view to help sort “folders” (the thing they call “notebooks”) but only because I am more used to just filesystem type structured filing. But the notebooks and tagging idea works for me too.

    I strictly use it for notes/note keeping, in particular “HOWTO’s” and specific topic notes. So I dont even do a great deal of markdown in my notes, but I love the ability to add screen captures etc to them for clarity.

    And being on nextcloud, I can access those notes anywhere on any device, PC, Android, Raspberry Pi!! Joplin has an app for all of them



  • Kernel Level Anti-Cheat. If you don’t understand that, then you don’t know if Linux is good or bad for “gaming”.

    Basically everything you want to play on Linux, that is not supported by the anti-cheat kernel is screwed.

    “Steam offers all these game to play on Linux” - yes, but I played them all 20 years ago.

    Try playing something like Genshin Impact. You cannot, the anticheat is Windows only. (PS and consoles, it relies on anticheat mech’s from the HW). They don’t offer a Linux version - so you are screwed.

    Does it have EAC or Battleeye? You are shit out of luck.

    The Linux Desktop is ready for primetime, but not for gaming. You need a windows boot for gaming, unless you are playing Half-Life…


  • Its in several more kernels than that.

    That patch was backported into known (and probably more): v5.10.202, v5.15.140, v6.1.64

    ext4 data corruption in 6.1 stable tree (was Re: [PATCH 5.15 000/297] 5.15.140-rc1 review

    So I’ve got back to this and the failure is a subtle interaction between iomap code and ext4 code. In particular that fact that commit 936e114a245b6 (“iomap: update ki_pos a little later in iomap_dio_complete”) is not in stable causes that file position is not updated after direct IO write and thus we direct IO writes are ending in wrong locations effectively corrupting data. The subtle detail is that before this commit if ->end_io handler returns non-zero value (which the new ext4 ->end_io handler does), file pos doesn’t get updated, after this commit it doesn’t get updated only if the return value is < 0.

    The commit got merged in 6.5-rc1 so all stable kernels that have 91562895f803 (“ext4: properly sync file size update after O_SYNC direct IO”) before 6.5 are corrupting data - I’ve noticed at least 6.1 is still carrying the problematic commit. Greg, please take out the commit from all stable kernels before 6.5 as soon as possible, we’ll figure out proper backport once user data are not being corrupted anymore. Thanks!

    https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/


  • I know this is not useful for most use cases, but if you login to the desktop on the ‘remote Wayland’, locally first then RD will work as expected. So if you can change the behaviour of the remote desktop to stay unlocked (IE its in a secure place where others cannot just access the device), then and RD will work with Wayland.

    I use NoMachine (since I manage all sorts of devices, and its nice that there is a client and server for everything including phones/arm) and it works for me because many of the machines are actually VM’s and I can keep the desktops unlocked and logged in. NoMachines solution for Wayland - is to disable it and use X11 !!

    But I wish many of the RD developers would just embrace Wayland and add/rewrite code to support it (If it is in their scope, I don’t know) It might not be, since I am aware of Waypipe and Pipewire, but I’d assume that RD devs would still need to include support for that.







  • Thats not how it works.

    You have a LAN and hopefully you have a firewall that shields your LAN from WAN. Your fw is probably handing out DHCP lease IP (like 192.168.x.y)

    When you “bridge” your VM looks like an independant device on you LAN. Nothing at this point has allowed it to the public. Your dhcp can even give it an IP (but its probably better to set a static ip). In bridge mode, a "fake mac is spoofed alongside you nic’s real mac, and only for said VM)

    At that point the VM id accessible likr any other device on the LAN.

    if you then want to use vpn, just connect to your LAN however that works(vpn to computer or vpn to firewall/vpn server) and access.

    if you want to access from WAN without vpn, then you need to understand reverse proxying and youll need a full proper firewall\gateway device at the front of your network (like OPNsense).




  • Let me offer another thought, if you are literally hanging on to windows for this, you could set up a VM in linux for this task. This is how I manage win only apps like my security client (camera vms). You have a license for windows, make it more useful. (and no rebooting to swap!)

    Or, a little more controversial, choose another player instead of Apple ipod. Plenty alternates that just work with linux.

    I used to have an ipod 20 years ago, and there was a linux “itunes” application, but I doubt its still maintained, or apple has made it impossible for 3rd parties to manage an ipod.


  • I run iRedMail (a collection of dovecot, postfix etc, plus sogo and roundcube web clients and managed by a nice web frontend, all open source and runs on any linux.

    I’ve run for about 8 years, no dramas other than my isp technocally doesnt allow it. But they don’t block anything and occasionally they submit their ip ranges for customers to places like spamhaus, so i just script check every month to see if they added my ip back, then i just submit removal, it takes all of 30sec. (IP is semi static, probably changes once every 9 months or so, so not a drama to update dkim on my domain registrar.)








  • the biggest issue with N.switch is that it requires static outgoing ports.

    i have not used pf in years (opnsense here so should be same) but what you need to do is set hybrid outgoing NAT, designate a static IP to the switch, and then tell outgoing NAT for that IP to use static ports, outgoing.

    by default pf\opn randomises the outgoing NAT port and that messes up the Nswitch royally. (especially online like MK8deluxe)

    most of what is being posted about uPNP and N.switch is not correct. As long as your firewall rules allow the switch to get out (lock ports if you want to, but its a console, so … why?)

    Nintendo servers simply do not like you joining a game lobby on outgoing 34567, and then starting the game on 23456, and then turning a corner on lap 2 switching to outgoing port 18845.