Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Start a nNew thread

CentOS-announce Digest, Vol 164, Issue 6
by centos-announce-request＠centos.org 26 Oct '18

26 Oct '18

1 0

Stupid C7 firewall question
by mark 26 Oct '18

26 Oct '18

Been looking, and haven't found the answer: in c7, is there a firewall-cmd command, or a systemctl cmd, to check whether ip6tables firewall is running mark

10 13

Centos7 & Selinux & Tor
by Robin Lee 23 Oct '18

23 Oct '18

I've just encountered a problem starting tor. When I do 'systemctl start tor' it fails and I get selinux errors in the log. There was suggestion to do full auditing with 'auditctl -w /etc/shadow -p w'. Which I did and it gave the following type=PROCTITLE msg=audit(1539540150.692:60570): proctitle=2F7573722F62696E2F746F72002D2D72756E61736461656D6F6E0030002D2 D64656661756C74732D746F727263002F7573722F73686172652F746F722F6465666175 6C74732D746F727263002D66002F6574632F746F722F746F727263002D2D76657269667 92D636F6E666967 type=PATH msg=audit(1539540150.692:60570): item=0 name="/var/lib/tor/hidden_service/" inode=201616393 dev=fd:02 mode=040700 ouid=494 ogid=490 rdev=00:00 obj=system_u:object_r:tor_var_lib_t:s0 objtype=NORMAL cap_fp=0000000000000000 cap_fi=0000000000000000 cap_fe=0 cap_fver=0 type=CWD msg=audit(1539540150.692:60570): cwd="/" type=SYSCALL msg=audit(1539540150.692:60570): arch=c000003e syscall=2 success=no exit=-13 a0=562d3767da80 a1=20000 a2=0 a3=1 items=1 ppid=1 pid=18283 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="tor" exe="/usr/bin/tor" subj=system_u:system_r:tor_t:s0 key=(null) type=AVC msg=audit(1539540150.692:60570): avc: denied { dac_read_search } for pid=18283 comm="tor" capability=2 scontext=system_u:system_r:tor_t:s0 tcontext=system_u:system_r:tor_t:s0 tclass=capability type=AVC msg=audit(1539540150.692:60570): avc: denied { dac_override } for pid=18283 comm="tor" capability=1 scontext=system_u:system_r:tor_t:s0 tcontext=system_u:system_r:tor_t:s0 tclass=capability So I had a look at the permissions for /var/lib/tor/hidden_service/ and they were drwx------. toranon toranon system_u:object_r:tor_var_lib_t:s0 hidden_service Could somebody help me out here? I have no idea what to make of this. I know that tor was working for me at least a month ago. I got tor from this package: tor-0.2.9.16-1.el7.x86_64 Cheers Robin

2 4

CentOS-announce Digest, Vol 164, Issue 5
by centos-announce-request＠centos.org 23 Oct '18

