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

2022-04-19 Thread Neil Bothwick
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.


pgp0pfOajc8sT.pgp
Description: OpenPGP digital signature


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

2022-04-19 Thread Dale
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

:-)  :-) 



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

2022-04-18 Thread Jack

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?





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

2022-04-18 Thread Peter Humphrey
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.






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

2022-04-18 Thread Peter Humphrey
On Sunday, 17 April 2022 20:17:47 -00 Rich Freeman wrote:
> On Sun, Apr 17, 2022 at 1:05 PM Martin Vaeth  wrote:
> > Peter Humphrey  wrote:
> > > On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
> > >> Peter Humphrey  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.






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

2022-04-17 Thread Rich Freeman
On Sun, Apr 17, 2022 at 1:05 PM Martin Vaeth  wrote:
>
> Peter Humphrey  wrote:
> > On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
> >> Peter Humphrey  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



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

2022-04-17 Thread Peter Humphrey
On Sunday, 17 April 2022 17:05:18 -00 Martin Vaeth wrote:
> Peter Humphrey  wrote:
> > On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
> >> Peter Humphrey  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.






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

2022-04-17 Thread Martin Vaeth
Peter Humphrey  wrote:
> On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
>> Peter Humphrey  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.




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

2022-04-17 Thread Peter Humphrey
On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote:
> Peter Humphrey  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.






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

2022-04-17 Thread Martin Vaeth
Peter Humphrey  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.