| |||||||||||||
On the need for a new removable device filesystemOn the need for a new removable device filesystemPosted Aug 23, 2012 4:04 UTC (Thu) by tnoo (subscriber, #20427)Parent article: On the need for a new removable device filesystem
> Well, there would be a few small problems. There are still some pesky
> users out there with non-Linux systems that might want to access the > filesystems on their devices.
Call the extra file system layer to install a "driver". Users are trained enough by their experience to have to install a driver for almost any external tool (sometimes from micro-CDs, or random manufacturer websites) that this will be their normal user experience.
(Log in to post comments)
On the need for a new removable device filesystem Posted Aug 23, 2012 8:58 UTC (Thu) by thoeme (subscriber, #2871) [Link]
Call the extra file system layer to install a "driver". Users are trained enough by their
experience to have to install a driver for almost any external tool
Can this be done on a (windows) system by a user *without* administrative priviledges?
On the need for a new removable device filesystem Posted Aug 23, 2012 9:37 UTC (Thu) by eru (subscriber, #2753) [Link] Can this be done on a (windows) system by a user *without* administrative priviledges?No, at least not in Windows Vista and later versions. Not a big problem for people managing their own computer, but would hamper users in corporations. What would work is if the drive would appear to formally just contain a VFAT or NTFS filesystem, with a single file containing the actual new filesystem filling almost all the space, plus a userspace archiver program for getting at the files on Windows. But clumsy, of course.
|
|||||||||||||