From Newsgroup: muc.lists.freebsd.stable
--=-8ADb99SqJX7eFMdNINO7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi,the only 'workaround' I know is this:# yes | env PAGER=3Dcat freebsd-upd= ate fetch --not-running-from-cron# yes | env PAGER=3Dcat freebs= d-update install --not-running-from-cronRegards,vermadenTemat: Non-interact= ive run of `freebsd-update upgrade` possible?Data: 2025-07-31 13:10Nadawca:=
"Patrick M. Hausen" <
hausen@punkt.de>Adresat: "Freebsd Stable" <f=
reebsd-stable@freebsd.org>; > Hi all,
>=20
> It's time to upgrade our ~100 hosts - again - and I would really
> like to at least partly automate the procedure.
>=20
> Current issue is that this sequence:
>=20
> freebsd-update upgrade -r 14.3 -b /tmp/be_mount.EkJx
> freebsd-update install -b /tmp/be_mount.EkJx
> freebsd-update install -b /tmp/be_mount.EkJx
>=20
> in my experience insists on asking "Does this look reasonable? (y/n)"
> interactively.
>=20
> And no version of
>=20
> export ASSUME_ALWAYS_YES=3Dyes
>=20
> or
>=20
> --not-running-from-cron
>=20
> seems to change that.
>=20
> Am I missing anything? I mean, after updating a handful of test
> systems - and especially when upgrading into a new BE -
> it should be possible to just rollout the new release via Ansible.
>=20
> Thanks and kind regards,
> Patrick
> --=20
> punkt.de GmbH
> Patrick M. Hausen
> .infrastructure
>=20
> Sophienstr. 187
> 76185 Karlsruhe
>=20
> Tel. +49 721 9109500
>=20
>
https://infrastructure.punkt.de
>
info@punkt.de
>=20
> AG Mannheim 108285
> Gesch=C3=A4ftsf=C3=BChrer: Daniel Lienert, Fabian Stein
>=20
>=20=
--=-8ADb99SqJX7eFMdNINO7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "
http://www.w= 3.org/TR/REC-html40/loose.dtd">
<html><body><div data-select-link-text=3D"1">Hi,<br><br>the only 'workaroun=
d' I know is this:<br><br><span style=3D"font-family: courier new, courier;=
" data-mce-style=3D"font-family: courier new, courier;"># yes | env PAGER= =3Dcat freebsd-update fetch=C2=A0 =C2=A0--not-running-from-cron</span><br><= br><span style=3D"font-family: courier new, courier;" data-mce-style=3D"fon= t-family: courier new, courier;"># yes | env PAGER=3Dcat freebsd-update ins= tall --not-running-from-cron</span><br><br><br><br><br>Regards,<br>vermaden= <br><br><br><br><div class=3D"inpl-collapsed">Temat: Non-interactive run of=
`freebsd-update upgrade` possible?<br>Data: 2025-07-31 13:10<br>Nadawca: "= Patrick M. Hausen" <
hausen@punkt.de><br>Adresat: "Freebsd Stable" <= ;
freebsd-stable@freebsd.org>; <br><br><blockquote style=3D"margin: 0; pa= dding-left: 1ex; border-left: 1px solid#CCC;" data-mce-style=3D"margin: 0; = padding-left: 1ex; border-left: 1px solid#CCC;"><pre>> Hi all,
>=20
> It's time to upgrade our ~100 hosts - again - and I would really
> like to at least partly automate the procedure.
>=20
> Current issue is that this sequence:
>=20
> freebsd-update upgrade -r 14.3 -b /tmp/be_mount.EkJx
> freebsd-update install -b /tmp/be_mount.EkJx
> freebsd-update install -b /tmp/be_mount.EkJx
>=20
> in my experience insists on asking "Does this look reasonable? (y/n)"
> interactively.
>=20
> And no version of
>=20
> export ASSUME_ALWAYS_YES=3Dyes
>=20
> or
>=20
> --not-running-from-cron
>=20
> seems to change that.
>=20
> Am I missing anything? I mean, after updating a handful of test
> systems - and especially when upgrading into a new BE -
> it should be possible to just rollout the new release via Ansible.
>=20
> Thanks and kind regards,
> Patrick
> --=20
> punkt.de GmbH
> Patrick M. Hausen
> .infrastructure
>=20
> Sophienstr. 187
> 76185 Karlsruhe
>=20
> Tel. +49 721 9109500
>=20
>
https://infrastructure.punkt.de
>
info@punkt.de
>=20
> AG Mannheim 108285
> Gesch=C3=A4ftsf=C3=BChrer: Daniel Lienert, Fabian Stein
>=20
> </pre><br></blockquote><br><br></div></div><style type=3D"text/css">#i= cselection13 {width: 100% !important; height: 100% !important; padding-top:=
0px !important; overflow: visible !important;}</style><style type=3D"text/= css">#icselection13 {width: 100% !important; height: 100% !important; paddi= ng-top: 0px !important; overflow: visible !important;}</style><style type= =3D"text/css">#icselection13 {width: 100% !important; height: 100% !importa= nt; padding-top: 0px !important; overflow: visible !important;}</style><sty=
le type=3D"text/css">#icselection13 {width: 100% !important; height: 100% != important; padding-top: 0px !important; overflow: visible !important;}</sty= le><style type=3D"text/css">#icselection13 {width: 100% !important; height:=
100% !important; padding-top: 0px !important; overflow: visible !important= ;}</style><style type=3D"text/css">#icselection13 {width: 100% !important; = height: 100% !important; padding-top: 0px !important; overflow: visible !im= portant;}</style><style type=3D"text/css">#icselection13 {width: 100% !impo= rtant; height: 100% !important; padding-top: 0px !important; overflow: visi= ble !important;}</style></body></html>
--=-8ADb99SqJX7eFMdNINO7--
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to
news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2