Re: [gentoo-user] systemd - are we forced to switch?
maybe you should not just believe everything posted. Especially from a systemd fanboi. 2013/7/22 Michael Hampicke m...@hadt.biz 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 that almost a year ago. Thanks, just purged consolekit from my system after setting USE=-consolekit and remerged the affected packages.
Re: [gentoo-user] systemd and initramfs
On Mon, Aug 19, 2013 at 5:58 AM, Helmut Jarausch jarau...@igpm.rwth-aachen.de wrote: Hi, what binaries and libraries have to be put into an initramfs for a system booting with init=/usr/lib/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.
Re: [gentoo-user] LVM2+mdraid5+LUKS+systemd (was Re: LVM2+mdraid+systemd)
On Sep 23, 2013 6:01 AM, Tanstaafl tansta...@libertytrek.org wrote: Man... watching this discussion just makes me want to avoid systemd like the plague/all the more... Please don't top post. After I got LVM2, mdraid, and LUKS working with systemd, I just decided that, for me, neither LVM2, mdraid, nor LUKS are worth it. I don't think I will ever use them. To each his own. Regards.
Re: [gentoo-user] can not mount USB stick as user
On 02/05/14 20:06, Alan McKinnon wrote:
On 05/02/2014 19:03, Joseph wrote:
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/udisks
sys-power/upower
gnome-base/gvfs
But now I have a BIG problem, I can not mount USB stick at all as user
(only as root).
Eject doesn't work either.
fast reply off the top of the head of someone who has never used systemd:
Systemd and udev are tightly interwoven. Did you restart udev?
--
Alan McKinnon
alan.mckin...@gmail.com
Yes, I restarted the system. I don't have udev installed; systemd is
replacing udev isn't it?
Before installing systemd I had to unmerge udev.
Here's how I understand how things work:
There's a body of code called udev which when runs performs a service
called udev.
There's also a body of code called systemd which when it runs is PID 1.
And there's a project called systemd which does all manner of PID 1
things and controls early startup amongst other things. There used to be
a project called udev which has been folded into the systemd project.
Both bodies of code are these days found in a tarball called systemd
from the systemd project which is why you download systemd sources when
installing the Gentoo udev package.
However, systemd doesn't just magically do what udev does out of thin
air. udev is still a functional running service and must be enabled in
systemd for it to run.
Confused yet? English is a hugely overloaded language.
I'm thinking you need systemd with the udev USE flag set.
--
Alan McKinnon
alan.mckin...@gmail.com
If I'm not mistaken my systemd is installed with gudev flag.
sys-apps/systemd-208-r2:0/1 USE=filecaps firmware-loader gudev introspection kmod pam policykit tcpd -acl -audit -cryptsetup -doc -gcrypt -http -lzma -python
-qrcode (-selinux) {-test} -vanilla -xattr ABI_X86=(64) (-32) (-x32) PYTHON_SINGLE_TARGET=python2_7 PYTHON_TARGETS=python2_7 0 kB
--
Joseph
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
On Wed, Feb 19, 2014 at 7:57 AM, Tanstaafl tansta...@libertytrek.org wrote: On 2014-02-18 4:05 PM, Sebastian Beßler sebast...@darkmetatron.de wrote: First I thought that with systemd I have to use all the things shipped with systemd like journald (which I don't like because I think that a binary file for syslogs is just broken) so I looked into the config files of systemd, deactivated journald and configured logging to rsyslog instead. And just like journald many (if not most or even all, I'm still at the surface of systemd configuration) of the new and ugly tools can be replaced by the good old tools we like and love. Thanks Sebastian. I had pretty much come to this same conclusion without even having tried systemd yet. This, combined with the new knowledge that it is relatively trivial to allow peaceful co-existence for systemd users through the use of profiles, and that these would need to be created and maintained by those who want or need the equivalent systemd version of any given profile, now boils down to one last thing... Getting the Gentoo Council behind this idea, and providing an officially supported - or maybe a better term is *mandated* - process whereby systemd proponents can create and then maintain new systemd versions of any existing profiles. Just jumping in here as one of Gentoo's systemd maintainers: There is no point in creating a second set of profiles just for systemd. Profiles do not perform any magic; they just set/mask use flags and set default values for some other ebuild variables. The reason we do not have a full set of systemd profiles is because they would serve no useful purpose; there is simply nothing to be gained from creating them. If I wanted to switch from systemd back openrc at this very moment, I would do the following: 1. Unset the systemd use flag. 2. Replace sys-apps/systemd with sys-fs/udev (optional). 3. Run emerge -uDNav world Having a separate profile does not make that process any easier.
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
On Fri, 21 Feb 2014 11:36:15 +0800 Mark David Dumlao wrote: [...] So, please, don't take it as an insult. In fact you have done a very good job of patiently spelling out the advantages of systemd, to the point I'm no longer afraid of it taking over and devouring the linux world. If systemd truly is, as you say taking over and devouring the linux world such that the majority of distro maintainers are individually choosing to use a feature or two from it, then yes, it definitely is the job of people who want to opt out of it to do the work. If Gnome wants systemd, and you don't, but you want to continue using Gnome, it's _your_ job to look for a method or patch or package or script that makes it work. 1. I do _not_ want to use Gnome (and never used it) as DE. 2. Someone called Lennart was a long-time Gnome contributor before Gnome required systemd without alternative. Coincidence? I don't believe in them. I trust probabilities and statistics. If udev wants systemd, and you don't, but you want to continue using udev, it's _your_ job to look for a method or patch or package or script that makes it work. We have eudev fork which is clean from systemd crapware and works perfectly on production setutps. If foo wants systemd, and you don't, but you want to continue using foo, it's _your_ job to look for a method or patch or package or script that makes it work. If everybody else wants to use systemd but you, it's your job to keep your system working the way you want to. Nobody else requires systemd mandatory now as to my knowledge. Nobody's going to go out of their way to specifically and targettedly break your system, because you don't like their way. However, you can co-opt some package maintainer's way and say he's obligated to make a pure and systemd uncorrupted system for you. Because he's not. Bottom line: since Gentoo's default and primary init system is (and hopefully will be for a very long time) OpenRC, it is on the systemd folks to do the work to get systemd fully supported. systemd IS supported and working. The problem arises when there are people that want to push for a system with no systemd whatsoever and act like it's the systemd maintainer's job to make that happen. OpenRC is default in Gentoo now, and it is my best hope it will be. Thus anyone willing to use something else should do an appropriate job. Best regards, Andrew Savchenko pgpiEf5yXsVgJ.pgp Description: PGP signature
Re: [gentoo-user] systemd-networkd: simpler config for my network
On Monday, 31 March 2014 16:14:44 MSK, Stefan G. Weichinger wrote: Aside from all the discussions around systemd, I simply gave the new systemd-networkd a try. It helped me to simplify my config for my main machine where I run KVM for virtualization and need a network bridge: I browsed through the man pages before and it seemed like systemd-networkd can't yet be configured to enable SLAAC on IPv6 interface. Am I right? And this is such a common configuration...
Re: [gentoo-user] Systemd upower
On 05/06/14 03:22, Alon Bar-Lev wrote: This effected stable tree of Gentoo as well, pulling undesired different layout into stable is something that should have been avoided. It is about time we split the profiles, systemd is not option for people who runs openrc. Indeed, I support the idea of having separate systemd profiles too, could have simply dropped a package.mask entry in base/ then, and then counter-effected it in systemd profiles - Samuli
Re: [gentoo-user] What to put in chroot mtab
On Friday 01 August 2014 10:00:40 Canek Peláez Valdés wrote: ... just for completeness, systemd actually requires /etc/mtab as a link to /proc/self/mounts, so don't be surprised if software in the future in Linux just assumes that. Well, that seems to imply that you can't run a systemd chroot on a systemd or openrc host, no? Because from inside the chroot, what /proc/self/mounts lists is inaccurate. I wouldn't like to be the one who has to write a new installation handbook for systemd-only systems! :) -- Regards Peter
[gentoo-user] Re: [OT] Linus Torvalds on systemd
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 are mistaken. No, I am not. I've helped a friend debug problems on a couple devices running a custom Arch system with systemd. How does that contradict the statement I made that the systems where I care about boot times do not have the resources required to run systemd? -- Grant
Re: [gentoo-user] Re: Get off my lawn?
On Tue, Jan 20, 2015 at 2:58 PM, Marc Stürmer m...@marc-stuermer.de wrote: Zitat von Tom H tomh0...@gmail.com: Lennart claims that the embedded world loves systemd. I suspect that, as in other corners of the Linux world, there are lovers and haters of systemd. Embedded systems also quite often means low on resources, CPU power, memory, space. If you are using hard space constrained systems, the sheer size of systemd in the file system can be a valid reason not to use it at all. So it does depend on the type of embedded system you are looking at. True. I've actually started comparing the direction systemd is moving in with busybox. The latter is of course already popular in embedded environments for the reasons you state. If you really want something super-minimal busybox is probably more of what you're looking for. On the other hand, if you want something more functional but still generally integrated then systemd might be the right solution. RAM use for systemd (plus its deps) seems to be on the order of maybe 2MB or so depending on what features you have resident (journal/etc). Most systemd utilities do not run continuously. Some of the shared memory use for systemd deps may be consumed already depending on what else is running on the system. Many systemd components would not necessarily need to be installed on-disk for an embedded system. For example, command-line utilities used by administrators to control their system might not need to be installed for systemd to still function (you don't need to manually change the runlevel of an embedded device, start/stop modules, etc - and all these tasks can be controlled over dbus without using the binaries on disk so your embedded application can still manage things). I'm not sure how systemd works with glibc alternatives, etc. If you can dispense with a shell entirely by moving to systemd then there could actually be some savings on that end, and performance will certainly be better. This page seems to be a fairly neutral/factual exploration of this issue: https://people.debian.org/~stapelberg/docs/systemd-dependencies.html This isn't really intended as a systemd is the right tool for every embedded solution or systemd is a horrible tool for embedded argument. It just is a tool and in the embedded world you should weigh its pros/cons as with anything else. Most likely an embedded environment is going to be highly-tailored in any case, so you'll be wanting to seriously consider your options for every component. If your embedded device is more like a phone with (relatively larger) gobs of RAM then systemd may be advantageous simply for its ubiquity. -- Rich
Re: [gentoo-user] syslog-ng: how to read the log files
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 reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. -- Neil Bothwick Weird enough for government work. pgpfUGXDctrCx.pgp Description: OpenPGP digital signature
[gentoo-user] openrc-systemd command comparison
Hey all, I've now converted two systems to systemd and so far haven't had too much issues with systemd itself, other than me constantly forgetting commands. Is there a nice table or chart somewhere that lists openrc commands with equivalent systemd commands? That would really help me from bashing my head and then wandering through man pages for a while trying to figure out what I want to do. I'll eventually remember but it would be nice to have something to help me along. My memory sure isn't what it used to be. Dan
Re: [gentoo-user] OK, so not everything works properly with systemd
On Sat, Mar 21, 2015 at 1:21 PM, Daniel Frey djqf...@gmail.com wrote: I also noticed this in the USE flags for systemd: - - sysv-utils : Install sysvinit compatibility symlinks and manpages for init, telinit, halt, poweroff, reboot, runlevel, and shutdown Should I enable that USE flag? It removes sysvinit (and systemd-sysv-utils if it's installed) and turns the listed binaries into symlinks to systemd.
[gentoo-user] Safe systemd "reload" command
I'm planning on adding USE=cron to mail-filter/spamassassin to perform nightly updates. I have a script that works for OpenRC, https://wiki.gentoo.org/wiki/SpamAssassin#Daily_updates but 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 for the commands). 3. Reload or restart the daemon if #1 and #2 hold; or do nothing if one of them doesn't.
Re: [gentoo-user] Re: udev -> eudev
2016-02-09 11:31 GMT-06:00 James <wirel...@tampabay.rr.com>: > emerge -uDvtp @world > shows just a few updates needed but nothing pulling in systemd. What I'm > missing is why the "-systemd" setting in make.conf did not overrule > these missteps? Is there way to set something, anything anywhere > what no packages with require systemd can be installed. I never contiously > overrode that concern. It is my overwhelming concern. NO systemd. > All else is optional. Where's that setting? The hierarchy is package.use > make.conf > profile
Re: [gentoo-user] UEFI booting
On Sun, 28 Aug 2016 10:43:17 +0100, Peter Humphrey wrote: > I'd still like to know where the directory /usr/lib64/systemd/boot/efi > came from though. Surely it's from systemd-boot, it is installed by systemd here. What does qfile tell you? $ qfile /usr/lib/systemd/boot/efi -- Neil Bothwick I get enough exercise just pushing my luck. pgpYREJBNQBOP.pgp Description: OpenPGP digital signature
Re: [gentoo-user] remove gnome/systemd
Am Tue, 12 Sep 2017 17:28:40 -0400 schrieb Mike Gilbert <flop...@gentoo.org>: > I would advise against this INSTALL_MASK setting. It is quite likely > to break things (like sys-fs/udev). No, it's not. I'd consider it a bug if systemd is not installed and another package that doesn't depend on systemd relies on something that is installed in a systemd subdirectory. And for me nothing was broken since several years now. And, like I said, I'm using eudev instead of udev. Heiko
[gentoo-user] Why do systemd scripts get installed with USE="-systemd"?
It looks like systemd scripts often (always?) get installed, regardless
of USE flag settings.
Why would they? Is this a policy?
E.g., in
cat /usr/portage/net-p2p/transmission/transmission-2.92-r2.ebuild | grep
systemd_
systemd_dounit daemon/transmission-daemon.service
systemd_install_serviced "${FILESDIR}"/transmission-daemon.service.conf
why not
if use systemd ; then
systemd_dounit daemon/transmission-daemon.service
systemd_install_serviced "${FILESDIR}"/transmission-daemon.service.conf
fi
instead?
signature.asc
Description: PGP signature
[gentoo-user] Re: Expect a ~15% average slowdown if you use an Intel processor
On 04/01/18 23:39, Nikos Chantziaras wrote: On 04/01/18 18:18, Rich Freeman wrote: For variant 1 the only known vulnerability is BPF which probably next to nobody uses I had to enable various BPF settings in the kernel because systemd wouldn't shut up about it. It prints warning messages during boot that the system doesn't support BPF. After enabling it, systemd was happy and stopped barking at me. https://github.com/systemd/systemd/issues/7188
Re: [gentoo-user] Re: Gentoo as NAS
On Fri, 2021-02-05 at 01:06 +, Grant Edwards wrote: > > The plex-server ebuild appears to require systemd, but it isn't listed > > as a dependency. Am I missing something? > > > Apparently so. The presence of the command systemd_newunit in the .ebuild > > doesn't mean that systemd is required. I am using plex-media-server from this overlay without systemd. It is not required.
Re: [gentoo-user] systemd-boot on openrc
On Sunday, 17 April 2022 12:13:06 -00 Neil Bothwick wrote: --->8 > It looks like this is cause my using mixed keywords, amd64 for udev and > ~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the > blocks? Yes, after keywording several others, thus: ~sys-apps/systemd-tmpfiles-249.9 ~sys-apps/systemd-utils-250.4 ~sys-fs/udev-250 ~virtual/tmpfiles-0-r2 But then, after rebooting because of the udev update, systemd-boot-250-r1 has come in. I can't revert those keywords though, because then I'd have to ditch elogind in favour of systemd. I really do not want to do that. So I have a running system now - thanks. If this gets more complicated in future, I can always try blocking =>sys-boot/systemd-boot-250. > > On another system, ~amd64 openrc, I was > > told to set USE=boot on systemd-utils, so I did that and now when I > > boot I have no mouse or keyboard. > > > > Is this the end of the road for systemd-boot on openrc? > > I think that USE flag just causes the systemd-boot part of systemd-utils > to be built. systemd-boot itself is just a virtual now. It doesn't sound > like that would cause this problem, did you emerge anything X related at > the same time? Nope, nothing else. And I forgot to say that smartd failed to start on that machine too, with nothing in dmesg or /var/log/messages. (I'm working on that machine via ssh.) -- Regards, Peter.
[gentoo-user] Re: A systemd-only Gentoo system
Canek Peláez Valdés caneko at gmail.com writes: But if you are interested in systemd, I think you should try it first in simple setups, and certainly as provided by the Gentoo devs. I'll keep an eye on systemd and keep reading up on it. I like what I read so maybe I'll give it a test drive, when I get some time. thanks, James
Re: [gentoo-user] The End Is Near ... or, get the vaseline, they're on the way!
For more information on why this has been done, see the following URL: http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken s/separate-usr/systemd and udev/ Too bad I'm not a developer. If udev and systemd become mandatory on Gentoo, I'll seriously consider LFS (Linux From Scratch). Maybe even BSD. -- Walter Dnes waltd...@waltdnes.org
[gentoo-user] systemd and gnome3
Does anyone use systemd on gentoo, with gnome3? Would someone share a tarball of /etc/systemd/system with me (off-list) so I could figure out what services and stuff are needed? Tried to follow the wiki-pages, but somehow after logging into gdm the session hangs ... Thanks, Stefan
Re: [gentoo-user] USB automount
On Fri, Sep 14, 2012 at 12:42 AM, Stefan G. Weichinger li...@xunil.at wrote: [snip] Great to hear, thanks so far. Looking forward to his reply Stefan, do you use systemd? David told me that he could only check the bug on monday, so I did a little research on the weekend. I installed Gentoo in a QEMU VM (using gnome-boxes), to see if I could reproduce the bug in a unmodified Gentoo installation (I use my systemd-only overlay). I could reproduce the bug, but I found a reasonable workaround: cat /etc/portage/package.use/no-systemd gnome-base/gdm -systemd gnome-base/gnome-session-systemd gnome-base/gnome-shell -systemd sys-auth/polkit -systemd If those four packages have systemd support disabled, then everything works as expected (the suspend/hibernate options returns, I can mount/umount USB sticks, etc.) If at least one of those packages have the systemd USE flag, then the bug appears. I updated the bug report (and I'm not really sure the bug is in polkit or gnome-shell): https://bugs.freedesktop.org/show_bug.cgi?id=53905 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 to be explicit, the versions are: gnome-base/gdm-3.4.1-r1 gnome-base/gnome-session-3.4.2.1 gnome-base/gnome-shell-3.4.2 sys-auth/polkit-0.107:0 I was really looking forward to use the integration of systemd into GNOME, but I suppose it's still a little green. Hopefully we will find and fix the exact bug soon; meanwhile, this workaround is much more usable than using pmount, pm-suspend, etc. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] systemd question
I just installed and booted with systemd and most services are working normally, except syslog.service and remote-fs.service. Both of those failed on bootup with a No such file or directory error. I can't figure out how to make systemd tell me which files it can't find. Any ideas?
Re: [gentoo-user] [ANNOUNCE] I like systemd now :)
On Mon, Nov 12, 2012 at 5:11 PM, Keith Dart ke...@dartworks.biz wrote: Re 20121112134014.632fa8c7@dartworks.biz20121112134014.632fa8c7@dartworks.bizCADPrc80e46k1JN3jE0Y=Xobbo7Vh6jotc=dnhzLo9-Z_vj+wkw@mail.gmail.com2012192731.149dc082@dartworks.bizCADPrc83TGeegA0UXadMEy=B62xZYOE50bqfw+dxDJ8f=FkPTHA@mail.gmail.com2012185801.58964939@dartworks.bizCADPrc83+5zUQ+GzCSvyHhZa7BZfMqqagZCosktasOY1sdhCx0Q@mail.gmail.com2012175313.54b9acf1@dartworks.bizCADPrc80EwExpbdcJX1a+aE0DA=iopqw-QOaozmUBJCs5FGew-g@mail.gmail.com20121109171149.1d8a3e18@dartworks.biz509D9C62.9040909@gmail.com509D8E00.4030208@coolmail.sek7k1hn$ce6$1...@ger.gmane.org, Canek Peláez Valdés said: Do an equery depends pambase and see what it's trying to pull pambase with consolekit. Perhaps do you have something in /etc/portage/package.use? It seems like polkit is actually the culprit. * These packages depend on pambase: app-admin/sudo-1.8.6_p3 (pam ? sys-auth/pambase) net-misc/openssh-6.1_p1 (pam ? =sys-auth/pambase-20081028) sys-apps/openrc-0.11.5 (pam ? sys-auth/pambase) sys-apps/shadow-4.1.5.1 (pam ? =sys-auth/pambase-20120417) sys-auth/polkit-0.107-r1 (pam ? sys-auth/pambase) (systemd ? sys-auth/pambase[systemd]) (!systemd ? sys-auth/pambase[consolekit]) sys-libs/pam-1.1.6 (sys-auth/pambase) x11-misc/lightdm-1.4.0 (=sys-auth/pambase-20101024-r2) diffing polkit 104 and 107 ebuilds shows some changes in the systemd related USE selection logic. I DO also have the systemd USE flag set. Yet, polkit is requiring pambase with consolekit. Enable the systemd USE flag in polkit and it will not require consolekit: pam? ( systemd? ( sys-auth/pambase[systemd] ) !systemd? ( sys-auth/pambase[consolekit] ) ) That means: you want pam?, then if you want systemd, I require pambase with systemd; otherwise, I require pambase with consolekit. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Systemd and static network
On Thursday 25 July 2013 17:23:56 I wrote: Systemd will not read /etc/conf.d/net like /etc/init.d/net.* scripts do. You need some service that will prepare the network. I personally prefer netctl, it is KISS enough. It was me who asked the devs to add it to the tree :) I tried NM too, it does not work out of the box with systemd, there are several issues.
[gentoo-user] Re: gentoo-systemd-only deprecation
On 28/07/13 11:22, Canek Peláez Valdés wrote: Basically, systemd is now a first class citizen in Gentoo (on par with OpenRC) This is great. Thanks to everyone involved! Does someone know whether a KDE system can work reliably with systemd, or there still issues?
Re: [gentoo-user] [Preliminary report] Gnome-3.8 update works with openrc :)
On 30/07/13 04:13, Mark David Dumlao wrote: walt, are you using pam_systemd? I have a hunch that systemd-logind should still work. nope, logind no longer works with anything else than systemd since 205 we have given up on logind+openrc, that's why gnome also now pulls in systemd at portage
[gentoo-user] Re: gentoo-systemd-only deprecation
On 07/31/2013 11:09 AM, Alan McKinnon wrote: There's an idea floating around that openrc could use systemd unit files but it's still just an idea. I must have crossed the line into grumpy-old-man-hood. That idea is insane. Someone is willing to re-write udev to use Lennart's config files but not Lennart's systemd binary? Go figure.
Re: [gentoo-user] systemd and initramfs
On 08/19/2013 10:58 AM, Helmut Jarausch wrote: Hi, what binaries and libraries have to be put into an initramfs for a system booting with init=/usr/lib/systemd/systemd ? (I am building the initramsfs myself) Thanks for some hints, Helmut my 2c would be to autobuild one using genkernel or dracut and then dissemble it this is because I always forget silly things like the special files dev/tty and sda
[gentoo-user] Re: trouble downgrading systemd and virtual/udev
On 09/25/2013 03:24 PM, gottl...@nyu.edu wrote: I want to downgrade systemd from 207-r2 to 204 (highest stable). I currently have virtual/udev-206-r2 installed, which prevents systemd-204. OK. So I need to downgrade virtual/udev to 200. I thought emerge -1 =virtual/udev-200 =sys-apps/systemd-204 would do it. But this failed (see below) and suggested masking might help. So I added package.mask/systemd, which contains =virtual/udev-201 =sys-apps/systemd-205 and then issued the same emerge as above. But this also failed (see below). What incantation do I need? thanks, allan [blocks B ] sys-apps/systemd (sys-apps/systemd is blocking sys-fs/udev-207) [blocks B ] sys-fs/udev (sys-fs/udev is blocking sys-apps/systemd-207-r2, sys-apps/systemd-204) These conflicts are often so confusing that I emerge -C both of the blocking packages and then re-run the emerge that I really want. In your particular case, if you actually remove both of those packages your machine will not be bootable until you successfully emerge the older versions (obviously) so I strongly recommend using quickpkg to save both packages before removing them. Then, if the worst happens and you can't install the older versions you can re-install the saved binary packages with emerge -K. Another officially unapproved workaround I use when really frustrated is to bypass emerge completely and do this instead: #ebuild /usr/portage/sys-apps/systemd/systemd-204.ebuild merge Sometimes it works :)
[gentoo-user] aiccu and systemd
Does anyone of you successfully use aiccu in these days, especially on systemd-based systems? I miss the functionality of having my very own IPv6-adresses on my thinkpad when I roam, for accessing ressources at home etc. But aiccu doesn't work for me anymore for months, I think. No gentoo-bug on this yet. I get right now: # systemctl status aiccu aiccu.service - Automatic IPv6 Connectivity Client Utility Loaded: loaded (/usr/lib64/systemd/system/aiccu.service; disabled) Active: inactive (dead) Nov 22 11:29:41 enzo systemd[1]: Got notification message for unit aiccu.service Nov 22 11:29:41 enzo systemd[1]: aiccu.service: Got notification message from PID 6932, but reception only permitted for PID 0 Nov 22 11:29:41 enzo aiccu[6932]: [AYIYA-tun-tundev] : (Socket to TUN) started Nov 22 11:29:41 enzo systemd[1]: aiccu.service: cgroup is empty Nov 22 11:29:41 enzo systemd[1]: aiccu.service changed stop-sigterm - dead Nov 22 11:29:41 enzo systemd[1]: Job aiccu.service/start finished, result=done Nov 22 11:29:41 enzo systemd[1]: Started Automatic IPv6 Connectivity Client Utility. Nov 22 11:29:41 enzo systemd[1]: Collecting aiccu.service Nov 22 11:29:43 enzo systemd[1]: Collecting aiccu.service Nov 22 11:29:59 enzo systemd[1]: Collecting aiccu.service What about that part with but reception only permitted for PID 0 ? The unitfile is rather simple ... I will see if I can dig up something more special. Stefan
Re: [gentoo-user] Systemd as drop-in replacement for udev?
Just remove init=/usr/lib/systemd/systemd from your kernel command line, and you can boot your old openrc installation (if you did un unmerge it) That should mean: ..if you did not unmerge it. signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] going from systemd to udev
On Tue, Feb 04 2014, Daniel Campbell wrote: On 02/04/2014 01:58 PM, Joseph 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 reports (email) on all incoming faxes and now these emails are empty. It all start happening after switching to systemd :-( systemd and udev are part of the same project, so I believe what you meant was switching from systemd to OpenRC. I've not made such a switch, but if you remember the steps you took, you can generally just reverse them. That is, emerge openrc again, change the kernel line in GRUB to point to regular init instead of systemd's init, reboot, and things *should* fall into place. USB drives mounting as root sounds like a udev thing rather than a systemd thing, and switching to OpenRC for your init won't fix it afaik. For the devices that you need this behavior for, it might be worth looking into writing some udev rules. You can get a start by consulting `lsusb` output and Googling for 'udev rules' to get a wide variety of guides for writing udev rules. Despite the recent changes to udev by the systemd team, udev still functions mostly the same and most guides will be accurate. I hope this helps! ~Daniel There are changes in USE. -systemd +consolekit If you switched to a systemd profile, switch back. The wiki for going from openRC -- systemd might be helpful https://wiki.gentoo.org/wiki/Systemd allan
Re: [gentoo-user] going from systemd to udev
On Tuesday 04 February 2014 18:38:27 Joseph wrote: I don't have pmount installed, and I'm not sure what XFCE4 is using. How to find out? You said that you have systemd installed, but did you actually *boot* systemd as init (PID 1)?
[gentoo-user] Can't Get Systemd to Work
Hi all. I am having issues with Systemd as well. I added to the GRUB2 configuration file the needed command line to get Systemd to start, but for whatever reason, the kernel is adamant that I must use OrenRC. I recompiled with Genkernel-next a new kernel and initramfs, and that, for whatever reason, doesn't automount my /boot partition. Is there a fix to this?
Re: [gentoo-user] Re: Systemd upower
On Thursday 05 June 2014 13:58:45 Mick wrote: .., I've keyworded sys-power/upower-0.99.0 for now on one machine and it seems to work fine, without imposing systemd at the moment. :-) I bet you have quite a lot of systemd components lurking in the background though, ready to take over the world the next time you aren't looking :-) -- Regards Peter
Re: [gentoo-user] I don't seem to have a system log. Help, please!
One little corner case; if you're running systemd 216 and syslog-ng 3.6, you need to add ForwardToSyslog=yes to /etc/systemd/journald.conf. With systemd 215 and earlier, messages are forwarded to syslog by default, and syslog-ng 3.6 is journald aware.
Re: [gentoo-user] openrc-systemd command comparison
On 04/01/2015 02:21 AM, Neil Bothwick wrote: Nice! Apart from the zap thing that Canek has already covered, I think it could be useful. Could you add a link to it to the main systemd page. I've added it to the See Also section at the end of the Systemd page. I didn't know where else to put it. Dan
[gentoo-user] Re: systemd-224 Look out for new networking behavior
walt w41...@gmail.com wrote: Oops, journalctl tells me that systemd-networkd is segfaulting repeatedly during boot. systemd has become very picky on cflags; e.g. -DNDEBUG and friends cause strange behaviour and segfaults.
[gentoo-user] systemd-224 Look out for new networking behavior
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 address during boot. Seems like this might be especially important for those of you who need to update remote machines.
Re: [gentoo-user] systemD?
On Wednesday, 30 August 2017 22:18:40 BST Rich Freeman wrote: > On Wed, Aug 30, 2017 at 4:39 PM, <mad.scientist.at.la...@tutanota.com> wrote: > > are some of the available kernels not systemd, > > Michael's answer was correct, but I just wanted to note that the > kernel and systemd are really two different things. You don't really > need to do anything special with the kernel to not use systemd. > > If you do use systemd (or openrc) you do need to make sure the kernel > has the required options enabled. The gentoo-sources package has menu > items that automatically select these, both for openrc and systemd. > There really isn't anything special here - lots of software requires > certain kernel features to work. There is generally no harm in > turning on options you don't need. > > You generally won't end up with systemd on Gentoo unless you go > looking for it. If something does pull it in there is usually a way > to avoid it, and somebody around here would be able to help you with > that until you accept your fate and line up for assimilation... BTW, if you run ps axf and come across '/lib/systemd/systemd-udevd --daemon' don't panic. RHL advocates of monolithic stack for Linux haven't taken over your machine, but that's how udev is packaged these days even if you have not installed or enabled systemd on your OS. PS. If you are still uncertain, this trick (I believe it must have been fixed in recent versions of systemd) may crash your systemd running PC :-p https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Is gnome becoming obligatory?
On 15/12/17 01:16, Marc Joliet wrote: > [ Just to be clear: autofs is a Linux kernel feature, systemd just exposes it > in an easy to use way. That is, BTW, a theme with systemd. ] Likewise, cgroups. I believe Lennart is regularly "blamed" for this, but it's been in the kernel a looonngg time, long before systemd. Just not with any easy way of using it. Cheers, Wol
[gentoo-user] Re: Using both Gnome and KDE Plasma?
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. If I switch to the "systemd" profile, then I lose what's in the "desktop" profile.
Re: [gentoo-user] *draft* for setting up network bridge with systemd (for qemu/kvm)
On Tue, Jan 29, 2013 at 2:00 PM, Alon Bar-Lev alo...@gentoo.org wrote: On Tue, Jan 29, 2013 at 9:49 PM, Canek Peláez Valdés can...@gmail.com wrote: I would not bet on that ;) too much resistance. However it is certainly getting better and better: the LWN article on The Biggest Myths about systemd had an overwhelmingly majority of comments positive to systemd, and just a handful of negative comments: http://lwn.net/Articles/534210/#Comments But that is in LWN; Gentoo is way behind, I believe. Gentoo is not behind, it provides you the option of using systemd. However openrc is superior in many ways, as unlike systemd it provides script base metadata vs static systemd units, so for example a service can depend on other services based on LOGIC. Also, it has the nature of virtual dependencies what systemd lacks, for example there are N services that provides timesync, in openrc you provide timesync and depend on timesync, in systemd there is no way to do so. I really should not enter into this discussion (again), and even less with a Gentoo dev (BTW, thanks for all the great work). However, this: for example there are N services that provides timesync, in openrc you provide timesync and depend on timesync, in systemd there is no way to do so it's just a lie (or missinformation). display-manager.service and syslog.service work like this; they are soft links to the desired service (gdm.service and syslog.service, for example), and other units depend on them. They work like virtuals in Gentoo. openrc is working in various environments including embedded, while systemd requires so much dependencies that it is not really usable at all environments. I don't know about all environments, but ProFUSION [1] works in embedded systems and several of its developers are systemd upstream. Also GENIVI, the standardized common software platform for developing in-vehicle infotainment (IVI), uses systemd. openrc can be used correctly in chroot environment, while systemd is inoperative. I know it's not exactly the same, but with systemd we have systemd-nspawn, which I (IMHO) consider far superior: man 1 systemd-nspawn. openrc supports extra commands for services, while systemd enforces only start/stop sequence. I can go on an on. Yeah, OpenRC needs zap, because sometimes a daemon ends unexpectedly, and OpenRC is unable to detect it. I would not call this an advantage, though. Just because there is hype of some branding, does not mean it is better. I believe it's better, but it's only my opinion; it's certainly better for my use-cases. I don't want to impose systemd on anyone, but I would be really happy if I could *easily* uninstall OpenRC from Gentoo, since I don't use it. I'm using an ovelay [2] right now, but is far from optimal. And, BTW, I didn't mean behind in the sense that Gentoo doesn't support systemd; I meant behind in the sense that us systemd users get a lot flak just by mention it in the list. [1] http://www.profusion.mobi/ [2] https://github.com/canek-pelaez/gentoo-systemd-only Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: must I mask gnome-3.8 until I am running systemd
On Fri, Sep 6, 2013 at 1:27 PM, gottl...@nyu.edu wrote: On Thu, Sep 05 2013, Canek Peláez Valdés wrote: On Thu, Sep 5, 2013 at 8:19 PM, walt w41...@gmail.com wrote: On 09/05/2013 05:43 PM, gottl...@nyu.edu wrote: [I will be going to systemd since it is aparently required for gnome-3.8. I first want to try systemd on a test system so am building that one up.] On my main system (currently running openrc) I have masked all of gnome-3.8. I wonder if this was an error and I can remove the mask. Is it the case that 1. Running openrc instead of systemd means you must mask gnome-3.8 or 2. It is ok to emerge gnome-3.8 without a mask but some pieces will stay at 3.6? In other words can I eliminate my file /etc/portage/package.mask/gnome-3.8 with all the 3.8 builds? Well, Canek is the systemd guru in this group, but I have been able to boot my ~amd64 test machine successfully using *either* openrc or systemd. This was a pleasant surprise to me because Canek posted not long ago that openrc is now incompatible with systemd. I'm pretty sure I never said such thing. Both sys-apps/systemd and sys-apps/openrc satisfy virtual/service-manager, so if you installed systemd, OpenRC was depcleaned some days ago, but since bug 373219[1] hasn't been closed, they added OpenRC into the @system set, so now it's not even depcleaned. You can put -*sys-apps/openrc in /etc/portage/profile/package to solve that. No incompatibility, and I never said that. Canek, please correct me if I'm wrong because I'm a bit lost in the details of the gnome3/systemd update at the moment. I believe you can install OpenRC and systemd in parallel without problems. GNOME 3 will pull systemd when installed, but that doesn't mean you will need to uninstall OpenRC. However, several GNOME packages (including gdm, if I'm not mistaken) will fail if not running with systemd as PID=1. I don't know how well it works OpenRC parallel installed with systemd, I haven't used it in years. Regards. [1] https://bugs.gentoo.org/show_bug.cgi?id=373219 Canek, Thanks for this information. But what about my original question, namely Can I remove my masks and let gnome-3.8 replace 3.6 (to the extent portage let's it) while I am running openrc and do *not* have systemd installed? No, you can't: systemd is now a requirement for GNOME 3; gdm-3.8.4 requires systemd unconditionally. If you try to install GNOME 3.8, it will install gdm 3.8.4, which will bring systemd. You cannot install gdm without systemd; therefore, you cannot install gnome-base/gnome without systemd. You could *try* to update the pieces of GNOME to 3.8 that doesn't require systemd, but I don't think that will end happily. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
On Tue, Feb 18, 2014 at 12:31 PM, Tanstaafl tansta...@libertytrek.org wrote: On 2014-02-18 1:14 PM, Canek Peláez Valdés can...@gmail.com wrote: On Tue, Feb 18, 2014 at 12:07 PM, Andrew Savchenko birc...@gmail.com wrote: On Tue, 18 Feb 2014 11:22:23 -0600 Canek Peláez Valdés wrote: Yet again, I respect ones right to use whatever one wants, but I ask to respect mine as well. That's why I propose a separate systemd profile for those willing to use it. Then write. Just be aware that to write a systemd profile, you need to use systemd. Or to create a non-systemd profile :) That's the best response I've read in, like, many years. That's perfect; I'm 100% behind it. I even volunteer to help (with testing) to anyone going for this. Canek, You've referred many times to other programs that *require* systemd. I meant in the Gentoo context (more below). And programs depend on *features* provided by systemd, not PID 1. I don't think any program will ever require a certain PID 1, and I would call that a bug. I'm curious as to the extent of these programs, and to what extent they *truly* require systemd. I don't understand what you mean by the extent of these programs. As to what extent they *truly* require systemd, the don't require systemd the package, they require some of the features provided by it. In particular, logind it's the one being used by GNOME (and Xfce and KDE soon, optionally, as in GNOME). I can't for the life of me think of any reason that server daemons like postfix, dovecot, apache, etc would or could ever *require* systemd. Neither of those packages would ever require systemd (nor any init system). If they do, I would call that a bug. All of those programs can use features provided by systemd (like socket activation, using the more advances features of the journal, etc.), but they can be made optional. I couldn't care less about gnome (don't use it, never used it, don't wanna use it), but what others are there? Well, KDE is talking about doing basically the same as GNOME and using logind. ConsoleKit will be still supported, as is (technically) in GNOME, and I just read that CK is actually being maintained. I don't know if it's getting new features, though, and logind is. Also, for those that do require it, what feature of systemd (that doesn't have an alternative available) is it that the program uses? Again, basically logind. And there *is* ConsoleKit available as an alternative. But basically all the GNOME developers are using systemd, so the CK support is getting bitrotten. That's why the Gentoo GNOME team decided to depend on systemd, although the requirement is really logind. If *someone* creates a logind compatible replacement (it uses a simple dbus API[1]), then even the GNOME suit in Gentoo could drop the requirement for systemd. Ubuntu has been working on something like this, and Mark Shuttleworth said that they will continue to work on it, even with Ubuntu choosing systemd[2], so if/when that's available, there will be no program that *requires* systemd, AFAIK. (Well, gnome-logs depends on the journal, but it's a GUI for a systemd specific feature). Like I've been saying; no one is forcing nothing on no one. But someone has to write/support/maintain the alternative. Regards. [1] http://www.freedesktop.org/wiki/Software/systemd/logind/ [2] http://www.markshuttleworth.com/archives/1316 -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
On Thu, Feb 20, 2014 at 12:18 PM, Tanstaafl tansta...@libertytrek.org wrote: On 2014-02-20 10:55 AM, Canek Peláez Valdés can...@gmail.com wrote: On Thu, Feb 20, 2014 at 6:53 AM, Tanstaafl tansta...@libertytrek.org wrote: while I agree with most everything you said, your primary point - that it should be the people who *don't* want systemd doing all of the work - was backwards, and that was what I wanted to point out. I still believe that a non-systemd profile should be done by the people not wanting to use systemd. But since I now support the systemd profile (since it's trivial) the point is moot. snip Bottom line: since Gentoo's default and primary init system is (and hopefully will be for a very long time) OpenRC, it is on the systemd folks to do the work to get systemd fully supported. Which has been the case up until now. As you have freely admitted that OpenRC being the default init system for gentoo is unlikely to change anytime soon, I'm at a loss as to how you can justify your first comment above? Your comment would only make sense if systemd was made the default init system. OK, I think I get the misunderstanding. This is how I saw the discussion: 1. Some people started to say that systemd should go on its own profile. The people saying that DID NOT wanted to use systemd. 2. I thought that the people using systemd were not interested in making a systemd profile (I was wrong, the profile basically already exists). 3. Since you cannot FORCE no one to work on something, then the burden of work of this systemd profile would have landed on the people NOT WANTING to use systemd. To me, this does not make sense. 4. When someone (don't remember whom) proposed a systemd-sucks profile, I thought that was perfect, because the burden of work then would have landed on the people that want this profile. I even volunteered to help. 5. The moment I saw that the profile is already done, I changed my mind; the people using systemd ALREADY did the work (which seems to be trivial, BTW; I didn't knew that either), therefore no one is trying forcing anyone to do work, then a systemd profile is fine (since it's already done). This is orthogonal to which init system is the default, I think. I was just arguing that if a group A of people want a profile X, that group A of people must do the work to get said profile X working. In the case of systemd, that means *using* systemd, so it made no sense to me that the group A did the work, when they *do not* want to use systemd. Once again, all of this is made moot by the fact that the systemd profile is basically available now. But that does not change my point that if someone wants a X profile, then the burden of work must fall on that someone. Clear now? Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Systemd reaches target Emergency Mode every boot
On Mon, Jan 28, 2013 at 3:08 PM, Stefan G. Weichinger li...@xunil.at wrote:
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 file is the one the package provides. I have gdm.service
as display-manager.service:
# ls -l /etc/systemd/system/display-manager.service
lrwxrwxrwx 1 root root 37 Oct 13 16:48
/etc/systemd/system/display-manager.service -
/usr/lib64/systemd/system/gdm.service
Nothing else, AFAICS.
Thanks. Same here, afaik.
I now get gdm up but I get thrown back after entering my (correct) password.
with xdm.service I am able to start gnome.
Do I have to take special care of polkit/consolekit/pam/whatever?
Yes, we had a long thread about that some months ago, around November.
Basically, there is lots of stuff that break if you mix up consolekit
and systemd (logind, actually). Maybe the situation has improved, but
in my case the simplest solution was to purge consolekit from my
systems (except in my media center, XBMC still uses its d-bus
interfaces). ConsoleKit is unmantained anyway.
I have USE=-consolekit where necessary (basically gdm, pambase and
bluez), and USE=systemd everywhere else. Please note that some
packages need to unmask the systemd flag:
# cat /etc/portage/profile/package.use.mask
media-sound/pulseaudio -systemd
net-misc/networkmanager -systemd
sys-auth/polkit -systemd
sys-fs/udisks -systemd
sys-power/upower-systemd
I believe polkit is the most important, since it's the one controlling
what program can do what, but since I switched completely to systemd
years ago, I just use it everywhere. Things just work most of the
time.
Thanks, Stefan
ps: my bigger hurdle will be the bridging-setup for running
KVM-virtualization. This was one of the reasons to go back to openrc
back then.
I have no experience with that, but if it works in OpenRC it should
work in systemd. Probably better, even.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd and initramfs
On 08/20/2013 08:54:26 AM, Canek Peláez Valdés wrote: On Tue, Aug 20, 2013 at 1:44 AM, Helmut Jarausch jarau...@igpm.rwth-aachen.de wrote: On 08/19/2013 04:55:29 PM, Mike Gilbert wrote: On Mon, Aug 19, 2013 at 5:58 AM, Helmut Jarausch jarau...@igpm.rwth-aachen.de wrote: Hi, what binaries and libraries have to be put into an initramfs for a system booting with init=/usr/lib/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 the mini /usr partition contained within the initramfs. Then it switches to real root and only then it tries to mount the real /usr partition. Does this all happen before the kernel hands control over to the init process (i.e. systemd) ? No, the kernel has a mini filesystem (doesn't matter which directory structure has inside), and it executes the init script (or binary program) in the root of the initramfs. This init program/script is the responsible for mounting the real root and other partitions, and handling control over to systemd (or OpenRC, or whatever). Dracut is able to create an initramfs (with the systemd Dracut module) that executes systemd inside the initramfs, which mounts /usr, switches to the real root, and gives control to the real systemd instance. At shutdown, the reverse happens: the real systemd surrenders control to the initramfs systemd, it umounts everything, and finish the shutdow process. If you generate an initramfs with Dracut using the systemd module, the init inside the initramfs is a link to /usr/lib/systemd/systemd. Unless you want to learn the ins and outs of using an initramfs (and having a lot of fun and failed boots in the process), I highly recommend using Dracut. It does everything for you. Yes, I'd like to generate the initramfs myself and let the kernel store it within its binary on /boot. This has been working just fine with openrc. Now I only need to now the additional requirements when using systemd as init process. I'll have a look at what Dracut is doing. Thanks to you and Alan, Helmut
Re: [gentoo-user] systemd and LUKS
On Tue, Sep 3, 2013 at 6:46 AM, Frank Steinmetzger war...@gmx.de wrote: Hey list after the many discussions here about systemd I had a flash of objectivity (“Who cares if people rant about Lennart, the concept seems sound and I don’t care about separate /usr”). So I wanted to try systemd on my netbook. I cloned the / partition from sda2 to sda7 and chrooted into it. In there I followed the systemd Gentoo wiki¹, i.e. I configured the kernel, installed systemd, added -consolekit systemd to my use flags, rebuilt world with --new-use and added init=/usr/lib/systemd/systemd to the kernel cmdline. Rebooting works until the point of mounting /home, which is a LUKS container. I get the message: A start job is running for dev-mapper-home.service and eventually a timeout and prompt for root password or Ctrl-D. The wiki references a bug report that /etc/crypttab was ignored. Well, I didn’t have one, but apparently my old crypt setup was heeded (because systemd knew that I wanted sda5 mounted as home). Mmmh. I don't use LUKS, but from what I understand, systemd generates the unit files necessary to mount encrypted partitions, and to do this it needs /etc/crypttab, in the same manner that it needs /etc/fstab to generate the unit files for the normal partitions. http://www.freedesktop.org/software/systemd/man/systemd-cryptsetup-generator.html I tried researching the problem. One I found was a Gentoo forum thread about LVM. I found out that I was missing CONFIG_DM_UEVENT. But enabling it didn’t help either. I found files in the partition’s /dev directory, which hinted that DEVTMPFS_MOUNT was not set. But I don’t suppose that’s really a problem. I would add it anyway. Does any of you have experience with this combination and would like to share it? Thanks. ¹ http://gentoo-en.vfose.ru/wiki/Systemd On a sidenote, for some reason, grub2 doesn’t find the kernel if I keep the menuentry’s search commands which are created by grub2-mkconfig. Only if I remove all the search --uuid...yadda yadda..., the entry boots. The boot partition (where the grub files lie) is still my normal / on sda2. It then boots the systemd installation on sda7 which was detected by os_prober. Are you sure it's not under the advanced submenu? One question: how is the /etc/fstab file in the systemd installation? Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: must I mask gnome-3.8 until I am running systemd
On Thu, Sep 05 2013, Canek Peláez Valdés wrote: On Thu, Sep 5, 2013 at 8:19 PM, walt w41...@gmail.com wrote: On 09/05/2013 05:43 PM, gottl...@nyu.edu wrote: [I will be going to systemd since it is aparently required for gnome-3.8. I first want to try systemd on a test system so am building that one up.] On my main system (currently running openrc) I have masked all of gnome-3.8. I wonder if this was an error and I can remove the mask. Is it the case that 1. Running openrc instead of systemd means you must mask gnome-3.8 or 2. It is ok to emerge gnome-3.8 without a mask but some pieces will stay at 3.6? In other words can I eliminate my file /etc/portage/package.mask/gnome-3.8 with all the 3.8 builds? Well, Canek is the systemd guru in this group, but I have been able to boot my ~amd64 test machine successfully using *either* openrc or systemd. This was a pleasant surprise to me because Canek posted not long ago that openrc is now incompatible with systemd. I'm pretty sure I never said such thing. Both sys-apps/systemd and sys-apps/openrc satisfy virtual/service-manager, so if you installed systemd, OpenRC was depcleaned some days ago, but since bug 373219[1] hasn't been closed, they added OpenRC into the @system set, so now it's not even depcleaned. You can put -*sys-apps/openrc in /etc/portage/profile/package to solve that. No incompatibility, and I never said that. Canek, please correct me if I'm wrong because I'm a bit lost in the details of the gnome3/systemd update at the moment. I believe you can install OpenRC and systemd in parallel without problems. GNOME 3 will pull systemd when installed, but that doesn't mean you will need to uninstall OpenRC. However, several GNOME packages (including gdm, if I'm not mistaken) will fail if not running with systemd as PID=1. I don't know how well it works OpenRC parallel installed with systemd, I haven't used it in years. Regards. [1] https://bugs.gentoo.org/show_bug.cgi?id=373219 Canek, Thanks for this information. But what about my original question, namely Can I remove my masks and let gnome-3.8 replace 3.6 (to the extent portage let's it) while I am running openrc and do *not* have systemd installed? thanks, allan
Re: [gentoo-user] can not mount USB stick as user
On 02/05/14 13:06, Canek Peláez Valdés wrote: On Wed, Feb 5, 2014 at 12:38 PM, Joseph syscon...@gmail.com wrote: [ humongous snip ] 4. Using systemd is more than just emerging it; you need to change your init= line in grub-legacy or GRUB2 and reboot. The contents of /proc/1/comm is systemd? I only have this: cat /proc/1/comm init [ snip ] systemctl --all --full Failed to get D-Bus connection: No connection to service manager. loginctl Failed to issue method call: Launch helper exited with unknown return code 1 Joseph, you are not running systemd. You have systemd *installed*, but you are still *running* OpenRC. Therefore, your system is obviously going to fail, since at least some parts of it believe you are running systemd when you are not. If you use GRUB, you need to change its config file and add the following to your kernel command line: init=/usr/lib/systemd/systemd If you are using GRUB2, change /etc/default/grub and modify GRUB_CMDLINE_LINUX so it has init=/usr/lib/systemd/systemd. Then run grub2-mkconfig again. Beware, systemd requires some kernel config options set or it will not work. For systemd 208, these are: AUTOFS4_FS BLK_DEV_BSG CGROUPS DEVTMPFS DMIID EPOLL FANOTIFY FHANDLE INOTIFY_USER IPV6 NET PROC_FS SECCOMP SIGNALFD SYSFS TIMERFD Also, the following kernel config options should *NOT* be set: IDE SYSFS_DEPRECATED SYSFS_DEPRECATED_V2 GRKERNSEC_PROC Lastly, if you have /usr in a different partition from /, you *need* an initramfs (this is now true also for OpenRC). Please check the instructions set in: https://wiki.gentoo.org/wiki/Systemd To finish, let me remark that systemd never had problems in your system. The problem was that you were not running systemd. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México Thank you for correction. You are correct I would need to switch to new systemd. I think for now I'll go back to udev as I'm afraid something might not work after switching :-/ -- Joseph
Re: [gentoo-user] Debian just voted in systemd for default init system in jessie
On 2014-02-18 1:54 PM, Canek Peláez Valdés can...@gmail.com wrote: On Tue, Feb 18, 2014 at 12:31 PM, Tanstaafl tansta...@libertytrek.org wrote: I'm curious as to the extent of these programs, and to what extent they *truly* require systemd. I don't understand what you mean by the extent of these programs. Sorry, worded that badly... I meant, basically, how many programs now require systemd... I can't for the life of me think of any reason that server daemons like postfix, dovecot, apache, etc would or could ever *require* systemd. Neither of those packages would ever require systemd (nor any init system). If they do, I would call that a bug. Then why should XFCE requiring it also not be a bug? I totally get XFCE *supporting* the use of logind, but why should it ever support *only* logind? That would seem insane to me. All of those programs can use features provided by systemd (like socket activation, OpenRC will supposedly soon support the use of sockets... using the more advances features of the journal, etc.), but they can be made optional. Exactly... it is the question of *requiring* it, or *only* supporting it, that doesn't make sense to me. Also, for those that do require it, what feature of systemd (that doesn't have an alternative available) is it that the program uses? Again, basically logind. And there *is* ConsoleKit available as an alternative. Ok, so the numerous times you and others have made comments about the 'many new features' of systemd, you only really meant logind? But basically all the GNOME developers are using systemd, so the CK support is getting bitrotten. That's why the Gentoo GNOME team decided to depend on systemd, although the requirement is really logind. If *someone* creates a logind compatible replacement (it uses a simple dbus API[1]), then even the GNOME suit in Gentoo could drop the requirement for systemd. Ubuntu has been working on something like this, and Mark Shuttleworth said that they will continue to work on it, even with Ubuntu choosing systemd[2], so if/when that's available, there will be no program that *requires* systemd, AFAIK. (Well, gnome-logs depends on the journal, but it's a GUI for a systemd specific feature). Like I've been saying; no one is forcing nothing on no one. But someone has to write/support/maintain the alternative. Excellent... so apparently, the only real new features that have any kind of dependency are logind and maybe journald, so all that would be needed are compatible replacements, and all of the noise about systemd consuming the world has been just that... noise?
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
On Mon, 19 Nov 2018 10:14:01 +0100, Stefan G. Weichinger wrote: > >> upgrading from sys-apps/systemd-236-r5 to 239-r2 > >> > >> the emerge runs through and warns me that it overwrites files ... > >> so it merges only partially ... > > > > What's the exact error message? You may get a suggested solution > > based on this vague description of the problem but it may not be > > the right one, or even safe. > > > > Normally emerge will put up a warning like this before installing > > anything. > > pasted error msg below > > --- > > * Package 'sys-apps/systemd-239-r2' merged despite file collisions. If > * necessary, refer to your elog messages for the whole content of the > * above message. According to this the file collisions were ignore and the updated package installed, so either something else prevented the installation from completing or eix is confused. What version does "qlist ICv systemd" show? How about "ls -ld /var/db/pkg/sys-apps/systemd-*"? > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: > warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: > warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: > warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: > warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) > !!! Failed to copy extended attributes. In order to avoid this error, > !!! set FEATURES="-xattr" in make.conf. > !!! copy > /var/tmp/portage/sys-apps/systemd-239-r2/image/var/log/journal/remote/.keep_sys-apps_systemd-0 > -> /var/log/journal/remote/.keep_sys-apps_systemd-0 failed. > !!! Filesystem containing file > '/var/log/journal/remote/.keep_sys-apps_systemd-0#new' does not > support extended attribute 'system.posix_acl_access' > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: > warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) > /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: > warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) > > * Messages for package sys-apps/systemd-239-r2: > > * CONFIG_CGROUP_BPF:is not set when it should be. > * Please check to make sure these options are set correctly. > * Failure to do so may cause unexpected problems. > > * Messages for package sys-apps/systemd-239-r2: > > * This package will overwrite one or more files that may belong to > other > * packages (see list below). You can use a command such as `portageq > * owners / ` to identify the installed package that owns a > * file. If portageq reports that only one package owns a file then do > * NOT file a bug report. A bug report is only useful if it identifies > at > * least two or more packages that are known to install the same > file(s). > * If a collision occurs and you can not explain where the file came > from > * then you should simply ignore the collision since there is not enough > * information to determine if a real problem exists. Please do NOT file > * a bug report at https://bugs.gentoo.org/ unless you report exactly > * which two packages install the same file(s). See > * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how > * to solve the problem. And once again, please do NOT file a bug report > * unless you have completely understood the above message. > * > * Detected file collision(s): > * > */lib64/libsystemd.so.0.23.0 > */lib64/libudev.so.1.6.11 > */lib/systemd/systemd-time-wait-sync > */lib/systemd/systemd-portabled > */lib/systemd/portablectl > */lib/systemd/systemd-user-runtime-dir > */lib/systemd/libsystemd-shared-239.so > */lib/systemd/portable/profile/trusted/service.conf > */lib/systemd/portable/profile/strict/service.conf > * /lib/systemd/portable/profile/nonetwork/service.conf > */lib/systemd/portable/profile/default/service.conf > */lib/systemd/system/system-update-pre.target > */lib/systemd/system/suspend-then-hibernate.target > */lib/systemd/system/user-runtime-dir@.service > */lib/systemd/system/systemd-time-wait-sync.service > */lib/systemd/system/systemd-portabled.service > */lib/systemd/system/systemd-suspend-then-hibernate.service > */lib/systemd/system/user-.slice.d/10-defaults.conf > */usr/bin/resolvectl > */usr/lib/tmpfiles.d/portables.conf > */usr/share/locale/ja/LC_MESSAGES/systemd.mo > *
Re: [gentoo-user] switch from gnome/systemd to xfce/openrc borked my system
On Mon, Aug 19, 2019 at 10:42 AM Raffaele Belardi wrote: > > Rich Freeman wrote: > > Next time you do something like this, keep in mind that Gnome and xfce > > can co-exist on the same system, and so can openrc and systemd. > > Good point, I did not know, in particular for the init systems I thought it > was exactly > the opposite. > The only area of incompatibility I'm aware of are the sysvinit-compatibility links. Both sysvinit and systemd provide implementations of common utilities like poweroff, halt, reboot, telinit, and so on. There is also init itself. The versions that come with sysvinit are compatible with both sysvinit and systemd. If you don't have sysvinit then systemd can supply these. Systemd itself doesn't require these utilities but they are useful both for compatibility and convenience. (ie "systemctl poweroff" works fine, as does sending the command via dbus, but scripts or sysadmins might prefer to be able to just run "poweroff"). The versions of these supplied by systemd are not compatible with sysvinit. A USE flag toggles whether systemd installs these utilities. If it does then it blocks sysvinit. So, you just have to switch that USE flag to install the two in parallel. If you don't have systemd install "init" then you do need to have a kernel command line to launch systemd directly as init. Offhand I think that is really the only conflict between the two. Systemd doesn't use anything but those compatibility utils from sysvinit but it doesn't mind them being around, and nothing in sysvinit/openrc should even notice that systemd is installed. As long as you set the USE flag appropriately you can dual-boot between the two very easily. The only gotcha is keeping all your configs up-to-date as openrc and systemd store things in different places. When you install systemd it takes a snapshot of many of your openrc settings but that is a one-time operation. Some of those settings are hard to change if systemd isn't running as PID 1 - I think the wiki has instructions for how to do this. -- Rich
Re: [gentoo-user] systemd-boot on openrc
On Sun, 17 Apr 2022 11:41:23 +, Peter Humphrey wrote:
> I've been using bootctl from sys-boot/systemd-boot for several years,
> with some success, but I'm stuck after today's --sync.
>
> First I was told I had to keyword sys-apps/systemd-utils, so I did
> that, but now I get this, which I can't decode:
>
> Calculating dependencies ... . . done!
> [ebuild N~] sys-apps/systemd-utils-250.4::gentoo USE="boot
> (split-usr) sysusers tmpfiles udev (-selinux) -test" ABI_X86="(64) -32
> (-x32)" 10,872 KiB [ebuild U ~] sys-boot/systemd-boot-250::gentoo
> [249.9::gentoo] 0 KiB [blocks b ] (" sys-apps/systemd-utils-250.4) [blocks B ]
> soft blocking sys-apps/systemd-utils-250.4) [blocks B ]
> apps/systemd-utils-250.4)
>
> Total: 2 packages (1 upgrade, 1 new), Size of downloads: 10,872 KiB
> Conflict: 3 blocks (2 unsatisfied)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> (sys-apps/systemd-tmpfiles-249.9-2:0/0::gentoo, installed) pulled in
> by sys-apps/systemd-tmpfiles required by
> (virtual/tmpfiles-0-r1-1:0/0::gentoo, installed) USE="" ABI_X86="(64)"
>
> (sys-apps/systemd-utils-250.4:0/0::gentoo, ebuild scheduled for
> merge) pulled in by
> sys-apps/systemd-utils[udev] required by (sys-boot/systemd-
> boot-250:0/0::gentoo, ebuild scheduled for merge) USE="" ABI_X86="(64)"
>
> (sys-fs/udev-249.6-r2-3:0/0::gentoo, installed) pulled in by
> >=sys-fs/
> udev-232:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>
> (>=sys-fs/udev-232:0/0[abi_x86_64(-)]) required by
> (virtual/libudev-232- r5-2:0/1::gentoo, installed) USE="-systemd"
> ABI_X86="(64) -32 (-x32)"
> >=sys-fs/udev-217 required by (virtual/udev-217-r3-1:0/0::gentoo,
> installed) USE="" ABI_X86="(64)"
>
> This is an amd64 openrc system.
It looks like this is cause my using mixed keywords, amd64 for udev and
~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the
blocks?
> On another system, ~amd64 openrc, I was
> told to set USE=boot on systemd-utils, so I did that and now when I
> boot I have no mouse or keyboard.
>
> Is this the end of the road for systemd-boot on openrc?
I think that USE flag just causes the systemd-boot part of systemd-utils
to be built. systemd-boot itself is just a virtual now. It doesn't sound
like that would cause this problem, did you emerge anything X related at
the same time?
--
Neil Bothwick
without C people would code in Basi, Pasal and Obol
pgpalhNg49Ji2.pgp
Description: OpenPGP digital signature
[gentoo-user] Re: systemd-boot on openrc
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] [ANNOUNCE] I like systemd now :)
Re 20121109171149.1d8a3e18@dartworks.biz20121109171149.1d8a3e18@dartworks.biz509D9C62.9040909@gmail.com509D8E00.4030208@coolmail.sek7k1hn$ce6$1...@ger.gmane.org, Canek Peláez Valdés said: Just a word of advice: if you are a normal laptop user, systemd has replaced most of the functionality of consolekit; so if you boot with systemd, several packages need to have enable the systemd USE flag (and the consolekit one disabled). In particular, pambase and polkit need to set either systemd or consolekit, but cannot set both. Thanks for the advice! So now I'm motivated to go do it. :) -- Keith -- -- ~ Keith Dart ke...@dartworks.biz public key: ID: 19017044 http://www.dartworks.biz/ =
Re: [gentoo-user] Re: [ANNOUNCE] I like systemd now :)
On Sun, Nov 11, 2012 at 01:49:03PM +0100, Volker Armin Hemmann wrote: hate is a natural reaction if something you don't need and don't want is forced upon you. If it is also based on lies, hate is a valid reaction. A lot of people don't need nor want pulseaudio or systemd. Now it is forced on everybody. When systemd devs took over udev, one was told that of course, one could use udev without [systemd] in the future. Now they are talking about making udev systemd only. -- #163933 -- Happy Penguin Computers ') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] systemd - are we forced to switch?
On 22 July 2013 21:57, Michael Hampicke m...@hadt.biz 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 that almost a year ago. Thanks, just purged consolekit from my system after setting USE=-consolekit and remerged the affected packages. Do you have systemd enabled? I mean USE=systemd. What is going to happen if my system does not have consolekit? -- -- Csanyi Andras (Sayusi Ando) -- http://sayusi.hu -- http://facebook.com/andras.csanyi -- Trust in God and keep your gunpowder dry! - Cromwell
[gentoo-user] Re: systemd - are we forced to switch?
On 23/07/13 08:43, Samuli Suominen wrote: On 23/07/13 00:46, Mark David Dumlao wrote: This would be a lot less of an issue if someone just wrote a logind ebuild (wink wink) that provides consolekit like it was originally 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 it no longer works, the contingency plan is to ship vendor based polkit files that possibly either restore 'plugdev' group or provide similar groups to ArchLinux like 'network', 'storage', 'power' to split up the old 'plugdev' Wouldn't it be better to switch to systemd instead?
Re: [gentoo-user] how to tell you are using systemd?
On Wed, Jul 31, 2013 at 9:39 PM, Wang Xuerui idontknw.w...@gmail.com wrote: 在 2013-8-1 上午10:26， cov...@ccs.covici.com写道： Can a shell script tell if systemd is the init? I have a couple of places where it would be nice to know this. Thanks in advance for any suggestions. Check /proc/1/comm or something like that, IIRC... Yep: if grep -q systemd /proc/1/comm; then echo systemd else echo not systemd fi Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] installing systemd
(I brought an old system upto the state of my real one and am trying to follow the wiki for converting to systemd). I am upto the part where the wiki says emerge --ask systemd I believe the wiki left out unmerging or something since the emerge gives conflicts (as expected). What must I unmerge? The emerge --ask systemd, specifically mentions a conflict with consolekit, which it states is pulled in by polkit and pambase. I tried adding these last three to package.mask hoping that the emerge would propose uninstalling them while installing systemd, but that didn't happen. What is/are the step(s) I am missing. thanks, allan
Re: [gentoo-user] Au revoir, gnome-3.8
On Tue, Aug 06 2013, Samuli Suominen wrote: that's only because gnome 3.8 hasn't been stabilized yet. as in, there are no plans in keeping gnome 2.x available after gnome 3.8 stabilization. Am I correct in believing that gnome-3.8 (whether in testing as now, or stable later) requires init=systemd? I am converting an old ~amd64 machine to systemd for practice so that I can convert my main laptop (also ~amd64) to systemd. The purpose of the conversions is to run gnome-3.8 and higher. I have other machines running stable. Will I need to convert them to systemd when gnome-3.8 becomes stable and if so will the systemd wiki be expanded. thanks, allan
Re: [gentoo-user] systemd and initramfs
On 08/19/2013 04:55:29 PM, Mike Gilbert wrote: On Mon, Aug 19, 2013 at 5:58 AM, Helmut Jarausch jarau...@igpm.rwth-aachen.de wrote: Hi, what binaries and libraries have to be put into an initramfs for a system booting with init=/usr/lib/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 the mini /usr partition contained within the initramfs. Then it switches to real root and only then it tries to mount the real /usr partition. Does this all happen before the kernel hands control over to the init process (i.e. systemd) ? Many thanks, Helmut
Re: [gentoo-user] trouble emerging (*not* running) systemd on stable amd64
On Fri, Dec 06 2013, Canek Peláez Valdés wrote: On Fri, Dec 6, 2013 at 8:45 AM, gottl...@nyu.edu wrote: I hadn't synced one of my stable boxes for a while and tried today. This brings in gnome-3.8 and with it systemd. I realize I will need to *run* systemd to go to gnome-3.10. Indeed I do run systemd on my two main systems (~amd64). The merge of systemd generates the following near the end of build.log. Cannot open src/hostname/org.freedesktop.hostname1.policy: No such file or directory That is weird. Have you tried to emerge it with MAKEOPTS=-j1? Bingo! Sorry for the noise. allan
Re: [gentoo-user] trouble emerging (*not* running) systemd on stable amd64
On Dec 6, 2013 9:20 PM, gottl...@nyu.edu wrote: On Fri, Dec 06 2013, Canek Peláez Valdés wrote: On Fri, Dec 6, 2013 at 8:45 AM, gottl...@nyu.edu wrote: I hadn't synced one of my stable boxes for a while and tried today. This brings in gnome-3.8 and with it systemd. I realize I will need to *run* systemd to go to gnome-3.10. Indeed I do run systemd on my two main systems (~amd64). The merge of systemd generates the following near the end of build.log. Cannot open src/hostname/org.freedesktop.hostname1.policy: No such file or directory That is weird. Have you tried to emerge it with MAKEOPTS=-j1? Bingo! Sorry for the noise. It's not noise; it's a bug, either in systemd's build sys or in the ebuild. Regards.
[gentoo-user] Re: Wireless fixed (network-manager but NO dhcpcd)
On Thu, Dec 19 2013, Neil Bothwick wrote: On Wed, 18 Dec 2013 20:07:16 -0500, gottl...@nyu.edu wrote: Switched to systemd and all was well for weeks. Then failure occurred (non-global ctrl_ifname). Tried network-manager (NM) with no success. New. 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. Maybe something should be added to the systemd wiki page to cover this. I added the comment about NM to the systemd wiki (It was already in the NM wiki; shamefully I didn't see it). The systemd wiki doesn't mention wicd so I didn't include anything about it. allan
Re: [gentoo-user] can not mount USB stick as user
On 02/05/14 14:02, Canek Peláez Valdés wrote: On Wed, Feb 5, 2014 at 1:55 PM, Joseph syscon...@gmail.com wrote: On 02/05/14 13:06, Canek Peláez Valdés wrote: On Wed, Feb 5, 2014 at 12:38 PM, Joseph syscon...@gmail.com wrote: [ humongous snip ] 4. Using systemd is more than just emerging it; you need to change your init= line in grub-legacy or GRUB2 and reboot. The contents of /proc/1/comm is systemd? I only have this: cat /proc/1/comm init [ snip ] systemctl --all --full Failed to get D-Bus connection: No connection to service manager. loginctl Failed to issue method call: Launch helper exited with unknown return code 1 Joseph, you are not running systemd. You have systemd *installed*, but you are still *running* OpenRC. Therefore, your system is obviously going to fail, since at least some parts of it believe you are running systemd when you are not. If you use GRUB, you need to change its config file and add the following to your kernel command line: init=/usr/lib/systemd/systemd If you are using GRUB2, change /etc/default/grub and modify GRUB_CMDLINE_LINUX so it has init=/usr/lib/systemd/systemd. Then run grub2-mkconfig again. Beware, systemd requires some kernel config options set or it will not work. For systemd 208, these are: AUTOFS4_FS BLK_DEV_BSG CGROUPS DEVTMPFS DMIID EPOLL FANOTIFY FHANDLE INOTIFY_USER IPV6 NET PROC_FS SECCOMP SIGNALFD SYSFS TIMERFD Also, the following kernel config options should *NOT* be set: IDE SYSFS_DEPRECATED SYSFS_DEPRECATED_V2 GRKERNSEC_PROC Lastly, if you have /usr in a different partition from /, you *need* an initramfs (this is now true also for OpenRC). Please check the instructions set in: https://wiki.gentoo.org/wiki/Systemd To finish, let me remark that systemd never had problems in your system. The problem was that you were not running systemd. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México Thank you for correction. You are correct I would need to switch to new systemd. I think for now I'll go back to udev as I'm afraid something might not work after switching :-/ Why don't you give it a try? You are almost there. When booting, edit the grub entry and add init=/usr/lib/systemd/systemd. If it works, great; otherwise, you reboot and get back to where you were. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México I've tried to switch my backup system to systemd by adding line init=/usr/lib/systemd/systemd to grub donfig and as I suspected the system did not boot. I got a kernel paanic. can not open root device hda3 or unknown block (0,0): error -6 -- Joseph
[gentoo-user] systemd and USE=static
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, which are needed by crytsetup and lvm for my initramfs, which mounts / from a LUKS partition. Forcing an unmask of these flags in /etc/portage/profile did no good because when those packages are built with USE=static they require a virtual/udev with matching flags, which systemd cannot provide. Is there a way around this or have a I found a reason for not using systemd that doesn't involve name calling? :-O -- Neil Bothwick Genius is 99% inspiration and 2% arithmetic signature.asc Description: PGP signature
Re: [gentoo-user] Peeve - finding kernel config options
On Wed, 26 Feb 2014 16:41:22 -0500, Tanstaafl wrote: Run make menuconfig Press / Type FHANDLE Then you can see it is enabled by switching on systemd support in the Gentoo specific options. I did say that I know how to search - that is how I was able to find it. But... I don't WANT to switch on systemd support. All that does is enable options needed by systemd, and udev is part of systemd. It's nothing more than a convenient shortcut, it doesn't install systemd. On the first system I tried to do this on, I needed to enable that option before the FHANDLE option even showed up. -- Neil Bothwick Experience is directly proportional to the value of equipment destroyed. signature.asc Description: PGP signature
[gentoo-user] Re: sys-power/upower-pm-utils
On Tue, 03 Jun 2014 11:30:11 + J. Roeleveld jo...@antarean.org wrote: Sounds like Samuli is being a pr*ck by forcing systemd on everyone now. AIUI from https://forums.gentoo.org/viewtopic-t-992290.html, no one is maintaining systemd-independent power management anywhere upstream any more. As of now, the upower 0.9 git branch still serves non-systemd users, but without any guarantee that will continue. Meanwhile, Samuli is giving us udev without systemd, not something he'd spend his time on if his goal were to force systemd on everyone.
Re: [gentoo-user] [OT] Linus Torvalds on systemd
Am 17.09.2014 um 21:02 schrieb Canek Peláez Valdés: On Wed, Sep 17, 2014 at 1:36 PM, Volker Armin Hemmann volkerar...@googlemail.com wrote: [snip] Now you use this to advertise for systemd? Systemd fanbois are becoming more and more desperate. So, systemd is used (or it has been announced that is going to be used) by default in all the major distributions, is available and working great in Gentoo, and many Gentoo users and developers use it happily. So, yeah, we are *really* desperate, obviously. Thanks for the laugh. Regards. you will stop laughing when redhatpoettering abandon systemd because it is 'fundamentally broken' and must be replaced with something else. Probably as soon as everybody got used to it. And if I guess correctly, pulseaudio will be the driving force behind it. Because history loves repetition.
Re: [gentoo-user] Re: [OT] Linus Torvalds on systemd
On Thu, 18 Sep 2014 07:19:21 +0200, Alan McKinnon wrote: Is systemd starting to encompass too much? I think so, but who cares? If we want an init manager that reads systemd-like files but doesn't do anything else (hostnamectl, logging, udev, etc.), I guess we'll have to make one. or trim it back. Conceptually, it shouldn't be too hard to remove those extra services leaving only an init manager. Reading posts over the years (I don't use systemd) most of that stuff can be disabled by config in systemd anyway A lot of it is disabled by default anyway, you have to turn it on if you want to use it. Otherwise it's just there. -- Neil Bothwick - We are but packets in the internet of Life- signature.asc Description: PGP signature
Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
On 11/14/2014 12:46 PM, Alan McKinnon alan.mckin...@gmail.com wrote: On 14/11/2014 18:18, Helmut Jarausch wrote: The only unusual message is Systemd is not detected as the running init system; which is true since I still use openrc (but with systemd installed, as well) Could this be the culprit? I doubt it, I also use 3.6.1 without systemd. But did you miss that: a) he has it installed, and b) he gets a message about 'systemd is not detected as the running init system' ? Maybe it is trying to use systemd but since it isn't running?
Re: [gentoo-user] Does systemd work with mdadm?
On Sat, Nov 29, 2014 at 8:44 PM, Daniel Frey djqf...@gmail.com wrote: So far, it's better than openrc in that there's a bug shutting down an imsm raid that's still not been addressed. It causes the array to do a rebuild next time it starts up and from my testing systemd doesn't have this issue. I can't speak to that particular bug but one of the nice things systemd does if you're using dracut is that during shutdown systemd will pivot back to the original initramfs and cleanly unmount root and so on. This allows a complete shutdown of things like lvm/mdadm/etc if done properly. When I first started using systemd I actually noticed the improvements in shutdown more than startup (parallel openrc is already pretty decent). -- Rich
Re: [gentoo-user] Custom ebuilds for CoreOS
On Mon, 1 Dec 2014, Neil Bothwick wrote: On Mon, 1 Dec 2014 20:46:54 + (UTC), James wrote: Given that CoreOS have sponsored some systemd development (systemd-networkd), I think it is reasonable to assume they plan to stick with systemd for the foreseeable future. CoreOS a gentoo derived distro, had made a very elegant use of 'systemd'. systemd consists of 'unit' and 'target'. 'unit' is config file containing 'docker run' command. 'target' is the grouping mechanism (equiv to fig.yml and upcoming 'docker group' command) systemtd is exclusively used to manage the lifecycle of 'docker' containers ! thanks Saifi.
Re: [gentoo-user] Re: minimal installation CD iso is where?,
2015-08-06 10:34 GMT-06:00 James wirel...@tampabay.rr.com: I think the Handbook is getting better and better. However the systemd-openrc choice is something that needs to be explained early in the handbook from a neutral prospective. Let's face it, lots of folks become interested in Gentoo, often when they hear that you do not have to run systemd. I'm not saying push one over the other, but explain and delineate that choice *early* in the handbook. WE owe the larger linux community that wisdom:: that gentoo has made peace with systemd and openrc:: imho. OpenRC is there on the stage3, systemd isn't, if you don't think about systemd you get an OpenRC installation, I think it would confuse more people to talk about choosing init system(especially noobs) right at the beginning of the handbook.
[gentoo-user] a few blockers I can't figure out
Hi. On my latest update of world, I have a few blockers which I am unable to figure out how to solve -- I will put the related output below with inserted comments. I am using unstable gentooand I have masked ncurses-6 for the time being. Portage also wants to downgrade my systemd from 221(0/2) to 219_p112(0/2). [blocks B ] sys-apps/systemd[gudev(-)] (sys-apps/systemd[gudev(-)] is blocking dev-libs/libgudev-230) [blocks B ] sys-apps/sysvinit (sys-apps/sysvinit is blocking sys-apps/systemd-219_p112) [blocks B ] dev-libs/libgudev (dev-libs/libgudev is blocking sys-apps/systemd-219_p112) Total: 75 packages (64 upgrades, 1 downgrade, 7 new, 2 in new slots, 1 reinstall), Size of downloads: 273,248 KiB Conflict: 3 blocks (3 unsatisfied) !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: media-libs/x264:0 (media-libs/x264-0.0.20150820:0/148::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) If I mask this off, this one goes away, but why is it trying to pull it? (media-libs/x264-0.0.20140308:0/142::gentoo, installed) pulled in by =media-libs/x264-0.0.20090923:0/142= required by (media-video/vlc-2.2.1:0/5-8::gentoo, installed) ^^^ (and 3 more with the same problem) net-firewall/iptables:0 (net-firewall/iptables-1.4.21-r3:0/10::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) And same for this one. (net-firewall/iptables-1.4.21-r1:0/0::gentoo, installed) pulled in by =net-firewall/iptables-1.4.20:0/0= required by (sys-apps/iproute2-4.1.1:0/0::gentoo, installed) ^ It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (sys-apps/sysvinit-2.88-r7:0/0::gentoo, installed) pulled in by =sys-apps/sysvinit-2.86-r6 required by (sys-apps/openrc-0.17:0/0::gentoo, installed) =sys-apps/sysvinit-2.87-r3 required by (sys-kernel/dracut-043-r2:0/0::gentoo, installed) (sys-apps/systemd-219_p112:0/2::gentoo, ebuild scheduled for merge) pulled in by sys-apps/systemd required by (media-sound/mpd-0.19.9-r1:0/0::gentoo, installed) =sys-apps/systemd-204[pam] required by (sys-auth/pambase-20150213:0/0::gentoo, installed) sys-apps/systemd:0/2= required by (net-fs/samba-4.1.19:0/0::gentoo, installed) =sys-apps/systemd-44:0= required by (x11-misc/colord-1.2.11:0/2::gentoo, installed) sys-apps/systemd required by (sys-apps/util-linux-2.26.2:0/0::gentoo, installed) =sys-apps/systemd-209 required by (sys-process/procps-3.3.10-r1:0/0::gentoo, installed) sys-apps/systemd:0/2= required by (net-nds/rpcbind-0.2.3:0/0::gentoo, installed) sys-apps/systemd required by (app-admin/syslog-ng-3.7.1:0/0::gentoo, ebuild scheduled for merge) =sys-apps/systemd-44:0/2= required by (x11-misc/colord-1.2.11:0/2::gentoo, installed) sys-apps/systemd:= required by (net-nds/rpcbind-0.2.3:0/0::gentoo, installed) sys-apps/systemd required by (gnome-base/gnome-settings-daemon-3.16.3:0/0::gentoo, ebuild scheduled for merge) sys-apps/systemd required by (sys-fs/udisks-2.1.6:2/2::gentoo, installed) sys-apps/systemd required by (net-wireless/bluez-5.33:0/3::gentoo, installed) sys-apps/systemd:0= required by (gnome-base/gvfs-1.24.2:0/0::gentoo, ebuild scheduled for merge) sys-apps/systemd:0= required by (net-fs/samba-4.1.19:0/0::gentoo, installed) =sys-apps/systemd-212-r5:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] (=sys-apps/systemd-212-r5:0/2[abi_x86_32(-),abi_x86_64(-)]) required by (virtual/libudev-215-r1:0/1::gentoo, installed) sys-apps/systemd:0= required by (sys-auth/polkit-0.113:0/0::gentoo, installed) =sys-apps/systemd-197 required by (app-admin/openrc-settingsd-1.0.1:0/0::gentoo, installed) sys-apps/systemd required by @selected sys-apps/systemd[python(-),python_targets_python2_7(-)?,python_single_target_python2_7(+)?,python_targets_python3_3(-)?,python_single_target_python3_3(+)?,python_targets_python3_4
Re: [gentoo-user] a few blockers I can't figure out
On Tue, Sep 1, 2015 at 5:55 AM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > Got it, finally :-) > > fail2ban wants sys-apps/systemd[python(-)], and systemd-219_p112 is the > highest version with an explicit python USE flag. All later versions do > not have the flag at all. > > Your choices are either to have fail2ban fixed to deal with recent > systemd USE, and tolerate the systemd downgrade meanwhile; or to replace > fail2ban with something equivalent > Sounds like this is covered by: https://bugs.gentoo.org/show_bug.cgi?id=558168 https://bugs.gentoo.org/show_bug.cgi?id=02 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. -- Rich
[gentoo-user] Re: udev -> eudev
Jc García gmail.com> writes: > >> What I'm > >> missing is why the "-systemd" setting in make.conf did not overrule > >> these missteps? Is there way to set something, anything anywhere > >> what no packages with require systemd can be installed. > > The hierarchy is package.use > make.conf > profile > I forgot USE as environment variable, so: > USE(env) > package.use > make.conf > profile Hmmm. Remember I posted that this package.use setting besides make.conf -system was there for a long time now:: # cat /etc/portage/package.use/package.use | grep systemd sys-apps/dbus -systemd So where does the magic "-systemd" setting go to override all? You know, one ring to rule them all? James
Re: [gentoo-user] Gummiboot -> efibootmgr
On Mon, 22 Aug 2016 15:59:41 +, J. Roeleveld wrote: > I really don't understand the urgency in treecleaning gummiboot. > Like grub1, it will still work in 10 years time... I agree, just copy it to a local overlay. If a serious bug does arise, you then have the choice of trying to persuade someone to backport the fix from systemd or switch bootloaders. I've no idea how tightly bootctl (as gummibot is now called after its assimilation in the the systemd collective) is bound to systemd. It may well be feasible to create an ebuild that builds bootctl from the systemd sources without the rest of systemd, as is already done with udev. -- Neil Bothwick Experience is what you get when you didn't get what you wanted. pgpp7BdDVLreW.pgp Description: OpenPGP digital signature
Re: [gentoo-user] GPT partitions
> The names are suggestive enough, but I have no clue about what does it > mean to use 8304 instead of just plain 8300 for /. The reason is that with efi bootloader the partitions with that GUID in the GPT table are automatically mounted by systemd-gpt-auto-generator. Here some links: https://www.freedesktop.org/software/systemd/man/systemd-gpt-auto-generator.html[1] https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/[2] bic -- Jabber: bi...@jabber.otr.im Key fingerprint = DCBA CE20 0322 934F 0E3E D20B DD13 1F6B 26AF 477B [1] https://www.freedesktop.org/software/systemd/man/systemd-gpt-auto-generator.html [2] https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/
Re: [gentoo-user] Portage spokes again...
On Wed, Dec 21, 2016 at 05:25:20AM +0100, meino.cra...@gmx.de wrote > sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo, > ebuild scheduled for merge) > > > For more information about Blocked Packages, please refer to the following > section of the Gentoo Linux x86 Handbook (architecture is irrelevant): > > > I have no systemd installed...my Linux is running good ole openrc... > Why all these systemd blockers? I wonder if systemd is a default USE flag for a package somewhere. Try adding " -systemd " to USE in make.conf to explicitly disable it, and re-run the emerge. -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Re: systemd questions: hdparm unit file, OpenRC packages
On Mon, 10 Apr 2017 17:45:59 +0200, Kai Krakow wrote: > All those services are well integrated with each other and suitable for > most stuff. Tho, systemd-networkd is not explicitly developed as a > desktop daemon currently, systemd folks still tend to recommend > NetworkManager to get all features. The systemd replacement perfectly > works for me, tho: My desktop PC is a stationary PC with wired network. > If you're mobile or use wifi, ymmv. I use systemd-networkd with WiFi. It's just a case of running wpa_gui when I want to connect to a new network. -- Neil Bothwick No, you *can't* call 999 now. I'm downloading my mail. pgpx9f6hWiuhq.pgp Description: OpenPGP digital signature
Re: [gentoo-user] systemD?
On Wed, Aug 30, 2017 at 7:28 PM, Heiko Baums <li...@baums-on-web.de> wrote: > Am Wed, 30 Aug 2017 23:27:12 +0100 > schrieb Mick <michaelkintz...@gmail.com>: > >> BTW, if you run ps axf and come across '/lib/systemd/systemd-udevd >> --daemon' don't panic. RHL advocates of monolithic stack for Linux >> haven't taken over your machine, but that's how udev is packaged >> these days even if you have not installed or enabled systemd on your >> OS. > > Why not using eudev? Works perfectly. No need for systemd-udev. > Other than one default setting and the filenames there really is little difference either way. If eudev has drifted further than that I'm curious to hear. -- Rich
Re: [gentoo-user] Why do systemd scripts get installed with USE="-systemd"?
On 2017-11-12 12:47, Neil Bothwick wrote: On Sun, 12 Nov 2017 10:55:04 +, Akater wrote: It looks like systemd scripts often (always?) get installed, regardless of USE flag settings. Because they are tiny so impact of them is negligible. On the other hand, if you don't have them and want to switch to systemd, you would end up having to recompile half of world just to get the service files. As long the ebuild doesn't have a USE flag "systemd" - may be. If the (local) USE flag is for service files only, it could may be considered as overhead. But if there is a USE flag "system" - doesn't have the package to be rebuild somehow or other? Why would they? Is this a policy? AFAIK, yes. -- Sent with eQmail-1.10
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
On 2018-11-19 08:14, "Stefan G. Weichinger" wrote: > upgrading from sys-apps/systemd-236-r5 to 239-r2 > > the emerge runs through and warns me that it overwrites files ... so it > merges only partially ... > > after that I see: > > # systemctl --version > systemd 239 > > (which is OK) > > > # eix -I systemd > > [U] sys-apps/systemd > Available versions: 239-r2(0/2) > > Installed versions: 236-r5 > > (which is scary) > > How to clean that up? Have you tried to run `eix-update`?
Re: [gentoo-user] empty cdrom drive is busy or mounted
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:: > > # ps auxf | grep systemd > root 24947 0.0 0.0 13964 996 pts/6S+ 15:43 0:00 > | | | \_ grep --colour=auto systemd > This is showing that the only process with systemd in its name is the grep command itself; you could pass anything to grep and it will be found in the process list, eg; $ ps auxf | grep blah adam 52359 0.0 0.0 7708 940 pts/3S+ 09:55 0:00 \_ grep --colour=auto blah So, there's no systemd process running on this system.
Re: [gentoo-user] sys-apps/systemd-239-r2 does not install completely
Am 19.11.18 um 09:41 schrieb Neil Bothwick: > On Mon, 19 Nov 2018 08:14:38 +0100, Stefan G. Weichinger wrote: > >> upgrading from sys-apps/systemd-236-r5 to 239-r2 >> >> the emerge runs through and warns me that it overwrites files ... >> so it merges only partially ... > > What's the exact error message? You may get a suggested solution > based on this vague description of the problem but it may not be > the right one, or even safe. > > Normally emerge will put up a warning like this before installing > anything. pasted error msg below pls ignore that locale issue, comes from my fedora desktop (seems to set the variables through ssh as well ... I know how to fix the locale but I'm lazy) --- * Package 'sys-apps/systemd-239-r2' merged despite file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) !!! Failed to copy extended attributes. In order to avoid this error, !!! set FEATURES="-xattr" in make.conf. !!! copy /var/tmp/portage/sys-apps/systemd-239-r2/image/var/log/journal/remote/.keep_sys-apps_systemd-0 -> /var/log/journal/remote/.keep_sys-apps_systemd-0 failed. !!! Filesystem containing file '/var/log/journal/remote/.keep_sys-apps_systemd-0#new' does not support extended attribute 'system.posix_acl_access' /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 190: warning: setlocale: LC_NUMERIC: cannot change locale (de_AT.UTF-8) /var/tmp/portage/sys-apps/systemd-239-r2/temp/environment: line 192: warning: setlocale: LC_TIME: cannot change locale (de_AT.UTF-8) * Messages for package sys-apps/systemd-239-r2: * CONFIG_CGROUP_BPF: is not set when it should be. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * Messages for package sys-apps/systemd-239-r2: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / ` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /lib64/libsystemd.so.0.23.0 * /lib64/libudev.so.1.6.11 * /lib/systemd/systemd-time-wait-sync * /lib/systemd/systemd-portabled * /lib/systemd/portablectl * /lib/systemd/systemd-user-runtime-dir * /lib/systemd/libsystemd-shared-239.so * /lib/systemd/portable/profile/trusted/service.conf * /lib/systemd/portable/profile/strict/service.conf * /lib/systemd/portable/profile/nonetwork/service.conf * /lib/systemd/portable/profile/default/service.conf * /lib/systemd/system/system-update-pre.target * /lib/systemd/system/suspend-then-hibernate.target * /lib/systemd/system/user-runtime-dir@.service * /lib/systemd/system/systemd-time-wait-sync.service * /lib/systemd/system/systemd-portabled.service * /lib/systemd/system/systemd-suspend-then-hibernate.service * /lib/systemd/system/user-.slice.d/10-defaults.conf * /usr/bin/resolvectl * /usr/lib/tmpfiles.d/portables.conf * /usr/share/locale/ja/LC_MESSAGES/systemd.mo * /usr/share/doc/systemd-239-r2/NEWS.bz2 * /usr/share/doc/systemd-239-r2/TODO.bz2 * /usr/share/doc/systemd-239-r2/nsswitch.conf.bz2 * /usr/share/doc/systemd-239-r2/UIDS-GIDS.md.bz2 * /usr/share/doc/systemd-239-r2/README.md.bz2 * /usr/share/doc/systemd-239-r2/TRANSLATORS.bz2 * /usr/share/doc/systemd-239-r2/README.bz2 * /usr/share/doc/systemd-239-r2/TRANSIENT-SETTINGS.md.bz2 * /usr/share/doc/systemd-239-r2/GVARIANT-SERIALIZATION.bz2 * /usr/share/doc/
Re: [gentoo-user] sys-apps/systemd is blocking app-emulation/docker-19.03.12
On Sat, Aug 22, 2020 at 09:48:00PM +0200, Hogren wrote:
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild N ] app-emulation/docker-19.03.12::gentoo USE="container-init
> overlay seccomp -apparmor -aufs -btrfs -device-mapper -hardened" 0 KiB
> [blocks B ] sys-apps/systemd[-cgroup-hybrid(+)]
> ("sys-apps/systemd[-cgroup-hybrid(+)]" is blocking
> app-emulation/docker-19.03.12)
>
> Total: 1 package (1 new), Size of downloads: 0 KiB
> Conflict: 1 block (1 unsatisfied)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> (sys-apps/systemd-245.5:0/2::gentoo, installed) pulled in by
> sys-apps/systemd required by @selected
>
> (app-emulation/docker-19.03.12:0/0::gentoo, ebuild scheduled for merge)
> pulled in by
> app-emulation/docker
systemd is not blocking Docker; Docker is blocking systemd. From the ebuild
(gentoo.git/app-emulation/docker/docker-19.03.12.ebuild):
RDEPEND="
${COMMON_DEPEND}
!sys-apps/systemd[-cgroup-hybrid(+)]
[...]
I.e., "block systemd unless the `cgroup-hybrid` flag is set". The `(+)` suffix
means that the flag is assumed to be enabled if it does not exist [1]. For your
particular case (systemd v. 245.5), this suffix is irrelevant.
Just re-emerge systemd with USE="cgroup-hybrid" and see if that helps.
Ashley.
[1]
https://devmanual.gentoo.org/general-concepts/dependencies/#use-dependency-defaults
--
Ashley Dixon
suugaku.co.uk
2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
signature.asc
Description: PGP signature
Re: [gentoo-user] sys-apps/systemd is blocking app-emulation/docker-19.03.12
Thank you Ashley to help me to read the ebuild/emerge syntax !
With your advice, docker is installing !!
Thank thank thank :)
Bye
Hogren
On 22/08/2020 22:09, Ashley Dixon wrote:
On Sat, Aug 22, 2020 at 09:48:00PM +0200, Hogren wrote:
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] app-emulation/docker-19.03.12::gentoo USE="container-init
overlay seccomp -apparmor -aufs -btrfs -device-mapper -hardened" 0 KiB
[blocks B ] sys-apps/systemd[-cgroup-hybrid(+)]
("sys-apps/systemd[-cgroup-hybrid(+)]" is blocking
app-emulation/docker-19.03.12)
Total: 1 package (1 new), Size of downloads: 0 KiB
Conflict: 1 block (1 unsatisfied)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(sys-apps/systemd-245.5:0/2::gentoo, installed) pulled in by
sys-apps/systemd required by @selected
(app-emulation/docker-19.03.12:0/0::gentoo, ebuild scheduled for merge)
pulled in by
app-emulation/docker
systemd is not blocking Docker; Docker is blocking systemd. From the ebuild
(gentoo.git/app-emulation/docker/docker-19.03.12.ebuild):
RDEPEND="
${COMMON_DEPEND}
!sys-apps/systemd[-cgroup-hybrid(+)]
[...]
I.e., "block systemd unless the `cgroup-hybrid` flag is set". The `(+)` suffix
means that the flag is assumed to be enabled if it does not exist [1]. For your
particular case (systemd v. 245.5), this suffix is irrelevant.
Just re-emerge systemd with USE="cgroup-hybrid" and see if that helps.
Ashley.
[1]
https://devmanual.gentoo.org/general-concepts/dependencies/#use-dependency-defaults
Re: [gentoo-user] A couple of problems with systemd
On Fri, 27 May 2022 19:51:06 -0400, John Covici wrote: > On Fri, 27 May 2022 17:49:24 -0400, > Neil Bothwick wrote: > > > > [1 ] > > On Fri, 27 May 2022 17:03:29 -0400, John Covici wrote: > > > > > I have one service which always times out, but slows down the boot > > > process. It is > > > /lib/systemd/system/systemd-networkd-wait-online.service. Because > > > many jobs wait in queue for a while, till this fails. > > > > Are you using systemd-networkd or something else to manage your > > network? > > > Also, I have a couple of services, ntpdate and proftpd which always > > > fail because when they try to execute named has not started yet. I > > > can restart them once the system is fully booted and I can login. > > > > You can create a drop-in to require the service to start after named, > > run "systemctl edit ntpdate.service" and add > > > > [Unit] > > Requires=named.service > > After=named.service > > > > That will create a drop-in file in > > /etc/systemd/system/ntpdate.service.d containing your additions - you > > can also create these files manually. > Thanks. I am not usingsystemd-network or anything like that.I > created a service called network and use the %i and links in > /etc/systemd/system/multi-user-target.wants to start my two cards. > Maybe this is not the normal way, but when I first started using > systemd, this is the best I could come up with at the time. If you are not starting systemd-networkd, network-online will fail. You only need to create a file in /etc/systemd/network to configure your card, something like [Match] Name=eth0 [Network] Description=Wired network DHCP=yes Then start systemd-networkd.service. > > I will try the drop-in, I had kind of forgot about them. > > -- Neil Bothwick The cow is nothing but a machine that makes grass fit for us people to eat. pgpe0nxze5Ib0.pgp Description: OpenPGP digital signature
Re: [gentoo-user] systemd question
On Tue, Sep 25, 2012 at 2:24 PM, walt w41...@gmail.com wrote: I just installed and booted with systemd and most services are working normally, except syslog.service and remote-fs.service. Both of those failed on bootup with a No such file or directory error. I can't figure out how to make systemd tell me which files it can't find. Any ideas? The syslog.service works as a place-holder for whatever syslog you have installed (or not). So, if you have syslog-ng, you do ln -s /usr/lib/systemd/system/syslog-ng.service /etc/systemd/system/syslog.service If you have rsyslog, you do: ln -s /usr/lib/systemd/system/rsyslog.service /etc/systemd/system/syslog.service If you (like me) don't have any syslog because you want to use journald, you do: ln -s /dev/null /etc/systemd/system/syslog.service That is the common way to mask services in systemd. If you don't need remote filesystems (NFS, cifs shares, etc.) mounted at boot time, mask remote-fs.service: ln -s /dev/null /etc/systemd/system/remote-fs.service I do however have the remote-fs.service (systemd-191, out of the oven), I don't know why it isn't installed in your case. Which version are you using. Regards -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] NetworkManager problem after migrating to systemd
On Mon, Oct 29, 2012 at 4:42 PM, João Matos jaon...@gmail.com wrote: I found the solution a few hours ago here http://en.gentoo-wiki.com/wiki/Systemd#PAM_support:_su.2C_sudo.2C_screen... . Now everything is fine :) About the packages you mentioned, you've ran 'equery uses pambase polkit udisks upower', and none of them has the userflag systemd. # equery uses pambase polkit udisks upower [: I - package is installed with flag ] * Found these USE flags for sys-auth/pambase-20120417-r1: [snip] + + systemd : Use pam_systemd module to register user sessions in the systemd control group hierarchy. * Found these USE flags for sys-auth/polkit-0.107-r1: [snip] + + systemd : Use sys-apps/systemd instead of sys-auth/consolekit for session tracking * Found these USE flags for sys-fs/udisks-2.0.0: [snip] + + systemd : Support sys-apps/systemd's logind * Found these USE flags for sys-power/upower-0.9.18: [snip] + + systemd : Use sys-apps/systemd for hibernate and suspend Depends on the versions ;) Anyway, systemd is globally set on my system, and it is good to know I can disable consolekit. I'll try it right now. The problem with ck is that it will make some things fail subtlety. I did uninstall it, and everything has been working great (including the awesome app-admin/system-config-printer-gnome). Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] *draft* for setting up network bridge with systemd (for qemu/kvm)
On Tue, Jan 29, 2013 at 9:49 PM, Canek Peláez Valdés can...@gmail.com wrote: I would not bet on that ;) too much resistance. However it is certainly getting better and better: the LWN article on The Biggest Myths about systemd had an overwhelmingly majority of comments positive to systemd, and just a handful of negative comments: http://lwn.net/Articles/534210/#Comments But that is in LWN; Gentoo is way behind, I believe. Gentoo is not behind, it provides you the option of using systemd. However openrc is superior in many ways, as unlike systemd it provides script base metadata vs static systemd units, so for example a service can depend on other services based on LOGIC. Also, it has the nature of virtual dependencies what systemd lacks, for example there are N services that provides timesync, in openrc you provide timesync and depend on timesync, in systemd there is no way to do so. openrc is working in various environments including embedded, while systemd requires so much dependencies that it is not really usable at all environments. openrc can be used correctly in chroot environment, while systemd is inoperative. openrc supports extra commands for services, while systemd enforces only start/stop sequence. I can go on an on. Just because there is hype of some branding, does not mean it is better. openrc networking is the best network configuration I ever used, and I used a lot of distributions. I used the following[1][2][3][4] configuration on my environment. Regards, Alon [1] http://en.gentoo-wiki.com/wiki/VM_Tap_Networking [2] http://en.gentoo-wiki.com/wiki/Stealth_DHCP [3] http://en.gentoo-wiki.com/wiki/Firewall_Using_Firehol [4] http://en.gentoo-wiki.com/wiki/OpenVPN_Non_Root
