XFCE: Pompous (amd64 Beta) Release News

[machinebacon]

The output you see is not an error, it's the kernel vomiting its messages into the login screen (I think!). Simply enter your username/password combo there. Then follow pidsley's howto. Or did you do it already and it doesn't log in straightly?

In this case, post your
cat /etc/systemd/system/getty.target.wants/[email protected]
(basically, the "ExecStart=-/sbin/agetty --noclear %I 38400 linux" should have your username there)

[wayne]

yeah.. follow pidsley's posts...not sure if any typo, but all i did was copy and paste plus amend <username> to wayne

here is the file:

wayne@bbqxfce64:~$ cat /etc/systemd/system/getty.target.wants/[email protected]# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.

[Unit]
Description=Getty on %I
BindTo=dev-%i.device
After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service

# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target

[Service]
Environment=TERM=linux
ExecStart=-/sbin/agetty %I 38400
Restart=always
RestartSec=0
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes
KillMode=process
IgnoreSIGPIPE=no

# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE= LC_MEASUREMENT= LC_IDENTIFICATION=

# Some login implementations ignore SIGTERM, so we send SIGHUP
# instead, to ensure that login terminates cleanly.
KillSignal=SIGHUP

[Install]
Alias=getty.target.wants/[email protected]
wayne@bbqxfce64:~$

[wuxmedia]

now that's interesting, I was having no joy at all, on BLOAT using Pidsleys method - it refused to autologin...
I've just now altered the ExecStart line, to basically the same as pidsleys line, in getty.target.wants file - it works.
when I install 'Unia' i followed Pid's method and the files were already there. then i simply put systemd back on...

[wayne]

wuxmedia...

so i tried your method

change it so the lines(just those few) are now

[Service]
Environment=TERM=linux
ExecStart=-/sbin/agetty --autologin wayne %I 38400
Restart=always
RestartSec=0

reboot, haha, autologin works...

[machinebacon]

now that's interesting, I was having no joy at all, on BLOAT using Pidsleys method - it refused to autologin...
I've just now altered the ExecStart line, to basically the same as pidsleys line, in getty.target.wants file - it works.
when I install 'Unia' i followed Pid's method and the files were already there. then i simply put systemd back on...

Unia does log into automagically, maybe that's why the line was there already (wink wink) ;)

[pidsley]

Thanks for the testing, wux and wayne. I will try to see why the method I used is not working for you.

[wuxmedia]

^^ understood. exactly - thats how I realised systemd was not PID1 - all the lines were indeed there.
@pidsley, thanks - the double-double-ues are happy to help. 8)
@wayne welcome back!

[bones]

It's not, it's not :) The number of installed packages shall not have any impact on the RAM usage after boot, so I'd recommend looking into what eats up RAM. I suppose it's the udisks2/upower/systemd trilogy that weighs heavy, although it should actually replace some stuff under the hood (policykit springs to mind). Maybe upgrading to experimental systemd is an idea - don't do it if you don't dare to. If I have time I try to break her.

Okay, I've got it committed to bare metal, now, and same results, about 180MB idling. Yes, I will look at tweaking the systemd services, and get to know each of those processes. Is it just a matter of deleting an entry from that menu?

[machinebacon]

No, it's about disabling services like you did with sudo service <service> stop. It's a bit more complex now, but no way a PITA. You can of course uninstall stuff like lvm2 if you don't need it, for example.

[bones]

Excellent, thanks Jules!

[wuxmedia]

just for shit and giggles, i tried the '2nd' method (/etc/systemd/system/gettysburg.address/whatever) of --autologin on my wheezy netinstall - works fine. drops right in.