Announcement

Collapse
No announcement yet.

KDE Dolphin Restoring Support For Seeing Samba Shares From Windows

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • KDE Dolphin Restoring Support For Seeing Samba Shares From Windows

    Phoronix: KDE Dolphin Restoring Support For Seeing Samba Shares From Windows

    KDE developers wrapped up February 2020 with many fixes and improvements throughout their desktop landscape...

    http://www.phoronix.com/scan.php?pag...rts-March-2020

  • #2
    That app review form looks cool!

    Comment


    • #3
      Is KDE Wayland now working with native NVIDIA drivers? GNOME supposed to, but it didn't work there either.

      Comment


      • #4
        Originally posted by Steffo View Post
        Is KDE Wayland now working with native NVIDIA drivers? GNOME supposed to, but it didn't work there either.
        Well, that is the BLOB downside, it may work with some versions and not others and some may even have bugs, so you have to wait until nVidia give enough of a fuck to actually battle test it or add it to its regular QA

        Comment


        • #5
          Originally posted by jrch2k8 View Post

          Well, that is the BLOB downside, it may work with some versions and not others and some may even have bugs, so you have to wait until nVidia give enough of a fuck to actually battle test it or add it to its regular QA
          And even then xwayland won't work with the blob - so most gaming is out of reach. And if gaming is not the goal, then nouveau would be the better idea anyways ^^

          Comment


          • #6
            What a fantastic week, first the screen rotation got fixed on Wayland and now Krunner is appearing on top of a top panel :-) Great work!!!
            Last edited by R41N3R; 03-01-2020, 03:51 PM.

            Comment


            • #7
              I thought WS-DISCOVERY wasn't "on" by default for Windows. Anyone? Also thought that Microsoft was saying it was deprecating that as well.

              I replaced my "neighborhood" with something nmap based.

              Comment


              • #8
                Originally posted by cjcox View Post
                I thought WS-DISCOVERY wasn't "on" by default for Windows. Anyone? Also thought that Microsoft was saying it was deprecating that as well.
                Seems to be the opposite, SMBv1 got deprecated in favour of WS-DISCOVERY

                https://docs.microsoft.com/en-us/win...ult-in-windows

                Comment


                • #9
                  Originally posted by mcloud View Post

                  Seems to be the opposite, SMBv1 got deprecated in favour of WS-DISCOVERY

                  https://docs.microsoft.com/en-us/win...ult-in-windows
                  No offense, but I'm going to stand by my original assessment of WS-DISCOVERY. Nothing in the link says "you should use this". In fact it pretty much says "i wouldn't use this if I were you". SMBv1 deprecation has been know for a long time, however, M$'s disdain for WS-DISCOVERY was more of a surprise to me. I say "use it" knowing that "you could lose it. (too)"

                  Microsoft's quote on WS-DISCOVERY:
                  We recommend that you map drives and printers instead of enabling this feature, which still requires searching and browsing for their devices. Mapped resources are easier to locate, require less training, and are safer to use. This is especially true if these resources are provided automatically through Group Policy. An administrator can configure printers for location by methods other than the legacy Computer Browser service by using IP addresses, Active Directory Domain Services (AD DS), Bonjour, mDNS, uPnP, and so on.

                  Comment


                  • #10
                    Originally posted by cjcox View Post
                    No offense, but I'm going to stand by my original assessment of WS-DISCOVERY. Nothing in the link says "you should use this". In fact it pretty much says "i wouldn't use this if I were you". SMBv1 deprecation has been know for a long time, however, M$'s disdain for WS-DISCOVERY was more of a surprise to me. I say "use it" knowing that "you could lose it. (too)"

                    Microsoft's quote on WS-DISCOVERY:
                    We recommend that you map drives and printers instead of enabling this feature, which still requires searching and browsing for their devices. Mapped resources are easier to locate, require less training, and are safer to use. This is especially true if these resources are provided automatically through Group Policy. An administrator can configure printers for location by methods other than the legacy Computer Browser service by using IP addresses, Active Directory Domain Services (AD DS), Bonjour, mDNS, uPnP, and so on.

                    I'm not seeing disdain, they are just saying this feature is slow as fuck even on a small network (192.168.X.0-255) and any administrator worthy of the name should map the devices directly or use a better way, especially in a domain environment.

                    Consumers that buy a printer or a NAS have a Windows application that does the "administrator" job for them by finding and connecting to the device.

                    It's not deprecated, but there are much better alternatives and they make no secret of it.

                    Comment

                    Working...
                    X