public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexey Sokolov <alexey+gentoo@asokolov.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [REVIEW] News Item - 2020-10-17-display-manager-init
Date: Sat, 17 Oct 2020 23:44:33 +0100	[thread overview]
Message-ID: <CAHK_jdhBq68eaGSqweYmwBRoJKis9MoN+UjQqeu173cUeyFOhw@mail.gmail.com> (raw)
In-Reply-To: <7fff12bc-c487-dc17-7bf4-d0242ab8244e@aisha.cc>

сб, 17 окт. 2020 г. в 23:05, Aisha Tammy <gentoo.dev@aisha.cc>:
>
> Hi,
>   I'm attaching the news item for the upcoming display-manager-init changes
>
> Thanks,
> Aisha
>
> -----------
>
> Title: New OpenRC Display Manager Initializer Scripts
> Author: Aisha Tammy <gentoo@aisha.cc>
> Posted: 2020-10-17
> Revision: 1
> News-Item-Format: 2.0

This will be shown even if no xdm was installed?

>
> There has been a refactoring of the old 'xdm' init script and its
> requirements from various packages into an independent package:
>
> gui-libs/display-manager-init
>
> This package provides the 'display-manager' startup script for
> handling your chosen display manager, without being dependent on
> Xorg server.
>
> To update to the new DM init scripts, you need to manually add the
> package in your @world set:
>
> emerge -vuDU gui-libs/display-manager-init
>
> To start using the new init scripts, change the DISPLAYMANAGER
> variable in the /etc/conf.d/display-manager to your preferred DM:
>
> DISPLAYMANAGER="gdm"
>
> To test the newly installed scripts, you can try to switch to
> 'display-manager' on the running computer.
> Run the following commands in a tty to test your current install:
>
> rc-service xdm stop
> rc-service display-manager start
>
> If the test succeeds, you can remove the old xdm startup script
> and add display-manager to the default runlevel:
>
> rc-update del xdm default
> rc-update add display-manager default
>
> Reboot your computer to perform a final test and check to see
> that your chosen display manager has started.

What happens if I ignore this news item and do nothing?


  parent reply	other threads:[~2020-10-17 22:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-17 22:05 [gentoo-dev] [REVIEW] News Item - 2020-10-17-display-manager-init Aisha Tammy
2020-10-17 22:41 ` Kent Fredric
2020-10-17 22:43   ` Aisha Tammy
2020-10-17 22:44   ` Kent Fredric
2020-10-17 22:59     ` Aisha Tammy
2020-10-17 22:44 ` Alexey Sokolov [this message]
2020-10-17 22:56   ` Aisha Tammy
2020-10-17 23:00     ` Alexey Sokolov
2020-10-18  5:48 ` Michał Górny
2020-10-18  6:29   ` Joonas Niilola
2020-10-18 11:02     ` Aisha Tammy
2020-10-18 13:40       ` Gordon Pettey
2020-10-18 14:17         ` Aisha Tammy
2020-10-18  7:41   ` Ulrich Mueller
2020-10-18  7:39 ` Ulrich Mueller
2020-10-18 12:22 ` Mikle Kolyada
2020-10-18 14:09   ` Aisha Tammy
2020-10-22 20:50 ` Aisha Tammy
2020-10-23  7:50   ` Ulrich Mueller
2020-10-23 10:37     ` Aisha Tammy
2020-10-23 15:36       ` Ulrich Mueller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHK_jdhBq68eaGSqweYmwBRoJKis9MoN+UjQqeu173cUeyFOhw@mail.gmail.com \
    --to=alexey+gentoo@asokolov.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox