Re: Re: Systemd getting in the way

On Monday, 9 March 2026 00:37:10 Greenwich Mean Time Katalin Rebhan wrote:

> What's the issue you're having with systemd-boot?

I was following the handbook to install a new system, but installing systemd-
utils seemed to require systemd as well. I've tried masking systemd, and 
--excluding it on the command line, but to little avail, by which I mean that 
the whole installation process seemed to revolve around systemd.

> On Monday, 9 March 2026 01:14:53 CET Peter Humphrey wrote:
> > $ eselect profile show
> > 
> > Current /etc/portage/make.profile symlink:
> >   default/linux/amd64/23.0/desktop/plasma
> 
> If you're using the systemd profile, it should pull in sys-apps/systemd. But
> since you're *not* using the systemd profile, you should get systemd-boot
> from sys-apps/systemd-utils and systemd should not be pulled in the first
> place. So FWIW I don't think this has to do with systemd-boot.

So I thought, too, so I was nonplussed when portage seemed to want to insist 
on systemd.

> Are you perhaps switching from the systemd profile to the non-systemd
> profile here?

Nope. New installation.

> Try removing the package.mask entry and then re-running emerge -pcv 
systemd.

I only put it in there to  try to resolve the impasse.

I'm beginning to wonder about the hardware. You know: when all other 
possibilities have been eliminated...
 
-- 
Regards,
Peter.