public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Andi Kleen <andi@firstfloor.org>
Cc: jassi brar <jassi_singh_brar@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: An idea .... with code
Date: Thu, 28 Aug 2008 11:41:13 +0200	[thread overview]
Message-ID: <1219916473.9776.19.camel@localhost> (raw)
In-Reply-To: <20080827150221.GV26610@one.firstfloor.org>

On Wed, 2008-08-27 at 17:02 +0200, Andi Kleen wrote:
> On Wed, Aug 27, 2008 at 04:49:35PM +0200, Kasper Sandberg wrote:
> > On Wed, 2008-08-27 at 14:47 +0200, Andi Kleen wrote:
> > > >  As far as features are concerned, please suggest me what could be done with /dev/loop0 and not for /dev/vblk?
> > > 
> > > Serious question?  cryptoloop, offsets are the big ticket items,
> > > i'm sure there are more.
> > 
> > As far as cryptoloop goes, isnt that obsoleted anyway? 
> 
> It's like saying: FAT -- isn't that obsolete by now? 
> As long as there are crypto loop files around it's not obsolete.
I disagree, as i recall, i stopped using cryptoloop and went directly to
dm-crypt with compatibility for my already existing files?

> 
> > is there anyone
> > that doesent use dm-crypt by now?
> 
> Wrong question. You lose.
In the case that i am correct above, it would appear that i did not
loose, given that the newer stuff has backwards compatibility (which i
am fairly certain it does)

also do not forget that i did say its unlikely that loop be removed due
to its heavily "established" status.

> 
> -Andi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  parent reply	other threads:[~2008-08-28 10:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24  8:53 An idea .... with code jassi brar
2008-08-25 12:22 ` Jochen Voß
2008-08-25 20:53   ` Marcin Slusarz
2008-08-26  2:47 ` Bill Davidsen
2008-08-26  8:24 ` Andi Kleen
2008-08-26 10:44   ` Alexey Dobriyan
2008-08-26 11:08     ` Andi Kleen
2008-08-27  7:24   ` jassi brar
2008-08-27  7:47     ` Andi Kleen
2008-08-27  9:57       ` David Newall
2008-08-27 10:01         ` Andi Kleen
2008-08-27 12:38       ` jassi brar
2008-08-27 12:47         ` Andi Kleen
2008-08-27 14:49           ` Kasper Sandberg
2008-08-27 15:02             ` Andi Kleen
2008-08-28  1:24               ` jassi brar
2008-08-28  9:41               ` Kasper Sandberg [this message]
2008-08-30  2:57             ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2008-08-27  0:44 jassi brar
2008-08-27  2:27 jassi brar

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=1219916473.9776.19.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=andi@firstfloor.org \
    --cc=jassi_singh_brar@yahoo.com \
    --cc=linux-kernel@vger.kernel.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