• 2 Posts
  • 62 Comments
Joined 2 years ago
Cake day: June 20th, 2023
  • Sailing7@lemmy.mltoSysadmin@lemmy.world•Thinking of a career change
    9·
    2 months ago

    […] and have been using various Linux distros as my main os for almost 20 years.

    Matey. Get into any company that has linux junior positions. You already have more experiance in linux than 90% of the average (windows) Sysadmin.

    For realzies now. Most will look weird at you if you ask them to edit a file in the shell or using a server VM that runs without graphical interface.

    Get into a linux junior position and get started.

    Learn lots and lots. After a few years moneywise you might be back your old job as experienced chemist.

  • Sailing7@lemmy.mltoPiracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com•German tracker recommendationEnglish
    4·
    6 months ago

    Try

    • scenenzbs(dot)com
    • or
    • drunkenslug

    (First one is better.) To get .nzb files. Then use a Usenet Access Provider. Those save all files shared via usenet over a predefined time period. – though some archive different usenet publications than others. Simply differs by what servers they connect to afaik.

    Not entirely sure on the architectural work here but thats the best you’ll get from me in a minuite.

    Search for diffetent providers. Check the link for them. Maybe the available payment methods might be worth a look.

    Eweka supports paypal i think, but not sure on this one.

    For automation you will need an api access to the sites from the bulletpoints above – the free access gives very limited access via api. Which is why automation tools fail on a free account to automatically download new episodes .nzb files from them.

  • Sailing7@lemmy.mltohomelab@lemmy.ml•How are you sharing your GPU with multiple VMs?
    5·
    7 months ago

    Currently I simply dont.

    On Xenn you should be capable with the correct drivers to put a couple of virtual GPU Profiles on your VMs to use.

    On Hyper-V there is a command out there, but I don’t know if its a dedicated access or if you are capable of sharing it across multiple instances.

    On Proxmox though? Not sure but i think it was possible to forward it to a VM but thats all. Just dedicated acces afaik.

  • Sailing7@lemmy.mltohomelab@lemmy.ml•Looking for help with TrueNAS/AD/Linux setup.
    1·
    8 months ago

    Just for the sake of testing maybe try it with a oneliner:

    sudo mount -t cifs -o user=testuser,domain=testdomain //192.168.1.100/share /mnt

    Either way using the logs is the best way to check for discepancies. Also check in on the logs on the fileserver. Though idk what to advice to trace the logon stuff and trace whats making it fail.

    Just for the case that you dont know where to look in windows: eventviewer is the place to go. Which predifined filter though - simply google that.

    Wishing ya the best of luck mate!

  • Sailing7@lemmy.mltohomelab@lemmy.ml•Looking for help with TrueNAS/AD/Linux setup.
    1·
    8 months ago

    Well not so much the adress of the AD server.

    It should be the domain name of your domain that you have created.

    As in Joh.Doe@CompanyWork.internal

    The part behind the @ is the domain the user is registered to and even though the AD server might be named prod-ad-001 the text should be the domain you are trying to auth towards and the share you are accessing to should obvioisly have a connection the the AD to forward the credentials and ask if Auth is positive.

  • Sailing7@lemmy.mltohomelab@lemmy.ml•Looking for help with TrueNAS/AD/Linux setup.
    2·
    8 months ago

    In FSTAB:

    //192.168.188.52/media /home/shareuser/shared/ cifs vers=3.0,credentials=/home/shareuser/.smbcred,uid=1000,gid=1000,iocharset=utf8 0 0

    In .smbcred are the credentials. The content of the file:

    username=shareuser
password=shicjwvfiak                        domain=192.168.188.52

    Should work.

    Instead of the IP put the FQDN of your Share holding Server and make sure DNS is properly working.

  • Sailing7@lemmy.mltoSysadmin@lemmy.ml•How do you track the "mess" you are doing with your system?
    8·
    8 months ago

    Yes. Documentation. Documentation aaaalll the way.

    You are right. In two months you wont remember the shit you had to enable/disable to make things work.

    Doing things that arent a reocurring doing should be documented. Not crazy. A basic how to set up is enough.

    Common/reocurring errors/situations? Document 'em

    Got a semi permanent fix for problem, so that it will most likely never come up again, but possibly in 5 years? Document it fella.

    You’ll kiss your past self on the head and say thanks when you have an critical ticket in 5 years and remember nothing about the doing itself but that you wrote some documentation.

    It will save your ass and possibly you might come out as the hero of the day for having a solution right away for a super nieche problem.

    I’ve making a private hosted documentation for stuff, tricks and problems i learn at work.

    I’ve had plenty of situatuons where i remembered that i already encountered such a situation yeeeaars ago at my previois employer and that i’ve written somtehting down in my personal documentation. Bam and just by a few mins I’ve got either a really good or at least a shittysysadmin-style solution that works.

  • Sailing7@lemmy.mltohomelab@lemmy.ml•Should I get a firewall appliance?
    2·
    1 year ago

    Nah, probably not. All routers you can buy today will route and by default have their firewall active. Make sure, auto-updates are activated on your router.

    Check your server OS’ses and the Software running on them for updates on a regular basis - since they are partially made available to the public and are potential attack vectors.

    Though if you only port-forwarded a couple ports that dont include the RDP port or something wildly stupid, you should be safe.

    Follow some best practises as:

    • try to dont run your Gameserver Software as administrator but instead with a account with as low privileges as possible.
    • update your OS’ses, Softwares and Router/FW Appliance.

    Don’t let yourself fool by the guys telling ya to setup a full fledged firewall system when you obviously don’t even know basic networking. You would be overwhelmed by the configurationpossibilities.

    If you want to dangle your foot in some cold water - try em out and put some machines behind them to learn what behaves how. But dont make em your only protection against the public internet when you don’t know basic networking stuff.

    Happy Sailin’ matey!