fw_update is being replaced with a new program, and this is being tested in snapshots to ensure we have coverage all all circumstances.
The new program is capable of updating firmwares while in the bsd.rd install/upgrade phase. This means some firmwares (specially *drm firmwares) will get updated then, rather than after the reboot. This means noone needs a 2nd reboot to activate those firmwares. Some behaviours of the existing program may not survive, and others may get changes. It isn't finished yet, when it is, then documentation will be updated. Alexander <xan....@posteo.org> wrote: > Hi all, > > I just wanted to check for new firmware versions: > > $ fw_update -n > fw_update: unknown option -- -n > usage: fw_update [-d | -D] [-av] [-p path] [driver | file ...] > > This used to work and is still documented like this in > > $ man 8 fw_update > [...] > -n Dry run. Do not actually install or update any firmware > and whether it appears to be required by a driver. > [...] > (also https://man.openbsd.org/fw_update) > > But /usr/sbin/fw_update does not contain this option anymore and > consequently produces the error above. > This mismatch puzzles me a bit and I'm even more confused when looking > at https://cvsweb.openbsd.org/src/usr.sbin/fw_update/ which has been in > the attic for the last 6 years. > > I'm guessing I'm just uninformed and don't understand CVSweb but I'd > like to learn, so: > Is the documentation for fw_update outdated? > Where do I actually find the version history of the fw_update that is > installed on my system in CVSweb? > > My system: > $ head -1 /etc/motd > OpenBSD 7.0-current (GENERIC.MP) #200: Fri Dec 24 22:15:01 MST 2021 > > Thanks in advance. > > Best regards, > Alexander >
