1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] Re: systemd-boot on openrc

    From Martin Vaeth@21:1/5 to Peter Humphrey on Sun Apr 17 18:50:01 2022
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote:

    Can't you just fix your USE flags with systemd-utils? Why revert?

    No, because the flag I'd need is 'boot', and that triggers switching from elogind to systemd.

    No, USE=boot for systemd-util does not trigger anything like that.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Sun Apr 17 19:00:01 2022
    On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote:
    Can't you just fix your USE flags with systemd-utils? Why revert?

    No, because the flag I'd need is 'boot', and that triggers switching from elogind to systemd.

    No, USE=boot for systemd-util does not trigger anything like that.

    I meant, if I set that flag, portage wants me to remove elogind andinstall systemd.

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Vaeth@21:1/5 to Peter Humphrey on Sun Apr 17 19:10:01 2022
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote:
    Can't you just fix your USE flags with systemd-utils? Why revert?

    No, because the flag I'd need is 'boot', and that triggers switching from >> > elogind to systemd.

    No, USE=boot for systemd-util does not trigger anything like that.

    I meant, if I set that flag, portage wants me to remove elogind andinstall systemd.

    Maybe, but the fault is certainly not this flag but something else.
    For instance, that you do not have keyworded something which you should have.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Sun Apr 17 19:30:01 2022
    On Sunday, 17 April 2022 17:05:18 -00 Martin Vaeth wrote:
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote:
    Can't you just fix your USE flags with systemd-utils? Why revert?

    No, because the flag I'd need is 'boot', and that triggers switching
    from
    elogind to systemd.

    No, USE=boot for systemd-util does not trigger anything like that.

    I meant, if I set that flag, portage wants me to remove elogind andinstall systemd.

    Maybe, but the fault is certainly not this flag but something else.
    For instance, that you do not have keyworded something which you should
    have.

    Ok. I'll look again in the morning.

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rich Freeman@21:1/5 to martin@mvath.de on Sun Apr 17 22:20:01 2022
    On Sun, Apr 17, 2022 at 1:05 PM Martin Vaeth <martin@mvath.de> wrote:

    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote:
    Can't you just fix your USE flags with systemd-utils? Why revert?

    No, because the flag I'd need is 'boot', and that triggers switching from
    elogind to systemd.

    No, USE=boot for systemd-util does not trigger anything like that.

    I meant, if I set that flag, portage wants me to remove elogind andinstall systemd.

    Maybe, but the fault is certainly not this flag but something else.
    For instance, that you do not have keyworded something which you should have.

    It would probably be helpful to post more relevant output, like
    portage output including --verbose and so on so that it is clear what
    it is actually doing.

    systemd-utils blocks systemd, so I can't see how it could force you to
    install systemd (after all, it just supplies things that are otherwise
    bundled with systemd already). Maybe in addition to setting the boot
    USE flag you also changed something else?

    --
    Rich

    --
    Rich

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Mon Apr 18 18:10:01 2022
    On Sunday, 17 April 2022 20:17:47 -00 Rich Freeman wrote:
    On Sun, Apr 17, 2022 at 1:05 PM Martin Vaeth <martin@mvath.de> wrote:
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
    Peter Humphrey <peter@prh.myzen.co.uk> wrote:
    On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote:
    Can't you just fix your USE flags with systemd-utils? Why revert?

    No, because the flag I'd need is 'boot', and that triggers switching >> > from
    elogind to systemd.

    No, USE=boot for systemd-util does not trigger anything like that.

    I meant, if I set that flag, portage wants me to remove elogind andinstall
    systemd.

    Maybe, but the fault is certainly not this flag but something else.
    For instance, that you do not have keyworded something which you should have.
    It would probably be helpful to post more relevant output, like
    portage output including --verbose and so on so that it is clear what
    it is actually doing.

    systemd-utils blocks systemd, so I can't see how it could force you to install systemd (after all, it just supplies things that are otherwise bundled with systemd already). Maybe in addition to setting the boot
    USE flag you also changed something else?

    The machine is sick. I now have no mouse or keyboard after POST. They're fine in UEFI BIOS setup, and they're fine after the default kernel has finished booting - just not at boot menu time.

    :(

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jack@21:1/5 to Peter Humphrey on Tue Apr 19 05:10:01 2022
    On 4/18/22 22:53, Peter Humphrey wrote:
    On Monday, 18 April 2022 16:05:24 -00 Peter Humphrey wrote:
    The machine is sick. I now have no mouse or keyboard after POST. They're
    fine in UEFI BIOS setup, and they're fine after the default kernel has
    finished booting - just not at boot menu time.
    And now it's perfectly all right. What is one supposed to do in the face of such chaos?

    I confess that the machine is perilously close to being hurled through the window.

    I generally blame such behavior on "phase of the moon and blue magic
    dust."  Is it time to go to your local church to ask if the priest will perform an exorcism?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Tue Apr 19 05:00:01 2022
    On Monday, 18 April 2022 16:05:24 -00 Peter Humphrey wrote:

    The machine is sick. I now have no mouse or keyboard after POST. They're
    fine in UEFI BIOS setup, and they're fine after the default kernel has finished booting - just not at boot menu time.

    And now it's perfectly all right. What is one supposed to do in the face of such chaos?

    I confess that the machine is perilously close to being hurled through the window.

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neil Bothwick@21:1/5 to Dale on Tue Apr 19 09:10:01 2022
    On Tue, 19 Apr 2022 01:09:02 -0500, Dale wrote:

    And now it's perfectly all right. What is one supposed to do in the
    face of such chaos?

    I confess that the machine is perilously close to being hurled
    through the window.

    There were updates to udev and systemd-utils, I wonder if they fixed it.

    Get sledge hammer, bigger is better.  Place sledge hammer beside
    computer.  Use a camera if the puter has one.  Let computer know that is Plan B, there is no Plan C.  :-) 

    I've done it before with hal.  Neil, remember my situation with hal?
    ;-) 

    I try not to :-/


    --
    Neil Bothwick

    Ninety-Ninety Rule Of Project Schedules - The first ninety percent of
    the task takes ninety percent of the time, and the last ten percent
    takes the other ninety percent of the time.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmJeXjUACgkQ92eFu0QS MJirJg//UowYMZDzDcXa+jNR3QdwGgO57S2inOmIP+dCwXtvc+jTXzvvp+r/wzPV 7RE+f08DpHBIOTlMMe82Gb99HLV4tU37GeCBeHhGSicjtRjxjt21HbGYdXMs4Ms7 RozWafVh7w0INu9dfShFBTamXwEaqQm9iHLisFH8lLsaeXWpy3VHT0sNsAakqqGY I+bV5fZtErMORiGh5xKbuJyooNqv6iP0J6zvdxJIyPt3cpX1RC6JfrEICQ9EZbXO 1pdT/Mfc6Dy1qWrGEtiRr8aWvqhxk7e5WhRtK4PXqXX1jG7j502RXypze8aeHPJf i1jupqXyxBTuplNH/1dLixmZf5FpVOm+B2zei/ueMYNGCSV+QIfJnMA7FT8Ial4F VkFYcaWOmOA5buMRRHdof6N1IUqngvLR0njQPl1OobyxIh3c0RqkoRANNdN+xcYv 7TrX19r74hoYsllET52QsxwohS9PPlqFh4CiAaIsxTm3/83PWO+GQVzJH8vHeIl4 h/WP5EzBKnd1PDNckLnjtPSmZuemf+Scdcz2ddTnPJeGUuUB0xCYgjVkfVXqKS1L UmuYsHnoYLAvr5RqGTY0XVAuHQ62RU5DMYoxq1Imb9x2HfZp6gmPcTPVbcmCbGid dQcdpwgNQsw6J1vvP+JZKdl2f3ONKwNcM+c62e6QWPMRQ4f41nQ=
    =H
  • From Dale@21:1/5 to Peter Humphrey on Tue Apr 19 08:20:01 2022
    Peter Humphrey wrote:
    On Monday, 18 April 2022 16:05:24 -00 Peter Humphrey wrote:

    The machine is sick. I now have no mouse or keyboard after POST. They're
    fine in UEFI BIOS setup, and they're fine after the default kernel has
    finished booting - just not at boot menu time.
    And now it's perfectly all right. What is one supposed to do in the face of such chaos?

    I confess that the machine is perilously close to being hurled through the window.



    Get sledge hammer, bigger is better.  Place sledge hammer beside
    computer.  Use a camera if the puter has one.  Let computer know that is
    Plan B, there is no Plan C.  :-) 

    I've done it before with hal.  Neil, remember my situation with hal?  ;-) 

    Hope that helps.

    Dale

    :-)  :-) 

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)