- This topic has 56 replies, 6 voices, and was last updated Oct 24-1:56 pm by melodie.
-
Posts
-
melodie
how can I get the installer to show on the desktop in the live?
Prior to launching isosnapshotmaker, edit /etc/isosnapshot.conf and ensure that it contains this declaration:
force_installer=trueHello,
the installer is installed alright. Just I think I don’t use “isosnapshotmaker”, but one of the tools which allow creating a redistributable version.
At the end of this day, I have added a command line in /etc/rc.local, as I have found in one of the cli-installer scripts information about /etc/rc.local being replaced by an rc.local.install antiX made (I don’t have the computer and the ISO under the hand at this time, can’t say more at the moment).
melodie
From a troubleshooting standpoint, we can’t guess whether you have encountered a separate, newly introduced, bug ~~ without hearing exact O/S version (e.g. antiX Full 17.4.1) (and, dist-upgrade was performed immediately prior to running the snapshot tool?) along with the exact installed versions of packages: “iso-snapshot-antix”, “remaster-antix”, “iso-template-antix”. During troubleshooting I would also ask: is the package “xorriso” currently installed on the machine performing the snapshot operation.
Skip the troubleshooting.
The following instructions should enable you to achieve the desired result.
(…)Hello Skidoo,
Thanks a lot, I’ll get into it and follow point by point, and report back, starting again tomorrow provided I find time for it. Else, it will be the next day or the following.Anonymous
The correct name of the antiX command is “isosnapshot” (/usr/bin/isosnapshot).
It is also available via the antiX controlCenter
melodie
Hi skidoo,
I have found one source of issues, in /usr/local/share/excludes. For some reason, the files have a copy of the old version, renamed “*.orig”. But, the one file having for name “general-remaster-exclude” existed only with the *.orig extention. I relamed it from “general-remaster-exclude.org” to “general-remaster-exclude.list”, which solved one of the issues I had met at the start of the isosnapshot program.
Another source of issues, was the old iso-snapshot package. Each time I would start the ISO in Virtualbox I would get an error message at the start, stating it would not find the “live aufs” something.
The tool I used successfully the last days is the iso-snapshot-antix last version available for the 17.4 antiX 32bits distribution. It is one having for name “0.3.8”.
I find the different tools to “remix/remaster/redo/remaster in a live/remaster a livecd” confusing, because all come with a desktop file placed in a different menu (I don’t use antiX control center, I do use the lxde applications menu, which follows the freedesktop specifications) and because the tooltips mostly say the same thing (“it’s me! – it’s me!… ) All are related to remix/creating one or other kind of respin, but, which kind? 😀
Next will be the 11th test. I still didn’t get a launcher on the Desktop in the live, to initiate the installation of the live to the virtual disk in Virtualbox.
Also, the desktop file I would like to have on the Desktop in the Live, in order to install has for name “antixsources.desktop”, belongs to the live-init-antix package, and is installed into /usr/share/applications/antix. I still need help to find a way to get it to the Desktop in the live. 🙂
Many thanks,
MélodiePS: to see the images below fully, you need to click on each of them.
- This reply was modified 3 years, 7 months ago by melodie.
- This reply was modified 3 years, 7 months ago by melodie.
melodie
Hello again,
what is different between “persist-makefs” and “persist-config” ? Both desktop files live in /usr/share/applications/antix and no way to know which one does what, and the toolip and menus have the same name.
Thanks for clarifying, and help report a bug or a wish against it?
what is different between “persist-makefs” and “persist-config” ?
You can easily discover the answer by launching each of them and noting the choice of actions offered by each of them. Also, they are shell scripts ~~ you can inspect their content in in a text editor. However, neither of them is relevant to isosnapshot.
in /usr/local/share/excludes. For some reason, the files have a copy of the old version, renamed “*.orig”. But, the one file having for name “general-remaster-exclude” existed only with the *.orig extention.
Here again, what you describe does not seem relevant to isosnapshot.
To confirm this, as a test, I removed the “general-remaster-exclude.list” file and ran isosnapshot ~~ it successfully completed test runs for both a “resetting accounts” and preserving accounts” snapshot.I can’t fathom the reason “.orig is present but .list is missing” on your system. In any event, that file would have been placed during installation of the “antix-libs” package (not the “iso-snapshot-antix” package).
the tooltips mostly say the same thing (“it’s me! – it’s me!… )
That suggests no one has yet contributed localized version of those tooltips for your locale, right?
Filing a “bug” for that would amount to “barking at the moon”.Okay, are ya ready?
Ready to follow the instructions I posted in the prior message?
“sudo isosnapshot” from a terminal prompt (so that you can watch for any errormsg output)
or, launch it via the controlCenter…melodie
Okay, are ya ready?
Ready to follow the instructions I posted in the prior message?
“sudo isosnapshot” from a terminal prompt (so that you can watch for any errormsg output)
or, launch it via the comtrolCenter…Hello Skidoo,
thanks a lot for your continous support!
* except for the controlcenter which I don’t have (my isos are now ~= 680MB large for having removed a lot), I have followed and tested everything you told me so far. Well not starting it from console, but, everything else.
* Then, I made clean : removed all remix/remaster/iso maker isosnapshot related packages, dependencies, and remaining files from the system, (“dpkg -S”, “dpkg -L”, updatedb and locate are among my best friends here). And I reinstalled fresh iso-snapshot-antix version 0.3.8 along with it’s dependencies.
* I have used more than one of the tips you provided to me, among which : what to modify and add in the /etc/isosnapshot.conf file, the tip to reconfigure the isolinux.cfg file using the isosnapshot option to do that with the text editor. I have not resumed reconfiguring the syslinux.cfg file yet, nor the message.cfg files, because when I did that I ran into big trouble. (I use mcedit as root, using the F4 option of mc if needed, and I do not open graphical file managers as root, ever).
* The version 12 of my tests is working fine. I will fine tune a few details before releasing it as a test version for all to try.
* About the ““persist-makefs” and “persist-config” commands, you are right, it’s not isosnapshot related, it’s distro related. I am trying to make the menus look well, ie: some script launchers there miss an icon, I have modified the seamonkey desktop file (and put the modified version in /etc/skel/.local/share/applications), because the “seamonkey-32×32.png” does not exist in /usr/share/pixmaps/seamonkey. The “preserve configuration” launchers related to ““persist-makefs” and “persist-config” both have the same “no icon”, both have the same descriptions, be it in French or in English, and possibly in other languages.
* I am ok to contribute by improving some translations from English to French, but I can’t here because the English descriptions are the same in both desktop files.
* in bento antiX test v12 once installed, I get “Le dépôt http://security.debian.org testing/updates Release n’a pas de fichier Release.” (the said repos does not have a Release file). This is in Synaptic, as I have chosen “Testing” when I started the install, using antixsources.sh.
How can I fix it? (ATM I have switched it with the “buster” security update repos, not sure if there is a better way).- This reply was modified 3 years, 6 months ago by melodie.
melodie
I get “Le dépôt http://security.debian.org testing/updates Release n’a pas de fichier Release.” (the said repos does not have a Release file).
. . .
I have chosen “Testing” when I started the install, using antixsources.sh.
How can I fix it?From you earlier screenshot (blue colored stripes across gray background) I’m guessing you have built atop antiX 19 beta. Specifying debian “testing” repo(s) may not be suitable until antiX 19 final is released.
If you had performed a dist-upgrade today (12 October) you would have been shown an advisement stating that some sources.list.d content has changed. If not, that recent change may be the cause of “xyz does not have a release file”…
…or it may simply be a mismatched timestamp, which might be resolved by running ntp to update the datetime on your machine.
melodie
From you earlier screenshot (blue colored stripes across gray background) I’m guessing you have built atop antiX 19 beta.
…or it may simply be a mismatched timestamp, which might be resolved by running ntp to update the datetime on your machine.
No, it’s not an antiX 19 beta, I think I mentioned earlier, it’s a 17.4 antiX.
Else, do you have any idea if there is a post-install script in the system where I can specify to remove the antixsources.sh desktop file (or hide it) and the antix installer at the end of install time?
is there a file in the installer for post-install removals?
If there is, I’m not aware of it. I’m not an expert on use of the installer & was only prepared to coach snapshot tool usage.From my perspective, a “post-install removal list” is rendered moot when performing a live-to-installed transition.
Theinstallersnapshot tool is designed to faithfully transfer all details of the currently running live system, minus any {files|dirs|patterns} specified in the excludes list. What would be the point, the benefit, from copying unwantedstuff during installation then immediately (post-install) deleting that unwantedstuff?edit: (strikeout texts b/c skidoo is struggling, trying to mentally shift tracks back and forth between snapshot vs install)
Technically, the installer does perform some automated behind behind-the-scenes housekeeping.
You can find some hardcoded removal items stated within /usr/sbin/live-to-installed (provided by package “installer-data-antix”)
and maybe you will wish to add some additional hardcoded removal items therein.
If you do, bear in mind that your edits are subject to being overwritten if a future updated version of the “installer-data-antix” package gets installed (installed on end-user live systems, via dist-upgrade).
phillw
Hi good people, I’ve just tried to run the installer in a KVM virtual machine and neither the installer nor gparted can ‘see’ the logical volume (vda) that I’ve allocated to the instance. Any ideas?
Thanks,
Phill.**EDIT** As requested I’ve tried the Full AntiX ISOs, the 32 bit one cannot ‘see’ the lvm but the 64 bit one can.
- This reply was modified 3 years, 6 months ago by phillw. Reason: more information
Education is the route to freedom, make it free to all.
melodie, if you are receiving this error
read this
https://www.antixforum.com/forums/topic/expkeysig-error/
Follow the “Method 1, steps 1-3” in the link topic to remove the error.melodie
What would be the point, the benefit, from copying unwantedstuff during installation then immediately (post-install) deleting that unwantedstuff?
Some packages can be useful in a Live ISO/CD/USB whatever live that is also meant to be used for install, but not wanted or needed anymore after, such as : an installer, live remixing tools (lots of end users I know would never ever in their life think about using them, the basic uses are already a struggle to them), another one which is very good on a live, is the zram config package, once it will be working in antiX (as for now it doesn’t). It appeared that in a final install it may or may not be a good idea to keep it, sometimes, if there is enough RAM in the targeted machine, and has a nvidia GPU, it was triggering freezes.
You can find some more examples in the post-install files in some ISOs, such as at Ubuntu (while it is what I have known best the last years, I think other distros also might use this way of building live ISOS).
You can find some hardcoded removal items stated within /usr/sbin/live-to-installed (provided by package “installer-data-antix”)
and maybe you will wish to add some additional hardcoded removal items therein.
If you do, bear in mind that your edits are subject to being overwritten if a future updated version of the “installer-data-antix” package gets installed (installed on end-user live systems, via dist-upgrade).I’ll have a look there, thank you!
- This reply was modified 3 years, 6 months ago by melodie.
melodie
What would be the point, the benefit, from copying unwantedstuff during installation then immediately (post-install) deleting that unwantedstuff?
Some packages can be useful in a Live ISO/CD/USB whatever live that is also meant to be used for install, but not wanted or needed anymore after, such as : an installer, live remixing tools (lots of end users I know would never ever in their life think about using them, the basic uses are already a struggle to them), another one which is very good on a live, is the zram config package, once it will be working in antiX (as for now it doesn’t). It appeared that in a final install it may or may not be a good idea to keep it, sometimes, if there is enough RAM in the targeted machine, and has a nvidia GPU, it was triggering freezes.
You can find some more examples in the post-install files in some ISOs, such as at Ubuntu (while it is what I have known best the last years, I think other distros also might use this way of building live ISOS).
You can find some hardcoded removal items stated within /usr/sbin/live-to-installed (provided by package “installer-data-antix”)
and maybe you will wish to add some additional hardcoded removal items therein.
If you do, bear in mind that your edits are subject to being overwritten if a future updated version of the “installer-data-antix” package gets installed (installed on end-user live systems, via dist-upgrade).I’ll have a look there, thank you!
- You must be logged in to reply to this topic.
