Re: [CentOS] kickstart compat C7 -> C8
Once upon a time, Stephen John Smoogen said: > Software seems to grow to the maximum space it can occupy. I think in 1989 > we were complaining about BSD not being able to fit on our VAX 750's boot > drive anymore and we needed to put in a 40MB drive system instead. I expect > by the 2040's we will be looking at petabyte drives and wondering how we > can fit anything on it. I first installed Linux on a 386SX (16MHz IIRC) system with a pair of 20MB hard drives and 2MB RAM... it took a little while. :) I think we ended up just using one drive for the root filesystem and the other for swap! This was probably 1992 or 1993, can't remember. Today I installed Linux on a system wtih 48 CPU cores... -- Chris Adams ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
> Am 08.05.2019 um 21:12 schrieb Chris Adams : > > Once upon a time, Leon Fauster via CentOS said: >> And this only for Fedora29, a C7 installation works fine (dynamically >> expands to the boundaries of the disk). > > You are asking about Fedora - you'd probably get better results on the > Fedora mailing lists, forums, etc. Well, F29 is very close to EL8 but you are right. Anyway, for the sake of precision. I made the same installation with RHEL8 (anaconda 29.19 vs 29.24 on F29). The results are same! Following "logvol" stanza "--percent=100 --grow" works for EL7 but not for EL8. While doing this again I found a solution; "--size=SIZE --grow" as options with an arbitrary SIZE will grow the LV to the size of the free VG size. -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
On 2019-05-08 15:05, Stephen John Smoogen wrote: On Wed, 8 May 2019 at 13:48, Valeri Galtsev wrote: On 2019-05-08 12:28, Stephen John Smoogen wrote: On Wed, 8 May 2019 at 13:24, mark wrote: Yep. Minimum for that is going to be about the same as your RESCUE. The other would just be to confirm that the sda has space and nothing still on it which it was trying to work around. In CentOS releases 5 --> 6 --> 7 the demand for /boot size doubles if not triples with each release... Otherwise one day you may fill it up before number of kernels will be such that kernel update will remove oldest kernel. And _we_ called Windows 2000 "bloated pig" when it was released... Sigh. Software seems to grow to the maximum space it can occupy. Of course, this is true. I do remember big upgrade: 40 MB hard drive replacing 20 MB one. Still, during the same decade an a half covering CentOS releases I mentioned, on my FreeBSD boxes /boot grew up less than twice, whereas on my CentOS boxes it grew up at least 5 times. I safely run CentOS 5 through its whole lifespan with /boot as small as 200MB. On CentOS 7 I make /boot 3 GB (maybe slight overkill, but boxes with 1 GB went into /boot size issue after several kernel updates). But what one can do: Linux kernel has a lot of stuff that, hmm..., one can probably live without, and what comes with Linux distributions covers widest variety of hardware it will run on ;-) Valeri PS Yes, I run and programmed for machines with 4 - 16 Kb of RAM, and now administer machine with almost 1 TB of RAM. Now you can pretty much pinpoint my age ;-) I think in 1989 we were complaining about BSD not being able to fit on our VAX 750's boot drive anymore and we needed to put in a 40MB drive system instead. I expect by the 2040's we will be looking at petabyte drives and wondering how we can fit anything on it. Valeri mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos -- Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos -- Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] youtube-dl No module named 'pkg_resources'
On Tue, May 7, 2019 at 7:55 PM Michael Hennebry wrote: > > youtube-dl doesn't work for me after a recent update. > I do not use it often, so do not know whether the update matters. > It gives the error message: > Traceback (most recent call last): >File "/usr/bin/youtube-dl", line 6, in > from pkg_resources import load_entry_point > ModuleNotFoundError: No module named 'pkg_resources' > > I've tried reinstalling python-setuptools, > installing python34-setuptools and reinstalling youtube-dl . > > I'm aware there is a bugzilla on it. > That and stackoverflow are where I got the ideas above. > > How do I make youtube-dl work on Centos 7? If you are using the EPEL one, you can resolve it by installing: (1) python36-setuptools from epel and (2) youtube-dl from epel-testing Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Issues trying to change the selinux context
On Wed, May 08, 2019 at 01:04:02PM -0400, mark wrote: > Hmmm, didn't complain when I did that... but they're still bin_t, not lib_t. 'semanage fcontext ...' updates the policy, but doesn't actually change the context on the paths (which may or may not even exist at the time the command runs). Run 'restorecon -r -v /your/path/with/actual/files' to reassign the selinux attributes to reflect the new fcontext policy. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
On Wed, 8 May 2019 at 13:48, Valeri Galtsev wrote: > > > On 2019-05-08 12:28, Stephen John Smoogen wrote: > > On Wed, 8 May 2019 at 13:24, mark wrote: > > >> > > Yep. Minimum for that is going to be about the same as your RESCUE. The > > other would just be to confirm that the sda has space and nothing still > on > > it which it was trying to work around. > > > > In CentOS releases 5 --> 6 --> 7 > > the demand for /boot size doubles if not triples with each release... > Otherwise one day you may fill it up before number of kernels will be > such that kernel update will remove oldest kernel. And _we_ called > Windows 2000 "bloated pig" when it was released... Sigh. > > Software seems to grow to the maximum space it can occupy. I think in 1989 we were complaining about BSD not being able to fit on our VAX 750's boot drive anymore and we needed to put in a 40MB drive system instead. I expect by the 2040's we will be looking at petabyte drives and wondering how we can fit anything on it. > Valeri > > > > > > >> mark > >> > >> ___ > >> CentOS mailing list > >> CentOS@centos.org > >> https://lists.centos.org/mailman/listinfo/centos > >> > > > > > > -- > > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox esr repackage
R C wrote: > cool!! that works for now.. thanks Mark!! Glad it helped. > > On Wed, May 8, 2019 at 11:21 AM mark wrote: > > >> firefox_repackage via CentOS wrote: >>> Hi everyone, I use firefox on centos 7 at work but due to the fairly >>> well know extension signing problem, I cannot use ublock origin. >>> >>> From what I can tell, the latest version of firefox in the updates >>> repository is 60.6.1-1.el7. It looks like Mozilla have just released >>> firefox esr 60.6.2 which should fix the signing issue. (see >>> https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/) >>> >> >> The answer that I found Sunday (after being on a trip, and unable to >> play music Sat eve on my netbook) was this: >> >> 1. Go to about:config >> 2. Type signature in the search bar. >> 3. You'll see this key: xpinstall.signatures.required, click on it, to >> change the boolean from true to false. >> >> Stuff may work again. If not, go to tools add-ons, and reenable (which >> you could not do before the boolean change). >> >> mark >> >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos >> >> > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] youtube-dl No module named 'pkg_resources'
On Wed, 8 May 2019 09:08:12 -0500 (CDT) Michael Hennebry wrote: > On Wed, 8 May 2019, Nux! wrote: > > > How did you install it? > > Most recently > yum reinstall youtube-dl > > > I'm using their binary and it works great, just tested it. > > > > https://ytdl-org.github.io/youtube-dl/download.html So am I. Despite generally favoring regular repositories, in the particular case of youtube-dl I prefer to uninstall the repo version, and follow the instructions on their website above. I just do a wget and a chmod as explained there, and it downloads itself into /usr/local/bin. Whenever it fails to work, usually a simple sudo youtube-dl -U will update itself to the latest version, which does work. The errors you encounter are typically not a problem in the script itself, nor in python, but a change in the structure of the youtube.com html code. It gets changed often, and then the older youtube-dl fails to parse the new youtube.com code structure, and errors out. But usually there is an updated version (often the same day) of youtube-dl, which parses the new html code correctly. If you use the repo version of youtube-dl, it may take a couple of weeks even for the update to land. On the other hand, the above manual update works immediately, with no hassle. Never failed me so far. HTH, :-) Marko ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Issues trying to change the selinux context
On May 8, 2019, at 11:44 AM, mark wrote: > > Warren Young wrote: >> On May 8, 2019, at 11:04 AM, mark wrote: >> >>> >>> semanage fcontext -m -t lib_t "/path/smwa/webagent/bin/*.so” >> >> Glob expansion doesn’t happen in double quotes. Not in Bash, anyway. > > Huh? I thought it didn't occur in single quotes, but did occur in quotes. Nope. The only difference I’m aware of is that single quotes prevent variable expansion (echo "hello $USER") while double quotes do not. > semanage insists on having the filespec in quotes. No, it just takes a single file spec, which may name a single file or it may be a regex. This, the parens issue, and the symptom you notice with looking at the permission on individual contained files are explained in point 2 of the section "Changing a Directory's Type” here: https://docs.fedoraproject.org/en-US/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
Once upon a time, Leon Fauster via CentOS said: > And this only for Fedora29, a C7 installation works fine (dynamically > expands to the boundaries of the disk). You are asking about Fedora - you'd probably get better results on the Fedora mailing lists, forums, etc. -- Chris Adams ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
Am 08.05.2019 um 20:56 schrieb Markus Falb : > > On 08.05.19 19:16, Leon Fauster via CentOS wrote: > ... >> I get a "device is too small for new format" error. Any hints? > ...> part pv.0104 --fstype="lvmpv" --ondisk=sda --grow > > pv.0104 > >> volgroup ee --pesize=4096 pv.1974 > > pv.1974 > > mismatch! Yep, I saw it after sending the mail. Its just a cut and paste and cleanup mistake. The ks file has the matching ids correct. Thanks. -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
On 08.05.19 19:16, Leon Fauster via CentOS wrote: ... > I get a "device is too small for new format" error. Any hints? ...> part pv.0104 --fstype="lvmpv" --ondisk=sda --grow pv.0104 > volgroup ee --pesize=4096 pv.1974 pv.1974 mismatch! -- Kind Regards, Markus Falb signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
> Am 08.05.2019 um 19:20 schrieb mark : > > Leon Fauster via CentOS wrote: >> Hi all, >> >> >> I still use the following kickstart partition scheme for C7 installations >> (via virt-install): >> Briefly, fixed size for /root and /boot, and the rest is filled up for >> /srv. >> >> The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work >> with Fedora29 (EL8). I get a "device is too small for new format" error. >> Any hints? >> >> part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part >> /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT >> part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096 >> pv.0104 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" >> --name=00 --vgname=ee >> logvol /srv --fstype="ext4" --percent=100 --grow --encrypted --label="SRV" >> --name=01 --vgname=ee >> > If I'm reading that correctly - haven't worked on a kickstart in years - > I'd start by increasing root to 1024 (1M) for /boot. That sounds reasonable but it doesn't help (tested up to 3GB for boot). The point is, that with fixed sizes everything works (even with 3GB root, 512MB boot, 768 RAM). The anaconda text-installation process passes without any problems. Only when "--grow" option comes in the problem appears. And this only for Fedora29, a C7 installation works fine (dynamically expands to the boundaries of the disk). Looking into the docs doesn't show any modifications: https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#chapter-3-kickstart-commands-in-red-hat-enterprise-linux It seems that with every new major release the headaches starts again :-(. While writing I did a new installation; the grow option for the "part" command seems to work. The VG expands to the disk boundaries. So, the problem gets more located around the "logvol" command ... -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Issues trying to change the selinux context
Warren Young wrote: > On May 8, 2019, at 11:04 AM, mark wrote: > >> >> semanage fcontext -m -t lib_t "/path/smwa/webagent/bin/*.so” > > Glob expansion doesn’t happen in double quotes. Not in Bash, anyway. Huh? I thought it didn't occur in single quotes, but did occur in quotes. Odd, I'm seeing it doesn't, at least in a basic test. On the other hand, from the example in the man page, semanage insists on having the filespec in quotes. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
On 2019-05-08 12:28, Stephen John Smoogen wrote: On Wed, 8 May 2019 at 13:24, mark wrote: Leon Fauster via CentOS wrote: Hi all, I still use the following kickstart partition scheme for C7 installations (via virt-install): Briefly, fixed size for /root and /boot, and the rest is filled up for /srv. The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096 pv.1974 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" --name=00 --vgname=ee logvol /srv --fstype="ext4" --percent=100 --grow --encrypted --label="SRV" --name=01 --vgname=ee If I'm reading that correctly - haven't worked on a kickstart in years - I'd start by increasing root to 1024 (1M) for /boot. Yep. Minimum for that is going to be about the same as your RESCUE. The other would just be to confirm that the sda has space and nothing still on it which it was trying to work around. In CentOS releases 5 --> 6 --> 7 the demand for /boot size doubles if not triples with each release... Otherwise one day you may fill it up before number of kernels will be such that kernel update will remove oldest kernel. And _we_ called Windows 2000 "bloated pig" when it was released... Sigh. Valeri mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos -- Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Issues trying to change the selinux context
On May 8, 2019, at 11:04 AM, mark wrote: > > semanage fcontext -m -t lib_t "/path/smwa/webagent/bin/*.so” Glob expansion doesn’t happen in double quotes. Not in Bash, anyway. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox esr repackage
cool!! that works for now.. thanks Mark!! On Wed, May 8, 2019 at 11:21 AM mark wrote: > firefox_repackage via CentOS wrote: > > Hi everyone, I use firefox on centos 7 at work but due to the fairly well > > know extension signing problem, I cannot use ublock origin. > > > > From what I can tell, the latest version of firefox in the updates > > repository is 60.6.1-1.el7. It looks like Mozilla have just released > > firefox esr 60.6.2 which should fix the signing issue. (see > > https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/) > > The answer that I found Sunday (after being on a trip, and unable to play > music Sat eve on my netbook) was this: > > 1. Go to about:config > 2. Type signature in the search bar. > 3. You'll see this key: xpinstall.signatures.required, click on it, to > change the boolean from true to false. > > Stuff may work again. If not, go to tools add-ons, and reenable (which you > could not do before the boolean change). > >mark > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
On Wed, 8 May 2019 at 13:24, mark wrote: > Leon Fauster via CentOS wrote: > > Hi all, > > > > > > I still use the following kickstart partition scheme for C7 installations > > (via virt-install): > > Briefly, fixed size for /root and /boot, and the rest is filled up for > > /srv. > > > > The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work > > with Fedora29 (EL8). I get a "device is too small for new format" error. > > Any hints? > > > > part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part > > /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT > > part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee > --pesize=4096 > > pv.1974 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" > > --name=00 --vgname=ee > > logvol /srv --fstype="ext4" --percent=100 --grow --encrypted > --label="SRV" > > --name=01 --vgname=ee > > > If I'm reading that correctly - haven't worked on a kickstart in years - > I'd start by increasing root to 1024 (1M) for /boot. > > Yep. Minimum for that is going to be about the same as your RESCUE. The other would just be to confirm that the sda has space and nothing still on it which it was trying to work around. >mark > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart compat C7 -> C8
Leon Fauster via CentOS wrote: > Hi all, > > > I still use the following kickstart partition scheme for C7 installations > (via virt-install): > Briefly, fixed size for /root and /boot, and the rest is filled up for > /srv. > > The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work > with Fedora29 (EL8). I get a "device is too small for new format" error. > Any hints? > > part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part > /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT > part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096 > pv.1974 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" > --name=00 --vgname=ee > logvol /srv --fstype="ext4" --percent=100 --grow --encrypted --label="SRV" > --name=01 --vgname=ee > If I'm reading that correctly - haven't worked on a kickstart in years - I'd start by increasing root to 1024 (1M) for /boot. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Issues trying to change the selinux context
Warren Young wrote: > On May 8, 2019, at 9:31 AM, mark wrote: > >> semanage -fcontext -a -t lib_t "//smwa/webagent/bin(/.*).so” > > [snip] > >> What am I doing wrong? >> > Also, I’m confused by the parens in your file path. Whether your shell > is or not is a different question. I'm following the manpage, semanage-fcontext, example as much as possible. EXAMPLE remember to run restorecon after you set the file context Add file-context for everything under /web # semanage fcontext -a -t httpd_sys_content_t "/web(/.*)?" # restorecon -R -v /web If semanage worked "normally", I'd have been able to do semanage fcontext -m -t lib_t "/path/smwa/webagent/bin/*.so" Hmmm, didn't complain when I did that... but they're still bin_t, not lib_t. On the selinux list, I was asked for the context of the directory, which is bin_t, which might be correct... if the idiots of CA had a ./lib directory, which they do not. Windows turkeys mark mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] kickstart compat C7 -> C8
Hi all, I still use the following kickstart partition scheme for C7 installations (via virt-install): Briefly, fixed size for /root and /boot, and the rest is filled up for /srv. The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096 pv.1974 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" --name=00 --vgname=ee logvol /srv --fstype="ext4" --percent=100 --grow --encrypted --label="SRV" --name=01 --vgname=ee Thanks, LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox esr repackage
firefox_repackage via CentOS wrote: > Hi everyone, I use firefox on centos 7 at work but due to the fairly well > know extension signing problem, I cannot use ublock origin. > > From what I can tell, the latest version of firefox in the updates > repository is 60.6.1-1.el7. It looks like Mozilla have just released > firefox esr 60.6.2 which should fix the signing issue. (see > https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/) The answer that I found Sunday (after being on a trip, and unable to play music Sat eve on my netbook) was this: 1. Go to about:config 2. Type signature in the search bar. 3. You'll see this key: xpinstall.signatures.required, click on it, to change the boolean from true to false. Stuff may work again. If not, go to tools add-ons, and reenable (which you could not do before the boolean change). mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [Fwd: [Bug 1699331] gssproxy segmentation fault]
Hi, Johnny, Johnny Hughes wrote: > On 5/2/19 9:15 AM, mark wrote: >> >> Especially Johnny - could you possibly push this fix through as soon as >> upstream puts it out? It's a real issue for us - we've had a number of >> servers whether gssproxy keeps SEGVing, which hits NFS and samba. > > See if this fixes your issues .. if do, let me know and we can get it > released into the fasttrack repo: > > https://buildlogs.centos.org/c7-fasttrack.x86_64/gssproxy/ > > Note: This packages are unsigned and if it fixes your issue, I'll sign > and release them into fasttrack repo > > Note2: Here is some info on our new fasttrack repo: > > https://wiki.centos.org/AdditionalResources/Repositories > (see CentOS-Fasttrack) Huh. Well, I don't see it SEGVing, but it suddenly started throwing May 8 12:21:21 kernel: gssproxy: server localhost not responding, timed out errors. That's the other thing we've been seeing, and I thought the two were related, but perhaps not mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL 8 released
You can experience RHEL8 via the developer version allowing you to work out how your configurations and management will have to change, which may coincide with CentOS arriving by the time you finish. /mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox esr repackage
> I was told lately about this workaround, check it out. > https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/ The signing thing is a security feature. I don't like a workaround to disable a security feature instead of fixing it. What makes me feel a bit bad is that everybody has fixed versions by now, only we enterprise Linux users using the ESR version still don't have fixed versions available. I don't complain because we usually get very fast updates, but this time we seem stuck. I can live with it but it's a bit difficult to explain to our users. Did upstream already release new packages? Regards, Simon > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - >> From: "CentOS mailing list" >> To: "CentOS mailing list" >> Sent: Wednesday, 8 May, 2019 16:50:20 >> Subject: [CentOS] Firefox esr repackage > >> Hi everyone, I use firefox on centos 7 at work but due to the fairly >> well know >> extension signing problem, I cannot use ublock origin. >> >> From what I can tell, the latest version of firefox in the updates >> repository is >> 60.6.1-1.el7. >> It looks like Mozilla have just released firefox esr 60.6.2 which should >> fix the >> signing issue. >> (see https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/) >> >> Would it be possible for someone to pass this message on to someone who >> can >> package this, so that users like me can update? >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Issues trying to change the selinux context
On May 8, 2019, at 9:31 AM, mark wrote: > > semanage -fcontext -a -t lib_t "//smwa/webagent/bin(/.*).so” [snip] > What am I doing wrong? -fcontext isn’t an option, it’s a verb; drop the dash. Also, I’m confused by the parens in your file path. Whether your shell is or not is a different question. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox esr repackage
so basically it says... "sit tight and wait..." Of course I tried to update the restclient, and when that didn't work uninstallit and tried to reinstallit...which didn't work either... On Wed, May 8, 2019 at 9:56 AM Nux! wrote: > I was told lately about this workaround, check it out. > > https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/ > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "CentOS mailing list" > > To: "CentOS mailing list" > > Sent: Wednesday, 8 May, 2019 16:50:20 > > Subject: [CentOS] Firefox esr repackage > > > Hi everyone, I use firefox on centos 7 at work but due to the fairly > well know > > extension signing problem, I cannot use ublock origin. > > > > From what I can tell, the latest version of firefox in the updates > repository is > > 60.6.1-1.el7. > > It looks like Mozilla have just released firefox esr 60.6.2 which should > fix the > > signing issue. > > (see https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/) > > > > Would it be possible for someone to pass this message on to someone who > can > > package this, so that users like me can update? > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Issues trying to change the selinux context
We're forced to use Siteminder, by CA, who have no clue what they're doing in *nix. No packages, tarballs... Anyway, I'm trying clean up some stuff, and in /*/smwa/webagent/bin (all their binaries, including .so's, are in there, duh... I'm trying to set the .so's to lib_t. semanage -fcontext -a -t lib_t "//smwa/webagent/bin(/.*).so" gives me the completely unexpected response of semanage: error: argument subcommand: invalid choice: 'lib_t' (choose from 'import', 'export', 'login', 'user', 'port', 'ibpkey', 'ibendport', 'interface', 'module', 'node', 'fcontext', 'boolean', 'permissive', 'dontaudit') What am I doing wrong? mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox esr repackage
I was told lately about this workaround, check it out. https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/ -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "CentOS mailing list" > To: "CentOS mailing list" > Sent: Wednesday, 8 May, 2019 16:50:20 > Subject: [CentOS] Firefox esr repackage > Hi everyone, I use firefox on centos 7 at work but due to the fairly well know > extension signing problem, I cannot use ublock origin. > > From what I can tell, the latest version of firefox in the updates repository > is > 60.6.1-1.el7. > It looks like Mozilla have just released firefox esr 60.6.2 which should fix > the > signing issue. > (see https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/) > > Would it be possible for someone to pass this message on to someone who can > package this, so that users like me can update? > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox esr repackage
might fix the signing issue... but a lot of plugins/addons broke... like the restclient ... dangit... On Wed, May 8, 2019 at 9:50 AM firefox_repackage via CentOS < centos@centos.org> wrote: > Hi everyone, I use firefox on centos 7 at work but due to the fairly well > know extension signing problem, I cannot use ublock origin. > > From what I can tell, the latest version of firefox in the updates > repository is 60.6.1-1.el7. > It looks like Mozilla have just released firefox esr 60.6.2 which should > fix the signing issue. > (see https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/) > > Would it be possible for someone to pass this message on to someone who > can package this, so that users like me can update? > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Firefox esr repackage
Hi everyone, I use firefox on centos 7 at work but due to the fairly well know extension signing problem, I cannot use ublock origin. >From what I can tell, the latest version of firefox in the updates repository >is 60.6.1-1.el7. It looks like Mozilla have just released firefox esr 60.6.2 which should fix the signing issue. (see https://www.mozilla.org/en-US/firefox/60.6.2/releasenotes/) Would it be possible for someone to pass this message on to someone who can package this, so that users like me can update? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] No network on cloned CentOS 7 installation
Nicolas Kovacs wrote: > Le 03/05/2019 à 20:10, Leon Fauster via CentOS a écrit : > >> Any MACs in /etc/udev/rules.d/70-persistent-net.rules ? > > After some more experimenting, I found out the showstopper was > completely unrelated to cloning. Someone had the unfortunate idea of doing > a hard reset on a local wireless access point, which resulted in two > active DHCP servers for two different subnets. As soon as this problem was > solved, all cloned PCs booted perfectly. > > The only thing I had to do was edit the hardcoded hostnames in > /etc/hostname. Right, and of course you weren't on the need-to-know list Glad to hear it worked out. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] No network on cloned CentOS 7 installation
Le 03/05/2019 à 20:10, Leon Fauster via CentOS a écrit : > Any MACs in /etc/udev/rules.d/70-persistent-net.rules ? After some more experimenting, I found out the showstopper was completely unrelated to cloning. Someone had the unfortunate idea of doing a hard reset on a local wireless access point, which resulted in two active DHCP servers for two different subnets. As soon as this problem was solved, all cloned PCs booted perfectly. The only thing I had to do was edit the hardcoded hostnames in /etc/hostname. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] youtube-dl No module named 'pkg_resources'
On Wed, 8 May 2019, Nux! wrote: How did you install it? Most recently yum reinstall youtube-dl I'm using their binary and it works great, just tested it. https://ytdl-org.github.io/youtube-dl/download.html - Original Message - From: "Michael Hennebry" To: "CentOS mailing list" Sent: Wednesday, 8 May, 2019 03:55:12 Subject: [CentOS] youtube-dl No module named 'pkg_resources' youtube-dl doesn't work for me after a recent update. I do not use it often, so do not know whether the update matters. It gives the error message: Traceback (most recent call last): File "/usr/bin/youtube-dl", line 6, in from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' I've tried reinstalling python-setuptools, installing python34-setuptools and reinstalling youtube-dl . I'm aware there is a bugzilla on it. That and stackoverflow are where I got the ideas above. How do I make youtube-dl work on Centos 7? -- Michael henne...@web.cs.ndsu.nodak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [Fwd: [Bug 1699331] gssproxy segmentation fault]
Hi, Johnny, Johnny Hughes wrote: > On 5/2/19 9:15 AM, mark wrote: >> >> Especially Johnny - could you possibly push this fix through as soon as >> upstream puts it out? It's a real issue for us - we've had a number of >> servers whether gssproxy keeps SEGVing, which hits NFS and samba. > > See if this fixes your issues .. if do, let me know and we can get it > released into the fasttrack repo: > > https://buildlogs.centos.org/c7-fasttrack.x86_64/gssproxy/ > > > Note: This packages are unsigned and if it fixes your issue, I'll sign > and release them into fasttrack repo > > Note2: Here is some info on our new fasttrack repo: > > > https://wiki.centos.org/AdditionalResources/Repositories > (see CentOS-Fasttrack) > Thank you very much. I've d/l the x86_64 rpm, and yum upgraded to it on one server, so it's soaking now, and we'll see what happens. One question: the email I got from RH bugzilla referred to the package as gssproxy-0.7.0-25, not 21, while I see you've got it as 21.el7.0.1. Will there be a name change, or will it be 21.whatever? mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Slow performance with NFSv4.1 on CentOS 7.5 ?
James Pearson wrote: > > We have a number of identical NFS clients mounting a server using > NFSv4.1 - server and clients are all running CentOS 7.5 (kernel > 3.10.0-862.14.4.el7.x86_64) > > However, on some clients, the NFS performance 'degrades' with time ... > > Running a simple test - a python script that just imports a module > (python and its modules are installed on the NFS share) can be an order > of magnitude or more slower on some clients. i.e. very little data is > transferred, it is the rate of stat'ing and opening files on the NFS > server that is 'slow' > > Running a tcpdump on a 'slow' client shows that the NFS traffic > generated on the 'slow' client is again an order of magnitude or more > when compared with that generated by a 'fast' client > > The majority of the extra NFS traffic in the slow case, appears to be a > large number of NFS 'TEST_STATEID' calls the client makes - which are > not there in the tcpdump on the fast client > > The issue can be 'fixed' in the short term by rebooting the affected > client - and after a reboot, running the same tcpdump shows no > TEST_STATEID calls - however after a while (several days), the > performance might degrade again > > I've found a number of reports of excessive TEST_STATEID calls - but > most seem to relate to NFSv4 client hangs - which is not happening here > - things are working, but much slower than they should be ... > > Has anyone come across this issue - and have any fixes/workarounds? After a bit of further poking about, it looks like we are hitting the issue described in: https://bugzilla.redhat.com/show_bug.cgi?id=1552203 The fix should be in 7.7, but the linked: https://access.redhat.com/solutions/3915571 (login required) has a few suggested workarounds which includes mounting with NFSv4.0 or disabling 'NFSv4 delegations' on the server via: sysctl -w fs.leases-enable=0 I've used the above sysctl which appears to have fixed the issue - although I had to restart NFS on the server to notice any change with the affected clients - so I'm not sure if the sysctl change or the NFS restart 'fixed' the issue ... James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [Fwd: [Bug 1699331] gssproxy segmentation fault]
On 5/2/19 9:15 AM, mark wrote: > Hi, folks, > >Especially Johnny - could you possibly push this fix through as soon as > upstream puts it out? It's a real issue for us - we've had a number of > servers whether gssproxy keeps SEGVing, which hits NFS and samba. > Mark, See if this fixes your issues .. if do, let me know and we can get it released into the fasttrack repo: https://buildlogs.centos.org/c7-fasttrack.x86_64/gssproxy/ Note: This packages are unsigned and if it fixes your issue, I'll sign and release them into fasttrack repo Note2: Here is some info on our new fasttrack repo: https://wiki.centos.org/AdditionalResources/Repositories (see CentOS-Fasttrack) signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] What happened if install a el7 package on a el6 system
On Wed, 8 May 2019 at 07:08, Peter wrote: > On 8/05/19 12:22 AM, Robert Heller wrote: > The >> are from me. > >> Many CentOS-7 packages will not install because they will need > dependencies > >> that the EL-6 does not have. > > Correct, and different versions of dependencies, and files go in > different locations, etc. > > >> The kernel is different because it is mostly > >> self-contained and meant to be parallel installed. > > Correct. > > > In most cases, it should > >> result in an unbootable system because the boot is going to be > >> dracut+systemd bits and the EL-6 has none of that. > > Older versions of dracut will run on newer kernels just fine. When you > install the kernel on CentOS 6 it will run the CentOS 6 version of > dracut at the time of the install and create a CentOS 6 compatible > initramfs image. > > I wasn't sure if this would work, but since the person has a working system and you have explained why.. I learned something new. Thank you. > Systemd is user-space and does not include components in the kernel (as > far as I'm aware). Even if it does, the kernel is still > backwards-compatible and would boot just fine to upstart (which is the > init system in CentOS 6), it simply would not use those modules and > features that are used for systemd. > > > And I wonder if the EL7 kernel will even show up as an available > kernel. EL7 > > uses Grub 2 and EL6 uses Grub [1]. > > CentOS 7 does have grub legacy (1) as an option and does work fine with > grub legacy. I have set up CentOS 7 systems that use grub legacy in the > past. It stands to reason that a kernel that installs and configures > just fine in grub legacy on CentOS 7 will do the same in grub on CentOS 6. > > > I know that when I installed Ubuntu 18.04 as a *second* OS, that even > though > > the /boot file system is shared between CentOS 6 and Ubuntu 18.04 the > Ubuntu > > 18.04 installer did not touch /boot/grub/grub.conf and installed > > /boot/grub/grub.cfg along side (I manually reinstalled grub 1 and > manually > > hacked /boot/grub/grub.conf to put the Ubuntu 18.04 boot option in). > > This is not the case with CentOS. You can run dual-boot CentOS 6 and 7 > on the same grub legacy boot loader and CentOS 7 will boot up and run > just fine. > > While I cannot make any guarantees that a CentOS 7 kernel will not cause > issues running in CentOS 6, and indeed I would not support a system that > used such, the Linux kernel, being self-contained and largely > backwards-compatible should in theory, at least, not have issues running > a CentOS 7 kernel on CentOS 6, and indeed there are newer kernels that > are specifically built for CentOS 6 (elrepo kernel-ml) that run just > fine as well. > > The main thing that might stand in your way would be any changes to the > rpm file format (which does happen from time to time) that prevent an > rpm built for CentOS 7 from being recognized and installible by rpm or > yum in older versions of CentOS 6. I am aware of such changes from > older versions of CentOS but none between CentOS 6 and 7. > > So in summary, it would probably work just fine, but I wouldn't do it, > recommend it or support it. > > > Peter > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] What happened if install a el7 package on a el6 system
On 8/05/19 12:22 AM, Robert Heller wrote: Many CentOS-7 packages will not install because they will need dependencies that the EL-6 does not have. Correct, and different versions of dependencies, and files go in different locations, etc. The kernel is different because it is mostly self-contained and meant to be parallel installed. Correct. In most cases, it should result in an unbootable system because the boot is going to be dracut+systemd bits and the EL-6 has none of that. Older versions of dracut will run on newer kernels just fine. When you install the kernel on CentOS 6 it will run the CentOS 6 version of dracut at the time of the install and create a CentOS 6 compatible initramfs image. Systemd is user-space and does not include components in the kernel (as far as I'm aware). Even if it does, the kernel is still backwards-compatible and would boot just fine to upstart (which is the init system in CentOS 6), it simply would not use those modules and features that are used for systemd. And I wonder if the EL7 kernel will even show up as an available kernel. EL7 uses Grub 2 and EL6 uses Grub [1]. CentOS 7 does have grub legacy (1) as an option and does work fine with grub legacy. I have set up CentOS 7 systems that use grub legacy in the past. It stands to reason that a kernel that installs and configures just fine in grub legacy on CentOS 7 will do the same in grub on CentOS 6. I know that when I installed Ubuntu 18.04 as a *second* OS, that even though the /boot file system is shared between CentOS 6 and Ubuntu 18.04 the Ubuntu 18.04 installer did not touch /boot/grub/grub.conf and installed /boot/grub/grub.cfg along side (I manually reinstalled grub 1 and manually hacked /boot/grub/grub.conf to put the Ubuntu 18.04 boot option in). This is not the case with CentOS. You can run dual-boot CentOS 6 and 7 on the same grub legacy boot loader and CentOS 7 will boot up and run just fine. While I cannot make any guarantees that a CentOS 7 kernel will not cause issues running in CentOS 6, and indeed I would not support a system that used such, the Linux kernel, being self-contained and largely backwards-compatible should in theory, at least, not have issues running a CentOS 7 kernel on CentOS 6, and indeed there are newer kernels that are specifically built for CentOS 6 (elrepo kernel-ml) that run just fine as well. The main thing that might stand in your way would be any changes to the rpm file format (which does happen from time to time) that prevent an rpm built for CentOS 7 from being recognized and installible by rpm or yum in older versions of CentOS 6. I am aware of such changes from older versions of CentOS but none between CentOS 6 and 7. So in summary, it would probably work just fine, but I wouldn't do it, recommend it or support it. Peter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] youtube-dl No module named 'pkg_resources'
How did you install it? I'm using their binary and it works great, just tested it. https://ytdl-org.github.io/youtube-dl/download.html -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Michael Hennebry" > To: "CentOS mailing list" > Sent: Wednesday, 8 May, 2019 03:55:12 > Subject: [CentOS] youtube-dl No module named 'pkg_resources' > youtube-dl doesn't work for me after a recent update. > I do not use it often, so do not know whether the update matters. > It gives the error message: > Traceback (most recent call last): > File "/usr/bin/youtube-dl", line 6, in > from pkg_resources import load_entry_point > ModuleNotFoundError: No module named 'pkg_resources' > > I've tried reinstalling python-setuptools, > installing python34-setuptools and reinstalling youtube-dl . > > I'm aware there is a bugzilla on it. > That and stackoverflow are where I got the ideas above. > > How do I make youtube-dl work on Centos 7? > > -- > Michael henne...@web.cs.ndsu.nodak.edu > "Sorry but your password must contain an uppercase letter, a number, > a haiku, a gang sign, a heiroglyph, and the blood of a virgin." > -- someeecards > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Re-install workstation - best repo's
I'm going to rebuild my workstation because maintaining it is now a nightmare after using "recommended" repo's that now conflict with each other. Every time I do a yum update I it fails with conflicts. I'm looking for new recommendations for which repo's to use to have a stable Centos 7 workstation. Much like Centos itself, most of the web pages are very old now. I'm looking for a KDE workstation with mp3 support and video editing. I use simple command line tools such as ffmpeg. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
