[CentOS] CentOS7 wireless config on command line on asus
Hi all, I'm trying to configure wireless on my Asus laptop running CentOS7. I see wlan0 when I type iw dev, but if I type ip link set wlan0 up I get the following error: RTNETLINK answers: Operation not possible due to RF-kill Any idea what is wrong?? Adrian -- Adri P. van Bloois Antonlaan 104 email: adr...@pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax:NONE 52 05'15.77"N 5 4'44.56"E QTH-locater JO 22 OC "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] USB Serial ports (ttyACMn) CentOS 6.7 (64-bit) vs. CentOS 6.7 (64-bit)
I have two computers: both running CentOS 6.7, 64-bit, with kernel 2.6.32-573.12.1.el6.x86_64. One is a laptop with an 2 core Intel processor and the other is a desktop machine with a 4 core AMD processor. Both with selinux enabled. I have a USB serial port device (a RR-CirKits LCC-Buffer USB). On the desktop I am getting this error: sauron.deepsoft.com% sudo minicom Device /dev/ttyACM0 access failed: No such file or directory. sauron.deepsoft.com% dir -lZ /dev/ttyACM0 crw-rw. root dialout system_u:object_r:tty_device_t:s0 /dev/ttyACM0 But it is working on the laptop! gollum.deepsoft.com% dir -lZ /dev/ttyACM1 crw-rw. root dialout system_u:object_r:tty_device_t:s0 /dev/ttyACM1 Same kernel, same device (except it is showing up as ttyACM1 on the laptop). What is going on here? -- Robert Heller -- 978-544-6933 Deepwoods Software-- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] devtoolset-4
On 28/01/16 10:54, Kay Diederichs wrote: > Hi, > > is there any way to get access to devtoolset-4 ? > > I see alot of stuff at > http://cbs.centos.org/koji/packageinfo?packageID=2076 . Is this not yet > released? > not as yet, the SCL Sig guys are working through the initial bootstrap, and should have it done soon - I would recommend dropping into the next SCL SIG meeting ( they are held on IRC in #centos-devel on irc.freenode.net at 16:00 UTC on alternate Wednesdays ). https://www.centos.org/community/calendar/#Software_Collections_SIG_Sync-up regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange performance issue on CentOS 6.7 server
On Feb 3, 2016, at 3:23 PM, Alfred von Campewrote: > > On Feb 3, 2016, at 17:10, Warren Young wrote: > >> smartctl can see through several different types of RAID controller to the >> underlying physical disks via its -d option. > > This is what I have: > > # smartctl --all /dev/sda > smartctl 5.43 2012-06-30 r3573 [i686-linux-2.6.32-573.12.1.el6.i686] (local > build) > Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net > > Vendor: IBM > Product: ServeRAID M5110e A bit of Googling says that’s an LSI 2208 based card. So, try smartctl -a -d megaraid,0 If that works, you should be able to walk through each disk by incrementing that trailing number. Then, you can add -t flags to do active tests. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 wireless config on command line on asus
On 04/02/16 21:29, Adrian P. van Bloois wrote: > Hi all, > I'm trying to configure wireless on my Asus laptop running CentOS7. > I see wlan0 when I type iw dev, but if I type > ip link set wlan0 up > I get the following error: > RTNETLINK answers: Operation not possible due to RF-kill > > Any idea what is wrong?? your laptop has a switch to turn on/ turn off the wifi - and its currently turned off. this might be a real switch, or a key combination. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kernel Panic post kernel-2.6.32-504.23.4.el6.x86_64
On Feb 3, 2016, at 5:28 PM, Peter Q.wrote: > > probably open bug I don’t know how you get “probably” out of these two screenshots. Both machines seem to be crashing in about the same place in the boot, and both seem to have Intel graphics, but the resulting crashes are quite different. The test is simple, though: Max, try removing “nomodeset” from one of the failing kernel option lines and see what happens. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-virt] c7 xen-4.6 crash.
Installing xen on a fairly clean c7.2 system. I get a xen kernel panic. (XEN) Bad console= option 'tty' Xen 4.6.0-9.el7 (XEN) Xen version 4.6.0-9.el7 (mockbu...@centos.org) (gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)) debug=n Wed Jan 20 12:25:53 UTC 2016 (XEN) Latest ChangeSet: Thu Jan 14 15:35:35 2016 + git:6e8597a-dirty (XEN) Bootloader: GRUB 2.02~beta2 (XEN) Command line: placeholder dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 2 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ac00 (usable) (XEN) 0009ac00 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - bffc7280 (usable) (XEN) bffc7280 - bffceac0 (ACPI data) (XEN) bffceac0 - c000 (reserved) (XEN) e000 - f000 (reserved) (XEN) fec0 - 0001 (reserved) (XEN) 0001 - 00084000 (usable) (XEN) ACPI: RSDP 000FDFD0, 0024 (r2 IBM ) (XEN) ACPI: XSDT BFFCE980, 0054 (r1 IBMSERVALNT 1000 IBM 45444F43) (XEN) ACPI: FACP BFFCE8C0, 0084 (r2 IBMSERVALNT 1000 IBM 45444F43) (XEN) ACPI: DSDT BFFC7280, 2F12 (r2 IBMSERVALNT 1000 INTL 20041203) (XEN) ACPI: FACS BFFCA7C0, 0040 (XEN) ACPI: APIC BFFCE800, 0084 (r1 IBMSERVALNT 1000 IBM 45444F43) (XEN) ACPI: SRAT BFFCE6C0, 00E8 (r1 IBMSERVALNT 1000 IBM 45444F43) (XEN) ACPI: HPET BFFCE680, 0038 (r1 IBMSERVALNT 1000 IBM 45444F43) (XEN) ACPI: MCFG BFFCE640, 003C (r1 IBMSERVALNT 1000 IBM 45444F43) (XEN) ACPI: ERST BFFCA800, 0230 (r1 IBMSERVALNT 1000 IBM 45444F43) (XEN) System RAM: 32767MB (33553796kB) (XEN) SRAT: PXM 0 -> APIC 0 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 1 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 6 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 7 -> Node 0 (XEN) SRAT: Node 0 PXM 0 0-c000 (XEN) SRAT: Node 0 PXM 0 1-84000 (XEN) SRAT: Node 0 PXM 0 84000-84100 (hotplug) (XEN) NUMA: Using 18 for the hash shift. (XEN) Domain heap initialised (XEN) found SMP MP-table at 0009ad40 (XEN) DMI 2.4 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x588 (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:584,1:0], pm1x_evt[1:580,1:0] (XEN) ACPI: wakeup_vec[bffca7cc], vec_size[20] (XEN) ACPI: Local APIC address 0xfee0 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) (XEN) Processor #1 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) (XEN) Processor #6 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) (XEN) Processor #7 6:15 APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) (XEN) ACPI: IOAPIC (id[0x0e] address[0xfec0] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 14, version 32, address 0xfec0, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed0 (XEN) Invalid bit width in GAR (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 24 GSI, 760 MSI/MSI-X (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) CMCI: CPU0 has no CMCI support (XEN) CPU0: Thermal monitoring enabled (TM2) (XEN) Intel machine check reporting enabled (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2992.543 MHz processor. (XEN) Initing memory sharing. (XEN) alt table 82d0802b8c50 -> 82d0802b9ff4 (XEN) PCI: MCFG configuration 0: base e000 segment buses 00 - 25 (XEN) PCI: MCFG area at e000 reserved in E820 (XEN) PCI: Using MCFG for segment bus 00-25 (XEN) I/O virtualisation disabled (XEN) CPU0: Intel(R) Xeon(R) CPU5160 @ 3.00GHz stepping 06 (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pde. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed0 (XEN) Invalid bit width in GAR (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 24 GSI, 760 MSI/MSI-X (XEN) CPU: L1 I cache:
Re: [CentOS-virt] Where is QXL driver for Windows?
On Thu 4.Feb'16 at 0:10:18 +0100, Alexander Dalloz wrote: > Am 03.02.2016 um 22:29 schrieb Alexander Dalloz: > >Am 03.02.2016 um 17:40 schrieb C. L. Martinez: > >>Hi all, > >> > >> Where can I found QXL driver for Windows 2012 R2/Windows 8.1? I > >>don't see inside latest/stable iso images from fedoraproject ... > >> > >>Thanks. > >> > > > >Don't know what you are checking, but it is definitely included in > > > >https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso > > > > > >Have used it myself just recently for a few Windows Server 2012 R2 VM > >installs. > > > >Regards > > > >Alexander > > Page > > https://fedoraproject.org/wiki/Windows_Virtio_Drivers > > states > > qxl/: QXL graphics driver for Windows 7 and earlier. (build > virtio-win-0.1.103-1 and later) > qxldod/: QXL graphics driver for Windows 8 and later. (build > virtio-win-0.1.103-2 and later) > > So stable is not fresh enough while latest contains both. > > Alexander Got it. Many thanks Alexander. I have downloaded stable iso only ... Sorry. -- Greetings, C. L. Martinez ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS] Issue with installation on wireless-only desktop workstation, CentOS 7(1511)
I realize that many on this list have likely applauded the NetworkManager package split that removed wireless stuff into its own package, NetworkManager-wifi, because for wired workstations and servers it might be desirable to not have any wifi software installed. And I believe it was a sound technical decision to do the split. However, in doing a fresh installation of what most call CentOS 7.2, or 7.2.1511, I ran into a real issue that required a bit of deep-diving to find, and a simple 'yum install NetworkManager-wifi' to fix. (although my actual 'yum install' command included the full path to the actual RPM on the install media...) I have a personal workstation at home, a Dell Optiplex 745 with a Core2Quad Q6600, that is on the other end of the house from the router. While I could run cat5 to the location, it would involve quite a bit of labor, and I have a known-supported USB wifi nic based on the ralink rt3070 (cheap, but works well), so why should I run the cable when wifi should work well? Especially given that the Dell is not going to be there for very long it wouldn't make sense to run cable. Anyway, I configured the wifi network during installation (I actually am growing to like, even prefer, the hub-and-spoke anaconda), it associated with the WPA2-protected AP, grabbed an IP address, and all was good. Did the install; no errors. I rebooted, and now there is no wireless. At all. Doing a bit of troubleshooting shows that the kernel sees the NIC, but NetworkManager shows it as 'unmanaged' ('nmcli d' is the command to use from a shell). So I warmed up my google-fu on my laptop and finally tracked it to a post that mentioned having to install NetworkManager-wifi. Sure enough, on the workstation NetworkManager-wifi was not installed. I mounted the USB install drive's ISO partition and manually installed it, restarted NetworkManager, and it now works just fine. But why did anaconda not select the NetworkManager-wifi package to be installed if a wireless network connection was configured in the installer? Anaconda should have some way of forcing the install of the appropriate NetworkManager modules if those are needed (but only if they are actually needed) for a configured connection during install. I can file a bugzilla, but I thought I'd post about it here first to get an idea of which package in which to file the report, since it's not a bug in NetworkManager-wifi. Anaconda? (that is my first impression of the proper place). So if you have this situation arise where wifi doesn't work after install of current CentOS 7(1511) but does during install, manually install NetworkManager-wifi from the install media and that should clear it up. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] delete directories with find and exclude other directories
From: Valeri Galtsev Sent: Wednesday, February 03, 2016 12:58 PM On Wed, February 3, 2016 11:37 am, Tim Dunphy wrote: > Hi all, > > I'm attempting to delete some directories and I want to be able to exclude > a directory called 'logs' from being deleted. > > This is my basic find operation (without the exclusion) > > # find . -type d |tail -10 > ./d20160124-1120-df8mfb/deployments > ./d20160124-1120-df8mfb/releases > ./d20160131-16993-vazqg5 > ./d20160131-16993-vazqg5/metadata > ./d20160131-16993-vazqg5/deployments > ./d20160131-16993-vazqg5/releases > ./logs > ./d20160203-27735-1tqbjh6 > ./d20160125-1120-1yccr9p > ./d20160131-16993-1yf9lnc crude thing I would do is: find . -type d | grep -v logs , but that will also exclude other names containing "logs" it is like: Semilogs2 logs4me #just skip the local logs dir find . -type d -not -wholename ./logs #skip dirs that start with /logs any where in the search find . -type d -not -wholename \*/logs\* #skip dirs that have log anywhere in their name, like Valeri's find . -type d -not -wholename \*logs\* and to actually get rid of the found _empty_dirs_ that are not logs... find . -type d -not -wholename \*logs\* -exec rmdir {} \; note 1: as written would have to be ran multiple times to empty deeper directory trees. note 2: just because a logs dir is not shown/passed by the above command, does not mean that there was not one deep within a tree, so recursive removals might do more than you want. See recent UEFI thread. :) note 3: rmdir can be replaced with your favorite destruction command, choose wisely. note 4: I recommend when using an rm command, use a specific directory _name_ to find instead of '.', so there is _less_ chance of using it where you don't want to. Even when this disclaimer is not here: I am not a contracting officer. I do not have authority to make or modify the terms of any contract. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-announce] CEBA-2016:0111 CentOS 6 pango FASTTRACK BugFix Update
CentOS Errata and Bugfix Advisory 2016:0111 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0111.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1ae8ed9e7dfc0a5d162f1fb129bfdd2c7fb7d849ca0595da225a73796e770cb6 pango-1.28.1-11.el6.i686.rpm bf2effc6dc9d35fbd5b0505dbcd3971733cd0ca4f909423fbed66aaaf8c33ede pango-devel-1.28.1-11.el6.i686.rpm x86_64: 1ae8ed9e7dfc0a5d162f1fb129bfdd2c7fb7d849ca0595da225a73796e770cb6 pango-1.28.1-11.el6.i686.rpm 0663a5ce99cebf5285d96c4d92fc83155e859976bfd72980bf8691c3e89f92ad pango-1.28.1-11.el6.x86_64.rpm bf2effc6dc9d35fbd5b0505dbcd3971733cd0ca4f909423fbed66aaaf8c33ede pango-devel-1.28.1-11.el6.i686.rpm 1536c68fa4ab95ebf1a5852d86d5b3b70d50e14ad213c03d4a79379e12784092 pango-devel-1.28.1-11.el6.x86_64.rpm Source: b7769f4cfbec69171ef48b8e2bb686555a578515eec225ebebfae286a343e384 pango-1.28.1-11.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #cen...@irc.freenode.net Twitter: @JohnnyCentOS ___ CentOS-announce mailing list CentOS-announce@centos.org https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CEBA-2016:0114 CentOS 6 gedit FASTTRACK BugFix Update
CentOS Errata and Bugfix Advisory 2016:0114 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0114.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5849aebc9ed3b1e12d44b61d9aee1a256a3bdd116261586f042edbeaf1fa41d3 gedit-2.28.4-4.el6.i686.rpm 433783573ba98a06768256f918acfdef155428a0da9191929ffee8631fd32dc7 gedit-devel-2.28.4-4.el6.i686.rpm x86_64: 4e1971a77c40178e51681780705e5de9d905bff6b8409ef469f7cfd93fbc14ac gedit-2.28.4-4.el6.x86_64.rpm 433783573ba98a06768256f918acfdef155428a0da9191929ffee8631fd32dc7 gedit-devel-2.28.4-4.el6.i686.rpm c6e34f37c82dea4f926e359e3794ef8b946cf8690634695c4cfc8b55b759fa63 gedit-devel-2.28.4-4.el6.x86_64.rpm Source: 0956db00b0cd9e04fbf230ef7406467459c1b9f3d408003b22d8e2844fdc8118 gedit-2.28.4-4.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #cen...@irc.freenode.net Twitter: @JohnnyCentOS ___ CentOS-announce mailing list CentOS-announce@centos.org https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CEBA-2016:0113 CentOS 6 pulseaudio FASTTRACK BugFix Update
CentOS Errata and Bugfix Advisory 2016:0113 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0113.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4c589de07eb7a99d5e7b53663f729c99a175dc29c8381f08ca956a75589a674b pulseaudio-0.9.21-24.el6.i686.rpm 267af660554bcd901bd18ef0589ca2fc68cd4dc73335435b4a53ac343c0187f7 pulseaudio-esound-compat-0.9.21-24.el6.i686.rpm 71657db3b779d30494918e188b70310147e92b1fa224509079ce601a1c91b959 pulseaudio-gdm-hooks-0.9.21-24.el6.i686.rpm ebb56fd219094a860dab8c3d703fc6c50d084384083df1fe04a9616d423fd2f9 pulseaudio-libs-0.9.21-24.el6.i686.rpm 70358534593525744fdd92a8d85d4453e28c09ceb1eb4d2ce029b38c6e3765ce pulseaudio-libs-devel-0.9.21-24.el6.i686.rpm ee0884955f5ab06488b2049b8065fdca2742404e72a74b39387f57b027bdb15a pulseaudio-libs-glib2-0.9.21-24.el6.i686.rpm a8e7c5f5dc349797a2a6753aefe4ef0ebfb93223c0b9ff16f34c81c53ae69cb1 pulseaudio-libs-zeroconf-0.9.21-24.el6.i686.rpm 2de4b1e2b89ba63677dfb055b5019829f55fa5cdb8a236c1f95987341a078e73 pulseaudio-module-bluetooth-0.9.21-24.el6.i686.rpm 744089a86c8bc4fd633113b078862c58f8bda61044f36ce7e5d85e2030ae6386 pulseaudio-module-gconf-0.9.21-24.el6.i686.rpm fab49205f7498c88ab89210d6ab7cf2f9d4743e296c8a6df77dcb7cd3aec01d2 pulseaudio-module-x11-0.9.21-24.el6.i686.rpm ef2eb4541211bea9288a956da901cf6dca023eba52f86c8f87b13527c2047ab9 pulseaudio-module-zeroconf-0.9.21-24.el6.i686.rpm 32de7887a9cc5ddfd301c790376404d91690b4ba309201b8247676d3c61bcab1 pulseaudio-utils-0.9.21-24.el6.i686.rpm x86_64: 0ea4f6fda07bf5bae0b547b5aea8f3e159b12a96ca09961021610c891201e4da pulseaudio-0.9.21-24.el6.x86_64.rpm 226a3e53366272dc59e1415b380189dc4bf96a657dc2aab66dd16d566542e9c5 pulseaudio-esound-compat-0.9.21-24.el6.x86_64.rpm 7c7a81172658d198d3b83282ff57f7045948ddf1aeb97fde68d6d3557a5082a0 pulseaudio-gdm-hooks-0.9.21-24.el6.x86_64.rpm ebb56fd219094a860dab8c3d703fc6c50d084384083df1fe04a9616d423fd2f9 pulseaudio-libs-0.9.21-24.el6.i686.rpm aa10e4e3dd1eec5b1db5f881ff4d3c51f29390029cc2837fffeb9c93bc34106c pulseaudio-libs-0.9.21-24.el6.x86_64.rpm 70358534593525744fdd92a8d85d4453e28c09ceb1eb4d2ce029b38c6e3765ce pulseaudio-libs-devel-0.9.21-24.el6.i686.rpm 0a6de74b5db14015c1a48382aab5ceef1dbab2b42f63909b747579d459220cc3 pulseaudio-libs-devel-0.9.21-24.el6.x86_64.rpm ee0884955f5ab06488b2049b8065fdca2742404e72a74b39387f57b027bdb15a pulseaudio-libs-glib2-0.9.21-24.el6.i686.rpm 6a0948fbcfc1131c5eb8a48a17b3d9a7c325cbc112f3d982012bfafc6abc6d59 pulseaudio-libs-glib2-0.9.21-24.el6.x86_64.rpm a8e7c5f5dc349797a2a6753aefe4ef0ebfb93223c0b9ff16f34c81c53ae69cb1 pulseaudio-libs-zeroconf-0.9.21-24.el6.i686.rpm 063a8f2ea4832bb8ae834b2065f1f9c6c94b317d9ba778796073e4e70725e025 pulseaudio-libs-zeroconf-0.9.21-24.el6.x86_64.rpm 3bc75e942608c68b23cf0558a81eb603f0b09b61f746b21a6eeb7c2c2b73a565 pulseaudio-module-bluetooth-0.9.21-24.el6.x86_64.rpm ccc7e36bb82f5f9e0043aea2cd86ae1fd95ceb6189e82fdcc301711b9cc8e627 pulseaudio-module-gconf-0.9.21-24.el6.x86_64.rpm c22d5a893787abc488f1faf5a83d7bab930847b5855d53454a7e50d67e49ccbf pulseaudio-module-x11-0.9.21-24.el6.x86_64.rpm 84ac4da72f98afda36c43287a9cdc9f787ff9d5c0021fa26d866af01807491d3 pulseaudio-module-zeroconf-0.9.21-24.el6.x86_64.rpm 32de7887a9cc5ddfd301c790376404d91690b4ba309201b8247676d3c61bcab1 pulseaudio-utils-0.9.21-24.el6.i686.rpm fc0c61ac740953695ad5de56995baf04754a134b9b0091a0276f5793406c4ff0 pulseaudio-utils-0.9.21-24.el6.x86_64.rpm Source: 2f389e54669332bdc4676fb2c62520a6f71aa54a153bfbbc5c89f5de9f84834e pulseaudio-0.9.21-24.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #cen...@irc.freenode.net Twitter: @JohnnyCentOS ___ CentOS-announce mailing list CentOS-announce@centos.org https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CEBA-2016:0112 CentOS 6 cups-pk-helper FASTTRACK BugFix Update
CentOS Errata and Bugfix Advisory 2016:0112 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0112.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 67aaac8ee7bce20c58ecccae6ef50b97bc6e43b94abe0fb74d24d48cac255520 cups-pk-helper-0.0.4-13.el6.i686.rpm x86_64: 93cb016bf995f20f612d711f9f0b41ccd31ef79d53530e6674f84cc385e2173c cups-pk-helper-0.0.4-13.el6.x86_64.rpm Source: bc7096b268fc16456e9f63fc55bce2090e246f568cf0dd71357a06c19e21c35c cups-pk-helper-0.0.4-13.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #cen...@irc.freenode.net Twitter: @JohnnyCentOS ___ CentOS-announce mailing list CentOS-announce@centos.org https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CEBA-2016:0115 CentOS 6 urw-fonts FASTTRACK BugFix Update
CentOS Errata and Bugfix Advisory 2016:0115 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0115.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 30ae1a14b811b5901ecdd71ec8a3f3f2077aa677bc5a167e36ebdcd7b8b7a62b urw-fonts-2.4-11.el6.noarch.rpm x86_64: 30ae1a14b811b5901ecdd71ec8a3f3f2077aa677bc5a167e36ebdcd7b8b7a62b urw-fonts-2.4-11.el6.noarch.rpm Source: 1ce20bfa857d46472a6e791e5f152e58f7aa6fa3cebf6cd360b5c7a491d2ee8c urw-fonts-2.4-11.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #cen...@irc.freenode.net Twitter: @JohnnyCentOS ___ CentOS-announce mailing list CentOS-announce@centos.org https://lists.centos.org/mailman/listinfo/centos-announce
Re: [CentOS] Pi 2 Alternatives
On 04/02/2016 15:33, Chris Olson wrote: We have a requirement for a new application that will be used fixed, portable, and mobile. The hardware requirements drive the need for networking as well as some general purpose and special purpose interfaces. The software requirements are quite simple in comparison to many of our much larger systems with similar hardware requirements. We are not significantly restricted in choice of storage peripherals or other devices that may be needed. We believe that a small, single board computer will meet all requirements as long as it can run Linux. We have identified the need for approximately six prototyping units to support the initial production of about 200 to 300 operational systems. Our development and deployment time frame does not drive the need for an extremely rapid product decision, and there are pre-planned upgrade cycles over the next five years. An internal group has achieved a significant head of steam in support of using the Pi 2 Model B. The support enthusiasm may be partly technical and partly the hype associated with jumping into the Pi community. The number of suppliers does appear to support our supply chain and sustainment requirements, however the Linux available for the Pi 2 does not appear to be optimal. It would be better if there were choices that include a standard Linux distribution such as CentOS. This certainly seems like one of those situations where a trade of single board computer products is appropriate and achievable. There are products similar to the Pi 2 capable of running a more standard Linux distribution that we might consider. Does anyone have an experience-based single board computer recommendation? Thanks in advance for any product recommendations. Not sure if you are aware of this https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32 But that might help the Pi fit your needs. Tris * This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmas...@bgfl.org The views expressed within this email are those of the individual, and not necessarily those of the organisation * ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-virt] c7 xen-4.6 crash.
I wrote about this a couple months back. George asked me to submit to the Xen developers list, but I never had the time due to work demands on getting the new server set up. In my case, I had to use a different server. The new motherboard/CPU had no issues with the second CPU. If you turn off and unplug the second CPU, it will work. Check the archives for my e-mail address and see George's replies. If you can follow through with reporting it, that would be great. -- Craig Thompson, President Caldwell Global Communications, Inc. +1 (423) 559-5465 caldwellglobal.com -Original message- From: Alvin StarrSent: Thursday 4th February 2016 9:30 To: Discussion about the virtualization on CentOS Subject: [CentOS-virt] c7 xen-4.6 crash. Installing xen on a fairly clean c7.2 system. I get a xen kernel panic. (XEN) Bad console= option 'tty' Xen 4.6.0-9.el7 (XEN) Xen version 4.6.0-9.el7 (mockbu...@centos.org) (gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)) debug=n Wed Jan 20 12:25:53 UTC 2016 (XEN) Latest ChangeSet: Thu Jan 14 15:35:35 2016 + git:6e8597a-dirty (XEN) Bootloader: GRUB 2.02~beta2 (XEN) Command line: placeholder dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 2 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ac00 (usable) (XEN) 0009ac00 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - bffc7280 (usable) (XEN) bffc7280 - bffceac0 (ACPI data) (XEN) bffceac0 - c000 (reserved) (XEN) e000 - f000 (reserved) (XEN) fec0 - 0001 (reserved) (XEN) 0001 - 00084000 (usable) (XEN) ACPI: RSDP 000FDFD0, 0024 (r2 IBM ) (XEN) ACPI: XSDT BFFCE980, 0054 (r1 IBM SERVALNT 1000 IBM 45444F43) (XEN) ACPI: FACP BFFCE8C0, 0084 (r2 IBM SERVALNT 1000 IBM 45444F43) (XEN) ACPI: DSDT BFFC7280, 2F12 (r2 IBM SERVALNT 1000 INTL 20041203) (XEN) ACPI: FACS BFFCA7C0, 0040 (XEN) ACPI: APIC BFFCE800, 0084 (r1 IBM SERVALNT 1000 IBM 45444F43) (XEN) ACPI: SRAT BFFCE6C0, 00E8 (r1 IBM SERVALNT 1000 IBM 45444F43) (XEN) ACPI: HPET BFFCE680, 0038 (r1 IBM SERVALNT 1000 IBM 45444F43) (XEN) ACPI: MCFG BFFCE640, 003C (r1 IBM SERVALNT 1000 IBM 45444F43) (XEN) ACPI: ERST BFFCA800, 0230 (r1 IBM SERVALNT 1000 IBM 45444F43) (XEN) System RAM: 32767MB (33553796kB) (XEN) SRAT: PXM 0 -> APIC 0 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 1 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 6 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 7 -> Node 0 (XEN) SRAT: Node 0 PXM 0 0-c000 (XEN) SRAT: Node 0 PXM 0 1-84000 (XEN) SRAT: Node 0 PXM 0 84000-84100 (hotplug) (XEN) NUMA: Using 18 for the hash shift. (XEN) Domain heap initialised (XEN) found SMP MP-table at 0009ad40 (XEN) DMI 2.4 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x588 (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:584,1:0], pm1x_evt[1:580,1:0] (XEN) ACPI: wakeup_vec[bffca7cc], vec_size[20] (XEN) ACPI: Local APIC address 0xfee0 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) (XEN) Processor #1 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) (XEN) Processor #6 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) (XEN) Processor #7 6:15 APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) (XEN) ACPI: IOAPIC (id[0x0e] address[0xfec0] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 14, version 32, address 0xfec0, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed0 (XEN) Invalid bit width in GAR (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 24 GSI, 760 MSI/MSI-X (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) CMCI: CPU0 has no CMCI support (XEN) CPU0: Thermal monitoring enabled (TM2) (XEN) Intel machine check
[CentOS] Squid as interception HTTPS proxy under CentOS 7
Hi all, I am trying to configure squid as a interception HTTPS proxy under CentOS 7. At every https request, I am receiving a certificate error. My current config for squid is: # My localnet acl localnet src 172.22.55.0/28 acl localnet src 172.22.58.0/29 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT # # Recommended minimum Access Permission configuration: # # Deny requests to certain unsafe ports http_access deny !Safe_ports # Deny CONNECT to other than secure SSL ports http_access deny CONNECT !SSL_ports # Only allow cachemgr access from localhost http_access allow localhost manager http_access deny manager # We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on "localhost" is a local user #http_access deny to_localhost # # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # # Example rule allowing access from your local networks. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed http_access allow localnet http_access allow localhost # And finally deny all other access to this proxy http_access deny all # Squid normally listens to port 3128 #http_port 3128 # Uncomment and adjust the following to add a disk cache directory. #cache_dir ufs /var/spool/squid 100 16 256 # Leave coredumps in the first cache dir coredump_dir /var/spool/squid # # Add any of your own refresh_pattern entries above these. # refresh_pattern ^ftp: 144020% 10080 refresh_pattern ^gopher:14400% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 # My custom configuration http_port 8079 http_port 8080 intercept https_port 8081 ssl-bump intercept generate-host-certificates=on dynamic_cert_mem_cache_size=4MB key=/etc/squid/custom.private cert=/etc/squid/custom.cert # Anonymous proxy forwarded_for off request_header_access Allow allow all request_header_access Authorization allow all request_header_access WWW-Authenticate allow all request_header_access Proxy-Authorization allow all request_header_access Proxy-Authenticate allow all request_header_access Cache-Control allow all request_header_access Content-Encoding allow all request_header_access Content-Length allow all request_header_access Content-Type allow all request_header_access Date allow all request_header_access Expires allow all request_header_access Host allow all request_header_access If-Modified-Since allow all request_header_access Last-Modified allow all request_header_access Location allow all request_header_access Pragma allow all request_header_access Accept allow all request_header_access Accept-Charset allow all request_header_access Accept-Encoding allow all request_header_access Accept-Language allow all request_header_access Content-Language allow all request_header_access Mime-Version allow all request_header_access Retry-After allow all request_header_access Title allow all request_header_access Connection allow all request_header_access Proxy-Connection allow all request_header_access User-Agent allow all request_header_access Cookie allow all request_header_access All deny all # SSL Bump Config always_direct allow all ssl_bump server-first all sslproxy_cert_error deny all sslproxy_flags DONT_VERIFY_PEER I have tried disabling "sslproxy_cert_error" and "sslproxy_flags" directives, without luck. Any ideas about what am I doing wrong? Thanks. -- Greetings, C. L. Martinez ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 regression, can not take a KVM qcow2, convert it and boot it on ESXi...
On 4 February 2016 at 06:58, John Hodrienwrote: > On Thu, 4 Feb 2016, Martinx - ジェームズ wrote: > >> My last try was, during Packer build, to append "add_drivers+=" >> sd_mod" to /etc/dracut.conf and re-building initramdisk by running >> "dracut -f". However, it does not boot either (on ESXi)! >> >> I can still boot using Rescue mode on VMWare, then, I can see that >> sd_mod is inside of initramfs as expected (lsinitrd FTW) but, dracut >> does not load it! I tried "force_drivers+=" sd_mod", doesn't work >> too... >> >> Weird is that, while during Rescue, if I run "dracut -f" again, then, >> it works! Normal boot proceeds... But this is unacceptable, because I >> can not ship a half-broken VMDK and tell customers to first boot on >> Rescue, run "dracut -f" and then, use the system. >> >> So, why the heck the "dracut -f" executed when as a KVM guest have no >> effect for later ESXi usage? >> >> What am I missing? >> >> I really appreciate any help! > > > Is this possible the hostonly option in dracut causing fun? > > "On RHEL-7 the hostonly mode is the default mode. Generic "non-hostonly" > images are created, if the dracut-config-generic rpm is installed. The > rescue kernel entry in the bootloader menu is also a generic image." > > jh You're the man!!! Thank you so much!! YAY!! I need to install the package "dracut-config-generic" during Packer build, which sets "hostonly=no" and, voialá! :-D Thank you again! Cheers! Thiago ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Squid as interception HTTPS proxy under CentOS 7
On 04/02/2016 13:24, C. L. Martinez wrote: Hi all, I am trying to configure squid as a interception HTTPS proxy under CentOS 7. At every https request, I am receiving a certificate error. My current config for squid is: # My localnet acl localnet src 172.22.55.0/28 acl localnet src 172.22.58.0/29 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT # # Recommended minimum Access Permission configuration: # # Deny requests to certain unsafe ports http_access deny !Safe_ports # Deny CONNECT to other than secure SSL ports http_access deny CONNECT !SSL_ports # Only allow cachemgr access from localhost http_access allow localhost manager http_access deny manager # We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on "localhost" is a local user #http_access deny to_localhost # # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # # Example rule allowing access from your local networks. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed http_access allow localnet http_access allow localhost # And finally deny all other access to this proxy http_access deny all # Squid normally listens to port 3128 #http_port 3128 # Uncomment and adjust the following to add a disk cache directory. #cache_dir ufs /var/spool/squid 100 16 256 # Leave coredumps in the first cache dir coredump_dir /var/spool/squid # # Add any of your own refresh_pattern entries above these. # refresh_pattern ^ftp: 144020% 10080 refresh_pattern ^gopher:14400% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 # My custom configuration http_port 8079 http_port 8080 intercept https_port 8081 ssl-bump intercept generate-host-certificates=on dynamic_cert_mem_cache_size=4MB key=/etc/squid/custom.private cert=/etc/squid/custom.cert # Anonymous proxy forwarded_for off request_header_access Allow allow all request_header_access Authorization allow all request_header_access WWW-Authenticate allow all request_header_access Proxy-Authorization allow all request_header_access Proxy-Authenticate allow all request_header_access Cache-Control allow all request_header_access Content-Encoding allow all request_header_access Content-Length allow all request_header_access Content-Type allow all request_header_access Date allow all request_header_access Expires allow all request_header_access Host allow all request_header_access If-Modified-Since allow all request_header_access Last-Modified allow all request_header_access Location allow all request_header_access Pragma allow all request_header_access Accept allow all request_header_access Accept-Charset allow all request_header_access Accept-Encoding allow all request_header_access Accept-Language allow all request_header_access Content-Language allow all request_header_access Mime-Version allow all request_header_access Retry-After allow all request_header_access Title allow all request_header_access Connection allow all request_header_access Proxy-Connection allow all request_header_access User-Agent allow all request_header_access Cookie allow all request_header_access All deny all # SSL Bump Config always_direct allow all ssl_bump server-first all sslproxy_cert_error deny all sslproxy_flags DONT_VERIFY_PEER I have tried disabling "sslproxy_cert_error" and "sslproxy_flags" directives, without luck. Any ideas about what am I doing wrong? Thanks. Do you have a copy of the Root CA you are using to re-encrypt the SSL stream installed in the browser? Tris * This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmas...@bgfl.org The views expressed within this email are those of the individual, and not necessarily those of the organisation * ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Pi 2 Alternatives
We have a requirement for a new application that will be used fixed, portable, and mobile. The hardware requirements drive the need for networking as well as some general purpose and special purpose interfaces. The software requirements are quite simple in comparison to many of our much larger systems with similar hardware requirements. We are not significantly restricted in choice of storage peripherals or other devices that may be needed. We believe that a small, single board computer will meet all requirements as long as it can run Linux. We have identified the need for approximately six prototyping units to support the initial production of about 200 to 300 operational systems. Our development and deployment time frame does not drive the need for an extremely rapid product decision, and there are pre-planned upgrade cycles over the next five years. An internal group has achieved a significant head of steam in support of using the Pi 2 Model B. The support enthusiasm may be partly technical and partly the hype associated with jumping into the Pi community. The number of suppliers does appear to support our supply chain and sustainment requirements, however the Linux available for the Pi 2 does not appear to be optimal. It would be better if there were choices that include a standard Linux distribution such as CentOS. This certainly seems like one of those situations where a trade of single board computer products is appropriate and achievable. There are products similar to the Pi 2 capable of running a more standard Linux distribution that we might consider. Does anyone have an experience-based single board computer recommendation? Thanks in advance for any product recommendations. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Squid as interception HTTPS proxy under CentOS 7
check out sslbump documentation: http://wiki.squid-cache.org/Features/SslBump -- Eero 2016-02-04 15:24 GMT+02:00 C. L. Martinez: > Hi all, > > I am trying to configure squid as a interception HTTPS proxy under CentOS > 7. At every https request, I am receiving a certificate error. > > My current config for squid is: > > # My localnet > acl localnet src 172.22.55.0/28 > acl localnet src 172.22.58.0/29 > > acl SSL_ports port 443 > acl Safe_ports port 80 # http > acl Safe_ports port 21 # ftp > acl Safe_ports port 443 # https > acl Safe_ports port 70 # gopher > acl Safe_ports port 210 # wais > acl Safe_ports port 1025-65535 # unregistered ports > acl Safe_ports port 280 # http-mgmt > acl Safe_ports port 488 # gss-http > acl Safe_ports port 591 # filemaker > acl Safe_ports port 777 # multiling http > acl CONNECT method CONNECT > > # > # Recommended minimum Access Permission configuration: > # > # Deny requests to certain unsafe ports > http_access deny !Safe_ports > > # Deny CONNECT to other than secure SSL ports > http_access deny CONNECT !SSL_ports > > # Only allow cachemgr access from localhost > http_access allow localhost manager > http_access deny manager > > # We strongly recommend the following be uncommented to protect innocent > # web applications running on the proxy server who think the only > # one who can access services on "localhost" is a local user > #http_access deny to_localhost > > # > # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS > # > > # Example rule allowing access from your local networks. > # Adapt localnet in the ACL section to list your (internal) IP networks > # from where browsing should be allowed > http_access allow localnet > http_access allow localhost > > # And finally deny all other access to this proxy > http_access deny all > > # Squid normally listens to port 3128 > #http_port 3128 > > # Uncomment and adjust the following to add a disk cache directory. > #cache_dir ufs /var/spool/squid 100 16 256 > > # Leave coredumps in the first cache dir > coredump_dir /var/spool/squid > > # > # Add any of your own refresh_pattern entries above these. > # > refresh_pattern ^ftp: 144020% 10080 > refresh_pattern ^gopher:14400% 1440 > refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 > refresh_pattern . 0 20% 4320 > > # My custom configuration > http_port 8079 > http_port 8080 intercept > https_port 8081 ssl-bump intercept generate-host-certificates=on > dynamic_cert_mem_cache_size=4MB key=/etc/squid/custom.private > cert=/etc/squid/custom.cert > > # Anonymous proxy > forwarded_for off > request_header_access Allow allow all > request_header_access Authorization allow all > request_header_access WWW-Authenticate allow all > request_header_access Proxy-Authorization allow all > request_header_access Proxy-Authenticate allow all > request_header_access Cache-Control allow all > request_header_access Content-Encoding allow all > request_header_access Content-Length allow all > request_header_access Content-Type allow all > request_header_access Date allow all > request_header_access Expires allow all > request_header_access Host allow all > request_header_access If-Modified-Since allow all > request_header_access Last-Modified allow all > request_header_access Location allow all > request_header_access Pragma allow all > request_header_access Accept allow all > request_header_access Accept-Charset allow all > request_header_access Accept-Encoding allow all > request_header_access Accept-Language allow all > request_header_access Content-Language allow all > request_header_access Mime-Version allow all > request_header_access Retry-After allow all > request_header_access Title allow all > request_header_access Connection allow all > request_header_access Proxy-Connection allow all > request_header_access User-Agent allow all > request_header_access Cookie allow all > request_header_access All deny all > > # SSL Bump Config > always_direct allow all > ssl_bump server-first all > sslproxy_cert_error deny all > sslproxy_flags DONT_VERIFY_PEER > > I have tried disabling "sslproxy_cert_error" and "sslproxy_flags" > directives, without luck. > > Any ideas about what am I doing wrong? > > Thanks. > -- > Greetings, > C. L. Martinez > ___ > 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] CentOS 7, NSF, "feature" [SOLVED]
On 4 Feb 2016 03:10, "Always Learning"wrote: > > > On Wed, 2016-02-03 at 13:57 -0700, Warren Young wrote: > > > On Feb 3, 2016, at 10:30 AM, Ricardo J. Barberis wrote: > > > > > > El Miércoles 03/02/2016, Warren Young escribió: > > >> > > >> Again, I don’t know why they couldn’t just do it with links. > > > > > > I guess that's probably to execute scripts and "hide" the name of the > > > interpreter, e.g.: > > > > I get why second-rate programmers would care to do that, but what I don’t get is why systemd would need a feature to support that wish. > > Perhaps the Systemd are all 'second-rate' programmers ? Good > programmers always try to avoid the crap. > > That's enough. You've been around these lists long enough to realise attacks like that nonsense are inappropriate and won't be tolerated. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 regression, can not take a KVM qcow2, convert it and boot it on ESXi...
On Thu, 4 Feb 2016, Martinx - ジェームズ wrote: My last try was, during Packer build, to append "add_drivers+=" sd_mod" to /etc/dracut.conf and re-building initramdisk by running "dracut -f". However, it does not boot either (on ESXi)! I can still boot using Rescue mode on VMWare, then, I can see that sd_mod is inside of initramfs as expected (lsinitrd FTW) but, dracut does not load it! I tried "force_drivers+=" sd_mod", doesn't work too... Weird is that, while during Rescue, if I run "dracut -f" again, then, it works! Normal boot proceeds... But this is unacceptable, because I can not ship a half-broken VMDK and tell customers to first boot on Rescue, run "dracut -f" and then, use the system. So, why the heck the "dracut -f" executed when as a KVM guest have no effect for later ESXi usage? What am I missing? I really appreciate any help! Is this possible the hostonly option in dracut causing fun? "On RHEL-7 the hostonly mode is the default mode. Generic "non-hostonly" images are created, if the dracut-config-generic rpm is installed. The rescue kernel entry in the bootloader menu is also a generic image." jh___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos