#USE NETDRIVE TO DOWNLOAD A GOOGLE DRIVE CODE#
#USE NETDRIVE TO DOWNLOAD A GOOGLE DRIVE WINDOWS#

We require file systems to support one of a few directory information classes that we use to enumerate directories link(2) fails by-design and stat.st_nlink for files is 1. So in the case of missing required info (and again we're just using Dockany as an illustrative example here) say: ' no hardlinks for you'. Hard links are not well supported on some FUSE filesystems anyway for example, the canonically popular sshfs. If WSL 'requires' the schmancy NumberOfAccessibleLinks (to track deleted links), punt on hard links altogether. It is fixable in Dockany for someone motivated, totally.īut this said, can we reasonably or realistically survive without (in this arbitrary example) NumberOfAccessibleLinks? If we fail to get FILE_STANDARD_LINK_INFORMATION, fall back to less esoteric FILE_STANDARD_INFORMATION, which you gotta know the filesystem implements, or they'd fall down on Windows. I didn't bother you with it at the time not your problem. Didn't work they don't implement FILE_STANDARD_LINK_INFORMATION.

For example I took a run once at getting Dockany mounted on WSL. I have been half-meaning to ask for some time (but didn't) whether it is possible/practical to loosen our definition of 'requires' for a few (probably common) pain points.

#USE NETDRIVE TO DOWNLOAD A GOOGLE DRIVE WINDOWS#

Windows has more information classes than the ones that WSL supports, but they don't provide the information WSL requires. Thanks for the details Sven your write-ups are always appreciated. To do that, I needĪccess to a machine from someone who as an account, since it's a paid Much only possible if I can get it under a debugger. Mystifies it, and if it's something we can work around, but that's pretty I would definitely not mind taking a look at GDrive to see what we do that Everything that works besides that is pretty much We've long since updated it to support the various flavors of FAT supportedīy Windows, CDFS, and SMB (with the main target being a Windows SMB server DrvFs was originally designed to access only NTFS. In this context, that also refers to the 9p server used to access Has more information classes than the ones that WSL supports, but theyĭon't provide the information WSL requires.ĭrvFs is the component of WSL that interacts with native Windows file For example, we require file systems to support one of a fewĭirectory information classes that we use to enumerate directories.

#USE NETDRIVE TO DOWNLOAD A GOOGLE DRIVE CODE#

This goes both for WSL 1 and WSLĢ, because while the mechanism of actually getting to the files is quiteĭifferent, the actual code that interacts with the file system is mostly WSL as a file system client is a bit more strict about how a file system To do that, I need access to a machine from someone who as an account, since it's a paid service so I don't have one. I would definitely not mind taking a look at GDrive to see what we do that mystifies it, and if it's something we can work around, but that's pretty much only possible if I can get it under a debugger. Everything that works besides that is pretty much just lucky, not officially supported. We've long since updated it to support the various flavors of FAT supported by Windows, CDFS, and SMB (with the main target being a Windows SMB server sharing an NTFS volume). In this context, that also refers to the 9p server used to access Windows files on WSL 2. Windows has more information classes than the ones that WSL supports, but they don't provide the information WSL requires.ĭrvFs is the component of WSL that interacts with native Windows file systems.

For example, we require file systems to support one of a few directory information classes that we use to enumerate directories. This goes both for WSL 1 and WSL 2, because while the mechanism of actually getting to the files is quite different, the actual code that interacts with the file system is mostly the same. WSL as a file system client is a bit more strict about how a file system needs to behave than Windows in general. Reply to this email directly, view it on GitHub You are receiving this because you were mentioned. This change, you might perhaps have to consider other cloud file sync If the driveīehaves, one can access the drive from WSL:Īnd I don't want to sound biased, but if GDrive isn't able/willing to make

I advise this reluctantly - I hate it too when vendors seem to pointįingers - but WSL just treats drives as. This issue is likely caused by GDrive misbehaving. On Fri, at 6:25 PM Rich Turner and - As per response above

Use netdrive to download a google drive