On Fri, 15 Dec 2006, Vaclav Barta wrote: > > Do you remember where you read this? > Sorry, no. Some kind of online discussion or howto about flash drives on > Linux > I read a few months ago... It said that since flash memory has a limited > number of writes, they should be mounted read-only by default and configured > not to update file access times.
It's true that the number of writes is limited, but one doesn't need to go overboard. Mounting read-write won't make any significant difference. > > > Under Windows, the stick does show as 2 drives (a big, 479 MB, originally > > > empty one and a small 1,44 MB drive with some PDF documentation and an > > > executable I still didn't have the occasion to run), but both drives are > > > normally readable and writeable. Under Linux, ``mount -t > > > vfat /dev/sdb1 /mnt/stick'' mounts the small storage. > > Maybe the information you want is in the PDF documentation. It's also > > possible that the executable (a Windows program, no doubt) will allow you > > to "unlock" the first LUN, so that all these difficulties would then go > Not really... :-( The documentation describes how the executable can be used > to lock the big drive (so that its access requires a password), which works > (under Windows) but isn't really what I'm interested in. The default has been > unlocked, which behaves transparently under Windows but is apparently causing > trouble for Linux. The executable does allow changing the size of the two > drives, so I made the always-accessible one as big as possible and now get > the following on Linux: ... Just like before, except for the relative sizes. > So, sdb looks big enough and sdb1 can be mounted, but just read-only. > Documentation mentions a "read-only switch" but the hardware doesn't have > any. :-( How do I remove (or ignore) the write protection? I don't know. Maybe you can't. It would be interesting to see how Windows manages to go about accessing the first LUN. You could try using a USB sniffer program (like USB Snoopy) to find out exactly what Windows does. It may be that the first LUN isn't accessible until the second LUN has been used. If that's true, then all you have to do is mount /dev/sdb1 and then "blockdev --rereadpt /dev/sda", after which /dev/sda1 should be available. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
