Hi,
this doesn't seem to be a trivial task as the state of the boot medium
prior to the fai installation as well as the UEFI settings for the
single network interface both can have all kinds of states, e.g.:
(of course for production I'd disable unneeded UEFI setting, in my case
all IPv6 and
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die
eigentliche Nachricht steht dadurch in einem Anhang.
This message was wrapped to be DMARC compliant. The actual message
text is therefore in an attachment.--- Begin Message ---
Hi Thomas,
> I wonder why the second machine has tw
Hi,
I found this code that move the first boot entry (which is expected to
be the new entry after an installation) to the end of the boot list.
https://community.theforeman.org/t/efi-boot-order-with-centos-7-network-boot-vs-local-boot/10529/2
# the EFI boot manager is only installed on UEFI host
Oh, you can set an efi boot entry inactive using -A
Maybe this helps changing the boot device, without changing the
overall boot order.
--
regards Thomas
Hi
for one-time changes in the boot order, you can use
efibootmgr --bootnext
and set this to the network device. From man efibootmgr:
BootNext - the boot entry which is scheduled to be run on next
boot. This supercedes BootOrder for one boot only, and is
deleted by the boot
Hi all,
I'm wondering whether this issue concerning bad/wrong UEFI boot order
after a fai installation already was resolved in the meantime (since
September, 2021)?
https://lists.uni-koeln.de/pipermail/linux-fai/2021-September/012770.html
The idea was to e.g. add a few lines in
config/scr
Seasons greeting to everyone,
there's something that didn't let me rest since I discovered it.
A while back I had suggested to restore the UEFI BootOrder that was in effect
before GRUB-EFI was installed:
On Fri, 2021-09-17 at 11:24:52 +0200, Thomas Lange wrote:
> > On Fri, 17 Sep 2021 11:06:3
> On Fri, 17 Sep 2021 11:06:30 +0200, Steffen Grunewald
> said:
> That would either involve additions to GRUB_EFI/10-setup itself, or two
> extra scripts 09-x and 11-x which would have to communicate e.g. via
> ${LOGDIR}/bootorder ...
> I can imagine using an extra class,
On Mon, 2021-02-08 at 12:31:22 -0600, John G Heim wrote:
> In these days when so many of us are working from home, I thought I'd give a
> tip I discovered today on how to trigger an FAI install remotely.
>
> For years I've been triggering an FAI install remotely by wiping the hard
> drive and hopi
Systemd is pretty good at this.
Get FAI to install a unit file to run your thing, and add a unit option
like ConditionPathExists=/foo/bar or ConditionPathExists=!/foo/bar
Then make your thing touch or delete a flag file [ /foo/bar ] if
successfully run.
There you have it, a service/script that onl
Well, it's not really to the point. Maybe my example was bad but there
are lots of other reasons one might want to run a script after the
install is finished. Actually, the reason this came up is that I want
the linux cli screen reader to run on the first boot and then get
disabled. But I just
You can configure the nfsroot with your ldap configs so you can have them
available during fai. I used this (at another UW department) for rescue
consoles to support natural logins from admins.
As far as the sudo config, why not just copy a sudoers (.d) snippet down
that references the user during
Hi John,
if you are using LDAP - why not permitting a LDAP group (which already
exists during install) and then configure sudo via LDAP?
Thats how I solved it for my soho environment.
See: https://www.sudo.ws/man/1.8.17/sudoers.ldap.man.html
Kind Regards
Martin
On Wed, Jan 9, 2019, 22:06 John
Thanks, good to know.
btw, I use the following POSIX shell function (IPv4, or course):
ip2hex () { printf "%.2X%.2X%.2X%.2X\n" $( echo ${1:-$(hostname -i)} |
tr '.' ' ') ;}
ip2hex w/o argument gets you the current machine's hex format IP, 'ip2hex
IPADDR' converts an ipaddress to hex format
14 matches
Mail list logo
