at Nov 26 14:34:50 2022 >>> sys-apps/systemd-252.2
>merge time: 2 minutes and 19 seconds.
>
> Sat Dec 10 20:59:29 2022 >>> sys-apps/systemd-252.3
>merge time: 1 minute and 54 seconds.
>
> Wed Dec 14 13:56:52 2022 >>> sys-a
it right now, unfortunately I get:
# systemctl status ssd-thingies.service
ssd-thingies.service - SSD thingies
Loaded: loaded (/etc/systemd/system/ssd-thingies.service)
Active: failed since Tue, 11 Oct 2011 23:28:05 +0200; 21s ago
Process: 6696 ExecStart=/etc/local.d
On 17/03/12 13:53, Alan Mackenzie wrote:
Hello, Nikos.
On Sat, Mar 17, 2012 at 08:25:48AM +0200, Nikos Chantziaras wrote:
Happy Computer Users, systemd is on your horizon.
No, we don't. I hope systemd arrives soon. It's the best init system I
ever saw.
What's so good about it? What
On Sat, Mar 17, 2012 at 6:48 PM, Nikos Chantziaras rea...@gmail.com wrote:
On 17/03/12 13:53, Alan Mackenzie wrote:
Hello, Nikos.
On Sat, Mar 17, 2012 at 08:25:48AM +0200, Nikos Chantziaras wrote:
Happy Computer Users, systemd is on your horizon.
No, we don't. I hope systemd arrives
Users, systemd is on your horizon.
No, we don't. I hope systemd arrives soon. It's the best init
system I
ever saw.
What's so good about it? What will it do for me?
I have this horrible sneaking suspicion that it will be more
complicated
than /sbin/init + OpenRC, just like udev
don't see the point in preaching systemd's
greatness (or Lennart's). I'm not going to try it anyway. Also, I really
don't see a point in booting fast (and I don't see anything wrong with
openrc). So why do you feel the need to preach? Just curious...
systemd is not just about booting fast
. I stopped using that overlay years ago. It's still maintained?
Must be, it had all the necessary .service files that were missing from
the systemd install. You probably still had those laying around from
when you did use the overlay.
You can also link /etc/systemd/system/display-manager.service
On Friday 11 January 2013, Kevin Chadwick wrote:
On Thu, 10 Jan 2013 23:46:29 +0700
Robin Atwood robin.atw...@attglobal.net wrote:
Thanks for the tips, now I can get more output to tty1 if I want. I
still can't get any systemd messages to syslog-ng, however. A bit of
a mystery
Am 28.01.2013 20:34, schrieb Canek Peláez Valdés:
My gdm USE-flags are:
[ebuild R ~] gnome-base/gdm-3.6.2 USE=audit fallback gnome-shell
introspection ipv6 ldap plymouth systemd tcpd -accessibility
-consolekit -debug -fprint (-selinux) -smartcard {-test} -xinerama 0
kB
The service
that for others ...):
systemd and acpid and Gnome all try to handle suspending my thinkpad to
RAM ... it seems.
So I get the behavior that it suspends fine when I close the lid but
when I open it again I get an immediate suspend *again* ... I then tried
to disable acpid completely, same behavior.
I also
On 27/03/13 at 11:27am, »Q« wrote:
Eventually, as I understand it, GNOME and KDE will require systemd
because they want full control of they system. For people not using
GNOME or KDE, other init systems will still be possible, with either
udev or a udev alternative. I have no idea how far
On Wed, 27 Mar 2013 22:33:05 +0530
Yohan Pereira yohan.pere...@gmail.com wrote:
On 27/03/13 at 11:27am, »Q« wrote:
Eventually, as I understand it, GNOME and KDE will require systemd
because they want full control of they system. For people not using
GNOME or KDE, other init systems
On 27/03/13 at 11:27am, »Q« wrote:
Eventually, as I understand it, GNOME and KDE will require systemd
because they want full control of they system. For people not using
GNOME or KDE, other init systems will still be possible, with either
udev or a udev alternative. I have no idea how
intended.
not possible, logind since systemd = 205 requires systemd and won't
work on openrc, upstart, and such
as in, the idea of using logind outside of systemd is a dead end
so keeping ConsoleKit in portage for long as it works for long as we
need openrc for Linux based systems
and when
On Monday 22 July 2013 21:57:06 Michael Hampicke wrote:
Am 22.07.2013 17:02, schrieb Canek Peláez Valdés:
ConsoleKit is for all practical purposes unmaintained, and all of the
packages you mentioned it support systemd just fine. Emerge systemd,
and purge CK from your system; I did
Am 28.07.2013 10:07, schrieb Stefan G. Weichinger:
Am 28.07.2013 10:04, schrieb Canek Peláez Valdés:
The only special thing I'm doing is to mask sys-apps/systemd-204,
since 205 introduced the new cgroups management code (with systemd as
the only writer of the cgroups hierarchy), and it seems
to lie to people it's somehow solving something currently is
annoying as 'ell and should be corrected where seen.
It is solving the problem of *when* (not if - if the words I have read
from the systemd maintainers can be taken at face value) the systemd
maintainers decide to pull the plug
/systemd/systemd ?
(I am building the initramsfs myself)
You need to get your root filesystem and /usr mounted. Just keep that
goal in mind and start adding files to support it.
There doesn't need to be anything systemd-specific.
I am not sure about timing.
Initially the kernel has only
- pykde4-4.11.0 - USE=script.
(4) udisks - USE=gudev.
(5) then I see :
sys-apps/systemd-206-r3::gentoo (Change USE: +kmod)
virtual/udev-206-r2::gentoo (Change USE: -kmod)
Adding -kmod to the USE list gets 54 pkgs, incl systemd ,
which I've masked in package.mask with sys-fs/systemd
) udisks - USE=gudev.
(5) then I see :
sys-apps/systemd-206-r3::gentoo (Change USE: +kmod)
virtual/udev-206-r2::gentoo (Change USE: -kmod)
Adding -kmod to the USE list gets 54 pkgs, incl systemd ,
which I've masked in package.mask with sys-fs/systemd.
It gets more complex
) udisks - USE=gudev.
sys-apps/systemd, right?
Sorry, it's a busy day. With that correction, I get :
sys-fs/eudev-1.2-r1::gentoo (Change USE: +hwdb +keymap +modutils)
Then 54 pkgs, but eudev for systemd .
Well, with that at least you escape from the newfangled systemd ;)
If I'm
All,
I can clarify one part of the systemd issue, because I have been
involved in this part of the issue for months. Again, I am not trying
to start a dispute here, just providing a clarification.
The choice to install all of the systemd binaries in /usr is not an
upstream choice
On Nov 8, 2013 4:27 PM, Pavel Volkov negai...@gmail.com wrote:
Does sys-fs/udev-init-scripts serve any purpose on a system that:
1. Has systemd installed and openrc uninstalled
2. Has INSTALL_MASK=/etc/init.d/ set in make.conf
I'm asking because sys-fs/udev-init-scripts is a dependency
good by to GDM.
You could *try* to run systemd and see if you like it.
Many of us do.
For the option to try systemd, I would first require a detailed how-to on
how to switch back to OpenRC without requiring reverting to backups or
doing a full reinstall.
Just remove init=/usr/lib/systemd
On Thu, 19 Dec 2013 10:23:05 -0600, Canek Peláez Valdés wrote:
Canek told me off-list that, when using NM, you don't enable dhcpcd,
NM handles it all. Poof and when the smoke cleared ...
The same applies to Wicd, the default systemd config appears to have
broken both in the same way
On Tue, Feb 4, 2014 at 1:58 PM, Joseph syscon...@gmail.com wrote:
Is it possible to go from systemd to udev?
I don't like the way systemd works. I have a problem with mounting USB sick
(it mounts as root:root) and I can not even change the permission.
I am receiving Hylafax fax transmission
On 02/04/14 18:03, Canek Peláez Valdés wrote:
On Tue, Feb 4, 2014 at 1:58 PM, Joseph syscon...@gmail.com wrote:
Is it possible to go from systemd to udev?
I don't like the way systemd works. I have a problem with mounting USB sick
(it mounts as root:root) and I can not even change
On 02/05/14 18:35, Alan McKinnon wrote:
On 05/02/2014 18:32, Joseph wrote:
Which program is responsible for mounting USB stick on XFCE4?
After enable systemd flag in make.conf USE=
the following packages were rebuild:
sys-apps/busybox
sys-apps/dbus
sys-auth/pambase
sys-auth/polkit
sys-fs
, race-free and deterministic way than ConsoleKit.
Do you have systemd with the policykit USE flag? And polkit with the
systemd USE flag? (I suppose the later must have it).
Yes systemd has polkit and polkit has systemd.
If you do, can you please show us the output (make sure to do
On Tue, Feb 18, 2014 at 2:19 AM, Nicolas Sebrecht nsebre...@piing.fr wrote:
The 17/02/14, Canek Peláez Valdés wrote:
It depends; right now you can't switch back and forth between OpenRC
and systemd without reemerging some stuff.
Interesting. Didn't know that. What packages need
On Wed, Feb 19, 2014 at 6:38 AM, Tanstaafl tansta...@libertytrek.org wrote:
On 2014-02-19 2:04 AM, Daniel Campbell li...@sporkbox.us wrote:
For such a profile to be legitimate, systemd would have to be chosen as
the default.
Ridiculous. Forget about Canek's rant...
This is about *choice
On Thu, Feb 20, 2014 at 4:48 PM, Neil Bothwick n...@digimed.co.uk wrote:
I thought I'd have another look at systemd, so switched profiles, made
sure I had all the kernel options needed and then did an emerge -uN world.
It seems the systemd profile masks the static and static-libs USE flags
to change profiles :)
It's not as complex as creating a lot of different systemd profiles
because of inheritance.
I'd also suggest throwing in a test for current running kernel config,
to make sure it fully supports booting with systemd, and maybe a new
emerge command that can also be maintained
with an improved service when it is so closely tied to the
init system.
It is started by the init system, as evidenced by the presence of
systemd-logind.service as well as there being a separate systemd-logind
executable; it is simply replaced by not starting the service, instead,
starting another service
On Thursday, May 22, 2014 04:54:45 AM cov...@ccs.covici.com wrote:
Hi. I am having a strange problem running under systemd since Monday.
I use logwatch to get nice summaries of things going on in the system,
it gives me once a day summaries of such things. When running under
openrc, I used
to require sys-apps/systemd to be pulled in as a
dependency, which I don't want to do.
If I understand the change log below correctly, I should uninstall
sys-power/upower and install sys-power/upower-pm-utils instead. Is that
right? Thanks.
Sounds like Samuli is being a pr*ck by forcing systemd
On 03/06/14 14:30, J. Roeleveld wrote:
Sounds like Samuli is being a pr*ck by forcing systemd on everyone
now. A proper solution would have been to have the upower ebuild
select systemd as a dependency ONLY when the systemd useflag is set.
And depend on upower-pm-utils when it is not set
Am 03.06.2014 22:14, schrieb Alan McKinnon:
This whole systemd thing looks awfully like the switch from a hosts file
to DNS so many years ago.
Not really. What many people bothers about systemd is that it is getting
more and more
a) a hard dependancy for software projects, e.g. like GNOME
infrastructure migrates towards systemd.
That comment right there - specifically the word *infrastructure* - screams
to me 'we intend to take over the world'.
Well, yeah; that has been the objective from day 1. That systemd is
used by default by almost all Linux users and distributions. Nobody
On June 6, 2014 01:27:51 cov...@ccs.covici.com wrote:
Hi. Whenever I issue the command shutdown -h now to shutdown the
system, having booted under systemd, the computer never actually shuts
down. It does stop some services, but eventually just sits there --
about the last one I see
On Sun, Jun 29, 2014 at 3:43 PM, cov...@ccs.covici.com wrote:
What is the significance of the warning when updating to systemd-214
that kernel 3.10 is required? I can't go to that now, what might break?
The README from systemd still says that you need 3.8 [1] (3.0 without
some features); also
Am 28.07.2014 23:20, schrieb Stefan G. Weichinger:
As far as I understand this:
if other ntp-software is installed, systemd-timedated.service uses the
ntp-unit with higher priority (in my current case chronyd.service) for
ntp-syncing.
So you may use the systemd-timedated.service to do
On 09/17/2014 10:40 PM, Mark David Dumlao wrote:
Fact is if it's _you_ that seems to give a tweet about systemd speed,
so it's on _you_ to measure it, I don't really care what you think. The
fact that you think pid1's speed or resource usage might be a big deal
is very indicative on how
On Sun, Sep 21, 2014 at 2:58 AM, Grant Edwards grant.b.edwa...@gmail.com
wrote:
On 2014-09-20, Mark David Dumlao madum...@gmail.com wrote:
The only Linux systems where I care about boot time are embedded
systems which are never going to have the resources needed to run
systemd.
You
On Sat, 15 Nov 2014 15:08:02 -0500, Walter Dnes wrote:
Worth a try. If it does fix it I would consider it a bug since adding
systemd support should not implicitly disable it under openrc.
I disagree. He's telling the build that it's running under systemd,
but there is no systemd
OK,
I decided I'm going to try systemd to see what all the hubbub is about.
I know there are people on here that use it so I'm hoping someone's can
alleviate my concerns on it with mdadm.
I use an IMSM container (Intel fakeraid) as I dual boot with Windows.
This has happily worked for some time
On 11/29/2014 12:19 AM, Mark Pariente wrote:
mdadm works perfectly fine with systemd. I am running a 4-disk RAID-10
configuration and it gets assembled properly by systemd. I have the
ARRAY ... definition in /etc/mdadm.conf and the /dev/mdXXX mount point
in /etc/fstab and AFAICT that's all
On 22/03/2015 03:32, Hans wrote:
On 22/03/15 08:44, walt wrote:
I'd be 100% sure this is a systemd bug except that the problem is so
obvious and (I think) so common that I can't believe I'm the only
systemd user seeing it:
I routinely share /usr/portage over NFS between several gentoo boxes
On Sat, Mar 21, 2015 at 3:38 PM, Daniel Frey djqf...@gmail.com wrote:
[...]
I was using genkernel, but it was whining about not supporting systemd,
so I tried dracut for the first time.
However, the initramfs created by genkernel has the same issue.
I didn't do any special configuation
On 22/03/15 08:44, walt wrote:
I'd be 100% sure this is a systemd bug except that the problem is so
obvious and (I think) so common that I can't believe I'm the only
systemd user seeing it:
I routinely share /usr/portage over NFS between several gentoo boxes
on my wireless network. When I
covered, I think it
could be useful. Could you add a link to it to the main systemd page.
It doesn't help me with the problem I still have running a mixture of
openrc and systemd setups, the different order of the arguments. I still
keep trying to run
systemctl someservice start :(
I
On Tue, Feb 24, 2015 at 3:27 PM, Stefan G. Weichinger li...@xunil.at wrote:
On 24.02.2015 17:01, Rich Freeman wrote:
Seems like there should be a systemd-users mailing list, actually.
This sort of situation is completely distro-agnostic.
Yes! And systemd-devel ml is always kind
Neil Bothwick n...@digimed.co.uk writes:
On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote:
I wonder if the OP is using systemd and trying to read the journal
files?
Nooo, I hate systemd ...
What good are log files you can't read?
You can't read syslog-ng log files without some
On Sun, Aug 2, 2015 at 10:03 AM, walt w41...@gmail.com wrote:
I've been running systemd for a long time without needing to enable
the dhcpcd service at boot time. Starting with systemd-224 that is no
longer true. Today I had to enable dhcpcd.service specifically or the
network interface
On Sun, 2 Aug 2015 08:03:11 -0700, walt wrote:
I've been running systemd for a long time without needing to enable
the dhcpcd service at boot time. Starting with systemd-224 that is no
longer true. Today I had to enable dhcpcd.service specifically or the
network interface didn't get an ip
On Mon, 3 Aug 2015 08:50:24 -0500, Canek Peláez Valdés wrote:
Is this server-related? I have only simple workstations/laptops and I
don't enable systemd-networkd at all. It seems that NetworkManager
takes care of both wired and wireless without assistance (including
dhcp
gt;> It seems to me like this is a portage issue with the resolver.
>> Running emerge -1 python-systemd sounds like it fixes the issue.
>> Apparently once it is installed portage will figure out it needs to
>> hang onto it.
>
> And portage will not let me do that even though I h
t I've commented where I would like to have something similar for
> systemd users. Anybody know how to do that?
>
> We can't count on systemd being installed, so we need to...
>
> 1. Test that systemd is installed.
>
> 2. Check if e.g. spamd is running (depends on #1
On Tue, 9 Feb 2016 13:30:04 + (UTC), James wrote:
> sys-apps/systemd is not even installed, but it shows up as a blocker?
> gentoo-systemd-integration is not installed, but it's a blocker.
It's showing up because it is blocking your update, which means something
you are installing a
-fs/eudev required by @selected
(sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled in by
sys-apps/systemd:0= required by (sys-apps/dbus-1.8.16:0/0::gentoo,
ebuild scheduled for merge)
sys-apps/systemd required by (sys-fs/udisks-2.1.4:2/2::gentoo, ebuild
s
el-printk.conf
>> kernel.printk = 3 4 1 3
>> $
>
> Thanks, I've never seen that before. I wonder why it started on my new
> installation?
You're welcome.
If this is new to you, then my tip might not be useful because I've
been using it with systemd since first using it on Fedora
On Sunday 29 Jan 2017 09:48:47 Daniel Frey wrote:
> On 01/29/2017 05:51 AM, Mick wrote:
> > Hi All,
> >
> > I am trying out a systemd installation on a MackBook Pro and I am not sure
> > the documentation on systemd + microcode is entirely correct. So, I re
quot;-u" or "-@".
> It generally makes sense to use a bootloader with EFI as a result.
+1
When the switch to systemd-boot happened, I grabbed the files needed
to compile it from the systemd tarball and compiled "gummiboot-ng."
But this started failing at some point so I comp
On 2016-12-20 18:57, Rich Freeman wrote:
No, your opinion doesn't affect me because the only thing you've been
contributing is noise.
That's a true word ...
If anything it works the other way around. There seem to be a lot
more Gentoo devs who run systemd who are actively contributing
After 10+ years of LXDE/OpenRC I decided to give Gnome/systemd a try.
1. With OpenRC I used hdparm to put an external USB disk to sleep:
$ cat /etc/conf.d/hdparm
sdb_args="-S24"
Looks like systemd does not provide a unit file for hdparm yet, right? If so I suppose
I'll have to wr
On Tue, Aug 29, 2017 at 1:50 AM, J García <jyo.gar...@gmail.com> wrote:
>
> I would recomed using something like the base livecd or systemrescuecd
> for an install with OpenRC. and only use something like CentOS(if you
> are talking about 7) if you want to use systemd,
On Tue, 12 Dec 2017 18:55:15 +, Alan Mackenzie wrote:
> You seem to know systemd reasonably well - maybe you've got it
> installed and you're using it. Please tell me whether my suspicion
> above (that systemd builds stuff into the system that is likely to be
> superfluo
On Sat, Nov 4, 2017 at 12:17 PM, Nikos Chantziaras <rea...@gmail.com> wrote:
>
> On 04/11/17 18:15, siefke_lis...@web.de wrote:
>>
>> I have a short question to systemd. I would like to ask your experience
>> in the changeover. Was it easy? Were there problems?
>
using either SSH or HTTP,
> whichever you prefer. My one complaint about the systemd journal is
> that there is not, AFAIK, a standalone reader. If I want to boot from
> a live CD, I can only read the logs if it is a systemd live CD, or I
> chroot into the original system. Unless som
Nikos Chantziaras wrote:
> On 25/01/18 04:34, Dale wrote:
>> This is what I would do. I would make sure emerge -uDNp world comes
>> back clean, no remerges or updates. Change profile to generic desktop.
>
> There's no "desktop/systemd" profile. I'm on systemd
On Thu, 2019-08-22 at 10:03 +1000, Adam Carter wrote:
> On Thu, Aug 22, 2019 at 5:48 AM james wrote:
> > On 8/16/19 12:44 PM, Jack wrote:
> > > ps auxf | grep systemd
> >
> > This is new turf for me. Upon issuing this command string I get::
> >
> > #
On Tue, 1 Oct 2019 at 13:18, Mick wrote:
> When using Secure Boot the UEFI firmware check the binaries to be
> loaded have been signed by Microsoft. The 'SHA256 verified' message
> indicates the systemd-boot binary is signed using a key which is
> ultimately signed by Microsoft and
OK, so I conducted another experiment, to see if I was able to make
systemd *not* to work with an exotic combination of underlying
storage. I did the following:
- 4 drives, all of them in RAID5.
- The resulting /dev/md127 was put in a Physical Volume, that in a
Volume Group, and that split into 5
done, because if that were the case, no distro would
have adopted systemd.
They adopted it because of the features it offers.
What features? As far as I can see if we compare to openrc, the only
missed feature is logind for which it is declared to be better than
consolekit. I can't argue here
On Mon, Sep 17, 2012 at 10:45 AM, Stefan G. Weichinger li...@xunil.at wrote:
Am 16.09.2012 20:45, schrieb Canek Peláez Valdés:
This workaround also works in my systemd-only overlay. So, if you have
the systemd flag in any of those four packages, disable it and
everything should work. Just
On Fri, Jan 11, 2013 at 10:42:37AM -0600, Canek Pel??ez Vald??s wrote
No, because the problem has never been in udev (nor systemd, for that
matter). It fixes how *Gentoo* packages udev; probably the devs read
the following comment from Lennart (note it was written almost a month
ago
On Wed, Mar 27, 2013 at 9:38 AM, Jake Margason jmargason...@gmail.com wrote:
I ran away from Arch last year to get away from all this systemd stuff. I
hope that you guys will continue to support openrc for as long as possible.
Don't do top posting, please.
One question though. why does
On 03/27/2013 01:08 PM, Canek Peláez Valdés wrote:
On Wed, Mar 27, 2013 at 9:38 AM, Jake Margason jmargason...@gmail.com wrote:
I ran away from Arch last year to get away from all this systemd stuff. I
hope that you guys will continue to support openrc for as long as possible.
Don't do top
and repair ... just rm it and spin up another instance.
Nothing to 'suspect'... they have made it very clear that that is precisely
where this (systemd) is coming from.
It makes sense in that market ... what doesn't is pushing it into areas
that are not appropriate and people dont want
of guy who *would* expend massive effort to find
a way round current udev and systemd.
[1] I didn't look myself. I have no idea what Exherbo's stance is on
this matter.
Exherbo recommends installing systemd [1]. Sabayon installs systemd by
default [2]. Funtoo is considering running GNOME =3.8
manager and give heart breaking good by to GDM.
You could *try* to run systemd and see if you like it.
Many of us do.
For the option to try systemd, I would first require a detailed how-to on
how to switch back to OpenRC without requiring reverting to backups or
doing a full reinstall.
You
On Wed, Jan 22, 2014 at 7:54 PM, gottl...@nyu.edu wrote:
On Wed, Jan 22 2014, Canek Peláez Valdés wrote:
On Jan 22, 2014 5:55 PM, gottl...@nyu.edu wrote:
Today, on one amd64/systemd machine, I tried updating 3.10.17 to
3.10.25. As expected make oldconfig showed nothing new, so I thought
is logged in, for example by
ssh), nor when using a USB stick.
I repeat my question (if you already answered I apologize), do you
have systemd emerged with the policykit USE flag?
Well, I know more now but understand less :) I recompiled both systemd
and polkit and they both have the correct
. systemd
3. upstart
4. openrc (experimental)
5. One system on Linux, something else on non-linux
6. multiple
It should also be noted that no one in the TC voted OpenRC above
systemd AND upstart, and that while a couple voted systemd below
everything else, it can be argued
On Sat, 7 Jun 2014 11:32:00 +0300
Gevisz gev...@gmail.com wrote:
On Tue, 03 Jun 2014 14:38:34 +0300
Samuli Suominen ssuomi...@gentoo.org wrote:
On 03/06/14 14:30, J. Roeleveld wrote:
Sounds like Samuli is being a pr*ck by forcing systemd on everyone
now. A proper solution would
On 09/22/2014 08:50 PM, Canek Peláez Valdés wrote:
On Mon, Sep 22, 2014 at 7:41 PM, walt w41...@gmail.com wrote:
My main desktop machine is obviously having a brain fart :(
systemd-journald is allegedly obligated to write its journal files
to /var/log/journal/ *if* that directory exists
s. Stop doing that please.
>
> Sorry - here's the full output;
# emerge -a1 =sys-apps/systemd-226-r2 dev-libs/libgudev virtual/libgudev
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] dev-libs/libgudev-230 USE="introspection -debug
(-
Neil Bothwick digimed.co.uk> writes:
>
> On Tue, 9 Feb 2016 16:13:10 + (UTC), James wrote:
>
> > > > sys-apps/systemd is not even installed, but it shows up as a
> > > > blocker? gentoo-systemd-integration is not installed, but it's a
> > > &g
On Monday, 8 April 2019 15:29:47 BST J. Roeleveld wrote:
> On April 8, 2019 1:14:38 PM UTC, Peter Humphrey
wrote:
> >Hello list,
> >
> >Is anyone else having trouble emerging systemd-boot-241? This machine
> >has a small rescue system as an alternative boot, and I get
On April 8, 2019 1:14:38 PM UTC, Peter Humphrey wrote:
>Hello list,
>
>Is anyone else having trouble emerging systemd-boot-241? This machine
>has a
>small rescue system as an alternative boot, and I get a mysterious
>error when
>I emerge the package. The end of the log sh
On Monday, April 8, 2019 4:44:58 PM CEST Peter Humphrey wrote:
> On Monday, 8 April 2019 15:29:47 BST J. Roeleveld wrote:
> > On April 8, 2019 1:14:38 PM UTC, Peter Humphrey
>
> wrote:
> > >Hello list,
> > >
> > >Is anyone else having trouble emergi
On Mon, Apr 8, 2019 at 9:14 AM Peter Humphrey wrote:
>
> Hello list,
>
> Is anyone else having trouble emerging systemd-boot-241? This machine has a
> small rescue system as an alternative boot, and I get a mysterious error when
> I emerge the package. The end of the log shows
January. Another example
>
> Sat Nov 26 14:34:50 2022 >>> sys-apps/systemd-252.2
> merge time: 2 minutes and 19 seconds.
>
> Sat Dec 10 20:59:29 2022 >>> sys-apps/systemd-252.3
> merge time: 1 minute and 54 seconds.
>
> Wed Dec
gt; > [6] default/linux/amd64/17.1/desktop/gnome (stable)
> > [7] default/linux/amd64/17.1/desktop/gnome/systemd (stable)
> > [8] default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr (stable)
> > [9] default/linux/amd64/17.1/desktop/plasma (stable)
> > [10] def
partition in fstab.
The problem is, I think, that systemd tries to activate as soon as
possible the swap partitions, even before
systemd-cryptsetup activates the devices in /dev/mapper.
The solution is to move the swap partition from fstab, and create a
system unit for it which has to wait until
unrecommended - probably because most init.d scripts were never
written with it in mind. A few notes that might be helpful for
anybody trying this out, based on my systemd experiences (where this
is standard functionality, but units are written with this in mind).
Please note that I'm not 100% sure about
On Friday 11 September 2015 15:08:54 walt wrote:
>My very old and slow ~amd64 machine took 3 hours and 45-minutes to
>compile systemd-226 today.
Just out of curiosity: exactly how old? My dual-core amd64 system is almost 9
years old now, and systemd compiles in about 6 minutes:
# gen
problems.
It turns out the systemd units as shipped just simply do not work, at
least for my hardware.
The custom unit I made to apply a new keytable and protocol change was
working fine. After a lot of reading about systemd units and also poring
through logs, I discovered udev was triggering
Am 30.01.2013 18:52, schrieb Canek Peláez Valdés:
On Wed, Jan 30, 2013 at 11:48 AM, Stefan G. Weichinger li...@xunil.at wrote:
Am 30.01.2013 18:36, schrieb Hinnerk van Bruinehsen:
I've just installed systemd on one of my systems to give it a test and I
had similar problems due to the systemd
environment more complicated due to generating an
initramfs.
Absolutely agreed.
Might be a good time to switch to freebsd :-(
I agree. This is the only escape plan against the new wind of
dictation into monolithic approach that comes from systemd sponsors
direction.
Let's see how
801 - 900 of 6173 matches
Mail list logo
