• 70 Posts
  • 469 Comments
Joined 1 year ago
cake
Cake day: February 8th, 2025

help-circle
  • As another person had suggested, test with a live image first before installing it to an SSD/HDD, however Linux is very well maintained by the community and even if there aren’t native drivers from your hardwares manufacturer, for example Corsair Keyboard Drivers, there usually is Open Sourced alternatives for these things like CKB-Next.

    I say this to everyone, once you get a grasp on BASH (Bourne Again Shell) and package managers & repositories (edit: and the filesystem structure) you’ll essentially be able to use any Linux distro, it just comes down to the nitty gritty of things.



  • Jellyfin isn’t the most secure piece of software out there, I would avoid giving it permissions it doesn’t need.


    Step 1) Check /dev/dri for the GPU

    user@debian:~/compose$ ls /dev/dri
    total 0
    drwxr-xr-x  3 root root        120 Jan 25 11:50 .
    drwxr-xr-x 18 root root       3360 Feb 11 03:03 ..
    drwxr-xr-x  2 root root        100 Jan 25 11:50 by-path
    crw-rw----  1 root video  226,   0 Jan 25 11:50 card0
    crw-rw----  1 root video  226,   1 Jan 25 16:39 card1
    crw-rw----  1 root render 226, 128 Jan 25 11:50 renderD128
    

    Documentation indicates renderDXXX typically refers to Intel GPU’s

    Make sure at least one renderD* device exists in /dev/dri. Otherwise upgrade your kernel or enable the iGPU in the BIOS.

    1. Edit your docker-compose.yaml and add this In your Jellyfin block
    devices:
     - /dev/dri/renderD128:/dev/dri/renderD128
    
    1. Start your container and enter it to verify the device is recognized.

    sudo docker compose up -d; sudo docker exec -it jellyfin bash

    Once inside ls /dev/dri to confirm the GPU is recognized inside the container, once you confirm it then you can exit the container.

    user@debian:~/compose$ sudo docker exec -it jellyfin bash
    I have no name!@jellyfin:/$ ls /dev/dri
    renderD128
    I have no name!@jellyfin:/$ exit
    exit
    user@debian:~/compose$
    
    1. On the Jellyfin dashboard go to the hardware acceleration page and follow the notes left by Jellyfin devs.




  • I can’t recall the length but anything before a limit of automatically considered a handgun by the RCMP.

    That is incorrect. Non-restricted, semi-auto, centre fire rifle and shotgun barrels must be greater than 18.5” and the overall length cannot be less than 26” otherwise the firearm will be classified as restricted which you have to register it under your possession and acquisition license.

    Edit - clarification on the above:

    it is possible to legally own a non-restricted shotgun with a barrel shorter than 18.5”, it cannot be semi-automatic and it must be a factory barrel, meaning no angling grinding or sawing barrels down.

    Non-restricted - What’s included in this class

    This class includes any firearm that is neither restricted nor prohibited. Most common rifles and shotguns are non-restricted, but there are exceptions.

    Restricted - What’s included in this class

    • Handguns that are not prohibited firearms
    • Firearms that:
    1. are not prohibited firearms
    1. have a barrel less than 470 mm in length
    1. are capable of discharging centre-fire ammunition in a semi-automatic manner
    • Firearms designed or adapted to be fired when reduced to a length of less than 660 mm by folding, telescoping or otherwise
    • Firearms of any other kind prescribed to be restricted firearms in the Regulations

    Prohibited - What’s included in this class

    • Handguns with barrels equal to or less than 105 mm in length
    • Handguns designed or adapted to discharge a 25 or 32 calibre cartridge
    1. This does not include handguns for use in international sporting competitions governed by the rules of the International Shooting Union and where the handgun is prescribed to be restricted
    • Firearms adapted from a rifle or shotgun, whether by sawing, cutting or any other alteration, and that, as so adapted are:
    1. less than 660 mm in length
    1. 660 mm or greater in length and has a barrel less than 457 mm in length
    • Automatic firearms, whether or not altered to discharge only one projectile with one pressure of the trigger
    • A firearm that is not a handgun and that
    1. discharges centre-fire ammunition in a semi-automatic manner;
    1. was originally designed with a detachable cartridge magazine with a capacity of six cartridges or more; and
    1. is designed and manufactured on or after December 15, 2023
    • Firearms prescribed to be prohibited firearms in the Regulations (including firearms prescribed by make and model; any firearm with a bore diameter of 20 mm or greater; and any firearm capable of discharging a projectile with a muzzle energy greater than 10,000 joules).

    It’s also worth mentioning while the Firearms Reference Table is not technically bound by law, the RCMP and Public Safety essentially treat it like it is, so no matter how much you (illegally) modify a rifle to look like a pistol it’s still was initially designed, manufactured and registered as a rifle.


    I’m still suspicious of the PAL plus removed weapons. Is it possible they bought a gun under the table after their weapons were confiscated?

    It’s important to note that non-restricted firearms are not registered to PAL licenses like how restricted firearms are (except in Quebec), the only thing noted is the transfer request between seller and buyer, currently the RCMP is claiming that neither the shooter nor mother had these firearms registered to them which can indicate these are non-restricted guns.










  • Setting up Element Call on my instance was difficult on its own, I understand why Synapse doesn’t come with it out of the box, essentially you spin up Matrix’s JWT service for authenticating clients and it if approved forwards the connection to the Livekit ports which must be opened on your firewall (ie port forwarded), otherwise people will not be able to connect to calls.

    Big PITA and in my experience, on my home network, can conflict with games with VOIP chats so don’t follow the default 50000:55000 port range Livekit recommends or you’ll run into issues like I did, each person consumes 2 ports so adjust the range to your need.


    Edit: I don’t suggest running Element Call standalone, it has issues of its own, once you get Livekit and JWT running and follow This guide you should have your element call support in Synapse now, pro-tip for those running synapse behind docker and get confused on the whole ./well-known part of the documentation you can edit your ./well-known in your homeserver.yaml file like such:

    serve_server_wellknown: true
    
    extra_well_known_client_content:
      optional: client
      "org.matrix.msc4143.rtc_foci": [
          {
              "type": "livekit",
              "livekit_service_url": "https://livekit-jwt.your.domain/"
          }
      ]
    







  • That you only used a noisemaker. This isn’t complicated.

    It’s not complicated to grasp the idea of self defence either.

    I’ll refer you to the time when you claimed that without your gun you would have been in trouble, when in fact you admitted you only used it as a noisemaker.

    What difference does it make? We used them as noise makers opposed to firing directly at bears?

    I never said them being noisemakers were effective either, I said we had left the area quickly afterwards avoiding the conflict all-together, ultimately the bears were approaching our campsite and if we had been asleep and they were outside our tents with no firearms we’d be cooked.