Father of two, husband, gamer, lover of free software, and willing teacher.

Microblog: https://social.ozoned.net/@ozoned Livestream: https://stream.ozoned.net Videos: https://video.thepolarbear.co.uk/@ozoned Matrix: https://matrix.to/#/#the-ozoned:matrix.org KoFi: https://ko-fi.com/ozoned

  • 14 Posts
  • 17 Comments
Joined 6 months ago
cake
Cake day: January 4th, 2024

help-circle

  • The next big thing is moving all of your servers to the cloud!

    The next big thing is moving all of your software to containers!

    The next big thing is moving all of your money to crypto!

    The next big thing is moving everything to AI!

    Yes we’re in ANOTHER tech gold rush. Not saying these things don’t have their place, but the tech industry is infatuated with the next big thing and burning through money and the ones that get burnt are the average working folks. Ask me how I know, currently in year two of a hiring and pay freeze as AWS isn’t as cheap as predicted… Who could have fucking guessed? They mean besides everyone but the CTO that’s fucking who!



  • I’ve been on Proton for years and I’ve had a Visionary account for years. Proton’s price doesn’t really go up, but the quality and features does immensely. They give me extra storage every year. I get more VPNs, more password managers, more and more and more. IMO they have a track that shows they care about privacy and want to make things better.




























  • You’ve made a directory path literally called

    /media/lucky/New Volume

    ?

    That REALLY doesn’t seem like a good idea considering that *'s are wildcards for anything, and Linux isn’t really fond of spaces.

    The error basically tells you that you have an error on line 18, which I’m assuming is this line you’re stating and that it’s ignored that line so that it can still go on and mount other things.

    Most likely you’d want something like:

    # mkdir /media/lucky/NewVol

    and then your fstab would be:

    UUID=D4C0A66EC0A65710 /media/lucky/NewVol ntfs rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000 0 0

    Also do you have a lib or something for linux to handle NTFS file system types? I haven’t run Windows in 17 years now, so I don’t have a clue if Linux can natively handle NTFS.

    You can also run:

    # lsblk

    or

    # blkid

    to get the storage information and verify the storage UUID is correct.