[CentOS] Unresolved dependencies when upgrade on centOS 8
Hi, Guys i got unresolved dependencies when trying to upgrade centOS 8, what should i do to fix this? [root@ws1 ebedsat]# dnf upgrade Last metadata expiration check: 0:14:27 ago on Sat 11 Jan 2020 12:16:02 PM WIB. Error: Problem 1: cannot install the best update candidate for package kmod-iwlegacy-0.0-1.el8.elrepo.x86_64 - nothing provides kernel >= 4.18.0-147.el8 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(__pci_register_driver) = 0xe85eaefe needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_unregister_driver) = 0x4883cfc3 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_set_master) = 0xe724f530 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(kmalloc_caches) = 0x8200293d needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_disable_device) = 0x24796ca2 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_enable_device) = 0x982a3dc2 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_release_regions) = 0xbf4a2a75 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_request_regions) = 0x9c656956 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_write_config_byte) = 0x21935607 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_read_config_word) = 0x3dc485cf needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_disable_msi) = 0xc174fcd7 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_enable_msi) = 0xda24a9c7 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_write_config_word) = 0x4b15b75c needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pci_disable_link_state) = 0x02f2f3f8 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(generic_file_llseek) = 0xc27ffb37 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(debugfs_create_dir) = 0x2f4ce417 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(debugfs_create_file) = 0x501d615e needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_alloc_hw_nm) = 0xba0c6cb1 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_beacon_get_tim) = 0x3e9fc88e needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_free_hw) = 0x1a211787 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_register_hw) = 0x94f9cf8d needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_rx_napi) = 0xe42fba8f needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_stop_queue) = 0x14b3a816 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_stop_queues) = 0x5d5f40f9 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_unregister_hw) = 0x740a5bb2 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_wake_queue) = 0xfa79b997 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_wake_queues) = 0xa900f2df needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(led_classdev_unregister) = 0x9fd8b0e4 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(of_led_classdev_register) = 0xe2dcc6bc needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(wiphy_rfkill_set_hw_state) = 0x1df077cc needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(debugfs_remove) = 0x9ef3e60b needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(debugfs_remove_recursive) = 0x4668b613 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(default_llseek) = 0x384172fd needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(pcie_capability_read_word) = 0xa785480e needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(__ieee80211_create_tpt_led_trigger) = 0x0d0ddd5f needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(__ieee80211_get_radio_led_name) = 0xd1d478f1 needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_chswitch_done) = 0xced3a36a needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_find_sta) = 0xc579589b needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_rate_control_register) = 0xabcd1b6e needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides kernel(ieee80211_rate_control_unregister) = 0x22eec09c needed by kmod-iwlegacy-0.0-2.el8_1.elrepo.x86_64 - nothing provides
[CentOS] firefox update
Any idea when firefox-68.4.1 will be available? Thanks, Email Confidentiality Notice: The information contained in this transmission may contain privileged and confidential and/or protected health information (PHI) and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act of 1996, as amended (HIPAA). This transmission is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, dissemination, distribution, printing or copying of this transmission is strictly prohibited and may subject you to criminal or civil penalties. If you have received this transmission in error, please contact the sender immediately and delete this email and any attachments from any computer. Vaso Corporation and its subsidiary companies are not responsible for data leaks that result from email messages received that contain privileged and confidential and/or protected health information (PHI). ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Building and packaging httpd
On 1/10/20 6:34 PM, Jonathan Billings wrote: On Fri, Jan 10, 2020 at 06:18:07PM +0300, Benson Muite wrote: Am rebuilding httpd from scratch to enable http2 and minimize extra modules on Cent Os 8. Am having trouble understanding the spec file [0] and systemd initialization [1][2][3] (these are very similar to those extracted from [4]). Why are 3 scripts needed to start the service and why is a pid setting not needed as used in the httpd.service file at [5]? The httpd-init.service handles some ssl cert generation on the first time a system runs, so httpd doesn't just die because there were missing SSL certs. They're self-signed. The httpd.socket unit lets you have systemd listen on port 80 and only start httpd if someone connects. THat's not a standard use, though. The httpd.service in the Fedora/CentOS systemd service unit uses Type=notify instead of Type=forking. While it's possible for systemd to keep track of all the subprocesses of a forking daemon, its difficult to determine if the service is "started". It uses the Pid file for that. With Type=notify, the daemon will send a notification back to systemd via sd_notify() when it is up, which makes it easier for systemd to know when a service has started, and start any dependencies or established that a target has been reached. You need a service that supports Type=notify, which httpd does. Thanks. Seems like need to use development version [0] or use patch [1] [0] https://svn.apache.org/viewvc/httpd/httpd/trunk/modules/arch/unix/mod_systemd.c?revision=1840555=markup [1] https://src.fedoraproject.org/rpms/httpd/blob/master/f/httpd-2.4.33-systemd.patch ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] copying files to fill flash drives
On 1/10/20 2:33 AM, Frank Cox wrote: Back in the days of DOS I had a program that I obtained from somewhere called FILL. ... Before I re-invent the wheel here, does someone already have a way to do this with Linux so you can write a series of flash drives and fill them with the contents of a specified directory without modifying the files that get written? This would, in my opinion, be a useful thing. I found several simple knapsack implementations; one of which is at https://github.com/vaeth/knapsack What would be very useful is to dynamically load the knapsack based on size of whatever USB drive you just plugged in; so if you have say 4 32GB drives, a 128GB drive, and a 64GB drive, the filling would be efficient no matter which order you plug the drives in. There have been several times I have wished for such a utility; I had one for the old TRS-80 LS-DOS 6 when I ran a TRS-80 Model 4 with a 20MB hard drive to copy to floppies, even when the floppies might have a different amount of free space. I've done the multi-floppy tar thing back in Xenix days, and that was painful to say the least. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] copying files to fill flash drives
On Fri, 10 Jan 2020, Chris Adams wrote: If it helps your search, what you are looking for is an application of the knapsack algorithm. Actually bin packing. -- 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] Building and packaging httpd
On Fri, Jan 10, 2020 at 06:18:07PM +0300, Benson Muite wrote: > Am rebuilding httpd from scratch to enable http2 and minimize extra modules > on Cent Os 8. Am having trouble understanding the spec file [0] and systemd > initialization [1][2][3] (these are very similar to those extracted from > [4]). Why are 3 scripts needed to start the service and why is a pid setting > not needed as used in the httpd.service file at [5]? The httpd-init.service handles some ssl cert generation on the first time a system runs, so httpd doesn't just die because there were missing SSL certs. They're self-signed. The httpd.socket unit lets you have systemd listen on port 80 and only start httpd if someone connects. THat's not a standard use, though. The httpd.service in the Fedora/CentOS systemd service unit uses Type=notify instead of Type=forking. While it's possible for systemd to keep track of all the subprocesses of a forking daemon, its difficult to determine if the service is "started". It uses the Pid file for that. With Type=notify, the daemon will send a notification back to systemd via sd_notify() when it is up, which makes it easier for systemd to know when a service has started, and start any dependencies or established that a target has been reached. You need a service that supports Type=notify, which httpd does. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Building and packaging httpd
Hi, Am rebuilding httpd from scratch to enable http2 and minimize extra modules on Cent Os 8. Am having trouble understanding the spec file [0] and systemd initialization [1][2][3] (these are very similar to those extracted from [4]). Why are 3 scripts needed to start the service and why is a pid setting not needed as used in the httpd.service file at [5]? Benson [0] https://src.fedoraproject.org/rpms/httpd/blob/HEAD/f/httpd.spec [1] https://src.fedoraproject.org/rpms/httpd/tree/f31 [2] https://src.fedoraproject.org/rpms/httpd/blob/f31/f/httpd.service [3] https://src.fedoraproject.org/rpms/httpd/blob/f31/f/httpd-init.service [4] http://vault.centos.org/8.0.1905/AppStream/Source/SPackages/httpd-2.4.37-12.module_el8.0.0+185+5908b0db.src.rpm [5] https://blacksaildivision.com/how-to-install-apache-httpd-on-centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] copying files to fill flash drives
Once upon a time, Frank Cox said: > FILL would take the name of a directory and then start writing files from > that directory onto a series of floppy disks in such a way that each disk was > made as full as possible, but without modifying the files that it was writing. I remember using a program like that. I'm not sure if something like that is available for Linux, and if it would handle USB (you'd have to actually look at each stick since they aren't always exactly the same size). If it helps your search, what you are looking for is an application of the knapsack algorithm. -- Chris Adams ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] copying files to fill flash drives
> On Jan 10, 2020, at 1:33 AM, Frank Cox wrote: > > Back in the days of DOS I had a program that I obtained from somewhere called > FILL. > > FILL would take the name of a directory and then start writing files from > that directory onto a series of floppy disks in such a way that each disk was > made as full as possible, but without modifying the files that it was writing. > > So you might end up with disk 1 having files A B and D on them since D fitted > but C was too big so it went onto Disk 2 along with files E and F. > > Before I re-invent the wheel here, does someone already have a way to do this > with Linux so you can write a series of flash drives and fill them with the > contents of a specified directory without modifying the files that get > written? The reason that I specify without modifying the files is that I > could do this easily with tar and split, but then I end up with a tar file > and can't just look on disk 1 and copy file A off of it later on. > I only can think of vaguely resembling thing: multi-volume tar archives, as in: https://mynixworld.info/2014/04/13/creating-multi-volume-tar-bz2/ Valeri > -- > MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com > ___ > 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] copying files to fill flash drives
On Fri, Jan 10, 2020 at 01:33:23AM -0600, Frank Cox wrote: > > Back in the days of DOS I had a program that I obtained from > somewhere called FILL. > > FILL would take the name of a directory and then start writing files > from that directory onto a series of floppy disks in such a way that > each disk was made as full as possible, but without modifying the > files that it was writing. > > So you might end up with disk 1 having files A B and D on them since > D fitted but C was too big so it went onto Disk 2 along with files E > and F. > > Before I re-invent the wheel here, does someone already have a way > to do this with Linux so you can write a series of flash drives and > fill them with the contents of a specified directory without > modifying the files that get written? The reason that I specify > without modifying the files is that I could do this easily with tar > and split, but then I end up with a tar file and can't just look on > disk 1 and copy file A off of it later on. GNU tar (and older BSD versions too) have always supported writing to multiple tapes. You can set a multi-volume tar file with tar -M -L ... https://www.gnu.org/software/tar/manual/html_node/Multi_002dVolume-Archives.html I suspect if you got the right length it'll work pretty well. It might work without specifying it, if it detects the end of the device correctly, but I'd test it first. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Blocking attacks from a range of IP addresses
Hi! I usually use a primary ssh jail via f2b, ontop of that I have a reapeat offenders (usually a check on the f2b logs and rotation needs to be modified) over a long time. https://wireflare.com/blog/permanently-ban-repeat-offenders-with-fail2ban/ this could be modified to block bigger pieces of the network. Sadly I have no direct example for you. A suggestion is to look into for instance the ipsets from firehol. Unless you have a more targeted attack using blocklists might be a good option. Thing is, you might be at a point were any automation does more harm then good. It depends on what your service does. If it is your homelab with port 22 exposed, the just add big blocks or import firehol-1 and 99% of the attacks will be dropped. If it is a popular website and you are in need of blocking webbots then more care needs to be taken. My suggestion is: Firehol+change ssh port (if that is the service in question)+ssh tarpit+repeat offenders Regards On Thu, Jan 9, 2020, 20:10 Pete Biggs wrote: > > > > > > > > As far as I can see fail2ban only deals with hosts and not networks - I > > > suspect the issue is what is a "network": It may be obvious to you > > > looking at the logs that these are all related, but you run the risk > > > that getting denied accesses from, say, 1.0.0.1 and 1.1.0.93 and > > > 1.2.0.124 may be interpreted as a concerted attack and you banning half > > > the internet - but that may not be a bad thing :-) > > > > > > > Since you can configure fail2ban to invoke scripts, I would think it > > would be possible to get it to block CIDRs (variable size subnets, i.e. > > 12.12.0.0/20). That said, I don't have a quick and easy implementation > > on hand. > > The OP was looking for an automated way of fail2ban doing it - he had > already sorted out the network range and had stopped this particular > DoS attack. > > P. > > > ___ > 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
