centos/fedora install without gui!

[bruce]

Hi guys/list.

Looking into installing centos/fedora and I'd like to increase the
inodes on the partitions. So I'm trying to find a step by step process
to accomplish this.

As far as I can tell, the GUI/Anaconda doesn't have any place for me
to insert the increased inode count.

Comments would be appreciated.

ps.

I know I can take a partition offline, reformat it, and increase the
nodes, but I don't see how one can do this with the primary/root
portion of the drive on the same system..

thanks

[Tom Horsley]

On Thu, 14 Aug 2014 14:29:12 -0400
bruce wrote:
> As far as I can tell, the GUI/Anaconda doesn't have any place for me
> to insert the increased inode count.

I've given up using anaconda on my targets. I almost always
install now into a virtual machine, partition a hard disk
manually, then guestmout and rsync the virtual install
onto a real disk partitioned the way I want it :-).

Need to clean up UUIDs and such, and chroot into it to
run the grub install, but one big advantage is that the
system is up and running the entire time I'm doing the
install into the virtual machine.

[William Oliver]

On Thu, 14 Aug 2014, Tom Horsley wrote:
> I've given up using anaconda on my targets. I almost always
> install now into a virtual machine, partition a hard disk
> manually, then guestmout and rsync the virtual install
> onto a real disk partitioned the way I want it :-).
>
> Need to clean up UUIDs and such, and chroot into it to
> run the grub install, but one big advantage is that the
> system is up and running the entire time I'm doing the
> install into the virtual machine.

That's a neat idea.  I've never tried it.  I think I will.

billo

[Chris Adams]

Once upon a time, bruce  said:
> As far as I can tell, the GUI/Anaconda doesn't have any place for me
> to insert the increased inode count.

So, I asked for the ability to set custom options many years ago, and
was told there's a way to do it through kickstart.  Basically, you have
to have a %pre that adds custom entries to /etc/mke2fs.conf, and then
you reference them in the logvol and/or part lines in the kickstart with
"--fsprofile=foo".

However, then it didn't work for me (in RHEL 6 IIRC) because of a bug
that there was no telling when it would be fixed, so I manually created
filesystems the way I wanted (still in kickstart) and I never looked
back at the "official" way to do it.  You can't do that anymore because
anaconda devs decided they should always format the root filesystem.