16 Feb
2012
16 Feb
'12
11:10 a.m.
On Thu, Feb 16, 2012 at 11:07, Caleb James DeLisle <calebdelisle(a)lavabit.com
wrote:
Hi,
I'd like to switch filesystem attachments to begin using the persistent
storage directory now instead of the work directory.
This means there's a new way of calculating where the attachments will be
stored so it might fail on upgrade.
I would like to not do any migration and just add to the release notes
because:
#1, it doesn't cause any permanent harm so long as nobody adds attachments
while it's in what is an obviously broken state.
#2 administrators who have FS attachments enabled are probably going to
know what's going on.
#3 migration code is scary, it requires lots of work and lots of review
and even if it works,
people might feel violated having files shuffled around on their system
without their permission.
WDYT?
+1 for this in 4.0M1
Putting this late in the 3.5 cycle risk to cause less attention to the
release notes, and more mistake. What is really bad, is that the permanent
directory is not defaulted to the work directory. So, without attention, it
will surely get broken in most cases.
On the other hand, I agree that moving file on the filesystem is the job of
the admin, and having this done almost silently is not good. If
attachements are large and the permanent directory is not setup correctly,
this could cause disk write or disk full issue and could be worse than the
above issues.
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO