You are not logged in.
TPOWA; i am trying to make new archboot iso's but when i do (as per archboot wiki) "systemd-nspawn --capability=CAP_MKNOD --register=no -M $(uname -m) -D x86_64_chroot" , i get the error : "Invalid machine name: x86_64"
Uname -a gives me : Linux pomme 5.0.7-arch1-1-ARCH #1 SMP PREEMPT Mon Apr 8 10:37:08 UTC 2019 x86_64 GNU/Linux
What is going on ?
Offline
Same question as about a year ago: Is there still some life in the project? The silence starts to become deafening.
Offline
Same question as about a year ago: Is there still some life in the project? The silence starts to become deafening.
Well, I suggest you check out this list of packages sorted by update date - the packages are still being maintained, with a kernel update today, for example. Yes, updates to the installer might be nice, and the no-updates-on-the-front-page thing might make some people worry, but as far as I can tell, everything is great behind the scenes, at least in terms of packages.
Offline
TPOWA; i am trying to make new archboot iso's but when i do (as per archboot wiki) "systemd-nspawn --capability=CAP_MKNOD --register=no -M $(uname -m) -D x86_64_chroot" , i get the error : "Invalid machine name: x86_64"
Uname -a gives me : Linux pomme 5.0.7-arch1-1-ARCH #1 SMP PREEMPT Mon Apr 8 10:37:08 UTC 2019 x86_64 GNU/LinuxWhat is going on ?
This is a bug in systemd #11765 machinectl saying "Invalid machine name" with underscores
replacing $(unman -m) with a name works
$ systemd-nspawn --capability=CAP_MKNOD --register=no -M archboot -D x86_64_chroot
Offline
Thank you for your help Da!vid.
Now the next problem:when I generate the images as per wiki, where are they placed?
Can't find any .iso or.img.
They are generated:when I do "archboot-x86_64-iso.sh, both -t and -g the whole process passes in the console, but I do not find any iso or image.
Or are there other steps to do?
Offline
To overand, I ment the disk.:D
Offline
Quite a year, I wonder if the last install still work
Well, I suppose that this is somekind of signature, no?
Offline
Here we go again, new ISO released. Reflects all recent changes to [core] repository.
Network installation routine is now stripped down to minimum boot requirements.
Have fun.
greetings
tpowa
Offline
Thank you very much Tpowa. Big elbow (no hugs!)
Offline
ArchBoot saved my tablet! Many thanks to those involved!
I bought the tablet specifically for Arch Linux, but when I received it I found that the tablet has UEFI 32Bits and 64Bits processor.
This way with ArchBoot I started normally and then gave alt + F2 and performed the installation normally as in the traditional ISO.
Offline
Hey folks,
lots of git commits happened on archboot, so time to get a new release out soon. Are there still fans out there?
Stay tuned.
greetings
tpowa
Offline
Hi folks,
new images are syncing to the servers: 2021.09
Have fun.
greetings
tpowa
Offline
Hi folks:
https://wiki.archlinux.org/title/Archboot
has been updated to reflect all changes done last week.
Have fun.
greetings
tpowa
Last edited by tpowa (2021-09-13 07:53:27)
Offline
Again, lots of things added:
- now you can install any package with pacman -S
- https://wiki.archlinux.org/title/Archbo … mage_files
Now you can update the image yourself, whenever you want from inside archboot.
Have fun.
greetings
tpowa
Offline
Latest changes:
- reordered setup steps
- added option in setup for updating the environment and caching packages for installation.
- added possibilty to activate testing repository for new archboot environment
- updated quickinst to use the local mirror by default.
Have fun,
greetings
tpowa
Offline
Latest changes:
- updated wiki to reflect latest changes
- more RAM optimisation
- introducing a small iso file called "latest", which will build the environment from scratch on boot up.
Have fun
greetings
tpowa
Offline
Latest changes:
- Release schedule added: new files will appear on 10th, 20th and 30th of a month
- PGP verification added to the wiki and mirrors
- added amdgpu for kms
Have fun
greetings
tpowa
Offline
It's been several years since I used archboot, but I do remember it fondly .
Soon (I keep delaying it) I'll install arch on my new laptop and will try encryption for the first time.
I'm considering "System encryption - whole hard drive except /boot partition" and intend to use archboot to do the install.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Latest Changes for tomorrow iso files:
- Finally full Secure Boot support has been added
- secureboot-keys.sh script added for keys generation
- added tools for key management to the environment
Have fun,
greetings
tpowa
Last edited by tpowa (2021-10-19 15:41:32)
Offline
Latest changes for today's image files 20211120:
- switched to use ntfs3 instead of ntfs-3g in setup script
Have fun,
greetings
tpowa
Last edited by tpowa (2021-11-20 07:23:38)
Offline
Latest changes for today's image files 20211201:
- added latest changes from mkinitcpio-31
- added compressed firmware and compressed kernel modules
- updated RAM requirements on wiki and on screen messages, depending on which action RAM usage dropped by 600 MB
Have fun,
greetings
tpowa
Last edited by tpowa (2021-12-01 06:08:52)
Offline
Latest changes for today 20211210:
- corrected firmware files
- increases size of images and RAM usage
Thanks for reporting the broken firmware Mr. Green
Have fun,
greetings
tpowa
Offline
You are very welcome ;-)
Mr Green
Offline
Hi,
big update for 2022.01 files:
- shrunk the ISO size by half due to changing the efi image file
- added aarch64 architecure support (running now on Mac M1 paralles desktop virtualization software)
https://archlinuxarm.org/forum/viewtopi … =8&t=15777
Have fun.
greetings
tpowa
Offline
I'm having trouble getting archboot working in rescue mode (kernel + initrd) using systemd-boot. I get an "Unsupported" message. I have the same issue with:
$ qemu-system-x86_64 --kernel vmlinuz --initrd initramfs.img
qemu: linux kernel too old to load a ram disk
I notice also that "file" cannot identify the type of the kernel file at all.
Does this mean that I need to do something clever to boot these, such as chainload the kernel as an efi image or something?
Many thanks for any help.
Offline