On 5 August 2014 09:12, Minchan Kim wrote:
> On Tue, Aug 05, 2014 at 09:07:16AM +0200, Karel Zak wrote:
>> On Tue, Aug 05, 2014 at 11:00:24AM +0900, Minchan Kim wrote:
>> > On Wed, Jul 30, 2014 at 12:14:42AM +0100, Sami Kerola wrote:
>> > > The zram devices are not created by any sort of equipment
On Tue, Aug 05, 2014 at 09:07:16AM +0200, Karel Zak wrote:
> On Tue, Aug 05, 2014 at 11:00:24AM +0900, Minchan Kim wrote:
> > On Wed, Jul 30, 2014 at 12:14:42AM +0100, Sami Kerola wrote:
> > > The zram devices are not created by any sort of equipment appearing in a
> > > bus so an method of creatin
On Tue, Aug 05, 2014 at 11:00:24AM +0900, Minchan Kim wrote:
> On Wed, Jul 30, 2014 at 12:14:42AM +0100, Sami Kerola wrote:
> > The zram devices are not created by any sort of equipment appearing in a
> > bus so an method of creating new or removing existing devices will be
> > needed. When the zr
On Wed, Jul 30, 2014 at 12:14:42AM +0100, Sami Kerola wrote:
> Hello,
>
> Not so long ago Timofey has reached both util-linux[1] and kernel[2]
> contributors with intention to make zram device management too. I think
> the proposal is good, and there should be distribution independent tool
> like
Cc Jerome
Hello,
my quick thoughts on the topic. first, I'm not against, and we might have
something like this one day, but...
On (07/30/14 00:14), Sami Kerola wrote:
> Hello,
>
> Not so long ago Timofey has reached both util-linux[1] and kernel[2]
> contributors with intention to make zram dev
Hello,
Not so long ago Timofey has reached both util-linux[1] and kernel[2]
contributors with intention to make zram device management too. I think
the proposal is good, and there should be distribution independent tool
like that. Also such command fits fairly well to a scope of util-linux
packa
6 matches
Mail list logo
