BTW I had to use UNetBootin to write the ISO to my USB stick, I used dd originally but then I could not even boot it in UEFI mode.
]]>Somehow I slept through time (a long time I did not have to reinstall) - procedures have changed since 2010/2011. Thanks!!
]]>I believe the way I have set it up is the best way. It works with my gimped EFI although I hear it may require a bit of tweaking with some EFIs since some will only exectue programs that end in .efi. Because of this I would suggest that Arch add .efi to the kernel name. Its not like the name matters to traditional bootloaders. From what i have read efibootmgr is striaght out as a standard since it borks some macs. Antying that boots off of something other then ESP:EFI/Boot/bootx64.efi is out thanks to gigabyte boards. That leaves our options for a sane default limited. I only have my stystem to test on. If others can test my layout to ensure that it works on all systems it seems like the most KISS option availaible.
]]>acvar, keshav knows uefi best, KISS is good but it seems it's not as easy.
The recommended setup is having UEFISYS separate from /boot. Archboot will not allow same partition as both as supporting all the possible user requirements is beyond the scope of the installer.
New release will show up soon, so if anything is needed for new release please tell it us now.
Highlight of upcoming release:
-systemd support
-signed packages support
I don't think its a good idea to release a new iso. Let the changes in [core] repo and "base" group and all the rebuilds be finalized first. I have not tries netinstall with the 2012.04-2 iso, but if it works the setup script in the iso, no need to release one now.
]]>New release will show up soon, so if anything is needed for new release please tell it us now.
Highlight of upcoming release:
-systemd support
-signed packages support
Is there a good reason that we can not just set our ESP to mount at /boot. Keep our kernel and initrds in the place they currently reside. Place refind in /boot/efi/boot/ and put an entry in refind.conf to boot the kernel and initrd from thier normal locations? This would remove the need to copy./move kernels and initrds, and would keep everything very similar to the current setup. This is how I set up my new system and it seems to be working just fine.
Having /boot separate from uefisys allows you to use a *nix filesystem for /boot rather than fat32/vfat , since vfat does not allow many things like symlinks, unix permissions etc. and e don't know when such filesystem features might be required for files in /boot .
Archboot does not support a common /boot and uefisys . During install just install refind to /boot/efi, and then copy the files back to /boot .
]]>EDIT:
what about the udev -> systemd-tools change by uptream?
an finaly any chancee for systemd configs files if systemd are installed, since now systemd are in core
the.ridikulus.rat wrote:If you are using systemd, you can try https://wiki.archlinux.org/index.php/UE … ng_Systemd .
I tried systemd as you suggested but it seems awfully convoluted (until it becomes the Arch standard at any rate) so I'm currently using incron.
Nice. Didn't know about this one. Anyway for me systemd is working fine. Please add incron related info to https://wiki.archlinux.org/index.php/UEFI_Bootloaders .
]]>If you are using systemd, you can try https://wiki.archlinux.org/index.php/UE … ng_Systemd .
I tried systemd as you suggested but it seems awfully convoluted (until it becomes the Arch standard at any rate) so I'm currently using incron.
]]>