-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Partitions in MB and not in % #62
Comments
|
Pull requests accepted on this. |
What should be done? I cannot create a Pull Request. |
I was thinking about this a bit - I could try to integrate both the percentage and the MB values on to the screen and link them. |
I ended up just changing the section where it writes the values to the kickstart with static values and just ignore the partition section of the menu. We use a dedicated VM for each application so I use a default minimal value on all my volumes and increase as required. I also make a few other changes to include extra packages, firewall changes, grub user/pass changes, our CA cert chain, and additional RPM GPG keys. |
So there will be change for MB or not? |
Sorry, I've been swamped with stuff I working on additional stuff this weekend - with a baby coming here in less than a month I don't have the free time I used to. |
Hi, Then I made following steps to get the filesystem mounted as it should do.
... all mountspoints are mounted correctly. Now to my question. Is there somewhere in the code a check for mountpoint called is /usr? I cannot find one. The coding if the file menu,py should be ok from my point if view. Any ideas for that? I would be glad to have a solution to that @fcaviggia I hope everything is fine getting father. I wish your wife and yourself a kind of "happy landing" cu |
I've actually done a fair bit of redesign to this project at work and that code is being integrated by the SIMP Project (https://simp-project.com/, https://github.com/NationalSecurityAgency/SIMP) The big change was around creating static (pre-defined) kickstarts for partitioning. Once life has settled a bit I want to contribute to that project more than this project. Anyway, where are you preforming those commands - in the installation (pre-, during, or post- install)? Are the modifications being used with LUKS? Adding the filesystem to fstab after it's created should be all that's needed. I'll try to respond better - weekends I've been extremely busy getting ready for the baby (2 weeks out) and work (travel, papers, presentations) - I don't mean to be ignoring stuff but life has priorities and bills. I'll try to be responsive, just swamped right now. 😄 |
Hi, |
Hello,
I was wondering to change the percent-mounts to mb-mounts, but I am not that good in python. First of all I changed it in the redhat6-hardening meny.py and it worked. Now I treid the same with the redhat7-hardening menu.py. Under redhat6-hardening I added a new variable "
". This new self.disk_mb should be the value:
First step: I changed the luks- configuration:
The server should be started up as far as possible without entering any data. In a data center this is sometimes necessary.
Second step: Example:
All partitions should be set from percent to an actual size. This has the advantage that the administrator can leave the defaults independent of the existing hard disk size. At a e.g. 500GB hard drive would be 10 percent for root way too much in my opinion.
Third Step:
There is a division of hard disk mountpoints. Here the standards are taken from a Linux operating system. Here I would separate the mountpoint /usr. With the optional mountpoints /opt or /var/www the question arises under Redhat, if /var/www is really necessary. The admin could set this up at any time on the console, if desired. Because if you also include repositories, under Redhat it can very easily happen that e.g. Apache (http24) does not have its files as usual under /var/www/html. These would then be under /opt/rh/httpd24/root/var/www/.
Now the question:
Does anyone already have such a working version? I would be very happy to get this version of the menu.py file.
The text was updated successfully, but these errors were encountered: