Sure, I could do that. However:
Well, it’s your time, not mine. Seems to me someone could ask and that would at least give you a starting place.
What I have ATM:
> ls -gG agama*
-rw-rw-r-- 1 805486592 Nov 3 21:54 agama-installer.x86_64-18.pre.0.0-openSUSE-Build9.20.iso
-rw-rw-r-- 1 123 Nov 3 23:55 agama-installer.x86_64-18.pre.0.0-openSUSE-Build9.20.iso.sha256
-rw-rw-r-- 1 832653312 Jan 22 11:17 agama-installer.x86_64-19.pre.0.0-openSUSE-Build3.6.iso
-rw-rw-r-- 1 122 Jan 22 11:40 agama-installer.x86_64-19.pre.0.0-openSUSE-Build3.6.iso.sha256
-rw-rw-r-- 1 833177600 Jan 22 12:32 agama-installer.x86_64-19.pre.0.0-openSUSE-Build3.9.iso
-rw-rw-r-- 1 122 Jan 22 13:42 agama-installer.x86_64-19.pre.0.0-openSUSE-Build3.9.iso.sha256
-rw-rw-r-- 1 692797440 Sep 29 09:47 agama-installer.x86_64-Leap_160GA.iso
-rw-rw-r-- 1 832260096 Jan 22 07:03 agama-installer.x86_64-openSUSE.iso
-rw-rw-r-- 1 102 Jan 22 11:22 agama-installer.x86_64-openSUSE.iso.sha256
lrwxrwxrwx 1 55 Jan 22 11:42 agama.iso -> agama-installer.x86_64-19.pre.0.0-openSUSE-Build3.6.iso
#
Perhaps a better question is should I try Agama soon. Is detailed package selection equivalent to YaST yet? If not, this thread is functionally moot for me for today, giving Agama a try prior to getting a fresh TW installed for getting back to my Plasma black screens thread. I don’t see that a full boat/kitchen sink Plasma installation would be helpful to that end. YaST WFM, remaining the best PC operating system installer I’ve ever used.
The questions is: why not. It does not hurt. It does not take much time. And you may learn something new. Simply fire up a VM and test…
As you already have several hundreds of installations, why not add one more.
The only VMs here are DOS sessions on OS/2. What hooked me on SUSE in the first place was the free tiny .isos that fit a CD for installing via HTTP. Not too terribly long later I found starting an installation with YaST was quicker and simpler, download a kernel and initrd, and with a little help from reading linuxrc, load them with Grub. Setting up a stanza to start Agama is more complicated, in part because the system boot partitions to host Grub and small selection of kernels and initrds don’t have room for .iso files of any consequence, and I don’t like fooling with USB sticks, either making ones that work, tracking what any of them contain, or managing a collection of no two alike, with inadequate room to write on them big enough to read, not to mention figuring out which if any are available for the purpose, since the simplicity of Ventoy is (supposedly, yet not IME to date) a no-no.
It is your way how you are used to setup your systems. But honestly it is overcomplicated for simple tasks like testing an installer like Agama or any other distribution imo.
Using a VM does not need any tinkering with kernel or initrd or grub. You also don’t need an USB stick. Creating a VM is a question of seconds. Then install the OS. Now you have a starting installation. Now you can clone the guest within few seconds and have identical copys where you can start your tests with. Guest is screwed up? No worry, simply delete it and use another starting copy. Using VMs does decrease the time for simple test dramatically imo.
But yes, everybody has another way of work.
VMs don’t fit my space available allocations or backup system, and aren’t apropos for the time I spend verifying issues that depend on specific hardware.
BTW, I’m running the YaST installer now…
@mrmazda AFAIK there won’t be, end users are expected to use profiles…
That’s my understanding as well. More discrete package selection is available by building your own custom installer that includes what you want and don’t want.
This is for agama 13, but talks specifically to this point, noting that there are no plans to add fine-grained package selection to the GUI-based/web-based installer.
I run the live images direct with qemu… download, run and done ![]()
Installation of TW20210121 went well with the YaST installer. I have an iMac that still doesn’t have 16.0 yet, so that could be where I give Agama a try, if and when I can develop a decent idea how to choose among the various sources of Agama .isos that showed up here, which as yet hasn’t happened. Or I could try whichever 16.1alpha shows up with. Or…
Read up on how to create profiles, I add a password to the image so can just boot a system and come back to my desktop and perform the install.
Worst case, the last of the version 18 releases would be a good one to use. It may not have what you’re looking for, but it sounds like what you’re looking for in terms of granular package selection isn’t in the plan, so if you want that, you’ll be waiting until someone outside SUSE decides to implement it.
Or until you decide to roll your own with your preferred package selections already made.
YaST detailed package selection, import/export, etc. was one of the features causing me choose SUSE over the competition originally, so loss of detailed package selection during installation is just one less reason to continue to choose.
Today with YaST’s detailed package selection I managed to get a working Plasma desktop in an installation using only about 2800k:
# df /
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nvme0n1p30 8024896 2807140 4804060 37% /
#
Profiles sound like a NIH duplication of doing similar things in Fedora or Debian that I’ve never been inclined to try to do. When YaST installation expires in TW I should be able to get by with Agama’s base install, then install my basics omitted by Agama’s base using zypper before using myrlyn to flesh out the rest.
That is probably what I’d do.
As you are well aware, complaining here isn’t going to count for anything to change people’s minds. While it sounds like the decision is made, you could always try to rally some developers who have an interest in creating this functionality, if it’s really important to you.
You know this, so I won’t belabor the point.
Which is exactly what I’d expect experienced users to do, unless they prefer creating a profile. ![]()
Or you could install like this (sorry it is in German however the commands should give you the idea).
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.