I’ve just fresh installed Manjaro and I have it configured to my preferences.
I’m trying to create an iso from my current setup.
I’m following this guide:
I’m getting an error at the end when I run the buildiso command where the process aborts and I’ve tried this once before in a live environment and I thought that maybe an errors were related to running this in a live environment but maybe I’m following this incorrectly, since now I’m running it on an install.
Appreciate the feedback in advance.
** I’m also new to linux so although I prefer a gui like in MX LInux but it seems there is none on Manjaro, but I thought to give this a try anyway. Therefore, there are many things especially in terminal I’m unfamiliar with, probably even basics.
Here are the details from the terminal:
System Info:
Operating System: Manjaro Linux
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.11-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Appreciate the reply. Would you know how I can fix this? I can provide more information in case that would help. Just let me know what you need me to do or provide.
cp: cannot stat '/manjaro_kd_imr/iso-profiles/imran/my-kde/desktop-overlay/etc/skel/.mozilla/firefox/xyrk2svk.default-release/lock': No such file or directory
cp: cannot stat '/manjaro_kd_imr/iso-profiles/imran/my-kde/desktop-overlay/etc/skel/.librewolf/rtkwxkrh.default-default/lock': No such file or directory
cp: cannot stat '/manjaro_kd_imr/iso-profiles/imran/my-kde/desktop-overlay/etc/skel/iso-profiles/manjaro/bladebook/live-overlay/etc/xdg': No such file or directory
cp: cannot stat '/manjaro_kd_imr/iso-profiles/imran/my-kde/desktop-overlay/etc/skel/iso-profiles/oem/infinitybookpro-oem-xfce/desktop-overlay/etc/fonts/conf.d/70-no-bitmaps.conf': No such file or directory
Does this give you any clue? I think you just have to remove the files it can’t find?
So I built a couple iso’s and tested them in Boxes. They start up fine in Boxes.
Problem is they hang on boot and I see no errors. Last entry on boot is something like:
Successfully written to Plymouth and then it just hangs and after 5 minutes I usually end up pressing [CTRL][ALT][DEL]
One step in this process I’m trying to pin down is:
“Modify the tools configuration to point to your storage partition’s mount point - use your favorite editor to edit the file”
micro ~/.config/manjaro-tools/manjaro-tools.conf
The terminal says there’s no such command so instead, I use Kate to edit the config file and there’s nothing about mount points, so I skipped this step after finding nothing about mountpoints in the config file. Which I dunno whether it effects the end result.
I did check the file thoroughly and found nothing where I could edit mountpoints. Maybe in case you or someone could explain how to correct this, I could try again. But again, the iso’s boot up fine on Boxes.
Let me know what you need from me or whether I should make a new thread. Thank you.
I get a blank screen with a bunch shortcuts? at the bottom. So I think it worked. Although, this interface is unfamiliar to me.
Is it ok to just use Kate to edit the config file instead? An in case that’s fine, the question remains on what to edit on the actual configuration file for “manjaro-tools.conf”
The directions say to “Modify the tools configuration to point to your storage partition’s mount point”
The manjaro-tools.config file it wants me to edit:
That’s perfectly fine. Although, as nano is the default editor, it might be worth your time to learn how to use it.
I’m afraid I’m unable to help with that. I’ve never needed to use these tools in Manjaro. Though, looking at your linked config, these lines look like possibilities:
# cache dir where buildpkg, buildtree cache packages/pkgbuild, builiso iso files
# cache_dir=/var/cache/manjaro-tools
# build dir where buildpkg or buildiso chroots are created
# chroots_dir=/var/lib/manjaro-tools
What specifically do your instructions tell you, and is there any context that’s missing? Perhaps offer a link to those instructions so that nobody is flying blind.
So, this tells me that if you don’t change the location, files will be stored at /var/cache/manjaro-tools by default. If you have sufficient space in / – because /var/ is under it – then you shouldn’t have a problem with that.
However, from the wording, it’s unclear whether you need to uncomment that default location to use it, or whether the respective scripts will use it automatically. My guess is that you would need to uncomment it.
However, if you want to change it (perhaps to a larger partition), change the path to the mount point of the partition you wish to use;
I especially wrote the guide to be clear and consise without unnecessary explanations.
Configuration files often shows the default values as comments - so there is no need to uncomment the value to use it.
If there is missing files - they may be invalid symlinks created by an application running at the time you copied your home. When the app is terminated the symlinks becomes invalid.
There is no need to edit the manjaro-tools.conf. Simply override using the -t argument as described in step 11.
When the buildiso script runs for the first time it will scan your system to locate the iso-profiles folder and create the iso-profiles.conf pointing to the location. ONLY if you have used buildiso before you must change that file to point to the /mybuild environment described in the mini-guide.
I was asking because the iso is created and works in a virtual machine (Boxes)…
But when booting the iso on the system, it hangs until I’m just forced to restart the computer.
I was maybe thinking I’m missing something because of that. That’s why I’m trying to seek clarification on this step,
I’m glad to read that. So the question remains on what do to about the iso that was created and doesn’t boot? Like I stated before it boots on a virtual machine but when I’m trying to install from it, it hangs on something like Writing to Plymouth successful Everything else appears to be ok.
I will see whether I could obtain a screenshot of the boot screen but on Boxes, I’m unable to emulate this.
** Note: Also, I have 3 other linux isos that boot fine. Including Garuda, Cachy and Manjaro. They are all downloaded from their respected websites though and not custom. I have a Custom iso from MX that also boots fine that was made with the iso tool that’s part of MX.