I am new to ArchLinux, migrating from Fedora 20/21 and I was wondering how one goes about creating a custom LiveCD. My idea is to create a LiveCD on the lines of archbang or Evolution Linux which I can then give my students for easy installation. This is possible on Fedora using livecd-creator and a kickstart file. Are there similar instructions available for ArchLinux?
I understand that this may be anathema to true-blood Arch users, but the reason I am thinking of dumping Fedora for Arch is because of the latter's rolling release model. My students (none of whom are computer science or related students) are able to use Linux systems but will not be able to install Arch from scratch using the necessary scripts.
Maybe they could use Archbang and if needed visit the archbang forums, but use the Arch wiki if needed..
It has an Installer, rolls with Arch repo's, openbox based pseudo desktop, bootable live cd which can run from ram, CD, or USB media.
I accidentally "sudo rm -rf /usr" (please don't ask why, really). So, I was told on IRC that I had to flash a .iso to a USB Drive. So I did, using another computer. I then rebooted the main computer where I sudo rm -rf'd /usr/ and booted this fresh .iso. So far, so good.
If I'm curt with you it's because time is a factor. I think fast, I talk fast and I need you guys to act fast if you wanna get out of this. So, pretty please... with sugar on top. Clean the [censored] car. -The Wolf
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
The "minimal bash thing" gave some error message before dumping you at the prompt, right? What were the error messages? Was this actually the recovery shell (# prompt) or was this the grub line (> prompt)?
That means the grub configuration is most likely wrong and it is not being properly directed to your boot parition. The grub wiki should describe how to (re)configure it. Just follow the directions as if your were just installing grub. With grub-legacy you would edit a text file, with the new grub there are some auto configuration tools that (in theory) should do most of this for you.
That worked guys! I had to mount /boot/ too, I already managed to boot into my computer and shut it down too, I can't believe I made it after "sudo rm -rf /usr/"! Now I have to reinstall all packages, but I can do that from my computer and not the livecd now.
I managed to make my system boot, I ran "pacman -S $(pacman -Qeq) --noconfirm" but not ALL packages were installed. A lot of them were, but "python" and "python2" for example weren't installed. I think only 300 packages were installed, but I had many more.
The reason your build is failing right now is that the french live kickstarter files exclude all ibus* packages, and ibus is a requirement for gnome-shell. You can determine this via
dnf repoquery --deplist --requires gnome-shell grep ibus
or
dnf repoquery --whatrequires ibus
I am not sure why you had the first problem. I did not try building that image, but be aware, those templates can be very old. The rpmfusion kickstarter templates is at least four years old and will not work without a lot of modification.
SELinux is left active and not changed for the purpose of the livecd creation process as you recommand. But here (dated 2020) it is said otherwise: Livemedia-creator- How to create and use a Live CD - Fedora Project Wiki)
That Koji article looks some good documentation. It looks like they have an IRC channel where you may be able to get live assistance. Other recommended reading:
_Your_Own_Remix_with_Fedora
man lorax
man livemedia-creator
The working kickstart file you would get started from is fedora-live-workstation.ks, if you want to start with the default GNOME environment. This may or may not work for you. It is still working for me.
To quote the livemedia-creator manpage
The general idea is to use qemu with kickstart and an Anaconda boot.iso to install into a disk image and then use the disk image to create the bootable media.
How can I know or check that a package or several packages from a kickstart file is/are deprecated for a specific fedora release. Is there a command line able to emulate the results found in: python-nineml Package Info koji
And the lack of updates is the main problem for me, even for the mainstream releases like Live Workstation. It seems - while I browsed through koji.fedoraproject.org - there are for upcoming Fedora 34 , a flatten kickstart file and build logs.
Yay, that makes sense. The spare space of my internal disc is rather small, only about 35gb or so. So maybe if I run timeshift using the original system, the spare space is barely enough for the copy operation. However, the livecd system occupies extra spaces in the internal disc (I guess), the remain spare space is not enough.
After flirting with linux for years, I finally switched and have been happily using Solus for about 6 months. With the windows 7 eos coming, I wanted to install Solus on my wifes desktop and moms laptop but I`ve had the same problem on both machines.
The livecd boots and the desktop loads up but almost nothing runs. I can connect the wifi and open budgie desktop settings but firefox, the file manager and install OS just give a flashing, busy icon which times out.
Its a shame as I think Solus would have been nice for them to use but Ive put Linux Mint on their machines now as I needed to get them running without losing their PCs for too long. Just wanted to give a heads up in case there`s an issue with the current livecd as my install went fine a few months ago and it seemed unusual to me to have the same issue on 2 very different PCs.
wildsnail73 Just wanted to give a heads up in case there`s an issue with the current livecd as my install went fine a few months ago and it seemed unusual to me to have the same issue on 2 very different PCs.
wildsnail73 I'd try with dd instead of Etcher and also verifying the sha256sum of your ISO and the ones listed in our "File" links for SHA256SUM on our Download page match (use the one for the edition you downloaded, you'll download a file, open it in a text editor and the sha256sum is the first part of the line).
Format your USB drive in FAT32 type by system command or third-part tools.
For USB drive with large capacity, maybe there is no FAT32 option when you format it in Windows. You can create a small partition by diskpart (e.g. 4GB) and format the small partition with FAT32 filesystem.
Ventoy LiveCDfor example ventoy-1.0.20-livecd.iso has only an EFI directory in it. Get the EFI directory and copy it to the root of the FAT32 partition above.5.3 Reboot your computer, and select USB boot option in UEFI modeRestart your computer (better to cold restart), change the BIOS mode to UEFI and boot the USB drive. Finally enter the LiveCD OS and then follow the prompts at the end of this article.
Note that when selecting the last step, make sure that the USB drive corresponds to PhysicalDrive0 or PhysicalDrive1 or other. This is very important. There are two ways for you to use to confirm: