You are not logged in.
Now, can this daemon start automatically in the default runlevel?
# rc-service test-service stop
* WARNING: test-service is already stopped
# rc-update add test-service default
* service test-service added to runlevel default
# v /etc/runlevels/default/
total 8
drwxr-xr-x 2 root root 4096 May 19 15:57 ./
drwxr-xr-x 9 root root 4096 May 15 15:54 ../
lrwxrwxrwx 1 root root 19 May 15 15:54 anacron -> /etc/init.d/anacron*
lrwxrwxrwx 1 root root 18 May 15 15:54 autofs -> /etc/init.d/autofs*
lrwxrwxrwx 1 root root 26 May 15 15:54 binfmt-support -> /etc/init.d/binfmt-support*
lrwxrwxrwx 1 root root 21 May 15 15:54 bluetooth -> /etc/init.d/bluetooth*
lrwxrwxrwx 1 root root 20 May 15 15:54 bootlogs -> /etc/init.d/bootlogs*
lrwxrwxrwx 1 root root 21 May 15 15:54 cgmanager -> /etc/init.d/cgmanager*
lrwxrwxrwx 1 root root 19 May 15 15:54 cgproxy -> /etc/init.d/cgproxy*
lrwxrwxrwx 1 root root 28 May 15 15:54 console-setup.sh -> /etc/init.d/console-setup.sh*
lrwxrwxrwx 1 root root 16 May 15 15:54 cron -> /etc/init.d/cron*
lrwxrwxrwx 1 root root 16 May 15 15:54 dbus -> /etc/init.d/dbus*
lrwxrwxrwx 1 root root 19 May 15 15:54 elogind -> /etc/init.d/elogind*
lrwxrwxrwx 1 root root 17 May 15 15:54 exim4 -> /etc/init.d/exim4*
lrwxrwxrwx 1 root root 19 May 15 15:54 hddtemp -> /etc/init.d/hddtemp*
lrwxrwxrwx 1 root root 22 May 15 15:54 irqbalance -> /etc/init.d/irqbalance*
lrwxrwxrwx 1 root root 24 May 15 15:54 lvm2-lvmetad -> /etc/init.d/lvm2-lvmetad*
lrwxrwxrwx 1 root root 25 May 15 15:54 lvm2-lvmpolld -> /etc/init.d/lvm2-lvmpolld*
lrwxrwxrwx 1 root root 16 May 15 15:54 lxdm -> /etc/init.d/lxdm*
lrwxrwxrwx 1 root root 16 May 15 15:54 motd -> /etc/init.d/motd*
lrwxrwxrwx 1 root root 16 May 15 15:54 nmbd -> /etc/init.d/nmbd*
lrwxrwxrwx 1 root root 15 May 15 15:54 ntp -> /etc/init.d/ntp*
lrwxrwxrwx 1 root root 20 May 15 15:54 rc.local -> /etc/init.d/rc.local*
lrwxrwxrwx 1 root root 21 May 15 15:54 rmnologin -> /etc/init.d/rmnologin*
lrwxrwxrwx 1 root root 17 May 15 15:54 rsync -> /etc/init.d/rsync*
lrwxrwxrwx 1 root root 19 May 15 15:54 rsyslog -> /etc/init.d/rsyslog*
lrwxrwxrwx 1 root root 23 May 15 15:54 samba-ad-dc -> /etc/init.d/samba-ad-dc*
lrwxrwxrwx 1 root root 16 May 15 15:54 smbd -> /etc/init.d/smbd*
lrwxrwxrwx 1 root root 15 May 15 15:54 ssh -> /etc/init.d/ssh*
lrwxrwxrwx 1 root root 22 May 15 15:54 sysfsutils -> /etc/init.d/sysfsutils*
lrwxrwxrwx 1 root root 24 May 19 15:57 test-service -> /etc/init.d/test-service*
lrwxrwxrwx 1 root root 16 May 15 15:54 wicd -> /etc/init.d/wicd*
lrwxrwxrwx 1 root root 15 May 15 15:54 xen -> /etc/init.d/xen*
lrwxrwxrwx 1 root root 22 May 15 15:54 xendomains -> /etc/init.d/xendomains*
Now reboot and when it comes up, check /var/log/rc.log :-
rc default logging started at Sat May 19 16:02:04 2018
[....] Starting enhanced syslogd: rsyslogd[ ok .
[....] Starting anac(h)ronistic cron: anacron[ ok .
[....] Starting automount...[ ok .
[....] Enabling additional executable binary formats: binfmt-support[ ok .
[....] Starting system message bus: dbus[ ok .
[....] Starting bluetooth: bluetoothd[ ok .
[....] Setting up console font and keymap...[ ok done.
[....] Starting periodic command scheduler: cron[ ok .
[....] Starting session management daemon: elogind[ ok .
[....] Starting MTA: exim4[ ok .
ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken
[....] Starting SMP IRQ Balancer: irqbalance[ ok .
[....] Starting LVM2 metadata daemon: lvmetad[ ok .
[....] Starting LVM2 poll daemon: lvmpolld[ ok .
[....] Starting X display manager: lxdm[ ok .
[....] Starting NTP server: ntpd[ ok .
[....] Starting OpenBSD Secure Shell server: sshd[ ok .
[....] Setting sysfs variables...[ ok .
[....] Starting Network connection manager: wicd[ ok .
[....] Not running within Xen or no compatible utils ...[warn (warning).
* Starting runsvdir ...
[ ok ]
* Starting test-service ...
* Failed to start test-service
[ !! ]
* ERROR: test-service failed to startrc default logging stopped at Sat May 19 16:02:06 2018
Although it is actually running :-
root 3132 0.0 0.0 4216 996 ? S 16:02 0:00 /usr/bin/runsvdir -P /run/openrc/sv log: ........................................................................
root 3165 0.0 0.0 4064 660 ? Ss 16:02 0:00 \_ runsv test-service
daemon 3166 0.0 0.0 4292 704 ? S 16:02 0:00 \_ /bin/sh /home/user1/test/test-daemon
daemon 3168 0.0 0.0 4200 672 ? S 16:02 0:00 \_ sleep 60
rc-status reports that test-service is stopped.
# rc-service test-service status
run: /run/openrc/sv/test-service: (pid 3166) 499s
# rc-service test-service start
* Starting test-service ... [ ok ]
rc-status now also reports that test-service is started.
Maybe I should try a real service.
Geoff
I suspect that you could use runit under OpenRC in the same way that it can run under SysVinit, starting it in inittab as described in :-
https://dev1galaxy.org/viewtopic.php?id=1748
Here I have tried to have it integrated with OpenRC, so that services appear as existing services.
The file set-up
OpenRC needs to know how to start Runit's runsvdir -
download runsvdir.in from
https://raw.githubusercontent.com/OpenR … unsvdir.in
Edit it to fix up the #! path to #!/sbin/openrc-run
and change :-
checkpath -m 0755 -o root:root -d ${RC_SVCDIR}/sv
to :-
install -m 0755 -o root -g root -d ${RC_SVCDIR}/sv
copy it to /etc/init.d/runsvdir
chmod a+x /etc/init.d/runsvdir
The following example is copied from :-
https://wiki.gentoo.org/wiki/Runit#Open … on_feature
and hacked to work on my machine. Do make sure that the file path names are correct for you, if you try and copy it.
Gentoo seems to have a service called localmount. In order to get things running I changed this to mountall.
They show the test-daemon being run under chpst with "-o 5". My /bin/sh test-daemon failed under this with
/bin/sh: 0: 3: Invalid argument
I therefore changed the argument to allow 20 files, i.e. "-o 20"
As an ordinary user create a test-daemon, which puts out a time stamp!
cd
mkdir -f test/svc-repo/test-service
cd test
cat << EOF > test-daemon
#!/bin/sh
while true
do
echo "This is the test-daemon `date`";
sleep 60;
done;
EOF
chmod a+x test-daemon
Then we create an executable "run" file for Runit.
cd svc-repo/test-service
cat << EOF2 > run
#!/bin/sh
exec \
chpst -o 20 \
chpst -u daemon \
/home/user1/test/test-daemon
EOF2
chmod a+x run
Then, as root, create the OpenRC init file.
cd /etc/init.d
cat << EOF3 > test-service
#!/sbin/openrc-run
description="A supervised test service"
supervisor=runit
runit_service=/home/user1/test/svc-repo/test-service
depend() {
need mountall runsvdir
}
EOF3
chmod a+x test-service
Now see if it will run :-
# rc-service test-service start
* Starting runsvdir ... [ ok ]
* Starting test-service ...
* Failed to start test-service [ !! ]
* ERROR: test-service failed to start
It is documented that this currently (0.23) produces a failure message. This is a timing problem and the service will be started at the next runsvdir scan (if no "down" file), or try again, but see the warning in :-
https://wiki.gentoo.org/wiki/Runit#Open … on_feature
# rc-service test-service start
* Starting test-service ... [ ok ]
# rc-service test-service status
run: /run/openrc/sv/test-service: (pid 4248) 163s
# ps uaxf
...
root 4224 0.0 0.0 4216 1108 ? S 14:31 0:00 /usr/bin/runsvdir -P /run/openrc/sv log: .................................................................................................
root 4247 0.0 0.0 4064 668 ? Ss 14:31 0:00 \_ runsv test-service
daemon 4248 0.0 0.0 4292 1488 ? S 14:31 0:00 \_ /bin/sh /home/user1/test/test-daemon
daemon 4338 0.0 0.0 5844 684 ? S 14:34 0:00 \_ sleep 60
# rc-service test-service stop
* Stopping test-service ... [ ok ]
# rc-service test-service status
fail: /run/openrc/sv/test-service: unable to change to service directory: file does not exist
As an old Tops 20 user, I have alias v='ls -alF' ;-)
# v /run/openrc/
total 44
drwxrwxr-x 15 root root 340 May 19 14:31 ./
drwxr-xr-x 25 root root 940 May 19 14:31 ../
drwxr-xr-x 2 root root 40 May 19 13:53 daemons/
-rw-r--r-- 1 root root 40021 May 19 13:53 deptree
drwxr-xr-x 2 root root 40 May 19 14:37 exclusive/
drwxr-xr-x 2 root root 40 May 19 13:53 failed/
drwxr-xr-x 2 root root 40 May 19 13:53 hotplugged/
drwxr-xr-x 2 root root 40 May 19 13:53 inactive/
drwxr-xr-x 3 root root 60 May 19 14:31 options/
drwxr-xr-x 2 root root 40 May 19 13:53 scheduled/
-rw-r--r-- 1 root root 7 May 19 13:53 softlevel
drwxr-xr-x 2 root root 1280 May 19 14:37 started/
drwxr-xr-x 2 root root 40 May 19 14:32 starting/
drwxr-xr-x 2 root root 40 May 19 14:37 stopping/
drwxr-xr-x 2 root root 40 May 19 14:37 sv/
drwxr-xr-x 2 root root 40 May 19 13:53 tmp/
drwxr-xr-x 2 root root 40 May 19 13:53 wasinactive/
# v /run/openrc/sv/
total 0
drwxr-xr-x 2 root root 40 May 19 14:37 ./
drwxrwxr-x 15 root root 340 May 19 14:31 ../
# rc-service test-service start
* Starting test-service ...
* Failed to start test-service [ !! ]
* ERROR: test-service failed to start
# rc-service test-service status
run: /run/openrc/sv/test-service: (pid 4489) 4s
# v /run/openrc/sv/
total 0
drwxr-xr-x 2 root root 60 May 19 14:40 ./
drwxrwxr-x 15 root root 340 May 19 14:31 ../
lrwxrwxrwx 1 root root 39 May 19 14:40 test-service -> /home/user1/test/svc-repo/test-service/
So, it seems to be basically working!
This could presumably be modified to do logging, as described in the docs.
Geoff
I am just keen to see how well the OpenRC that is shipped with ASCII works and it seems that if you don't want to do anything too odd, that it just works! In fact it works so well that you have to look quite closely to check if it is actually running!
I have tried editing /etc/rc.conf to set rc_logger="YES" in order to see what it was logging. Originally I also set rc_verbose="YES", but that put out too much info for me, but with that turned off the logging was quite reasonable.
Geoff
The version of OpenRC in ASCII is 0.23. In this version it still runs our old friend /sbin/init, which still refers to /etc/inittab which appears to be unaltered. When inittab sets the runlevel it uses /etc/init.d/rc (& rcS). It is here that OpenRC is used, as rc & rcS are replaced when OpenRC is installed. /etc/init.d/rc runs /sbin/openrc which then runs the services defined for that level and then stops. It therefore does not show on a ps listing.
You can see some of the housekeeping in /run/openrc.
Geoff
can't mount logical disk using PCManFM in ASCII RC, LXDE or OpenBox:
I am happily using SpaceFM instead of PCManFM. It can use udevil to mount disks.
https://dev1galaxy.org/viewtopic.php?pid=430#p430
Geoff
As well as the very good Gentoo docs, there is also a rich source of documentation and example stuff on the OpenRC GitHub :-
https://github.com/OpenRC/openrc
This includes a user guide as well as various scripts.
Geoff
As OpenRC is now available in ASCII, I thought that I should try it on my laptop, which has arrived at ASCII via Debian Jessie and Devuan Jessie.
I have been running runit as a process supervisor, which I chose to roll back before installing OpenRC. I report that in my thread on runit.
https://dev1galaxy.org/viewtopic.php?id=1748
The next thing was to install Openrc. Synaptic wanted to remove bum and sysv-rc and also install libeinfo1 and librc1. The installation proceeds normally producing the following warning :-
**********************************************************************
*** WARNING: if you are replacing sysv-rc by OpenRC, then you must ***
*** reboot immediately using the following command: ***
for file in /etc/rc0.d/K*; do s=`basename $(readlink "$file")` ; /etc/init.d/$s stop; done
**********************************************************************
I had seen a mesage on DNG that the above command hangs the system and that you should just reboot,
so I did just reboot and everything came back up normally.
https://lists.dyne.org/lurker/message/2 … d7.en.html
The next qustion was "is openrc running?" Running ps uaxf shows :-
root 1 1.6 0.0 15816 1884 ? Ss 15:59 0:00 init [2]
Switching to the console with <CTRL><ALT><F1> does not show any messages referring to openrc.
Checking with synaptic, openrc is installed ;-)
There are a couple of commands to check how things are running. You can run rc-status as yourself while rc-update show needs to be run as root. These seem to show that the services are running under openrc. It is also possible to check a specific service with, e.g. :
/etc/init.d/lxdm status
[ ok ] lxdm is running.
There is some documentation at :-
https://wiki.gentoo.org/wiki/OpenRC
I am hoping to try using runit under OpenRC
https://wiki.gentoo.org/wiki/Runit#runitintegration
Geoff
I was wanting to try replacing SysVinit with OpenRC. It appeared that the set up for runit under OpenRC was a little different. Therefore, the first thing to do was to back out of running stuff under runit. The easiest one for me to back out of as a test was bluetoothd.
cd /etc/service
rm bluetoothd
this has now stopped bluetoothd. It appears that in setting up the init links the command does not run if there is a conflicting set-up, so it is easiest to remove the links and then set them to the default.
cd /etc/init.d
update-rc.d bluetooth remove
update-rc.d bluetooth defaults
This has now re-instated the links in /etc/rc2.d etc.
The machine was rebooted and bluetoothd was running normally.
The next one to try was lxdm. I set up the links first and then stopped it under runit, as it may well crash X.
cd /etc/init.d
update-rc.d lxdm remove
update-rc.d lxdm defaults
I then logged out and switched to the console with <CTRL><ALT><F1> and logged in as root
cd /etc/service
rm lxdm
shutdown -r now
This then came back normally with lxdm running under init.
It was now clear to put the remaining services under init, which in the case of my laptop was autofs and wicd.
cd /etc/init.d
update-rc.d autofs remove
update-rc.d autofs defaults
update-rc.d wicd remove
update-rc.d wicd defaults
cd /etc/service
rm autofs wicd
and then reboot. (Although this reboot could probably have waited until after the following step.)
All the services are now running normally and runsvdir is still running but not doing anything!
I edited /etc/inittab and commented out the line at the end which was running runsvdir, thus :-
#runit-sysv maintscript -- BEGIN
#SV:123456:respawn:/etc/runit/2
#runit-sysv maintscript -- END
A reboot then left everything running in a normal state. I will report on OpenRC in another thread.
https://dev1galaxy.org/viewtopic.php?id=2072
Geoff
I am using the wrapper program which Didier Kryn posted on DNG. It looks like pkexec, but uses sudo or udevil to do the work.
For more details see :-
https://dev1galaxy.org/viewtopic.php?pid=7703#p7703
Geoff
Er... that is what lightdm is for. When you have closed down a session, it lets you log in again ;-)
If you want a console <CTRL><ALT><F1> will connect you through to tty1: and you can log in. If/when you want to get back to X you can type <CTRL><ALT><F7> as X runs on tty7:
Is that what you want?
Geoff
Sorry for the slow response, here you go :-
$ for i in consolekit elogind policykit polkit libpam ; do aptitude search ~i"$i" ; done
i A consolekit - framework for defining and tracking users, sessions and seats
i libpolkit-backend-consolekit-1-0 - PolicyKit backend API
i libpolkit-gobject-consolekit-1-0 - PolicyKit Authorization API
i A elogind - user, seat and session management daemon
i A libelogind0 - user, seat and session management library
i A libpam-elogind - elogind PAM module
i A lxqt-policykit - LXQt authentication agent for PolicyKit
i policykit-1 - framework for managing administrative policies and privileges
i policykit-1-gnome - authentication agent for PolicyKit
i A libpolkit-agent-1-0 - PolicyKit Authentication Agent API
i A libpolkit-backend-1-0 - PolicyKit Authorization API
i libpolkit-backend-consolekit-1-0 - PolicyKit backend API
i A libpolkit-gobject-1-0 - PolicyKit Authorization API
i libpolkit-gobject-consolekit-1-0 - PolicyKit Authorization API
i A libpolkit-qt5-1-1 - PolicyKit-qt5-1 library
i A libpam-cap - POSIX 1003.1e capabilities (PAM module)
i A libpam-elogind - elogind PAM module
i A libpam-gnome-keyring - PAM module to unlock the GNOME keyring upon login
i libpam-modules - Pluggable Authentication Modules for PAM
i libpam-modules-bin - Pluggable Authentication Modules for PAM - helper binaries
i libpam-runtime - Runtime support for the PAM library
i libpam0g - Pluggable Authentication Modules library
Geoff
I have now re-installed LXQT alongside LXDE. I did this by installing lxde. If I were to install task-lxqt-desktop, it would remove lxde and consolekit and install the elogind stuff.
I can select either lxde or lxqt from the lxdm login screen and they both work. lxde is fine, but with lxqt it does want me to enter the root password as the first thing. I have not yet worked out why it is doing this, but I guess that this is a problem with not having all the elogind stuff installed. Generally lxqt does seem to work reasonably well although I have not had a chance to polish it to my liking yet.
Is lxqt the way forwards? Should we be moving away from lxde?
Geoff
Yes, X does pull in libsystemd0, so maybe I shouldn't be too worried, but I thought that the fewer packages that pull in libsystemd0, the better.
As I check up, I see that I also have libpulse0 installed. If I were to remove that, then that would take out, inter alia :-
chromium, ffmpeg, flightgear, gimp, kodi, qemu, vlc, wireshark
I do not have pulseaudio installed but I do have apulse.
Is it easy to convey the abominability (?) that the devs felt about LXDE.
Geoff
I did initially have a look at LXQT :-
https://dev1galaxy.org/viewtopic.php?id=94
but I reverted to LXDE as lxqt-panel pulled in libpulse0 and libsystemd0.
Geoff
I have had a quick look at libpolkit-{backend|gobject}-elogind-1-0 to see if there is a problem.
$ aptitude why-not libpolkit-backend-elogind-1-0
i libpolkit-backend-consolekit-1-0 Conflicts libpolkit-backend-elogind-1-0
$ aptitude why-not libpolkit-gobject-elogind-1-0
i libpolkit-gobject-consolekit-1-0 Conflicts libpolkit-gobject-elogind-1-0
It appears that the libpolkits need either consolekit or elogind, but not both and LXDE only works with the consolekit versions.
Geoff
If I mark libpolkit-{backend|gobject}-elogind-1-0 for installation, then it wants to remove lxde. This is the case whether the 1-0 is at the end or in the middle.
I do have elogind, libelogind0 and libpam-elogind installed and elogind is running as is the console-kit-daemon.
Geoff
I have performed the same commands on my LXDE laptop and that also still works nicely and can also reboot from the exit menu.
Geoff
Yes, I can select "reboot" from the exit menu and it still works, although it does still produce the GDBus error message which I reported elsewhere.
https://dev1galaxy.org/viewtopic.php?pid=8185#p8185
The early signs are that this works ok, with the suggestion that maybe elogind doesn't work with LXDE.
Geoff
I saw the thread on DNG https://lists.dyne.org/lurker/message/2 … 53.en.html and have decided to go for it!
# apt-get install libpolkit-backend-consolekit-1-0 libpolkit-gobject-consolekit-1-0
This runs without errors and now I can run
# apt-get update
# apt-get dist-upgrade
And this runs without error. I now need to see if I can do things like shutdown.
Geoff
I see that Penguinwrangler has hit the same sort of problem with KDE
https://dev1galaxy.org/viewtopic.php?id=2007
and has managed to work round it by installing libpolkit-backend-elogind-1-0. I had a look at that and it wanted to remove LXDE.
Geoff
# apt-get install libpolkit-backend-consolekit-1-0 libpolkit-gobject-consolekit-1-0
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
chromium-inspector libavcodec56 libavresample2 libopenjpeg5 libschroedinger-1.0-0 libvpx1 libwebp5 libwebpdemux1 libx264-142
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 policykit-1
The following packages will be REMOVED:
libpolkit-backend-1-0-elogind libpolkit-gobject-1-0-elogind
The following NEW packages will be installed:
libpolkit-backend-1-0 libpolkit-backend-consolekit-1-0 libpolkit-gobject-1-0 libpolkit-gobject-consolekit-1-0
The following packages will be upgraded:
libpolkit-agent-1-0 policykit-1
2 upgraded, 4 newly installed, 2 to remove and 25 not upgraded.
Need to get 186 kB of archives.
After this operation, 43.0 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
That looks as though it shouldn't break too much. Is it ok that it would remove libpolkit-backend-1-0-elogind and libpolkit-gobject-1-0-elogind?
I had used slim earlier, but had switched to lxdm after upgrading to Ascii.
Geoff
# apt-cache depends consolekit
:
Depends: libpolkit-gobject-1-0
libpolkit-gobject-1-0-systemd
Neither of those is installed.
If I ask it to install libpolkit-gobject-1-0
then it will remove :-
libpolkit-backend-1-0-elogind
libpolkit-gobject-1-0-elogind
policykit-1-gnome
and install
libpolkit-gobject-consolekit-1-0
lxpolkit
and upgrade
libpolkit-agent-1-0
If I ask it to install
libpolkit-backend-1-0
then it will also remove
cups-pk-helper
upower
xfce4-power-manager
and also install
libpolkit-gobject-1-0-systemd
I think that I will try and install libpolkit-gobject-1-0, but I will post this while my machine is still working!
Geoff
No, it won't do it, "Fix broken packages first".
Looking at my posting from my laptop, I see that it wanted to remove policykit-1, so a quick check in Synaptic shows that removing policykit-1 would also remove LXDE.
Geoff
Investigating with Synaptic, and trying marking for upgrade, suggests that
upgrading policykit-1 wants to remove
libpolkit-backend-1-0-elogind
libpolkit-gobject-1-0-elogind
and install
libpolkit-backend-1-0
libpolkit-gobject-1-0
libpolkit-backend-consolekit-1-0
libpolkit-gobject-consolekit-1-0
Marking consolekit for removal would remove
lxde lxde-core lxsession lxsession-logout openbox-lxde-session slim
I haven't worked out yet why it wants to remove consolekit, but that would remove LXDE.
Geoff
I think that everything appears to be correct, the following are installed :-
policykit-1 0.105-18+devuan2.4
libpolkit-agent-1-0 0.105-18+devuan2.4
libpolkit-backend-1-0-elogind 0.105-18+devuan2.4
libpolkit-gobject-1-0-elogind 0.105-18+devuan2.4
These all want to go from v2.4 to 2.9
On my desktop consolekit is installed.
pam-auth-update offers
Pluggable Authentication Modules (PAM) determine how authentication, authorization,
and password changing are handled on the system, as well as allowing configuration
of additional actions to take when starting user sessions.
Some PAM module packages provide profiles that can be used to automatically adjust
he behavior of all PAM-using applications on the system. Please indicate which of
hese behaviors you wish to enable.
PAM profiles to enable:
[*] Unix authentication
[*] GNOME Keyring Daemon - Login keyring management
[*] elogind Session Management
[*] Inheritable Capabilities Management
I left these all selected and tabbed to <OK> and hit <return>.
apt-get still wants to remove LXDE.
Geoff