One thing I'm working on now is to automatically generate the persistence files (rootfs and/or homefs)
at boot-time if persistence is selected and the files don't yet exist.
AFAIK, no distro has ever provided such functionality, not even puppy.
I might have seen such an idea discussed, and discarded, based on a rationale that it would (duh!) bog the boot process.
I *think* that 13.1-base and 13.1-core can just be upgraded through apt to get to a 13.2 system.
A perceived pain point is the comparatively older kernel present in 13.1
It is easier to dl 13.2 full, strip out stuff & snapshot from live session
than it is to"install" 13.1 (in order to update kernel) then recreate pendrive.
Feedback on the forums helps drive development.
I wish antix would provide a first-run"welcome" app/dialog, ala puppy.
By first-run I mean LIVE.
Any welcome provided post-install is a separate critter (one which many new users will miss, cannot benefit from, during a live test drive).
I'm not prepared to suggest what content nuggets and/or links that"welcome" should present
(could create a"welcome suggestions" thread and collect ideas + links)
Feedback on the forums helps drive development.
Several of the yad -powered gui utils launched by antix controlcentre are far from ideal, in terms of usability.
If you (again, for the Nth time?)"run through them, pretending to be a new user", you might recognize the pain points. One early (and especially daunting) pain point is creation of new persistence file ~~ no progressbar displays during the lengthy operation, leaving user wondering whether anything is happening, wondering"is the program hung up, or what"? Another pain point is multi-step operations which launch new dialog windows... then dump user back to the parent dialog, with zero indication of"you are here" or"the next step is... (highlighted)"
bug:
(I believe I've already twice reported this, since 13.1)
mouse acceleration. Change the setting and it (value for that pref) does not persist across sessions.
Change the setting and user is told"kb setting updated" (or somesuch) wtf? (3 different prefs reported for a single change)
observation:
The default entries contained in the snapshot exclude list, as well as the remastercc (?) exclude list... seem oriented to a'body creating a remaster intended to be shared with a friend. From where I sit (as a primarily live-session user), the more common use case would be pushing one's tweaked build back to a pendrive (flatten the layers, incorporate the savefile). Even from an installed system,"making a copy for self" seems (to me) the most common use case. By"erring on the safe side" and excluding paths containing"personal stuffs" by default, the scenario really stacks a burden (wading through docs, editing excludes file) on the casual user ~~ setting him up for disappointment when he discovers that his bookmarks and Downloads and whatnot have not been retained and preserved in the resulting"snapshot" copy. To avoid misunderstandings/disappointments, probably a good idea to add a first-run"speedbump" by forcing the user to at least handle (locate and rename, if not edit) the default excludes list.