Mounting with ntfs-3g

Greg Helton gt at
Thu May 24 05:56:15 UTC 2007

The reasoning behind using UUID vs traditional device names is that an
UUID will not change for a partition (unless you reformat it) whereas a
device name can change if the drivers get loaded in different orders,
drives get moved around, etc :)

NoOp wrote:
> On 05/22/2007 08:56 AM, NoOp wrote:
>> On 05/22/2007 07:26 AM, Derek Broughton wrote:
>>> I have an ntfs partition  I want to mount at boot time.
>>> However, ntfs-3g, being a userspace filesystem, isn't available at boot time
>>> and I get an error message when from the script.
>>> Is this simply a matter of getting some modules into the initrd image, or is
>>> there another way to get a userspace filesystem to mount automatically
>>> (short of just creating another script at init level 2).
>> Edgy:
>> <>
>> Feisty:
>> <>
>> [note: ntfs-3g is now in the feisty univers repos]
> Sorry, forgot to add the relevent bits from my fstab; note that his is
> from the edgy to feisty upgrade so it shows both the edgy config (hda1)
> and the new feisty config (UUID):
> # Was: /dev/hda1     /media/windows     ntfs-3g
> auto,group=ntfs,umask=007       0       0
> # /dev/hda1 -- converted during upgrade to edgy
> UUID=EE68xyz /media/windows ntfs-3g defaults,local=en_US.utf8 0 0
> # /dev/<your partition> /media/<mount point> ntfs-3g
> defaults,locale=en_US.utf8 0 0
> I've yet to figure out the reasoning for the UUID vs hda1...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the ubuntu-users mailing list