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

  • 9 Posts
  • 15 Comments
Joined 10 months ago
cake
Cake day: January 4th, 2024

help-circle











  • ozoned@lemmy.worldtoLinux@lemmy.mlGNOME and AppIndicator/system tray
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    10 months ago

    Their design was more mobile type wherr you don’t minimize windows, you just switch between them or between spaces. I’ve used Gnome forever, including the rough times on Gnome 3.0, and I’ve always used a system tray as well. Never liked leaving clutter everywhere and imo it goes against the minimal design. But thankfully easily extendible.













  • 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.