Re: [CentOS] Chromium browser for C6
On 20 January 2015 at 03:44, Fred Smith wrote: > On Mon, Jan 19, 2015 at 08:01:02PM -0600, Johnny Hughes wrote: > > On 01/19/2015 06:49 PM, Fred Smith wrote: > > > On Mon, Jan 19, 2015 at 05:55:44PM -0600, Johnny Hughes wrote: > > >> On 01/19/2015 04:10 PM, Robert Arkiletian wrote: > > >>> On Mon, Jan 19, 2015 at 12:24 PM, Johnny Hughes > wrote: > > >>> > > On 01/19/2015 12:23 PM, Phelps, Matthew wrote: > > > On Mon, Jan 12, 2015 at 6:22 PM, Robert Arkiletian < > rob...@gmail.com> > > wrote: > > > > > >> On Mon, Jan 5, 2015 at 1:13 PM, Robert Arkiletian < > rob...@gmail.com> > > >> wrote: > > >> > > >>> Johnny, > > >>> > > >>> Any ETA on version 39.0.2171.95 > > >>> > > >>> cheers > > >>> > > >>> > > >> > > >> bump > > > > If I could build it, I would. At the present time, i can not build > it > > as the source is not on ftp.redhat.com or git.centos.org. > > > > Red Hat does not have permission for it to be built anywhere besides > > their supplemental channel for RHEL6, and I have asked Red Hat > legal and > > they are trying to get permission from Google to release it in > CentOS. > > > > I am sorry, but I can't build and release it at this time. I may > not be > > able to do so, even though I really, really do want to release it. > > > > > > > > >>> Thanks for the update Johnny. So was version 38 just a one time > special > > >>> permission thing? > > >>> > > >>> http://people.centos.org/hughesjr/chromium/6/x86_64/RPMS/ > > >> > > >> I very much got yelled at for that. > > >> > > >> > > > > > > wait,... I thought Chromium was "open source"... you need a license > > > to distribute it? (note that I haven't researched which license it > > > uses...) > > > > > > > Red Hat has permission to distribute, to paying customers, pieces of it > > that are not open source. I need to get permission to strip parts of > > that out and distribute the rest. > > > > I have asked for permission and am waiting on the answers of: > > > > 1. Can do that (take out some pieces and distribute) > > > > 2. If I can do that, are the pieces I took out good enough or do I need > > to make more changes. > > > > I want to make this happen and I am trying to do so. However, I have no > > idea what the outcome will be. > > > > One thing is for sure, people are watching me very closely on this .. > > therefore I must do it exactly the way they want me to. > > > > Thanks for the effort, Johnny, we all appreciate all that you do! > > Fred +1 - Thanks Johnny! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Kickstarting several *different* setups
I'm currently using kickstart for installing new servers and have run into the following scenario: all the machines will have the same basic setup of packages, however they will each be configured for a specific task. For example, some will be mail-serving machines and won't need things like a web or mySQL server installed. Others will be web servers and do need those packages. So my question is, is there some way do determine via kickstart, what to install on that machine based on some criteria, possibly the IP that's being assigned to it, or MAC address, or something ... Right now I have one single kickstart setup that all the machines are going to use, then I manually install the additional packages one by one, on each machine. It would be helpful if I can somehow tell kickstart to do that. Suggestions? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstarting several *different* setups
On 20/01/2015 16:29, Ashley M. Kirchner wrote: So my question is, is there some way do determine via kickstart, what to install on that machine based on some criteria, possibly the IP that's being assigned to it, or MAC address, or something ... If you just want to use kickstart, it would be pretty simple to serve these via HTTP, and have a simple script in PHP or similar that takes the requesting IP and uses it to choose which version of the kickstart to serve. I would suggest that the "right way" would be to kickstart all your machines the same way, and then use a configuration management tool (like Puppet or Chef) to customize them. This approach is likely to be more work, but also more maintainable in the long run. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstarting several *different* setups
On Tue, Jan 20, 2015 at 10:41 AM, Tom Grace wrote: > On 20/01/2015 16:29, Ashley M. Kirchner wrote: >> >> So my question is, is there some way do determine via kickstart, what to >> install on that machine based on some criteria, possibly the IP that's >> being assigned to it, or MAC address, or something ... > > If you just want to use kickstart, it would be pretty simple to serve these > via HTTP, and have a simple script in PHP or similar that takes the > requesting IP and uses it to choose which version of the kickstart to serve. > > I would suggest that the "right way" would be to kickstart all your machines > the same way, and then use a configuration management tool (like Puppet or > Chef) to customize them. This approach is likely to be more work, but also > more maintainable in the long run. Or, if you just want the packages that a custom kickstart would install, use a basic kickstart to bring it up, then run your own script (from an nfs mount, scp'd over, pasted into a command line or whatever you might find easier than learning puppet). The script just needs to determine the rest of the packages needed for this particular server and 'yum install ' them. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstarting several *different* setups
Tom: Thanks for the suggestion. I'll look into those tools. Mark: Yes, they are using pxeboot. Right now when they boot up, the pxe config offers two options, 32- and 64bit. Are you suggesting I create multiple entries that one selects based on what the machine is going to be? Is there a way to have this done automatically so I don't have to physically have to do that for each machine, but rather turn the thing on and have it determine what needs to get installed on that particular machine? Les: I was hoping for some way to have it all automated so if for some reason I'm not in the building, I can instruct someone else to reboot, pick the kickstart option in the pxeboot menu (be it a web, mail, db, or user server) and a few minutes later have a working machine without them needing to do anything else afterwards. Mirroring the data files from backup is a single step that can be done by any monkey, it's the configuration, or the manual selecting of a script to run, something they can easily screw up, that's I want to avoid. On Tue, Jan 20, 2015 at 9:51 AM, Les Mikesell wrote: > On Tue, Jan 20, 2015 at 10:41 AM, Tom Grace > wrote: > > On 20/01/2015 16:29, Ashley M. Kirchner wrote: > >> > >> So my question is, is there some way do determine via kickstart, what to > >> install on that machine based on some criteria, possibly the IP that's > >> being assigned to it, or MAC address, or something ... > > > > If you just want to use kickstart, it would be pretty simple to serve > these > > via HTTP, and have a simple script in PHP or similar that takes the > > requesting IP and uses it to choose which version of the kickstart to > serve. > > > > I would suggest that the "right way" would be to kickstart all your > machines > > the same way, and then use a configuration management tool (like Puppet > or > > Chef) to customize them. This approach is likely to be more work, but > also > > more maintainable in the long run. > > Or, if you just want the packages that a custom kickstart would > install, use a basic kickstart to bring it up, then run your own > script (from an nfs mount, scp'd over, pasted into a command line or > whatever you might find easier than learning puppet). The script just > needs to determine the rest of the packages needed for this particular > server and 'yum install ' them. > > -- >Les Mikesell > lesmikes...@gmail.com > ___ > 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
Re: [CentOS] Kickstarting several *different* setups
On Tue, Jan 20, 2015 at 11:13 AM, Ashley M. Kirchner wrote: > Tom: Thanks for the suggestion. I'll look into those tools. > > Mark: Yes, they are using pxeboot. Right now when they boot up, the pxe > config offers two options, 32- and 64bit. Are you suggesting I create > multiple entries that one selects based on what the machine is going to be? > Is there a way to have this done automatically so I don't have to > physically have to do that for each machine, but rather turn the thing on > and have it determine what needs to get installed on that particular > machine? > > Les: I was hoping for some way to have it all automated so if for some > reason I'm not in the building, I can instruct someone else to reboot, pick > the kickstart option in the pxeboot menu (be it a web, mail, db, or user > server) and a few minutes later have a working machine without them needing > to do anything else afterwards. Mirroring the data files from backup is a > single step that can be done by any monkey, it's the configuration, or the > manual selecting of a script to run, something they can easily screw up, > that's I want to avoid. There's always a tradeoff in hiding what is being done between simplifying things and making it completely impossible for anyone else to understand it or fix it if it breaks when you aren't there. I like a little balance between the extremes. Like making the scripts that do the work visible, but including some sanity checking so it won't run on the wrong machine - or anything else that you can guess ahead of time someone might do wrong with it. But you could embed the same thing in a cgi kickstart URL if there is some way it can deduce the right file to deliver or make your db restore process add/configure any missing packages needed at that point. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstarting several *different* setups
Gotcha. Thanks all! You guys gave me the answers I needed to know and hear. For the immediate futre I will likely go with multiple pxeboot options which then picks the specific kickstart file. It's easy for me to put a label on the server that says 'web' or 'mail' etc. Then just pick the same from the menu. Eventually I'll delve deeper into custom and automated setups. On Tue, Jan 20, 2015 at 10:35 AM, Les Mikesell wrote: > On Tue, Jan 20, 2015 at 11:13 AM, Ashley M. Kirchner > wrote: > > Tom: Thanks for the suggestion. I'll look into those tools. > > > > Mark: Yes, they are using pxeboot. Right now when they boot up, the pxe > > config offers two options, 32- and 64bit. Are you suggesting I create > > multiple entries that one selects based on what the machine is going to > be? > > Is there a way to have this done automatically so I don't have to > > physically have to do that for each machine, but rather turn the thing on > > and have it determine what needs to get installed on that particular > > machine? > > > > Les: I was hoping for some way to have it all automated so if for some > > reason I'm not in the building, I can instruct someone else to reboot, > pick > > the kickstart option in the pxeboot menu (be it a web, mail, db, or user > > server) and a few minutes later have a working machine without them > needing > > to do anything else afterwards. Mirroring the data files from backup is a > > single step that can be done by any monkey, it's the configuration, or > the > > manual selecting of a script to run, something they can easily screw up, > > that's I want to avoid. > > There's always a tradeoff in hiding what is being done between > simplifying things and making it completely impossible for anyone else > to understand it or fix it if it breaks when you aren't there. I like > a little balance between the extremes. Like making the scripts that > do the work visible, but including some sanity checking so it won't > run on the wrong machine - or anything else that you can guess ahead > of time someone might do wrong with it. But you could embed the same > thing in a cgi kickstart URL if there is some way it can deduce the > right file to deliver or make your db restore process add/configure > any missing packages needed at that point. > > -- >Les Mikesell > lesmikes...@gmail.com > ___ > 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
Re: [CentOS] Kickstarting several *different* setups
On 01/20/2015 08:41 AM, Tom Grace wrote: I would suggest that the "right way" would be to kickstart all your machines the same way, and then use a configuration management tool (like Puppet or Chef) to customize them Seconded. Personally, I recommend either ansible or bcfg2 over other tools. Puppet has a larger user base, but when I talk to users at conferences (such as LISA), ansible and bcfg2 users tend to like their tools, while an awful lot of people dislike Puppet but use it anyway due to inertia. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] leap second and Centos
Unix and ntp handle leap seconds a bit differently. Unix time increases during the leap second and drops back a second after. Ntp freezes time during the leap second. OS kernels may do either or neither. -- Michael henne...@web.cs.ndsu.nodak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstarting several *different* setups
On Tue, Jan 20, 2015 at 3:14 PM, Gordon Messmer wrote: > >> I would suggest that the "right way" would be to kickstart all your >> machines the same way, and then use a configuration management tool >> (like Puppet or Chef) to customize them > > > Seconded. > > Personally, I recommend either ansible or bcfg2 over other tools. Puppet has > a larger user base, but when I talk to users at conferences (such as LISA), > ansible and bcfg2 users tend to like their tools, while an awful lot of > people dislike Puppet but use it anyway due to inertia. There's also saltstack which is one of the newer of the bunch. It has some chance of working reasonably across different platforms. How you feel about it will probably depend on how you feel about python in general - and how you expect upgrades to go in the future. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Is anyone using C7 in production yet? (sssd, nss-pam-ldapd, kerberos, etc)
Hi all, Is anyone using C7 in production with LDAP and kerberos? Currently all of my machines run C5 or C6 with nss-pam-ldapd or nss_ldap, with kerberos and pam_krb5 for authentication. Before I fire up a test VM (is it even worth it?) I wanted to check feedback from the community. Cheers! Dan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstarting several *different* setups
don't forget you can define PXE config files based on the IP, IP range or MAC address of the server. This means that you don't have to select the correct pxeboot option from a PXE menu it will select the most precise config file automatically. see the following http://www.syslinux.org/wiki/index.php/PXELINUX#Configuration also you can pass additional arguments on the pxeboot line so that you can read from your pre and post scripts using /proc/cmdline. https://www.redhat.com/promo/summit/2010/presentations/summit/decoding-the-code/wed/cshabazi-530-more/MORE-Kickstart-Tips-and-Tricks.pdf Grant On 21/01/15 05:43, Ashley M. Kirchner wrote: Gotcha. Thanks all! You guys gave me the answers I needed to know and hear. For the immediate futre I will likely go with multiple pxeboot options which then picks the specific kickstart file. It's easy for me to put a label on the server that says 'web' or 'mail' etc. Then just pick the same from the menu. Eventually I'll delve deeper into custom and automated setups. On Tue, Jan 20, 2015 at 10:35 AM, Les Mikesell wrote: ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstarting several *different* setups
Les Mikesell wrote: > Gordon Messmer wrote: > >> I would suggest that the "right way" would be to kickstart all your > >> machines the same way, and then use a configuration management tool > >> (like Puppet or Chef) to customize them > > > > Seconded. > > > > Personally, I recommend either ansible or bcfg2 over other tools. Puppet has > > a larger user base, but when I talk to users at conferences (such as LISA), > > ansible and bcfg2 users tend to like their tools, while an awful lot of > > people dislike Puppet but use it anyway due to inertia. > > There's also saltstack which is one of the newer of the bunch. It has > some chance of working reasonably across different platforms. How > you feel about it will probably depend on how you feel about python in > general - and how you expect upgrades to go in the future. Take a look at Cobbler. I use this to create about 40 servers. Works really well, produces customized kickstarts, has a web GUI as well as command line operation, has lots of nice features to get the job done. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Is anyone using C7 in production yet? (sssd, nss-pam-ldapd, kerberos, etc)
On 01/20/2015 05:26 PM, Dan Irwin wrote: Before I fire up a test VM (is it even worth it?) I wanted to check feedback from the community. It works well. Use sssd instead of nss-pam-ldapd and nss_ldap and pam_krb5. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
