Bug 293420

Does yast2-storage trigger that package on fuse partions? Michael said libzypp does not yet support file system packages due to a bug, but looks worth a check

No, there is feature #301966 which tells package manager which filesystem depend
packages to install. If this is not supported due to a bug, I would suggest 
fixing that bug instead of added bloating code that will become obsolete soon
anyway.

I think I was wrong last time. The ntfsprogs-fuse package is not needed at all because it contains an obsolate version of the ntfsprogs driver. This driver does not have full write support for NTFS filesystems.

The real ntfs-3g package is missing from the alpha6 DVD at all. It is located at http://software.opensuse.org/download/filesystems/openSUSE_Factory/. So please include this RPM on the DVD and in the default installation too.

And I think it is time to update the ntfs-3g RPM package to the latest stable release: 1.710

*** Bug 293421 has been marked as a duplicate of this bug. ***

http://software.opensuse.org/download/filesystems/openSUSE_Factory/ 
does not have my ntfs-3g package, it has the package from the openSUSE
buildservice, which is provided by a community member and he hasn't updated
hist RPM. I think we should contact him and remove his rpm from the
buildservice because it is obsolete.

You can get my lastest ntfs-3g rpm currently from:
http://ftp.opensuse.org/pub/opensuse/distribution/SL-OSS-factory/inst-source/suse/i586/ntfs-3g-1.710-3.i586.rpm

I think it's best to reassign this to the CD/DVD creation team to include ntfs-3g
on the DVD and CDs, and once that is done to Michael who said libzypp
does not yet support file system packages due to a bug to get this bug fixed.

OTOH, as currently sold external USB harddisks are of a size (larger than 32GB) at which the format tool of Windows does not allow the creation of FAT32
filesystems, those drives only have NTFS filesystem and so to get plug-and-play
mounting working with out-of-the-box-formatted modern USB harddisks by default,
we should install ntfs-3g anyways independent of if the system has NTFS filesystems already accessible.

Reassigning to Rudi, he'll know which route this should take.

PS, a short personal note of my use of NTFS-3g: To access all my external USB disks, I've been using ext2 drivers for Windows so far, but they are not maintained anymore and have bugs which cause some Windows XP installation to bluescreen and are corrupting the ext2 filesystems also, so I'm switching to ntfs-3g for all my external USB disks (which have a capacity of nearly 3TB currently...), using ntfs-3g as the only interoperability solution in that area which looks good, so I see no alternative to ntfs-3g for me.

package ntfs-3g should be on all media starting with alpha7

coolo: what about ntfsprogs-fuse ?
 - add to patterns
 - add to (which) media ?

ntfs-3g is on the media and is trigged by yast if there is a NTFS partition (possibly still broken due to libzypp). ntfsprogs-fuse is the old way afaik and doesn't need to be any media.

okay, closing then.

ntfs-3g package is still not included in the default package selection so it is not installed by default.

Bernhard described the situation well in comment #5. We need ntfs-3g even if the system does not have any ntfs partitions at the time of the installation because external usb harddisk are often formatted to ntfs.

So I reopen this bug and I suggest to install ntfs-3g anyways.

Still not there in Beta1 (using KDE-CD for x86). Adjusting version.

Setting severity to mayor, because this is a big regression to 10.2: The user can't read anymore NTFS volumes with a standard installation.

Coolo ?

(In reply to comment #5 from Bernhard Kaindl)
> PS, a short personal note of my use of NTFS-3g: To access all my external USB
> disks, I've been using ext2 drivers for Windows so far, but they are not
> maintained anymore and have bugs which cause some Windows XP installation to
> bluescreen and are corrupting the ext2 filesystems also, so I'm switching to
> ntfs-3g for all my external USB disks (which have a capacity of nearly 3TB
> currently...), using ntfs-3g as the only interoperability solution in that area
> which looks good, so I see no alternative to ntfs-3g for me.

Personally, I create a large fat32 partion on those external disks using the tools on linux since they can create FAT32 filesystems larger than the tools on windows can do. Anyway I am looking forward to have the new ntfs-3g package being default selected in future SuSE dists.

*** Bug 297043 has been marked as a duplicate of this bug. ***

I just closed bug 297043 as duplicate of this bug. In it's initial comment,
the reporter provided a screenshot of "konqueror sysinfo:/" from Alpha 7,
at least that's what the bug is opened against.

It shows "ntfs-3g" as Filesystem label of disk/by-id/scsi-SATA_Maxtor_6Y0060L....

I think that the information source for this line in the sysinfo was an entry in /etc/fstab which YaST2 created during installation and because of sume bug (which I think we fixed meanwhile), ntfs-3g was not installed when YaST2 made that entry.

So I think the issue of not being able to mount NTFS partitions in the same customary way as it works in 10.2 should be fixed by really when yast2-storage requests installation of ntfs-3g when it adds an fstab entry for it.

On the other hand, we could reduce the impact of any remaining bug in the area of installing ntfs-3g thru yast2-storage by adding ntfs-3g to the KDE and GNOME package selections.

Adding ntfs-3g to the GNOME and KDE package selections would also be needed when we want to go forward with the approach of bug 293433 where we aim to change the fstype of NTFS partitions in HAL to ntfs-3g to allow HAL-assisted mounting of NTFS partitions in wead-write mode.

BTW: I tested the HAL approach with our latest HAL and it works with gnome-volume-manager as backend. If KDE's mediamanger kioslave does
the same, then e.g. automounting of external USB disk with NTFS partitions
should also be working in KDE. I'll write more on that into bug 293433.

293433 asks for a HAL change within the ntfs-3g package. And as long as installing ntfs-3g triggers actions on boot, I'm very much declined to install it.

And ntfs-3g is on all media now

Hi coolo, you closed this bug as fixed but only said:

> And ntfs-3g is on all media now

Whether ntfs-3g is on all media or not was was not the question why this bug
has been reopened by Péter Kerékfy in comment #9:

> ntfs-3g package is still not included in the default package selection so
> it is not installed by default.
>
> Bernhard described the situation well in comment #5. We need ntfs-3g even if
> the system does not have any ntfs partitions at the time of the installation
> because external usb harddisk are often formatted to ntfs.
> 
> So I reopen this bug and I suggest to install ntfs-3g anyways.

You also said:
> 293433 asks for a HAL change within the ntfs-3g package.

Meanwhile, after further testing and also finding a report which matches what we see, where the developer who answered made things clear, I found that it's better integrate these ntfs-3g storage policies directly into the hal package. I described this now it 293433#c12 .

You also said:
> And as long as installing ntfs-3g triggers actions on boot,
> I'm very much declined to install it.

It's fixed in the rebuild which was triggered Friday evening which has
the package branch-off from fuse into libfuse2, so now you can uninstall
fuse, and it's no longer pulled into the selections by ntfs-3g or compiz,
so now you can add it to the selection without adding to the code which
run while booting the system.

As described in comment #5:

> We need ntfs-3g even if
> the system does not have any ntfs partitions at the time of the installation
> because external usb harddisk are often formatted to ntfs.

So I don't understand why we need ntfs-3g also in the KDE and GNOME selections when it is installed anyway. Also when you have a system without X, ntfs-3g is usefull!

added to enhanced basis