Topic: Beta defaults to graphical installer

[compdoc]

The previous ISO (alpha?) had a script that bypassed the graphical installer, and installed SME on a standard partition rather than using an LVM layout.

Installing this Beta in a virtual machine, it seems to only provide the graphical installer with a default LVM layout. Is this the preferred file system now, or is this a problem that arises from using the Virtual Machine Manager and KVM?

Not a fan of LVM, I chose 'No LVM' from the Advanced Options menu.

[TerryF]

Thank you for testing and feedback

from one of the workers on the road to alpha and beta

Rocky8 default is lvm, so underlying option is lvm.
We could easily change default to non-lvm and the advanced options to be lvm.
Text install will do an automatic install. No option to change settings

I should say el8 ( as rhel and CentOS 8 do the same)

[allsorts]

Installing this Beta in a virtual machine, it seems to only provide the graphical installer with a default LVM layout.

Installing on bare metal, could only get a graphical installer, no text one at all. Even if I select the text option from the boot menu. Point me at where the boot sequence is and I'll have a quick look.

--
Cheers
Dave.

[TerryF]

Another may jump in here as well, but, if my memory serves me well, the text installer was disabled for the beta when doing a install, until the final of the config options etc was finalized, the man at the pointy end Trevor, is currently making his way to central Australia to be present for a once in a lifetime event   the filling of Lake Eyre.

He may answer as well, and/or others

[TerryF]

and yes dug back and found Trevors feedback in our etsting chats

I removed the text option as it just installed ( maybe call it automatic) and reintroduce)

Rocky8 default is lvm, so underlying option is lvm.
We could easily change default to non-lvm and the advanced options to be lvm.
Text install will do an automatic install. No option to change settings

More to come I do think

[compdoc]

LVM in Alpha caused a nightly email reporting an error about quotas, if I remember correctly. An update stopped the error from occurring, and i ran my Alpha system all this time using LVM with no issues.

I've always preferred a flat file system because some utilities like clonezilla didn't work well with LVM. However, I believe this is no longer true, and although I dont know the benefits of LVM or how to work with it, I suppose I can learn to live with it.

Besides, there was an option in Beta to not use LVM while installing, so I'm thinking this is not a problem and doesn't need the developers to waste time with it.

[ReetP]

As a lot use VMs on Proxmox that already has LVM, there is little point in doing it again unless on bare metal, IIRC.

Be an interesting stat to have!

[Jean-Philippe Pialasse]

as already reported pay attention that if you go in the gui utility disk our defined partitionning will be defaulted to all disks in one giant lvm.

Only fixes are
1- reboot the installer or
2- manually create your own partitionning.


for text based instaler Trevor did remark that in beta1 it did start the installer without promping any input. so was useless for the moment and we decided to just hide it for this release and move to verify all other situations with more people. 


the boot menu has however inteoduce few items to show you options that were previously only accessible by editing the command line, one of those is

Code: [Select]

Install Koozali SME Server 11.0 with noraid and nolvm
this is a suitable option for virtual machines. 

[compdoc]

As a lot use VMs on Proxmox that already has LVM, there is little point in doing it again unless on bare metal, IIRC.

Good point, it doesn't make sense to use in a VM.

[ReetP]

Good point, it doesn't make sense to use in a VM.

Yes, but admission - it wasn't an original idea from me.... ! Someone pointed it out many moons ago when I first started messing with Prox.