Re: [CentOS] Android on CentOS 7

[Ralf Prengel]

> Am 09.11.2020 um 04:15 schrieb mark :
> 
> Should I install android studio, or spin up a vm and use the android .iso?
> 
> 

Hallo,
backup and restore is more simple using a vm.

Ralf
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Android on CentOS 7

[mark]

Should I install android studio, or spin up a vm and use the android .iso?

mark
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] dbus packages' versions not making sense

[Jason Pyeron]

I have installed 1.12.8-10.el8_2, but when trying to install dbus-devel it is 
not available for that version, only 1.12.8-9.el8, which is also not available.

 

Suggestions?

 

# yum list | grep dbus

dbus.x86_64  1:1.12.8-10.el8_2  
  @BaseOS

dbus-common.noarch   1:1.12.8-10.el8_2  
  @BaseOS

dbus-daemon.x86_64   1:1.12.8-10.el8_2  
  @BaseOS

dbus-glib.x86_64 0.110-2.el8
  @anaconda

dbus-libs.x86_64 1:1.12.8-10.el8_2  
  @BaseOS

dbus-tools.x86_641:1.12.8-10.el8_2  
  @BaseOS

python3-dbus.x86_64  1.2.4-15.el8   
  @anaconda

python3-slip-dbus.noarch 0.6.4-11.el8   
  @anaconda

abrt-dbus.x86_64 2.10.9-11.el8  
  AppStream

dbus-devel.i686  1:1.12.8-9.el8 
  AppStream

 

dbus-devel.x86_641:1.12.8-9.el8 
  AppStream

 

dbus-glib.i686   0.110-2.el8
  BaseOS

dbus-glib-devel.i686 0.110-2.el8
  AppStream

dbus-glib-devel.x86_64   0.110-2.el8
  AppStream

dbus-libs.i686   1:1.12.8-10.el8_2  
  BaseOS

dbus-x11.x86_64  1:1.12.8-9.el8 
  AppStream

dleyna-connector-dbus.x86_64 0.3.0-2.el8
  AppStream

libblockdev-lvm-dbus.i6862.19-12.el8
  AppStream

libblockdev-lvm-dbus.x86_64  2.19-12.el8
  AppStream

libdbusmenu.i686 16.04.0-12.el8 
  AppStream

libdbusmenu.x86_64   16.04.0-12.el8 
  AppStream

libdbusmenu-gtk3.i68616.04.0-12.el8 
  AppStream

libdbusmenu-gtk3.x86_64  16.04.0-12.el8 
  AppStream

libvirt-dbus.x86_64  
1.2.0-3.module_el8.2.0+320+13f867d7  AppStream

lvm2-dbusd.noarch8:2.03.08-3.el8
  BaseOS

policycoreutils-dbus.noarch  2.9-9.el8  
  BaseOS

python3-dbus-client-gen.noarch   0.4-1.el8  
  AppStream

python3-dbus-python-client-gen.noarch0.7-3.el8  
  AppStream

python3-dbus-signature-pyparsing.noarch  0.03-2.el8 
  AppStream

python3-into-dbus-python.noarch  0.06-2.el8 
  AppStream

python3-pydbus.noarch0.6.0-5.el8
  AppStream

qt5-qdbusviewer.x86_64   5.12.5-1.el8.0.1   
  AppStream

sssd-dbus.x86_64 2.2.3-20.el8   
  BaseOS

usbguard-dbus.x86_64 0.7.4-4.el8
  AppStream

 

# yum install dbus-devel

Last metadata expiration check: 0:06:11 ago on Sun 08 Nov 2020 05:23:17 PM EST.

Error:

Problem: cannot install the best candidate for the job

  - nothing provides dbus-daemon = 1:1.12.8-9.el8 needed by 
dbus-devel-1:1.12.8-9.el8.x86_64

(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use 
not only best candidate packages)

 

# yum install dbus-devel-1.12.8-10.el8_2

Last metadata expiration check: 0:06:22 ago on Sun 08 Nov 2020 05:23:17 PM EST.

No match for argument: dbus-devel-1.12.8-10.el8_2

Error: Unable to find a match: dbus-devel-1.12.8-10.el8_2

 

 

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] systemd / services / current process list

[Leon Fauster via CentOS]

Am 06.11.20 um 14:57 schrieb Leon Fauster:

Hi,

following requirement is needed here (forced by application
migration from C6->C8):

I have two services running under supervision by systemd.

ServiceA: runs as user AppUser
ServiceB: runs as user AppUser

ServiceB can see "all" processes from AppUser (ps aux)
running by systemd (in fact it sees no other processes).
So ServiceB can see the processes of ServiceA.

I have also a cron job that runs every 5 minutes as user AppUser.

Now the problem is, that ServiceB via ps aux can't see the process of 
the cron job albeit running by the same AppUser.


Which security feature of systemd can be altered to allow seeing all
or at least AppUser's processes?

ServiceA as only this "features":
PrivateTmp=true

ServiceB as only this features:
PrivateTmp=true
RuntimeDirectory=calculation
RuntimeDirectoryMode=0755

Any hints would be great!



Okay, I got it now. The problem was SELinux related instead systemd.

Just a unconfined vs confined domain context that mismatched ...

--
Leon

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos