Bug#785457: cloud.debian.org: AMI don't need getty

On Mon, May 18, 2015 at 10:29 AM, Ognyan Kulev wrote: > На 18.05.2015 в 17:17, Emmanuel Kasper написа: >> >> My understanding of that applied to Xen virtualization platform that >> Amazon uses, is that systemd will *always* start a getty on the default >> system console, which for Xen will be /d

Bug#785457: cloud.debian.org: AMI don't need getty

На 18.05.2015 в 17:29, Ognyan Kulev написа: I'm new to Amazon EC2 but I don't see any way to access Xen console (hvc0). Quick googling didn't find anything. The only tty thing that I found is ec2-get-console-output command

Bug#785457: cloud.debian.org: AMI don't need getty

На 18.05.2015 в 17:17, Emmanuel Kasper написа: My understanding of that applied to Xen virtualization platform that Amazon uses, is that systemd will *always* start a getty on the default system console, which for Xen will be /dev/hvc0 instead of /dev/tty1 Actually you *want* to have this one g

Bug#785457: cloud.debian.org: AMI don't need getty

На 18.05.2015 в 17:17, Emmanuel Kasper написа: Can you please post a a process list of the getty processes you see in the Amazon hvm ? Now if you have more than one getty started, then there is indeed room for improvement. I already fixed my EC2 instance, so just now I artificially unmasked

Bug#785457: cloud.debian.org: AMI don't need getty

Ognyan, Can you please post a a process list of the getty processes you see in the Amazon hvm ? I am not aware of all the modifications made to the Debian AWS but according to http://0pointer.de/blog/projects/serial-console.html: Two VTs are handled specially by the auto-spawning logic: firstly

Bug#785457: cloud.debian.org: AMI don't need getty

> > but the reality is that getty processes exist in the official Jessie HVM > AMI Ooh! And I know why :-) The HVM AMIs are generated from James Brombergers fork, which most likely does not have those adjustments. OK, the issue here is then that James and I need to get together and figure out this

Bug#785457: cloud.debian.org: AMI don't need getty

On 18 May 2015 at 15:43, Ognyan Kulev wrote: > "I'm a little confused, we should already be doing that for AWS images: > https://github.com/andsens/bootstrap-vz/blob/f3be3e4543a37ef1af7b2b5193a8bb7b590d1b79/bootstrapvz/common/tasks/boot.py#L31 > " > > systemd does not use the /etc/inittab file. >

Bug#785457: cloud.debian.org: AMI don't need getty

На 18.05.2015 в 16:43, Ognyan Kulev написа: "I'm a little confused, we should already be doing that for AWS images: https://github.com/andsens/bootstrap-vz/blob/f3be3e4543a37ef1af7b2b5193a8bb7b590d1b79/bootstrapvz/common/tasks/boot.py#L31 " systemd does not use the /etc/inittab file. Oh, actua

Bug#785457: cloud.debian.org: AMI don't need getty

"I'm a little confused, we should already be doing that for AWS images: https://github.com/andsens/bootstrap-vz/blob/f3be3e4543a37ef1af7b2b5193a8bb7b590d1b79/bootstrapvz/common/tasks/boot.py#L31 " systemd does not use the /etc/inittab file. signature.asc Description: OpenPGP digital signatur

Bug#785457: cloud.debian.org: AMI don't need getty

Package: cloud.debian.org Severity: wishlist User: cloud.debian@packages.debian.org Usertags: image Usertags: aws Hi, While fine-tuning the Debian 8.0.0 HVM AMI, I noticed that getty processes fill up space in the otherwise short default process list, so I disabled these with: systemctl