| 1 |
Holly Bostick wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> Sorry, I don't use NTFS, and I only have one user (me)-- and I don't use |
| 5 |
> /mnt/cdrom or /mnt/cdrw (or /mnt/ anything other than the self-created |
| 6 |
> /mnt/iso for mounting loopback images)-- my DVD is mounted to |
| 7 |
> /media/(cdrecorder) by udev (afaik it's udev that does it). |
| 8 |
|
| 9 |
I take it that you also have hald or ivman sorting out your mounts |
| 10 |
automatically for you? |
| 11 |
|
| 12 |
> I take it you don't use udev? Or are you just under the impression that |
| 13 |
> you have to have /mnt/something (I had this problem for the first bit |
| 14 |
> after I switched)? In general use, /mnt./blah is kinda deprecated. |
| 15 |
|
| 16 |
I am using udev but never bothered with automounting (yet). |
| 17 |
|
| 18 |
> However, I do know that enabling writing to NTFS partitions in the |
| 19 |
> kernel is not recommended, unless you meet very specific criteria (as |
| 20 |
> the kernel driver can only overwrite a file of the exact same size to |
| 21 |
> such a partition, making editing pre-existing files pretty much |
| 22 |
> impossible; no idea about creating a new file). |
| 23 |
|
| 24 |
As I understand it the same applies with editing unless the changes result |
| 25 |
in exactly the same size file. Right, what are the chances of that?! The |
| 26 |
only way to rw NTFS partitions safely is with Captive, which uses the |
| 27 |
ntfs.sys driver with WINE. |
| 28 |
|
| 29 |
> UID/GID is (kinda) necessary for VFAT partitions, only to deal with the |
| 30 |
> possible ownership issues; if you specify the UID/GID of the expected |
| 31 |
> owner, that UID/GID can/will have write privileges to the partition |
| 32 |
> (automatically if UID, when specified if GID), which is useful for |
| 33 |
> shared partitions across multiple distros or OSes and sometimes for |
| 34 |
> multiple users on the same OS. |
| 35 |
|
| 36 |
I just tried it out and as long as I do not specify ro vfat partitions get |
| 37 |
mounted with rw rights, even if I do not add the uid. From memory I think |
| 38 |
that I had to add the uid in the distant past when devfs/udev was playing |
| 39 |
up with a particular kernel version - but can't remember for sure. |
| 40 |
|
| 41 |
>> |
| 42 |
>> The specific one is that I tried to delete a folder from a |
| 43 |
>> re-writable CD: a)while I was browsing it in konqueror and b)using |
| 44 |
>> k3b, but it couldn't do it. I'll try again when I get home to see if |
| 45 |
>> it behaves as expected after I ensure that it has not been mounted. |
| 46 |
|
| 47 |
> Um, hello, this is not WindowsXP. We do not packet-write (that means |
| 48 |
> treat a CD as if it was a floppy and write to it directly from the file |
| 49 |
> manager). You can (kinda) do this, if your kernel is set up to enable |
| 50 |
> packet-writing, but honestly that functionality is quite unstable and I |
| 51 |
> wouldn't use it even if I did like packet writing (which I do not and |
| 52 |
> never have in the some 6 to 7 years since it was introduced). |
| 53 |
|
| 54 |
Sorry, I guess it shows that the only (limited) CD writing experience I had |
| 55 |
was in M$Windoze at work (with Nero & Roxio)? |
| 56 |
|
| 57 |
> Basically what would need to happen in the real (Linux) world, without |
| 58 |
> packet writing, is that a CD burning program would have to create a temp |
| 59 |
> ISO of the files on the CDRW (which afaik it would have to be) without |
| 60 |
> the folder that you intended to delete, erase the current contents of |
| 61 |
> the CDRW and then rewrite the CDRW with the new ISO (which would |
| 62 |
> essentially delete the folder). But I could be wrong, as I don't use -RW |
| 63 |
> media anymore (and this is one of the reasons why). |
| 64 |
|
| 65 |
I can't remember if I have enabled packer writing in that machine. When I |
| 66 |
get access to it I'll check it out. Thanks for your help! :-) |
| 67 |
|
| 68 |
-- |
| 69 |
Regards, |
| 70 |
Mick |
| 71 |
|
| 72 |
-- |
| 73 |
gentoo-user@g.o mailing list |
Archives