Re: [CentOS] Dual boot with 2 drives

2014-08-09 Thread Alan McRae
No problems Joe. I have done this multiple times. I assume you have Fedora 20 on sda (the first disk) with the bootloader (grub2) on sda. Your BIOS will be set to boot sda. You install CentOS 7 on sdb (obvious). Your options are with the bootloader (grub2). If you install the bootloader on sdb

Re: [CentOS] Dual boot with 2 drives

2014-08-09 Thread Tony Molloy
On Saturday 09 August 2014 11:23:10 Alan McRae wrote: No problems Joe. I have done this multiple times. I assume you have Fedora 20 on sda (the first disk) with the bootloader (grub2) on sda. Your BIOS will be set to boot sda. You install CentOS 7 on sdb (obvious). Your options are with

Re: [CentOS] Dual boot with 2 drives

2014-08-09 Thread anax
I have a desktop with two disks, both wich Centos 7 backing up each other. Both disks have Grub2 in the MBR. On the first disk, in the Grub2 Menu /boot/grub2/grub.conf, I added a menuentry to chainload the second disk. This chainloader menuentry looks like: menuentry '3boot via chainloader

Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?

2014-08-09 Thread Neil Aggarwal
Earl: I am looking at the documentation of the new firewalld service in CentOS 7. You can check out the following document https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/ht ml/Security_Guide/sec-Using_Firewalls.html That is the document I read when I referred to

Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?

2014-08-09 Thread Eero Volotinen
2014-08-09 0:55 GMT+03:00 Neil Aggarwal n...@jammconsulting.com: Hello all: I am looking at the documentation of the new firewalld service in CentOS 7. It looks like no matter what I configure with it, outgoing connections are still going to be allowed. That does not seem very secure. I

Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?

2014-08-09 Thread Jim Perrin
On 08/08/2014 04:55 PM, Neil Aggarwal wrote: Hello all: I am looking at the documentation of the new firewalld service in CentOS 7. It looks like no matter what I configure with it, outgoing connections are still going to be allowed. That does not seem very secure. I always set my

Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?

2014-08-09 Thread Tom Bishop
On Sat, Aug 9, 2014 at 8:44 AM, Jim Perrin jper...@centos.org wrote: On 08/08/2014 04:55 PM, Neil Aggarwal wrote: Hello all: I am looking at the documentation of the new firewalld service in CentOS 7. It looks like no matter what I configure with it, outgoing connections are still going to

Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?

2014-08-09 Thread Neil Aggarwal
Tom: I thought we were supposed to be moving forward That is my thought exactly. This is a step backwards. I guess I will disable firewalld and go back to iptables. Thanks, Neil -- Neil Aggarwal, (972) 834-1565 We lend money to investors to buy or refinance single family rent houses. No

Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?

2014-08-09 Thread Valeri Galtsev
On Sat, August 9, 2014 9:15 am, Neil Aggarwal wrote: Tom: I thought we were supposed to be moving forward That is my thought exactly. This is a step backwards. I guess I will disable firewalld and go back to iptables. Systemd, firewalld... Linux from what formerly was UNIX-like becomes

Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?

2014-08-09 Thread Steve Clark
On 08/08/2014 05:55 PM, Neil Aggarwal wrote: Hello all: I am looking at the documentation of the new firewalld service in CentOS 7. It looks like no matter what I configure with it, outgoing connections are still going to be allowed. That does not seem very secure. I always set my servers

Re: [CentOS] slow i/o with a raid 50 on a 3ware controller

2014-08-09 Thread Markus Falb
On 7.8.2014 03:04, John R Pierce wrote: On 8/6/2014 5:32 PM, Markus Falb wrote: Do you have barriers enabled? Just another shot in the dark, but 5 didn't have that. If you have battery backed Cache with your Controller, you can safely disable barriers anyway. are you sure about this? thats

[CentOS] CentOS 6.5 printer weirdness...

2014-08-09 Thread Robert Heller
Ok, it is consistent and repeatable: *Everytime* I do a routine 'yum update' on the CentOS 6.5 server (64-bit) the printers (both of them networked laser printers, one an [old] HP Laserjet 4200 and one a [new] Brother MFC-9970CDW), cups loses the ability to print (its filter chain becomes

Re: [CentOS] CentOS 6.5 printer weirdness...

2014-08-09 Thread Fred Smith
On Sat, Aug 09, 2014 at 05:12:59PM -0400, Robert Heller wrote: Ok, it is consistent and repeatable: *Everytime* I do a routine 'yum update' on the CentOS 6.5 server (64-bit) the printers (both of them networked laser printers, one an [old] HP Laserjet 4200 and one a [new] Brother

Re: [CentOS] CentOS 6.5 printer weirdness...

2014-08-09 Thread John R Pierce
On 8/9/2014 2:12 PM, Robert Heller wrote: The*appearent* cure (workaround?) is to delete the printers, and re-install them. how are you installing/configuring the printers? are you editing any .conf files that are included in the packages ? -- john r pierce

Re: [CentOS] CentOS 6.5 printer weirdness...

2014-08-09 Thread Valeri Galtsev
On Sat, August 9, 2014 4:25 pm, Fred Smith wrote: On Sat, Aug 09, 2014 at 05:12:59PM -0400, Robert Heller wrote: Ok, it is consistent and repeatable: *Everytime* I do a routine 'yum update' on the CentOS 6.5 server (64-bit) the printers (both of them networked laser printers, one an [old]

[CentOS] Centos 7 - iptables service failed to start

2014-08-09 Thread Neil Aggarwal
Hello all: I did a fresh install of CentOS 7 on a new machine. I wrote /usr/local/bin/firewall.stop to remove all the firewall rules. It contains this code: # Flush the rules /usr/sbin/iptables -F # Set the default policies to accept /usr/sbin/iptables -P INPUT ACCEPT /usr/sbin/iptables -P

Re: [CentOS] Centos 7 - iptables service failed to start

2014-08-09 Thread Neil Aggarwal
Hey everyone: The process /usr/local/bin/firewall.start could not be executed and failed. I just realized I forgot to put #!/bin/sh at the top of my firewall scripts. I added that and it is working perfectly fine now. Sorry for any trouble. Thanks, Neil -- Neil Aggarwal, (972) 834-1565