Displaying 12 results from an estimated 12 matches for "awkwared".
Did you mean:
awkward
2015 Apr 30
0
CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
I think the command-line is far more flexable then the GUI interface.
I use ec2-api-tools, but the python boto stuff works virtually the same.
On Thu, 30 Apr 2015, Nico Kadel-Garcia wrote:
> On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott <kprescott at coolip.net> wrote:
>> to follow-up, I will give an example.
>> Here is the listing for the official centos AMI:
>>
2015 Apr 30
0
CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
This is not really a problem at all.
when you launch your image for the first time, you can specify a larger /
volume size and cloud-init-tools will take care of the rest.
This is well documented in the AWS userguides.
-- Kelly Prescott
On Wed, 29 Apr 2015, Nico Kadel-Garcia wrote:
> I'm staring at the free CentOS images on AWS, and seeing that whoever
> set those up elected to use a
2015 Apr 30
0
CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
to follow-up, I will give an example.
Here is the listing for the official centos AMI:
IMAGE ami-96a818fe aws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS
HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2
aws-marketplace available public [marketplace:
aw0evgkw8e5c1q413zgy5pjce] x86_64 machineebs hvm xen
BLOCKDEVICEMAPPING EBS /dev/sda1
2015 Apr 30
2
CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott <kprescott at coolip.net> wrote:
> to follow-up, I will give an example.
> Here is the listing for the official centos AMI:
>
> IMAGE ami-96a818fe aws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS
> HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace
> available public [marketplace:
2015 Apr 29
4
CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
I'm staring at the free CentOS images on AWS, and seeing that whoever
set those up elected to use a partition for /dev/xvda1 rather than
taking advantage of Amazon's tendency to use "/dev/xvda", "/dev/xvdb",
etc. for each disk and use those directly as a file system.
The result is that if you elect to allocate a larger base disk image,
for example allocating 50 Gig to
2020 Jul 07
2
[RFC]: mm,power: introduce MADV_WIPEONSUSPEND
On Fri 03-07-20 15:29:22, Jann Horn wrote:
> On Fri, Jul 3, 2020 at 1:30 PM Michal Hocko <mhocko at kernel.org> wrote:
> > On Fri 03-07-20 10:34:09, Catangiu, Adrian Costin wrote:
> > > This patch adds logic to the kernel power code to zero out contents of
> > > all MADV_WIPEONSUSPEND VMAs present in the system during its transition
> > > to any suspend
2020 Jul 07
2
[RFC]: mm,power: introduce MADV_WIPEONSUSPEND
On Fri 03-07-20 15:29:22, Jann Horn wrote:
> On Fri, Jul 3, 2020 at 1:30 PM Michal Hocko <mhocko at kernel.org> wrote:
> > On Fri 03-07-20 10:34:09, Catangiu, Adrian Costin wrote:
> > > This patch adds logic to the kernel power code to zero out contents of
> > > all MADV_WIPEONSUSPEND VMAs present in the system during its transition
> > > to any suspend
2020 Jul 07
3
[RFC]: mm,power: introduce MADV_WIPEONSUSPEND
On Tue 07-07-20 10:07:26, Pavel Machek wrote:
> Hi!
>
> > > > > This patch adds logic to the kernel power code to zero out contents of
> > > > > all MADV_WIPEONSUSPEND VMAs present in the system during its transition
> > > > > to any suspend state equal or greater/deeper than Suspend-to-memory,
> > > > > known as S3.
> > >
2020 Jul 07
3
[RFC]: mm,power: introduce MADV_WIPEONSUSPEND
On Tue 07-07-20 10:07:26, Pavel Machek wrote:
> Hi!
>
> > > > > This patch adds logic to the kernel power code to zero out contents of
> > > > > all MADV_WIPEONSUSPEND VMAs present in the system during its transition
> > > > > to any suspend state equal or greater/deeper than Suspend-to-memory,
> > > > > known as S3.
> > >
2020 Jul 07
0
[RFC]: mm,power: introduce MADV_WIPEONSUSPEND
Hi!
> > > > This patch adds logic to the kernel power code to zero out contents of
> > > > all MADV_WIPEONSUSPEND VMAs present in the system during its transition
> > > > to any suspend state equal or greater/deeper than Suspend-to-memory,
> > > > known as S3.
> > >
> > > How does the application learn that its memory got wiped?
2020 Jul 03
5
[RFC]: mm,power: introduce MADV_WIPEONSUSPEND
On Fri 03-07-20 10:34:09, Catangiu, Adrian Costin wrote:
> This patch adds logic to the kernel power code to zero out contents of
> all MADV_WIPEONSUSPEND VMAs present in the system during its transition
> to any suspend state equal or greater/deeper than Suspend-to-memory,
> known as S3.
How does the application learn that its memory got wiped? S2disk is an
async operation and it can
2020 Jul 03
5
[RFC]: mm,power: introduce MADV_WIPEONSUSPEND
On Fri 03-07-20 10:34:09, Catangiu, Adrian Costin wrote:
> This patch adds logic to the kernel power code to zero out contents of
> all MADV_WIPEONSUSPEND VMAs present in the system during its transition
> to any suspend state equal or greater/deeper than Suspend-to-memory,
> known as S3.
How does the application learn that its memory got wiped? S2disk is an
async operation and it can