Holly Bostick wrote: > > Sorry, I don't use NTFS, and I only have one user (me)-- and I don't use > /mnt/cdrom or /mnt/cdrw (or /mnt/ anything other than the self-created > /mnt/iso for mounting loopback images)-- my DVD is mounted to > /media/(cdrecorder) by udev (afaik it's udev that does it).
I take it that you also have hald or ivman sorting out your mounts automatically for you? > I take it you don't use udev? Or are you just under the impression that > you have to have /mnt/something (I had this problem for the first bit > after I switched)? In general use, /mnt./blah is kinda deprecated. I am using udev but never bothered with automounting (yet). > However, I do know that enabling writing to NTFS partitions in the > kernel is not recommended, unless you meet very specific criteria (as > the kernel driver can only overwrite a file of the exact same size to > such a partition, making editing pre-existing files pretty much > impossible; no idea about creating a new file). As I understand it the same applies with editing unless the changes result in exactly the same size file. Right, what are the chances of that?! The only way to rw NTFS partitions safely is with Captive, which uses the ntfs.sys driver with WINE. > UID/GID is (kinda) necessary for VFAT partitions, only to deal with the > possible ownership issues; if you specify the UID/GID of the expected > owner, that UID/GID can/will have write privileges to the partition > (automatically if UID, when specified if GID), which is useful for > shared partitions across multiple distros or OSes and sometimes for > multiple users on the same OS. I just tried it out and as long as I do not specify ro vfat partitions get mounted with rw rights, even if I do not add the uid. From memory I think that I had to add the uid in the distant past when devfs/udev was playing up with a particular kernel version - but can't remember for sure. >> >> The specific one is that I tried to delete a folder from a >> re-writable CD: a)while I was browsing it in konqueror and b)using >> k3b, but it couldn't do it. I'll try again when I get home to see if >> it behaves as expected after I ensure that it has not been mounted. > Um, hello, this is not WindowsXP. We do not packet-write (that means > treat a CD as if it was a floppy and write to it directly from the file > manager). You can (kinda) do this, if your kernel is set up to enable > packet-writing, but honestly that functionality is quite unstable and I > wouldn't use it even if I did like packet writing (which I do not and > never have in the some 6 to 7 years since it was introduced). Sorry, I guess it shows that the only (limited) CD writing experience I had was in M$Windoze at work (with Nero & Roxio)? > Basically what would need to happen in the real (Linux) world, without > packet writing, is that a CD burning program would have to create a temp > ISO of the files on the CDRW (which afaik it would have to be) without > the folder that you intended to delete, erase the current contents of > the CDRW and then rewrite the CDRW with the new ISO (which would > essentially delete the folder). But I could be wrong, as I don't use -RW > media anymore (and this is one of the reasons why). I can't remember if I have enabled packer writing in that machine. When I get access to it I'll check it out. Thanks for your help! :-) -- Regards, Mick -- gentoo-user@gentoo.org mailing list
