Re: [CentOS] Not Quite Minimal CentOS 6.2
On Tue, Apr 24, 2012 at 11:02:49PM -0700, Al Sparks wrote: You're right. The stack was there. First, I was inaccurate when I said I installed 6.2. I actually installed 6.0, and later updated via yum. Second, yeah I was able to start the network service, so there was a stack. All I'd get would be the loopback or lo interface, but it was there. But going into /etc/sysconfig/network-scripts was a pain because there was no ifcfg-eth0 file I could play with. That's when I gave up and re-installed, but added more stuff beyond base just to be sure. As for not configuring the network during the install process, I was pretty sure I had. For some reason it didn't take. Maybe I didn't click a save box when I should have. I don't know. My recollection (from installing 6.0 a couple times) is that even if you check the aforementioned checkbox during the install, once you're done, the network is not (properly) configured. I think there's a bug on that in the upstream bugzilla. I do believe it has been fixed in 6.2, though. (this is all from memory, I didn't look it up, so YMMV.) -- Fred Smith -- fre...@fcshome.stoneham.ma.us - The Lord is like a strong tower. Those who do what is right can run to him for safety. --- Proverbs 18:10 (niv) - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On 04/25/2012 01:02 AM, Al Sparks wrote: You're right. The stack was there. First, I was inaccurate when I said I installed 6.2. I actually installed 6.0, and later updated via yum. Second, yeah I was able to start the network service, so there was a stack. All I'd get would be the loopback or lo interface, but it was there. But going into /etc/sysconfig/network-scripts was a pain because there was no ifcfg-eth0 file I could play with. That's when I gave up and re-installed, but added more stuff beyond base just to be sure. As for not configuring the network during the install process, I was pretty sure I had. For some reason it didn't take. Maybe I didn't click a save box when I should have. I don't know. === Al From: Johnny Hughes joh...@centos.org To: centos@centos.org Sent: Tuesday, April 24, 2012 6:04 PM Subject: Re: [CentOS] Not Quite Minimal CentOS 6.2 On 04/24/2012 08:53 PM, Al Sparks wrote: I recently did a minimal 6.2 install recently, and it was annoying that it didn't include the network stack. What use is an install w/o the network? It has the network stack ... you must configure it during the install. If you do not configure and enable the ethernet card then it does not turn on by default ... but it is in the installer to be able to do: http://wiki.centos.org/FAQ/CentOS6#head-b67e85d98f0e9f1b599358105c551632c6ff7c90 Don't get the wrong idea here ... I think it is a very silly way to do installs to not default with the network turned on. It should be turned on ... but upstream decided it differently and I do not get to be the decider :D One way to always get it to work is to do a network install. By default, you will get the same network after install that you input to do the install. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On Thu, April 26, 2012 08:55, Johnny Hughes wrote: It has the network stack ... you must configure it during the install. If you do not configure and enable the ethernet card then it does not turn on by default ... but it is in the installer to be able to do: http://wiki.centos.org/FAQ/CentOS6#head-b67e85d98f0e9f1b599358105c551632c6ff7c90 Don't get the wrong idea here ... I think it is a very silly way to do installs to not default with the network turned on. It should be turned on ... but upstream decided it differently and I do not get to be the decider :D I used to think the same thing. However, on reflection I think that the decision to keep the network down until deliberately enabled is a sensible and prudent security choice. This leaves up to the operator the decision as to whether or not a given system is sufficiently hardened against Internet attacks before connecting. Now, consider upstream's decision to enable network-manager by default on an enterprise distro. THAT I both understand and fundamentally disagree with. -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On Thu, Apr 26, 2012 at 11:36 AM, James B. Byrne byrn...@harte-lyne.ca wrote: I used to think the same thing. However, on reflection I think that the decision to keep the network down until deliberately enabled is a sensible and prudent security choice. This leaves up to the operator the decision as to whether or not a given system is sufficiently hardened against Internet attacks before connecting. Which way the default goes isn't a problem by itself, but having it set by a not-very obvious checkbox hidden out of the way with not mention of the need to check it seems like a pretty bad decision. And why would it ever be a good thing to not be able to do an update immediately after your first boot anyway? Now, consider upstream's decision to enable network-manager by default on an enterprise distro. THAT I both understand and fundamentally disagree with. Yes, that's a horrible thing for servers. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On Thursday, April 26, 2012 01:28:04 PM Les Mikesell wrote: On Thu, Apr 26, 2012 at 11:36 AM, James B. Byrne byrn...@harte-lyne.ca wrote: Now, consider upstream's decision to enable network-manager by default on an enterprise distro. THAT I both understand and fundamentally disagree with. Yes, that's a horrible thing for servers. I've said it before, and I'll say it again: enterprise != servers. Regardless, the network manager things is not something CentOS is likely to change unless and until upstream changes, which is not likely at all. But you're of course free to file a bug report against upstream.. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On Thu, Apr 26, 2012 at 1:09 PM, Lamar Owen lo...@pari.edu wrote: Yes, that's a horrible thing for servers. I've said it before, and I'll say it again: enterprise != servers. How's that? What kind of enterprise doesn't have some servers with nailed down NICs? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On Thursday, April 26, 2012 02:12:20 PM Les Mikesell wrote: On Thu, Apr 26, 2012 at 1:09 PM, Lamar Owen lo...@pari.edu wrote: Yes, that's a horrible thing for servers. I've said it before, and I'll say it again: enterprise != servers. How's that? A distribution being an 'enterprise' distribution does not equate with that distribution being an (exclusively) 'server' distribution. While CentOS makes a great server distribution, that is a subset of what an enterprise distribution needs to be able to do. And I've not had any NetworkManager issues with my upstream EL6.2 box running a local GUI, xrdp and vnc, some reverse ssh tunnels for remote maintenance of some dynamically addressed, behind-the-NAT boxes, among other things (development CMS/web serving, CIFS shares, and more, including a test OpenNMS instance). Multiple NICs, multiple subnets, and solid as a rock with nailed up addresses, running with NetworkManager. I've thus far not seen any of the issues others have seen, once I remembered to set up networking at install, and remembered the two checkboxes to check (which I've posted before on this list). ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On Thu, Apr 26, 2012 at 1:34 PM, Lamar Owen lo...@pari.edu wrote: Yes, that's a horrible thing for servers. I've said it before, and I'll say it again: enterprise != servers. How's that? A distribution being an 'enterprise' distribution does not equate with that distribution being an (exclusively) 'server' distribution. While CentOS makes a great server distribution, that is a subset of what an enterprise distribution needs to be able to do. And I've not had any NetworkManager issues with my upstream EL6.2 box running a local GUI, xrdp and vnc, some reverse ssh tunnels for remote maintenance of some dynamically addressed, behind-the-NAT boxes, among other things (development CMS/web serving, CIFS shares, and more, including a test OpenNMS instance). Multiple NICs, multiple subnets, and solid as a rock with nailed up addresses, running with NetworkManager. I've thus far not seen any of the issues others have seen, once I remembered to set up networking at install, and remembered the two checkboxes to check (which I've posted before on this list). But what is the point of running a daemon to manage something where you explicitly never, ever, under any circumstances want it to change, even if you are sometimes lucky about that part? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On 04/26/2012 01:12 PM, Les Mikesell wrote: On Thu, Apr 26, 2012 at 1:09 PM, Lamar Owen lo...@pari.edu wrote: Yes, that's a horrible thing for servers. I've said it before, and I'll say it again: enterprise != servers. How's that? What kind of enterprise doesn't have some servers with nailed down NICs? I think what Lamar is saying is that Servers are not the only use for RHEL or CentOS in the enterprise. There are many enterprises that use CentOS workstations as well as servers ... or many of the people use GUI servers or VNC or NX with X Windows on servers. Many enterprises use CentOS on mobile (in this case laptop or x86 tablet) devices for things like inventory control or Point of Sale systems ... OR kiosk systems. There are many, many uses of CentOS (or RHEL) in the enterprise that are not a server and/or use X. In most of those uses (other than a CLI only server), having NetworkManager setup the network is probably a good thing ... especially if there is a wireless device involved. That is just where upstream is moving. We are certainly not going to change the default installer behavior for CentOS to be non RHEL like. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
You're right. The stack was there. First, I was inaccurate when I said I installed 6.2. I actually installed 6.0, and later updated via yum. Second, yeah I was able to start the network service, so there was a stack. All I'd get would be the loopback or lo interface, but it was there. But going into /etc/sysconfig/network-scripts was a pain because there was no ifcfg-eth0 file I could play with. That's when I gave up and re-installed, but added more stuff beyond base just to be sure. As for not configuring the network during the install process, I was pretty sure I had. For some reason it didn't take. Maybe I didn't click a save box when I should have. I don't know. === Al From: Johnny Hughes joh...@centos.org To: centos@centos.org Sent: Tuesday, April 24, 2012 6:04 PM Subject: Re: [CentOS] Not Quite Minimal CentOS 6.2 On 04/24/2012 08:53 PM, Al Sparks wrote: I recently did a minimal 6.2 install recently, and it was annoying that it didn't include the network stack. What use is an install w/o the network? It has the network stack ... you must configure it during the install. If you do not configure and enable the ethernet card then it does not turn on by default ... but it is in the installer to be able to do: http://wiki.centos.org/FAQ/CentOS6#head-b67e85d98f0e9f1b599358105c551632c6ff7c90 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Not Quite Minimal CentOS 6.2
Hi All, I a working on configuring a not-quite minimal installation of CentOS 6.2. I tried doing the minimal installation available with the installer, but it's a bit too minimal to be useful. So I'm cutting down from a less minimal starting place. I'm pretty familiar with 5.x, but what I'm finding in 6.2 is a lot of new stuff, and a lot of odd behavior. For example, cups is starting at boot time, despite being disabled by chkconfig. And I'm finding things like qpidd, matahari, messagebus, and portreserve that really don't belong in a minimal setup. To clarify, I'm shooting for a simple config, like one would use for a dedicated DNS server. Can anyone point me to an up-to-date list of daemon processes that indicates what they do and whether they can be safely disabled? Also, any ideas as to what would be launching cups would be appreciated. Thanks, --Bill ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On Tue, 24 Apr 2012 16:22:17 -0700, listmail wrote Also, any ideas as to what would be launching cups would be appreciated. I answered one of my own questions: cups was being started by the VMware tools startup script. I fixed this for now by editing the VMware startup script and removing the command that starts it. Still interested in a list of daemons that can be cleanly stopped, if one exists for 6.2 yet. Thanks, --Bill ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Not Quite Minimal CentOS 6.2
On 4/24/2012 7:22 PM, listmail wrote: I a working on configuring a not-quite minimal installation of CentOS 6.2. I tried doing the minimal installation available with the installer, but it's a bit too minimal to be useful. So I'm cutting down from a less minimal starting place. I'm pretty familiar with 5.x, but what I'm finding in 6.2 is a lot of new stuff, and a lot of odd behavior. For example, cups is starting at boot time, despite being disabled by chkconfig. And I'm finding things like qpidd, matahari, messagebus, and portreserve that really don't belong in a minimal setup. To clarify, I'm shooting for a simple config, like one would use for a dedicated DNS server. Can anyone point me to an up-to-date list of daemon processes that indicates what they do and whether they can be safely disabled? Also, any ideas as to what would be launching cups would be appreciated. I did a 'basic server' for my dns and then did this for cleaning up... yum install yum-cron logwatch bind bind-chroot yum-cron remove packages yum remove samba-winbind-clients qpid-cpp-client matahari* cups the two clients will get rid of a lot. chkconfig atd off chkconfig autofs off chkconfig kdump off chkconfig netfs off chkconfig nfslock off chkconfig rpcidmapd off chkconfig rpcgssd off chkconfig rpcbind off I left the rest on but that pretty much did it for me.. here is my chkconfig list, off and on /root$ chkconfig --list |grep 3:on abrt-ccpp 0:off1:off2:off3:on4:off5:on6:off abrt-oops 0:off1:off2:off3:on4:off5:on6:off abrtd 0:off1:off2:off3:on4:off5:on6:off acpid 0:off1:off2:on3:on4:on5:on6:off auditd 0:off1:off2:on3:on4:on5:on6:off cpuspeed 0:off1:on2:on3:on4:on5:on6:off crond 0:off1:off2:on3:on4:on5:on6:off haldaemon 0:off1:off2:off3:on4:on5:on6:off ip6tables 0:off1:off2:on3:on4:on5:on6:off iptables 0:off1:off2:on3:on4:on5:on6:off irqbalance 0:off1:off2:off3:on4:on5:on6:off lvm2-monitor 0:off1:on2:on3:on4:on5:on6:off mcelogd0:off1:off2:off3:on4:off5:on6:off mdmonitor 0:off1:off2:on3:on4:on5:on6:off messagebus 0:off1:off2:on3:on4:on5:on6:off named 0:off1:off2:on3:on4:on5:on6:off network0:off1:off2:on3:on4:on5:on6:off ntpd 0:off1:off2:on3:on4:on5:on6:off portreserve0:off1:off2:on3:on4:on5:on6:off postfix0:off1:off2:on3:on4:on5:on6:off rsyslog0:off1:off2:on3:on4:on5:on6:off sshd 0:off1:off2:on3:on4:on5:on6:off sysstat0:off1:on2:on3:on4:on5:on6:off udev-post 0:off1:on2:on3:on4:on5:on6:off yum-cron 0:off1:off2:on3:on4:on5:on6:off /root$ chkconfig --list |grep 3:off atd0:off1:off2:off3:off4:off5:off 6:off autofs 0:off1:off2:off3:off4:off5:off 6:off certmonger 0:off1:off2:off3:off4:off5:off 6:off cgconfig 0:off1:off2:off3:off4:off5:off 6:off cgred 0:off1:off2:off3:off4:off5:off 6:off kdump 0:off1:off2:off3:off4:off5:off 6:off netconsole 0:off1:off2:off3:off4:off5:off 6:off netfs 0:off1:off2:off3:off4:off5:off 6:off nfs0:off1:off2:off3:off4:off5:off 6:off nfslock0:off1:off2:off3:off4:off5:off 6:off ntpdate0:off1:off2:off3:off4:off5:off 6:off oddjobd0:off1:off2:off3:off4:off5:off 6:off psacct 0:off1:off2:off3:off4:off5:off 6:off quota_nld 0:off1:off2:off3:off4:off5:off 6:off rdisc 0:off1:off2:off3:off4:off5:off 6:off restorecond0:off1:off2:off3:off4:off5:off 6:off rngd 0:off1:off2:off3:off4:off5:off 6:off rpcbind0:off1:off2:off3:off4:off5:off 6:off rpcgssd0:off1:off2:off3:off4:off5:off 6:off rpcidmapd 0:off1:off2:off3:off4:off5:off 6:off rpcsvcgssd 0:off
Re: [CentOS] Not Quite Minimal CentOS 6.2
I recently did a minimal 6.2 install recently, and it was annoying that it didn't include the network stack. What use is an install w/o the network? === Al From: Bob Hoffman b...@bobhoffman.com To: CentOS mailing list centos@centos.org Sent: Tuesday, April 24, 2012 5:18 PM Subject: Re: [CentOS] Not Quite Minimal CentOS 6.2 On 4/24/2012 7:22 PM, listmail wrote: I a working on configuring a not-quite minimal installation of CentOS 6.2. I tried doing the minimal installation available with the installer, but it's a bit too minimal to be useful. So I'm cutting down from a less minimal starting place. I'm pretty familiar with 5.x, but what I'm finding in 6.2 is a lot of new stuff, and a lot of odd behavior. For example, cups is starting at boot time, despite being disabled by chkconfig. And I'm finding things like qpidd, matahari, messagebus, and portreserve that really don't belong in a minimal setup. To clarify, I'm shooting for a simple config, like one would use for a dedicated DNS server. Can anyone point me to an up-to-date list of daemon processes that indicates what they do and whether they can be safely disabled? Also, any ideas as to what would be launching cups would be appreciated. I did a 'basic server' for my dns and then did this for cleaning up... yum install yum-cron logwatch bind bind-chroot yum-cron remove packages yum remove samba-winbind-clients qpid-cpp-client matahari* cups the two clients will get rid of a lot. chkconfig atd off chkconfig autofs off chkconfig kdump off chkconfig netfs off chkconfig nfslock off chkconfig rpcidmapd off chkconfig rpcgssd off chkconfig rpcbind off I left the rest on but that pretty much did it for me.. here is my chkconfig list, off and on /root$ chkconfig --list |grep 3:on abrt-ccpp 0:off 1:off 2:off 3:on 4:off 5:on 6:off abrt-oops 0:off 1:off 2:off 3:on 4:off 5:on 6:off abrtd 0:off 1:off 2:off 3:on 4:off 5:on 6:off acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off cpuspeed 0:off 1:on 2:on 3:on 4:on 5:on 6:off crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:off iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off irqbalance 0:off 1:off 2:off 3:on 4:on 5:on 6:off lvm2-monitor 0:off 1:on 2:on 3:on 4:on 5:on 6:off mcelogd 0:off 1:off 2:off 3:on 4:off 5:on 6:off mdmonitor 0:off 1:off 2:on 3:on 4:on 5:on 6:off messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off named 0:off 1:off 2:on 3:on 4:on 5:on 6:off network 0:off 1:off 2:on 3:on 4:on 5:on 6:off ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off portreserve 0:off 1:off 2:on 3:on 4:on 5:on 6:off postfix 0:off 1:off 2:on 3:on 4:on 5:on 6:off rsyslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off sysstat 0:off 1:on 2:on 3:on 4:on 5:on 6:off udev-post 0:off 1:on 2:on 3:on 4:on 5:on 6:off yum-cron 0:off 1:off 2:on 3:on 4:on 5:on 6:off /root$ chkconfig --list |grep 3:off atd 0:off 1:off 2:off 3:off 4:off 5:off 6:off autofs 0:off 1:off 2:off 3:off 4:off 5:off 6:off certmonger 0:off 1:off 2:off 3:off 4:off 5:off 6:off cgconfig 0:off 1:off 2:off 3:off 4:off 5:off 6:off cgred 0:off 1:off 2:off 3:off 4:off 5:off 6:off kdump 0:off 1:off 2:off 3:off 4:off 5:off 6:off netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off netfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off nfslock 0:off 1:off 2:off 3:off 4:off 5:off 6:off ntpdate 0:off 1:off 2:off 3:off 4:off 5:off 6:off oddjobd 0:off 1:off 2:off 3:off 4:off 5:off 6:off psacct 0:off 1:off 2:off 3:off 4:off 5:off 6:off quota_nld 0:off 1:off 2:off 3:off 4:off 5:off 6:off rdisc 0:off 1:off 2:off 3:off 4:off 5:off 6:off restorecond 0:off 1:off 2:off 3:off
Re: [CentOS] Not Quite Minimal CentOS 6.2
On 04/24/2012 08:53 PM, Al Sparks wrote: I recently did a minimal 6.2 install recently, and it was annoying that it didn't include the network stack. What use is an install w/o the network? It has the network stack ... you must configure it during the install. If you do not configure and enable the ethernet card then it does not turn on by default ... but it is in the installer to be able to do: http://wiki.centos.org/FAQ/CentOS6#head-b67e85d98f0e9f1b599358105c551632c6ff7c90 signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
