Fri, 13 Jan 2017 20:17:57 +0100 Sebastien Marie
> On Fri, Jan 13, 2017 at 11:14:16AM -0700, Theo de Raadt wrote:
> >
> > I would be very surprised to hear that people are using
> > vnconfig+mount+vnconfig+mount, to add such a file.
Hi Sebastien, Robert, Theo, Theo, everyone,
On Fri, 13 Jan 2017 12:01:36 -0700
"Theo de Raadt" wrote:
> [...]
>
> That is yet another example of interactive use, of an installer
> feature designed for NON-INTERACTIVE USE.
>
> I feel like we're being pushed to support a set of use cases which
> are not core
On Fri, 13 Jan 2017 18:06:35 +
Robert Peichaer wrote:
> On Fri, Jan 13, 2017 at 06:20:25AM -0600, Ed Ahlsen-Girard wrote:
> [...]
>
> The installer looks at the filesystem provided by bsd.rd itself, not
> the filesystem on disk.
>
Thanks.
--
Edward Ahlsen-Girard
On Fri, Jan 13, 2017 at 07:21:12PM GMT, Theo de Raadt wrote:
> > Given that there is no official supported way to put an
> > auto_upgrade.conf onto an existing bsd.rd, what would be a suggested
> > way to achieve the same end result - in this case, an automated
> > non-interactive, off-line
> Given that there is no official supported way to put an
> auto_upgrade.conf onto an existing bsd.rd, what would be a suggested
> way to achieve the same end result - in this case, an automated
> non-interactive, off-line upgrade?
Hack up a solution however you like.
But understand it isn't
On Fri, Jan 13, 2017 at 11:14:16AM -0700, Theo de Raadt wrote:
>
> I would be very surprised to hear that people are using
> vnconfig+mount+vnconfig+mount, to add such a file.
I am still using this (unsupported) method for auto_upgrading all
openbsd hosts I administrate. As all are running
On Fri, Jan 13, 2017 at 06:14:16PM GMT, Theo de Raadt wrote:
> > On Fri, Jan 13, 2017 at 06:20:25AM -0600, Ed Ahlsen-Girard wrote:
> > > The man page seems to indicate that autoinstall will work with an
> > > auto_upgrade.conf file on the local machine, but specifying the path as:
> > >
> > >
> On my actual disk at / I have auto_upgrade.conf and when I start the
> upgrade process at boot, I press s.
> This will allow me to mount /dev/wd0a mnt; cp mnt/auto_upgrade .; autoinstall
That is yet another example of interactive use, of an installer
feature designed for NON-INTERACTIVE USE.
I
> The original idea of this was to allow ...
>
>Welcome to the OpenBSD/amd64 6.0 installation program.
>(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
># cat <<_EOF >/auto_install.conf
>> system hostname = hostA
>> password for root = whateversecurepassword
>> http
On 13 January 2017 at 04:20, Ed Ahlsen-Girard wrote:
> The man page seems to indicate that autoinstall will work with an
> auto_upgrade.conf file on the local machine, but specifying the path as:
>
> /auto_upgrade.conf
> or
> file://auto_upgrade.conf
> or
>
On Fri, Jan 13, 2017 at 11:14:16AM -0700, Theo de Raadt wrote:
> > On Fri, Jan 13, 2017 at 06:20:25AM -0600, Ed Ahlsen-Girard wrote:
> > > The man page seems to indicate that autoinstall will work with an
> > > auto_upgrade.conf file on the local machine, but specifying the path as:
> > >
> > >
> On Fri, Jan 13, 2017 at 06:20:25AM -0600, Ed Ahlsen-Girard wrote:
> > The man page seems to indicate that autoinstall will work with an
> > auto_upgrade.conf file on the local machine, but specifying the path as:
> >
> > /auto_upgrade.conf
> > or
> > file://auto_upgrade.conf
> > or
> >
On Fri, Jan 13, 2017 at 06:20:25AM -0600, Ed Ahlsen-Girard wrote:
> The man page seems to indicate that autoinstall will work with an
> auto_upgrade.conf file on the local machine, but specifying the path as:
>
> /auto_upgrade.conf
> or
> file://auto_upgrade.conf
> or
> file:auto_upgrade.conf
On Fri, Jan 13, 2017 at 06:20:25AM -0600, Ed Ahlsen-Girard wrote:
> The man page seems to indicate that autoinstall will work with an
> auto_upgrade.conf file on the local machine, but specifying the path as:
>
> /auto_upgrade.conf
> or
> file://auto_upgrade.conf
> or
> file:auto_upgrade.conf
The man page seems to indicate that autoinstall will work with an
auto_upgrade.conf file on the local machine, but specifying the path as:
/auto_upgrade.conf
or
file://auto_upgrade.conf
or
file:auto_upgrade.conf
do not work.
Is this still a "watch this space!" feature?
--
Edward
15 matches
Mail list logo