It wouldnt really be such a big deal maybe, but some of the packages included dont make much sense. I mean, how many people need bluetooth on a server? A lot of places dont want firefox on a server, but that is installed by default, and while you may not need a full xwin install, most people use xclock to verify that its working. I really think the package selection conversation (or lack thereof) is probably the most irritating piece. On Thu, Jul 31, 2014 at 7:37 PM, Justin Mungal <justin@xxxxxxx> wrote: > So it sounds like they made it completely different from the RHEL7 > installation GUI, and it's also awful? I'll have to check it out sometime. > The last OL I used was version 6 for some 12c testing. It worked fine. I > recall manually disabling SELinux and iptables after the install, however > I'm not sure if that could have been done during the installation or not. > Looking at some screenshots I have of the OL 6 installation, it looks like > firstboot is no longer there (which is where I would disable SELinux and > iptables in CentOS 5). > > > On Thu, Jul 31, 2014 at 7:25 PM, Andrew Kerber <andrew.kerber@xxxxxxxxx> > wrote: > >> The biggest reason is there is no way to disable them during the install >> process. Having them enabled by default is not a big deal, but then having >> to go through the manual disable process is annoying to say the least, and >> a major change from previous versions. >> >> >> On Thu, Jul 31, 2014 at 6:57 PM, William Muriithi < >> william.muriithi@xxxxxxxxx> wrote: >> >>> >>> > Yeah, that would be interesting to know. To explain further, they >>> have several groups of packages you can choose for installation, but there >>> there is no way to pick and choose individual packages, eg X windows or >>> gnome desktop, only groups, eg network server. If that is intended to copy >>> RHEL, I would have to say neither one has a good understanding of their >>> user base. >>> > >>> >>> You could install minimal, then install whatever you need post operating >>> system install. You can install individual rpm instead of groups then. >>> >>> > Also, selinux and firewall are installed and enabled by default and >>> have to be manually disabled. >>> > >>> Odd, why is this bad? So many current security problems are due to >>> vendors defaulting to insecure setup. They seem to be thinking twice about >>> it these days. Heck, even windows by default have the firewall enabled. >>> > >>> > >>> >>> William >>> >> >> >> >> -- >> Andrew W. Kerber >> >> 'If at first you dont succeed, dont take up skydiving.' >> > > -- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.'