23 Oct '18

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2018:2943 Critical CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) 2. CESA-2018:2942 Critical CentOS 7 java-1.8.0-openjdk Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 22 Oct 2018 14:45:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2943 Critical CentOS 6 java-1.8.0-openjdk Security Update Message-ID: <20181022144540.GA62378(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2943 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:2943 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 10e294486f79da36e480a94314963c0f717e456e9012f7b06910fea207426df0 java-1.8.0-openjdk-1.8.0.191.b12-0.el6_10.i686.rpm 263fdc2d3ff25a6f22505624021937a5441a2590d233ffe64af12f4bb15ed717 java-1.8.0-openjdk-debug-1.8.0.191.b12-0.el6_10.i686.rpm 0720e6b37c2af702b40ff4a3be4d8359a13137d206dc58dbc8542b1e0d3df212 java-1.8.0-openjdk-demo-1.8.0.191.b12-0.el6_10.i686.rpm b3dbc54235955614622f83e7c019ae09344099d7e39276d6585d5c80600d488f java-1.8.0-openjdk-demo-debug-1.8.0.191.b12-0.el6_10.i686.rpm 37000c7965df7f72b3df937148a57dc360851bfd1caa5d84af4ddfb6099d86ef java-1.8.0-openjdk-devel-1.8.0.191.b12-0.el6_10.i686.rpm 7c034a5e931f94ac96f67f7685b01ccf4c1a016789d9e6ceb2fd6873f82f408e java-1.8.0-openjdk-devel-debug-1.8.0.191.b12-0.el6_10.i686.rpm f0cd73e105ec804bee3e94a0fc39af5ff160c0584df50fc5274802a036fc5f62 java-1.8.0-openjdk-headless-1.8.0.191.b12-0.el6_10.i686.rpm 92875f69d68f8c74f6a92c870e5274290d673a9a902e66b4b9ac891e7b1f4a13 java-1.8.0-openjdk-headless-debug-1.8.0.191.b12-0.el6_10.i686.rpm 104130bf5d4ed651bd1828f6657d3981d8d25049351fd37b5581a23a5ffc308d java-1.8.0-openjdk-javadoc-1.8.0.191.b12-0.el6_10.noarch.rpm a763f67e250a3215b92c7b501d169cf7851a864b1f086ba1f9df8ce6505da9c8 java-1.8.0-openjdk-javadoc-debug-1.8.0.191.b12-0.el6_10.noarch.rpm 368dc1878f3de0dc4bd0db96cad65366101ffcfbe34fd21213bfbdfb708371c4 java-1.8.0-openjdk-src-1.8.0.191.b12-0.el6_10.i686.rpm ed7d7a11c82daceabff7b535917d3949c2317c72ef371ae0c7c2478eea944535 java-1.8.0-openjdk-src-debug-1.8.0.191.b12-0.el6_10.i686.rpm x86_64: 2d2c6d2a280e29239e43ab60c80593a39339301bf9bcda87e88a7e31de3ca0f7 java-1.8.0-openjdk-1.8.0.191.b12-0.el6_10.x86_64.rpm bda285f5f4e207b90b159203f72ca8781aee4046a77b2a48c27c659933ac3982 java-1.8.0-openjdk-debug-1.8.0.191.b12-0.el6_10.x86_64.rpm e408a1d98e6160f93ca1ef352fd6267bfaacf76899172a0107745f6b1c3534c0 java-1.8.0-openjdk-demo-1.8.0.191.b12-0.el6_10.x86_64.rpm d6f8d3f0a49e0caf3aeaf13136456b7a605d8319fef057eb5648b351f8d8d8f2 java-1.8.0-openjdk-demo-debug-1.8.0.191.b12-0.el6_10.x86_64.rpm 45f67548838bf2d38bf4034fdde912c9508e54d3e430a5845d797eb1048c4461 java-1.8.0-openjdk-devel-1.8.0.191.b12-0.el6_10.x86_64.rpm a2366bcd33a170bc6e558582ebf25e33c098924f639f9048915a76c82046bbf9 java-1.8.0-openjdk-devel-debug-1.8.0.191.b12-0.el6_10.x86_64.rpm c8c235b12f05501925f0f7e984284f2028c6edc2d0ad4d8d35f8ace9838e1451 java-1.8.0-openjdk-headless-1.8.0.191.b12-0.el6_10.x86_64.rpm 619da945f3226c01f8cdb522050d00a3d5b7462632c4684eca049aaa80cea068 java-1.8.0-openjdk-headless-debug-1.8.0.191.b12-0.el6_10.x86_64.rpm 104130bf5d4ed651bd1828f6657d3981d8d25049351fd37b5581a23a5ffc308d java-1.8.0-openjdk-javadoc-1.8.0.191.b12-0.el6_10.noarch.rpm a763f67e250a3215b92c7b501d169cf7851a864b1f086ba1f9df8ce6505da9c8 java-1.8.0-openjdk-javadoc-debug-1.8.0.191.b12-0.el6_10.noarch.rpm 60db35ba2dbe7a5f76f627dfb2d70dde0952f7d2b4d9fb8ab990435c02eb3f43 java-1.8.0-openjdk-src-1.8.0.191.b12-0.el6_10.x86_64.rpm 810e2ab3386ee551a8e04192ae00d7e91d6f71b19caf3e2a829580ba9c5d786a java-1.8.0-openjdk-src-debug-1.8.0.191.b12-0.el6_10.x86_64.rpm Source: ca59253e2ebe94076af3f4188ea82542cbce3538326d9078c663c079096b8dbb java-1.8.0-openjdk-1.8.0.191.b12-0.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 22 Oct 2018 16:25:25 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2942 Critical CentOS 7 java-1.8.0-openjdk Security Update Message-ID: <20181022162525.GA3021(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2942 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:2942 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9b0e9718995176baa60a1b6255be237c6e5c1a32b992d0ec9b9d6dfdd63e53dd java-1.8.0-openjdk-1.8.0.191.b12-0.el7_5.i686.rpm de28afb2c6ac7ba0cabe579f18556d2db93dd353821f1afbd352c689e05d2594 java-1.8.0-openjdk-1.8.0.191.b12-0.el7_5.x86_64.rpm ebb413d9754ce3802915fafbd5e8981b384695cc63ef6b36f2fc3a1d1dca0a3d java-1.8.0-openjdk-accessibility-1.8.0.191.b12-0.el7_5.i686.rpm 200695ef0188b557a215a07240521ec10ba9ae8a3c1bd24f9a538560667f9419 java-1.8.0-openjdk-accessibility-1.8.0.191.b12-0.el7_5.x86_64.rpm 20d43426186ccea7f314bb648e172ea005dc20d4ac1579f1055197c5f9d03167 java-1.8.0-openjdk-accessibility-debug-1.8.0.191.b12-0.el7_5.i686.rpm 58fe7e287e6109c7aef6fe6ff2157f5cf55bc480c363b08d0f1160a53c741298 java-1.8.0-openjdk-accessibility-debug-1.8.0.191.b12-0.el7_5.x86_64.rpm f00fe6e02fd11d22ecd005467a3d290ded7da77fe12befc4f185c6348930084a java-1.8.0-openjdk-debug-1.8.0.191.b12-0.el7_5.i686.rpm 689bb6f3baf737044da0151c85a439c64e7510c2fd387b59a9e7e69c00f625a2 java-1.8.0-openjdk-debug-1.8.0.191.b12-0.el7_5.x86_64.rpm 0dccca8428044d48d68a14f05b33faf12bfa7e7538e542e697a4027074053b21 java-1.8.0-openjdk-demo-1.8.0.191.b12-0.el7_5.i686.rpm 0c2a3d25658ec786915729ded22d614befad39fd9760d30f728eb912ca4b4d01 java-1.8.0-openjdk-demo-1.8.0.191.b12-0.el7_5.x86_64.rpm 3d8a7d52c30d256d7121aab8b4c1ea890e873f65d1b567bced20dd4713d63add java-1.8.0-openjdk-demo-debug-1.8.0.191.b12-0.el7_5.i686.rpm 51edf6417f25ddec17820199829ea7ee023396dded46f0ecf4357ea69b78417c java-1.8.0-openjdk-demo-debug-1.8.0.191.b12-0.el7_5.x86_64.rpm 14da8e4faf28166a647f7e65f7142febe33b7172be1167a82983fff0d2af2d75 java-1.8.0-openjdk-devel-1.8.0.191.b12-0.el7_5.i686.rpm 656e24f21d2b5571656ca04543b71fc9289672d4823c3c2baa0c9c9e10f7a350 java-1.8.0-openjdk-devel-1.8.0.191.b12-0.el7_5.x86_64.rpm 897b6d04c02310e8911e4cd764501568334d5540698f7b191413d92fd9af3afd java-1.8.0-openjdk-devel-debug-1.8.0.191.b12-0.el7_5.i686.rpm 79f16d3c2a1b7f17f8656e45f5aff73f23faf3734029aad1cfe6f734f1dbbe98 java-1.8.0-openjdk-devel-debug-1.8.0.191.b12-0.el7_5.x86_64.rpm 75a66b41c490aaa5a937551bb55e4a1a0c7d8f62c9e6cb84e9a47e99f3581f50 java-1.8.0-openjdk-headless-1.8.0.191.b12-0.el7_5.i686.rpm 93d4359d53ad9fdd3c6bc185f354e58f1c1981476ac5079b10b1f3a7625c949b java-1.8.0-openjdk-headless-1.8.0.191.b12-0.el7_5.x86_64.rpm d1d183dd5fc0aae33f47a01198b9d6a23bb396ac772cca5bfd58da2dd78923a6 java-1.8.0-openjdk-headless-debug-1.8.0.191.b12-0.el7_5.i686.rpm 944271660651618b66ce31cf9a79f9fd4e7c9e449de17e8fcc349a6eb0a6fdb7 java-1.8.0-openjdk-headless-debug-1.8.0.191.b12-0.el7_5.x86_64.rpm 6d19225f904e922baa53c9b0970a38757851a0a74f38fae777f1b71da4ef17c5 java-1.8.0-openjdk-javadoc-1.8.0.191.b12-0.el7_5.noarch.rpm 745cac8aedcd76e3c30d11e2eda2edac2eb9e8049603b8c044d51dd8509afdc5 java-1.8.0-openjdk-javadoc-debug-1.8.0.191.b12-0.el7_5.noarch.rpm 4f616aa6afc6c10f3f4945328c9240f5137fa46ee3e7259f8cc605a7e805514b java-1.8.0-openjdk-javadoc-zip-1.8.0.191.b12-0.el7_5.noarch.rpm 51323aab38ddd36f4728cb357e4fd333175aeac53df6ff154ff440ea092071cc java-1.8.0-openjdk-javadoc-zip-debug-1.8.0.191.b12-0.el7_5.noarch.rpm c601c87a3c8a2379f3ab69d44ccb7d6eefd67dfa1b1debc494d30a6a4ce738a0 java-1.8.0-openjdk-src-1.8.0.191.b12-0.el7_5.i686.rpm 89499e98c3f7ef8e7804c237974c302ac7022708e0a199908c674928de742842 java-1.8.0-openjdk-src-1.8.0.191.b12-0.el7_5.x86_64.rpm 6bc179ef5abab92a4f46045cc10dc4348d2359bddaa5cdf85c86b2e9055f9a57 java-1.8.0-openjdk-src-debug-1.8.0.191.b12-0.el7_5.i686.rpm 0dc3e87d3c2fd2149d44250f654031b59023e312804a0ef689cd079fc9e6e4d5 java-1.8.0-openjdk-src-debug-1.8.0.191.b12-0.el7_5.x86_64.rpm Source: e98a223e70a66648032fee4515aa0ccd4c067a86e4cede1daf4e53974642a292 java-1.8.0-openjdk-1.8.0.191.b12-0.el7_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 164, Issue 5 ***********************************************

1 0

systemd automount of cifs share hangs
by Kenneth Porter 21 Oct '18

21 Oct '18

Running latest CentOS 7.5. Since I found out about automount unit files I've had mixed results using them to mount shares from my NAS. Lately they seem to hang if I touch the mount point, but I can start the mount unit without problems. I had it working months ago, so I'm thinking something changed in the systemd updates. For each mount point, I have two files in /etc/systemd/system named with the path of the mount point and with extensions .automount and .mount, following the systemd documentation. For example, srv-dav-name1.mount and srv-dav-name1.automount to mount a NAS share to /srv/dav/name1. I can issue "systemctl start srv-dav-name1.mount" and the mount completes instantly. But if I start the automount unit and ls the mount point, the shell hangs and eventually, a long time later (I haven't timed it, maybe an hour), I eventually get a prompt again. Control-C won't interrupt it. I can still ssh in and get another session so it's just the process that's accessing the mount point that hangs. Any suggestions on how I can debug this? I'm still new to finding the right log files. /var/log/messages doesn't show any errors like timeouts.

2 2

What are the differences between systemd and non-systemd Linux distros?
by Turritopsis Dohrnii Teo En Ming 20 Oct '18

20 Oct '18

Good afternoon from Singapore, What are the differences between systemd and non-systemd Linux distros? Is systemd implemented in all the latest Linux distros? Please advise. Thank you. ===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ [2] http://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming ===END SIGNATURE===

26 52

Re: [CentOS] Upstream and downstream (was Re: What are the differences between systemd and non-systemd Linux distros?)
by Brendan Conoboy 20 Oct '18

20 Oct '18

On Fri Oct 19 00:52:12 UTC 2018 Japheth Cleaver wrote: > This brings to mind a video I was pointed to not long ago of Brendan > Conoboy's talk at a Dojo recently: > > https://www.youtube.com/watch?v=HQsUdLPJW20 Hey, that's me! Hi. By the way, Jim Perrin did an updated version of this talk *today* at CERN in my absence (thanks Jim!). Hopefully the video will be posted soon. I expect we'll be doing updated versions of these at Devconf, future Dojos, etc- as things progress. > For quite a long time, many (perhaps most) folks had assumed that > Fedora functioned more or less directly as the internal alpha for > RHEL, with a branch at some point occurring, followed by pruning > of packages, hardening, vendor testing, and release. This is roughly true for new releases (plus or minus the kernel), but not for subsequent minor release updates. It is a shame because so much great work happens in Fedora between major RHEL releases. > Subsequently, > CentOS (even after the RH integration) functioned *strictly* as a > clean-room downstream rebuild, with the ability to do unsupported > things, like alternate architectures, or heavier kernels, restricted > to what could be done while maintaining a 100% binary compatible > rebuild. Any contributions back up where taken to be incidental, > from CentOS users reporting bugs that could be verified against RHEL. > > Conoboy, on the other hand, takes great pains during the speech to > describe a much more fluid and complex interaction between CentOS > and its upstream, and puts forth CentOS as a mechanism (perhaps > the best mechanism) for the winder EL community to contribute > (something?) back into RHEL's future. He also gives clear signals > that various Fedora steps have been in directions that Red Hat did > not want EL necessarily going, and that the simplistic assumptions > we've commonly been making aren't really correct. You might be reading into this more than is there. It's not so much that things are fluid as it is that they are undefined. There is no clear, consistent way for a member of the Fedora or CentOS communities, who create something great, to have that thing make its way into an update of an existing RHEL major release. Defining that path, making it possible, would be win for all. > Obviously, there seems to be a bit of a discrepancy there. > > The wider EL community is trapped between a rock and a hard place > somewhat. If you try to direct Fedora into the needs of EL users, > you stand a good chance of getting told to pound stand, and that > EL is getting in the way of bleeding-edge progress. Traditionally, > CentOS has had its hands tied since it aims to be 100% compatible > with upstream. Red Hat (and Red-Hat-as-a-sponsor-of-CentOS) might > do well to clarify just what type of back-and-forth it wants out of > the wider EL-using community. Does it want direct feedback in the > form of tickets? Should people form SIGs? Obviously RHEL7 is not > changing init systems, but where should one talk about the future? Man, it breaks my heart when I read things like this. There might be some historic truth to the above, but it doesn't have to be the future. The objective I mentioned near the end of the talk has been posted, but not yet voted on: https://fedoraproject.org/wiki/User:Pfrields/Lifecycle_Objective The beauty of community is that it can grow and shift according to the needs of its members. To me it looks like the lifecycle objective may be a partial answer to how Fedora, RHEL, and CentOS communities can reach a state of fluidity, a virtuous cycle. The thing that makes it the most likely to succeed is if members of the Fedora, RHEL, and CentOS communities work on it together. I hope those reading this who are interested in that join in. -- Brendan Conoboy / RHEL Development Coordinator / Red Hat, Inc.

2 1

No searchable archives for this mailing list?
by Kay Schenk 19 Oct '18

19 Oct '18

Hello all-- I can't seem to find a way to search the archives of this list right now though I DO remember doing that in the past. Any ideas? Thanks. -- Kay

2 1

Can't access Samba shares from Nautilus
by Nicolas Kovacs 19 Oct '18

19 Oct '18

Hi, I'm currently experimenting with Samba on a few sandbox machines. On the server side, I have setup CentOS 7 with a basic Samba setup and two shares, one public, the other password-protected. I have two Windows 7 boxes in my network, and I can access the shares perfectly, log in to the password-protected share, read and write files, so this seems to work OK. On my main Linux workstation (CentOS 7 + custom GNOME) I can't seem to access these shares. When I click on the "Parcourir le réseau" ("Browse network") icon in GNOME, Nautilus opens and shows a "Réseau Windows" ("Windows network") icon. Clicking on this icon, I only get the following error message: "Impossible d'accéder à l'emplacement". Unable to access this place. So I fire up GNOME Terminal and see what this looks like on the command line : [kikinovak@alphamule:~] $ smbclient -L //amandine -N Anonymous login successful Sharename Type Comment --------- ---- ------- Public Disk Partage Public Confidentiel Disk Partage Confidentiel IPC$ IPC IPC Service (Serveur de fichiers AMANDINE) Reconnecting with SMB1 for workgroup listing. Anonymous login successful Server Comment --------- ------- Workgroup Master --------- ------- WORKGROUP AMANDINE So far, so good. Now I try to connect as a user: [kikinovak@alphamule:~] $ smbclient //amandine/Confidentiel -U kikinovak Enter SAMBA\kikinovak's password: Try "help" to get a list of possible commands. smb: \> dir . D 0 Fri Oct 19 09:45:37 2018 .. D 0 Fri Oct 19 08:47:34 2018 Lighthouse.jpg N 561276 Tue Jul 14 07:32:31 2009 Jellyfish.jpg N 775702 Tue Jul 14 07:32:31 2009 Desert.jpg N 845941 Tue Jul 14 07:32:31 2009 Koala.jpg N 780831 Tue Jul 14 07:32:31 2009 Hydrangeas.jpg N 595284 Tue Jul 14 07:32:31 2009 Tulips.jpg N 620888 Tue Jul 14 07:32:31 2009 Penguins.jpg N 777835 Tue Jul 14 07:32:31 2009 Chrysanthemum.jpg N 879394 Tue Jul 14 07:32:31 2009 149030696 blocks of size 1024. 139929224 blocks available smb: \> This also looks good. Now let's check what Samba-related packages are installed on my workstation: [kikinovak@alphamule:~] $ rpm -qa | grep samba samba-client-libs-4.7.1-6.el7.x86_64 samba-client-4.7.1-6.el7.x86_64 samba-common-4.7.1-6.el7.noarch samba-common-libs-4.7.1-6.el7.x86_64 [kikinovak@alphamule:~] $ rpm -qa | grep gvfs gvfs-mtp-1.30.4-5.el7.x86_64 gvfs-smb-1.30.4-5.el7.x86_64 gvfs-afp-1.30.4-5.el7.x86_64 gvfs-client-1.30.4-5.el7.x86_64 gvfs-1.30.4-5.el7.x86_64 gvfs-archive-1.30.4-5.el7.x86_64 gvfs-goa-1.30.4-5.el7.x86_64 gvfs-fuse-1.30.4-5.el7.x86_64 gvfs-gphoto2-1.30.4-5.el7.x86_64 gvfs-afc-1.30.4-5.el7.x86_64 Any idea what's missing here or why this doesn't work as expected ? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 2

Check version from installer disc
by Elliott Balsley 19 Oct '18

19 Oct '18

Is there some way to see what version will be installed by an installation disc? I made a USB installer and I forgot whether it's CentOS 7.3 or 7.5. Short of running the whole installer and seeing what happens, I can't see any way to get this info from within Anaconda.

3 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss