From: Frankie Wild <green...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: Gnome 3 pulls out systemd dependencies
Date: Fri, 16 Oct 2015 02:38:28 -0700 (PDT) [thread overview]
Message-ID: <9170b80c-0523-41e7-b721-3c02b0e6f85a@googlegroups.com> (raw)
In-Reply-To: <43a732e2-ac49-4cd6-9788-b9aadd6fcf7b@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1376 bytes --]
xbps-remove -R gnome did the trick. Systemd traces are gone again.
On Friday, October 16, 2015 at 12:23:39 PM UTC+3, Frankie Wild wrote:
>
> It seems that Gnome 3 is pulling out some systemd dependencies. I have
> just noticed it and tried to remove the whole gnome meta package but some
> components are still there.
>
> [mar1n3r0@localhost user]$ whereis systemd
> systemd: /usr/lib/systemd
> [mar1n3r0@localhost user]$ cd /usr/lib/systemd/
> [mar1n3r0@localhost systemd]$ ls -al
> total 136
> drwxr-xr-x 3 root root 4096 Oct 13 14:29 .
> drwxr-xr-x 149 root root 126976 Oct 15 23:10 ..
> drwxr-xr-x 2 root root 4096 Oct 13 14:29 user
> [mar1n3r0@localhost systemd]$ cd user/
> [mar1n3r0@localhost user]$ ls -al
> total 36
> drwxr-xr-x 2 root root 4096 Oct 13 14:29 .
> drwxr-xr-x 3 root root 4096 Oct 13 14:29 ..
> -rw-r--r-- 1 root root 180 Oct 14 10:50 gvfs-afc-volume-monitor.service
> -rw-r--r-- 1 root root 123 Oct 14 10:49 gvfs-daemon.service
> -rw-r--r-- 1 root root 183 Oct 14 10:50 gvfs-goa-volume-monitor.service
> -rw-r--r-- 1 root root 184 Oct 14 10:50
> gvfs-gphoto2-volume-monitor.service
> -rw-r--r-- 1 root root 143 Oct 14 10:49 gvfs-metadata.service
> -rw-r--r-- 1 root root 185 Oct 14 10:50 gvfs-mtp-volume-monitor.service
> -rw-r--r-- 1 root root 181 Oct 14 10:50
> gvfs-udisks2-volume-monitor.service
> [mar1n3r0@localhost user]$
>
>
[-- Attachment #1.2: Type: text/html, Size: 1775 bytes --]
next prev parent reply other threads:[~2015-10-16 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 9:23 Frankie Wild
2015-10-16 9:38 ` Frankie Wild [this message]
2015-10-16 9:45 ` Juan RP
2015-10-16 10:54 ` Frankie Wild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9170b80c-0523-41e7-b721-3c02b0e6f85a@googlegroups.com \
--to="green..."@gmail.com \
--cc="void..."@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).