public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT encfs] When encfs gets hungup
Date: Sun, 10 Jul 2011 19:38:34 +0100	[thread overview]
Message-ID: <20110710193834.519e2d1a@digimed.co.uk> (raw)
In-Reply-To: <1310218305.304512.6.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

On Sat, 09 Jul 2011 09:31:45 -0400, Albert Hopkins wrote:

> > I wasn't suggesting that. But when the main reason for sticking with
> > the
> > older option is that you have a working system with data in it, the
> > loss
> > of both of those is a good time to investigate the newer
> > alternative.  
> 
> I see.  I guess I don't consider one as "older".  They are rather
> alternatives to one another (like openssl and gnutls).

Well, encfs was around for a while before ecryptfs. Otherwise there'd have
been no reason for anyone to write a FUSE filesystem to do it.
> 
> Generally speaking I'm usually discouraged by "I currently have a
> problem A, so I'll switch to B".. the old adage "Now you have two
> problems." 

I wasn't suggesting it as a solution so much as an opportune time to try
the alternative. I too am against fixing things by throwing them away,
it's like reinstalling - it my get rid of the problem temporarily but you
still have no idea of what the problem was or what to do should it
reoccur.


-- 
Neil Bothwick

Barnum was wrong....it's more like every 30 seconds!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-07-10 19:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 16:55 [gentoo-user] [OT encfs] When encfs gets hungup Harry Putnam
2011-07-08 17:10 ` Paul Hartman
2011-07-08 18:35 ` Albert Hopkins
2011-07-08 21:50   ` Neil Bothwick
2011-07-08 23:40     ` Albert Hopkins
2011-07-09  7:39       ` Neil Bothwick
2011-07-09 10:22         ` Albert Hopkins
2011-07-09 11:22           ` Neil Bothwick
2011-07-09 13:31             ` Albert Hopkins
2011-07-10 18:38               ` Neil Bothwick [this message]
2011-07-10 22:26                 ` Peter Humphrey
2011-07-11  9:10                   ` Neil Bothwick
2011-07-11 15:18                     ` Peter Humphrey
2011-07-11 16:26                       ` Sebastian Beßler
2011-07-11 16:49                         ` Bill Longman
2011-07-11 22:43                         ` Peter Humphrey
2011-07-11 23:40                           ` Neil Bothwick
2011-07-12  1:58                             ` Michael Orlitzky
2011-07-12  2:27                           ` Volker Armin Hemmann
2011-07-12  9:57                             ` Alan McKinnon
2011-07-11 21:01                       ` Neil Bothwick
2011-07-11 23:09                         ` Peter Humphrey
2011-07-11 23:39                           ` Neil Bothwick
2011-07-12  0:04                           ` [gentoo-user] " walt
2011-07-09 17:56     ` Harry Putnam
2011-07-10 18:45       ` Neil Bothwick
2011-07-09 17:51   ` Harry Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110710193834.519e2d1a@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox