Dear KDE developers, this issue is not caused by KDE itself, but I feel the KDE team should make its own decision if this is a but at all:
Preliminaries: If you create files in a freshly created directory, most filesystems won't remember the order those files had been created in. In 99.9% of all cases this might be sensible, because each fs has its own underlying system, and usually files are ordered by several well defined outer constraints (like date, name etc.). Problem Case: Rip a CD to ext4, and apparently "ls -f" will result in an arbitrary order, where old school FAT file systems (especially mounted on proprietary OS) would follow "first in, first out". If you later just copy your album to a mp3 player, using dolphin or just cp, files are written in that arbitrary order onto the vfat system of your player. And there are some players (e.g. iRiver E150) that would not sort play order by themselves, but play files one by one as written to the folder. So the assertion of mp3 players' firmware developers seem to comply to (formerly unresolved?) premises of microsoft fat developers, but collide with most native linux file systems. Solution. If this is a design bug (missing assertion for file systems in general), it should be addressed to the kernel team. Otherwise, it should be discussed, if dolphin or crusader could offer a workaround (feature request: option to copy files in the same order as files are displayed in source directory). Any comments on this? Thanks, regards Ralf
signature.asc
Description: OpenPGP digital signature
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
