Re: Autoinstall + FDE

[Stuart Henderson]

On 2023-09-14, prodejna-radian...@icloud.com  
wrote:
> I was able to auto-install OpenBSD/amd64 except full disk encryption
> (FDE). Is FDE supported in autoinstall?

No, it is not.



-- 
Please keep replies on the mailing list.

Re: autoinstall behavior on the nameservers has changed in OpenBSD 7.2

[Stuart Henderson]

z man*.tgz 
> site*.tgz
>  24HTTP proxy URL = none
>  25HTTP Server = update.example.net
>  26Server directory = OpenBSD/7.2/amd64
>  27Set name(s) = done
>  28Location of sets = done
>  29What timezone are you in = UTC
>  30Exit to (S)hell, (H)alt or (R)eboot = S
>
> Thanks,
>
> Frederik
>
>
>> Betreff: Re: autoinstall behavior on the nameservers has changed in
>> OpenBSD 7.2
>> Datum: Thu, 3 Nov 2022 10:45:54 - (UTC)
>> Von: Stuart Henderson 
>> An: misc@openbsd.org
>> 
>> On 2022-11-02, Frederik Konietzny  wrote:
>>> Hi,
>>>
>>> for our OpenBSD PXE/autoinstall environment we are using a IPv4 PXE
>>> server and a OpenBSD mirror with IPv6 address. Since OpenBSD 7.2 we have
>>> an issue with the nameservers during the autoinstall process. (OpenBSD
>>> 6.9, 7.0 and 7.1 work fine)
>>>
>>> If we start a VM to install OpenBSD 7.2 via PXE it gets an IPv4 address
>>> via dhcp, loads the ramdisk bsd.rd and loads the install.conf file
>>> successfully. Than it loads the install.conf file, where we define a
>>> IPv6 IP, IPv6 Route and IPv6 nameserver server:
>>>
>>> Choose your keyboard layout = de
>>> System hostname = test-openbsd-autoinst
>>> Which network interface do you wish to configure = vio0
>>> IPv4 address for vio0 = none
>> 
>> interesting, so you tell it not to use v4 here, but...
>> 
>>> nameserver yy.yy.yy.1 # resolvd: vio0
>>> nameserver yy.yy.yy.2 # resolvd: vio0
>> 
>> can you show more (ideally all) of the log?
>> 
>> 
>


-- 
Please keep replies on the mailing list.

Re: autoinstall behavior on the nameservers has changed in OpenBSD 7.2

[Frederik Konietzny]

Hi Stuart,

thank you for looking at the topic.

Here is the boot log, and the install.conf.

In the log, line 19, IPv4 nameservers are used,
but we define in the install.conf line 12 a IPv6 nameserver.

This IPv6 nameserver is ignored and will not be added to /etc/resolv.conf


### install log

 1  (I)nstall, (U)pgrade, (A)utoinstall or (S)hell?
 2  Could not determine auto mode.
 3  Response file location? [http://xxx.xxx.xxx.1/install.conf]
 4  Fetching http://xxx.xxx.xxx.1/install.conf
 5  Performing non-interactive install...
 6  Terminal type? [vt220] vt220
 7  System hostname? (short form, e.g. 'foo') test-openbsd-autoinst
 8  
 9  Available network interfaces are: vio0 vlan0.
10	Which network interface do you wish to configure? (or 'done') 
[vio0] vio0

11  IPv4 address for vio0? (or 'autoconf' or 'none') [autoconf] none
12	IPv6 address for vio0? (or 'autoconf' or 'none') [none] 
yyy.yyy.yyy:2830:1::aa

13  IPv6 prefix length for vio0? [64] 64
14  Available network interfaces are: vio0 vlan0.
15	Which network interface do you wish to configure? (or 'done') 
[done] done

16  IPv6 default router? yyy.yyy.yyy:2830::1
17  add net default: gateway yyy.yyy.yyy:2830::1
18  DNS domain name? (e.g. 'example.com') [my.domain] example.com
19  Using DNS nameservers at xx.xx.xx.1 xx.xx.xx.2
20  
21  Password for root account? 
22  Public ssh key for root account? [none] none
23  Start sshd(8) by default? [yes] yes
24  Do you expect to run the X Window System? [yes] no
25  Change the default console to com0? [yes] yes
26  Available speeds are: 9600 19200 38400 57600 115200.
27  Which speed should com0 use? (or 'done') [115200] 115200
28  Setup a user? (enter a lower-case loginname, or 'no') [no] no
29  Since no user was setup, root logins via sshd(8) might be useful.
30	WARNING: root is targeted by password guessing attacks, pubkeys 
are safer.

31  Allow root ssh login? (yes, no, prohibit-password) [no] yes


### resolv.conf

# cat /etc/resolv.conf
nameserver yy.yy.yy.1 # resolvd: vio0
nameserver yy.yy.yy.2 # resolvd: vio0
lookup file bind

### install.conf

 1# Under CM control, do not edit this file
 2Choose your keyboard layout = de
 3System hostname = test-openbsd-autoinst
 4Which network interface do you wish to configure = vio0
 5IPv4 address for vio0 = autoconf
 6IPv6 address for vio0 = :xxx:xxx:2830:1::aa
 7IPv6 prefix length for vio0 = 64
 8Which network interface do you wish to configure = done
 9Default IPv4 route = none
10IPv6 default router = :xxx:xxx:2830::1
11DNS domain name = example.net
12DNS nameservers = :xxx:xxx:2830::10
13Start sshd(8) by default = yes
14Do you expect to run the X Window System = no
15Setup a user = no
16Allow root ssh login = yes
17Password for root account = 
18Which disk is the root disk = sd0
19Use (W)hole disk MBR, whole disk (G)PT, (O)penBSD area or 
(E)dit = W
20Use (A)uto layout, (E)dit auto layout, or create (C)ustom 
layout = A
21URL to autopartitioning template for disklabel = 
http://[:xxx:xxx:2830::70]/autodisklabel

22Location of sets = https
23Set name(s) = -all bsd bsd.rd comp*.tgz base*.tgz man*.tgz 
site*.tgz

24HTTP proxy URL = none
25HTTP Server = update.example.net
26Server directory = OpenBSD/7.2/amd64
27Set name(s) = done
28Location of sets = done
29What timezone are you in = UTC
30Exit to (S)hell, (H)alt or (R)eboot = S

Thanks,

Frederik



Betreff: Re: autoinstall behavior on the nameservers has changed in
OpenBSD 7.2
Datum: Thu, 3 Nov 2022 10:45:54 - (UTC)
Von: Stuart Henderson 
An: misc@openbsd.org

On 2022-11-02, Frederik Konietzny  wrote:

Hi,

for our OpenBSD PXE/autoinstall environment we are using a IPv4 PXE
server and a OpenBSD mirror with IPv6 address. Since OpenBSD 7.2 we have
an issue with the nameservers during the autoinstall process. (OpenBSD
6.9, 7.0 and 7.1 work fine)

If we start a VM to install OpenBSD 7.2 via PXE it gets an IPv4 address
via dhcp, loads the ramdisk bsd.rd and loads the install.conf file
successfully. Than it loads the install.conf file, where we define a
IPv6 IP, IPv6 Route and IPv6 nameserver server:

Choose your keyboard layout = de
System hostname = test-openbsd-autoinst
Which network interface do you wish to configure = vio0
IPv4 address for vio0 = none


interesting, so you tell it not to use v4 here, but...


nameserver yy.yy.yy.1 # resolvd: vio0
nameserver yy.yy.yy.2 # resolvd: vio0


can you show more (ideally all) of the log?




--
Frederik Konietzny (Team ITS)
Phone:+49 40 808077-726 Fax:+49 40 808077556 Mail:koniet...@dfn-cert.de

DFN-CERT Services GmbH, https://www.dfn-cert.de/, Phone  +49 40 808077-555
Sitz / Register

Re: autoinstall behavior on the nameservers has changed in OpenBSD 7.2

[Stuart Henderson]

On 2022-11-02, Frederik Konietzny  wrote:
> Hi,
>
> for our OpenBSD PXE/autoinstall environment we are using a IPv4 PXE 
> server and a OpenBSD mirror with IPv6 address. Since OpenBSD 7.2 we have 
> an issue with the nameservers during the autoinstall process. (OpenBSD 
> 6.9, 7.0 and 7.1 work fine)
>
> If we start a VM to install OpenBSD 7.2 via PXE it gets an IPv4 address 
> via dhcp, loads the ramdisk bsd.rd and loads the install.conf file 
> successfully. Than it loads the install.conf file, where we define a 
> IPv6 IP, IPv6 Route and IPv6 nameserver server:
>
> Choose your keyboard layout = de
> System hostname = test-openbsd-autoinst
> Which network interface do you wish to configure = vio0
> IPv4 address for vio0 = none

interesting, so you tell it not to use v4 here, but...

> nameserver yy.yy.yy.1 # resolvd: vio0
> nameserver yy.yy.yy.2 # resolvd: vio0

can you show more (ideally all) of the log?

Re: autoinstall with local file

[lists]

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,

Absolutely correct, this had been known to me by reading the previous
discussions and following up logic, but, further overruled for my own
use as inconvenient enough, to make me defer scripting around it yet.
It would be a non canonical option, to the delegation of reliability.

> I am still using this (unsupported) method for auto_upgrading all
> openbsd hosts I administrate. As all are running -current, it means I
> use it very regulary.

I would have too if no automatic option is available to address this.
I am also always running current snapshots repeatedly upgrading, it's
totally the best way to optimise scarce resources, and keep updating.
Infrastructure here depends on auto-upgrading snapshots & I heart it.

For all but one machines I'm auto-upgrading by network boot over DHCP
(and gPXE for the 20 year old machines), it is incredibly convenient!
Per network and location, there is always at least one which can not.

For the machine that provides network booting for others, I have been
doing upgrades interactively manually over the serial line to the BMC
and despite it being slightly inconvenient, I'll hope for automation.
I can absolutely not netboot an edge network / bootstrap machine yet.

> autoinstall is a great possibility. But depending the network
> environnement, it could be not possible to netboot, and so to trigger
> autoinstall not-interactively. Fetching file using DHCP options isn't
> the hard part in my context: I would have only one host without control
> of the network.
> 
> but I didn't ask for making it a "supported" method. I know I use only a
> trick.

I also see the auto-install / auto-upgrade as a cool solution to this.

I have two very significant to me use cases, the small personal / work
networks many of us have at least one, others a few..  and the servers
in the data centre that still lack reliably secured access to the BMC.

On own infrastructure with physical access it's easy.  Leasing servers
in the data centre, where physical access is not really available.. it
is difficult to auto-upgrade safe without incurring unjustified costs.
Or increasing the risks just when the hacked up trick reaches an edge.

I am kindly asking for an automation method to the installer for which
I'll always be thankful to everyone reading and considering this plea.
It would be wonderful to use auto-upgrade non-interactively: automated
in place upgrades for the machine that provides netboot to the others.

Thank you for explaining these points again in this thread and for the
opportunity to enjoy self supporting our networked operations further.

Looking forward to non-interactive capable local auto-install/upgrade.

Kind regards,
Anton

Re: autoinstall with local file

[Ed Ahlsen-Girard]

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 functionality.
> 
> The installer will keep improving in various ways, but these narrow
> use cases will be first up against the wall (due to being ignored
> during development, they'll be fragile due to subtle changes).
> 
> It's a complicated shell script.  It doesn't deliver pizza, either.
>  

That's fine, I misunderstood, and I am not pushing for an extension. At
all.

-- 

Edward Ahlsen-Girard
Ft Walton Beach, FL

Re: autoinstall with local file

[Ed Ahlsen-Girard]

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
Ft Walton Beach, FL

Re: autoinstall with local file

[Raf Czlonka]

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 upgrade?
> 
> Hack up a solution however you like.
> 
> But understand it isn't within our mandate to keep your hack working.

Sure, I understand that.

> So basically, it will break because it is relying on behaviours which
> are not a mainline requirement.

Yes, I'm prepared to deal with it.

> It will break, like it just did.
> 

Oh, no - it works absolutely fine, had been since day one.
I'm must've not been very clear, sorry.

Cheers,

Raf

Re: autoinstall with local file

[Theo de Raadt]

> 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 within our mandate to keep your hack working.

So basically, it will break because it is relying on behaviours which
are not a mainline requirement.

It will break, like it just did.

Re: autoinstall with local file

[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.

I am still using this (unsupported) method for auto_upgrading all
openbsd hosts I administrate. As all are running -current, it means I
use it very regulary.

> And while doing so
> potentially running low on space issues (it isn't just a matter of
> the file fitting, there must be some slop left over because the
> installer needs a bit of /tmp)

As installer has sane defaults, the config file is generally small (from
84 to 161 bytes in my environment).

But yes, it could interfere with installer. I wouldn't report a bug on
it without be able to reproduce with interactive method.

> Should everything work in every way?  I'm not so sure.  My truck
> still doesn't fly.

autoinstall is a great possibility. But depending the network
environnement, it could be not possible to netboot, and so to trigger
autoinstall not-interactively. Fetching file using DHCP options isn't
the hard part in my context: I would have only one host without control
of the network.

but I didn't ask for making it a "supported" method. I know I use only a
trick.
-- 
Sebastien Marie

Re: autoinstall with local file

[Raf Czlonka]

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:
> > > 
> > > /auto_upgrade.conf
> > > or
> > > file://auto_upgrade.conf
> > > or
> > > file:auto_upgrade.conf
> > > 
> > > do not work.
> > > 
> > > Is this still a "watch this space!" feature?
> > 
> > It does work. However, / is the root of bsd.rd, not the root of the
> > system you want to upgrade (this would have to be guessed and the
> > upgrade script doesn't do guessing without asking for confirmation).
> > It's a bit of a pain to get the file there, and I don't think there's
> > any official documentation. semarie@ wrote some instructions a while
> > back:
> > https://marc.info/?l=openbsd-misc=141552533922277=2
> > see also:
> > https://marc.info/?l=openbsd-misc=146890249418788=2
> > where he indicates that there are more posts to be found on misc (but I
> > don't know where).
> 
> I would be very surprised to hear that people are using
> vnconfig+mount+vnconfig+mount, to add such a file.  And while doing so
> potentially running low on space issues (it isn't just a matter of
> the file fitting, there must be some slop left over because the
> installer needs a bit of /tmp)
> 
> Should everything work in every way?  I'm not so sure.  My truck
> still doesn't fly.
> 

OK, so I'll admit that I've been using Sebastien's tip for a couple of
years now but, it seem that, I have been lucky it always worked -
probably due to the fact that my auto_upgrade.conf file is only
three lines long (it was two-line long for a while):

Location of sets = disk
Is the disk partition already mounted = yes
Pathname to the sets = $DIR

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?

Cheers,

Raf

Re: autoinstall with local file

[Theo de Raadt]

> 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 feel like we're being pushed to support a set of use cases which
are not core functionality.

The installer will keep improving in various ways, but these narrow
use cases will be first up against the wall (due to being ignored
during development, they'll be fragile due to subtle changes).

It's a complicated shell script.  It doesn't deliver pizza, either.

Re: autoinstall with local file

[Theo de Raadt]

> 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 server = ftp.hostserver.de
>> _EOF
># exit
>erase ^?, werase ^W, kill ^U, intr ^C, status ^T
>
>Welcome to the OpenBSD/amd64 6.0 installation program.
>(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a

That strikes me as a little silly, and I wonder how many people
will decide to do that.

Why create a file to answer the prompts *interactively*, in lieu of
simply hitting return and answering the questions a moment later.

The key point here is the example is interactive.

> If the system had internet access during installation, it's even enough
> to create an empty /auto_upgrade.conf, because the last used mirror will
> be used automatically.
> 
>Welcome to the OpenBSD/amd64 6.0 installation program.
>(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
># >/auto_upgrade.conf
># exit
>erase ^?, werase ^W, kill ^U, intr ^C, status ^T
>
>Welcome to the OpenBSD/amd64 6.0 installation program.
>(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a

Another example of interactive use.

Re: autoinstall with local file

[jungle Boogie]

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
> file:auto_upgrade.conf
>
> do not work.
>
> Is this still a "watch this space!" feature?
>

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



> --
>
> Edward Ahlsen-Girard
> Ft Walton Beach, FL
>



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info

Re: autoinstall with local file

[Robert Peichaer]

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:
> > > 
> > > /auto_upgrade.conf
> > > or
> > > file://auto_upgrade.conf
> > > or
> > > file:auto_upgrade.conf
> > > 
> > > do not work.
> > > 
> > > Is this still a "watch this space!" feature?
> > 
> > It does work. However, / is the root of bsd.rd, not the root of the
> > system you want to upgrade (this would have to be guessed and the
> > upgrade script doesn't do guessing without asking for confirmation).
> > It's a bit of a pain to get the file there, and I don't think there's
> > any official documentation. semarie@ wrote some instructions a while
> > back:
> > https://marc.info/?l=openbsd-misc=141552533922277=2
> > see also:
> > https://marc.info/?l=openbsd-misc=146890249418788=2
> > where he indicates that there are more posts to be found on misc (but I
> > don't know where).
> 
> I would be very surprised to hear that people are using
> vnconfig+mount+vnconfig+mount, to add such a file.  And while doing so
> potentially running low on space issues (it isn't just a matter of
> the file fitting, there must be some slop left over because the
> installer needs a bit of /tmp)
> 
> Should everything work in every way?  I'm not so sure.  My truck
> still doesn't fly.

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 server = ftp.hostserver.de
   > _EOF
   # exit
   erase ^?, werase ^W, kill ^U, intr ^C, status ^T
   
   Welcome to the OpenBSD/amd64 6.0 installation program.
   (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a


If the system had internet access during installation, it's even enough
to create an empty /auto_upgrade.conf, because the last used mirror will
be used automatically.

   Welcome to the OpenBSD/amd64 6.0 installation program.
   (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
   # >/auto_upgrade.conf
   # exit
   erase ^?, werase ^W, kill ^U, intr ^C, status ^T
   
   Welcome to the OpenBSD/amd64 6.0 installation program.
   (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a


-- 
-=[rpe]=-

Re: autoinstall with local file

[Theo de Raadt]

> 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
> > 
> > do not work.
> > 
> > Is this still a "watch this space!" feature?
> 
> It does work. However, / is the root of bsd.rd, not the root of the
> system you want to upgrade (this would have to be guessed and the
> upgrade script doesn't do guessing without asking for confirmation).
> It's a bit of a pain to get the file there, and I don't think there's
> any official documentation. semarie@ wrote some instructions a while
> back:
> https://marc.info/?l=openbsd-misc=141552533922277=2
> see also:
> https://marc.info/?l=openbsd-misc=146890249418788=2
> where he indicates that there are more posts to be found on misc (but I
> don't know where).

I would be very surprised to hear that people are using
vnconfig+mount+vnconfig+mount, to add such a file.  And while doing so
potentially running low on space issues (it isn't just a matter of
the file fitting, there must be some slop left over because the
installer needs a bit of /tmp)

Should everything work in every way?  I'm not so sure.  My truck
still doesn't fly.

Re: autoinstall with local file

[Theo Buehler]

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
> 
> do not work.
> 
> Is this still a "watch this space!" feature?

It does work. However, / is the root of bsd.rd, not the root of the
system you want to upgrade (this would have to be guessed and the
upgrade script doesn't do guessing without asking for confirmation).
It's a bit of a pain to get the file there, and I don't think there's
any official documentation. semarie@ wrote some instructions a while
back:
https://marc.info/?l=openbsd-misc=141552533922277=2
see also:
https://marc.info/?l=openbsd-misc=146890249418788=2
where he indicates that there are more posts to be found on misc (but I
don't know where).

Re: autoinstall with local file

[Robert Peichaer]

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
> 
> do not work.
> 
> Is this still a "watch this space!" feature?
> 
> -- 
> 
> Edward Ahlsen-Girard
> Ft Walton Beach, FL
> 

The installer looks at the filesystem provided by bsd.rd itself, not the 
filesystem on
disk.

-- 
-=[rpe]=-

Re: autoinstall (eg: disklabel -T) doesn't support templates that specify partition sizes in sectors?

[Claus Assmann]

On Thu, Oct 06, 2016, Erling Westenvik wrote:

[I'm only replying because I ran into a problem in this area and
posted a patch suggestion to the tech list; a different fix was
applied after some discussion.]

> templates, I was a little surprised to find that disklabel(8) apparently
> does not support specifying partition sizes givin in sectors, only in
...
> or megabytes. But I got curious as to why templates cannot be specified
> in sectors?

Just a guess: maybe because nobody needed it (so far)?

apply_unit() in src/sbin/disklabel/editor.c might be something you
want to look at and provide a patch? If a developer considers it
interesting/important enough, it might get into the tree.

Re: Autoinstall via netboot over VLAN interface

[Robert Peichaer]

On Mon, Jan 04, 2016 at 09:35:04AM -0700, Darren S. wrote:
> I have a router on the end of a 802.1q trunk port that I'd like to
> netboot for install, but this is only possible if I can PXE boot using
> the correct VLAN to reach the PXE server. Some PXE boot ROMs support
> this (mine does not currently) and I was going to try it from a booted
> bsd.rd on the host, but looks like I only have options for physical
> interfaces to select from on an Autoinstall:
> 
> Welcome to the OpenBSD/amd64 5.8 installation program.
> (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a
> Available network interfaces are: re0 re1 re2 athn0.
> Which network interface should be used for the initial DHCP request?
> (or 'done') [re0]
> DHCPDISCOVER on re0 - interval 3
> DHCPDISCOVER on re0 - interval 5
> DHCPDISCOVER on re0 - interval 13
> DHCPDISCOVER on re0 - interval 19
> DHCPDISCOVER on re0 - interval 13
> DHCPDISCOVER on re0 - interval 8
> No acceptable DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> Could not determine next-server.
> Could not determine auto mode.
> Response file location?
> 
> With additional work I may be able to switch around network
> configurations to support a native VLAN (and then reconfigure
> post-install) but this isn't ideal. Is it feasible for the autoinstall
> support to handle the same VLAN features for booting as is available
> later in the installation for network configuration?
> 
>   Which network interface do you wish to configure = vlan0
>   Which interface:tag should vlan0 be on = re0:100
>   IPv4 address for vlan0 = 10.0.1.1
>   Netmask for vlan0 = 255.255.255.0
> 
> -- 
> Darren Spruell
> phatbuck...@gmail.com

You can put the response file into the bsd.rd as /auto_upgrade.conf or
/auto_install.conf. This way you can avoid the fetching of the response file.

https://marc.info/?l=openbsd-misc=141552533922277=2

Re: Autoinstall via netboot over VLAN interface

[Jiri B]

On Mon, Jan 04, 2016 at 09:35:04AM -0700, Darren S. wrote:
> I have a router on the end of a 802.1q trunk port that I'd like to
> netboot for install, but this is only possible if I can PXE boot using
> the correct VLAN to reach the PXE server. Some PXE boot ROMs support
> this (mine does not currently) and I was going to try it from a booted
> bsd.rd on the host, but looks like I only have options for physical
> interfaces to select from on an Autoinstall:

Try IPXE rom, iirc it does support vlan, even trunk/bond.

> Welcome to the OpenBSD/amd64 5.8 installation program.
> (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a
> Available network interfaces are: re0 re1 re2 athn0.
> Which network interface should be used for the initial DHCP request?
> (or 'done') [re0]
> DHCPDISCOVER on re0 - interval 3
> DHCPDISCOVER on re0 - interval 5
> DHCPDISCOVER on re0 - interval 13
> DHCPDISCOVER on re0 - interval 19
> DHCPDISCOVER on re0 - interval 13
> DHCPDISCOVER on re0 - interval 8
> No acceptable DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> Could not determine next-server.
> Could not determine auto mode.
> Response file location?
> 
> With additional work I may be able to switch around network
> configurations to support a native VLAN (and then reconfigure
> post-install) but this isn't ideal. Is it feasible for the autoinstall
> support to handle the same VLAN features for booting as is available
> later in the installation for network configuration?

IIUC install has no way to know you want to use tagged vlan.
You need to dedicate separate iface for booting or use custom
install script inside ramdisk.

I would redesign your network to have dedicated port based vlan
for netbooting...

j.

Re: Autoinstall Failing When Trying to Find Sets

[Raf Czlonka]

On Thu, Jun 11, 2015 at 11:58:40AM BST, Richard Laysell wrote:

Hi Richard,

 ./pub/OpenBSD/snapshots/amd64:
 total 448072
 drwxr-xr-x  2 root  wheel   512 Jun 11 09:15 .
 drwxr-xr-x  3 root  wheel   512 Jun 11 09:14 ..
 -r--r--r--  1 root  wheel 46518 Jun 11 09:15 INSTALL.amd64
 -r--r--r--  1 root  wheel  1535 Jun 11 09:15 SHA256.sig
 -r--r--r--  1 root  wheel  57380394 Jun 11 09:15 base57.tgz
 -r--r--r--  1 root  wheel  10029237 Jun 11 09:15 bsd
 -r--r--r--  1 root  wheel  10069780 Jun 11 09:15 bsd.mp
 -r--r--r--  1 root  wheel   7592389 Jun 11 09:15 bsd.rd
 -r--r--r--  1 root  wheel  51246149 Jun 11 09:15 comp57.tgz
 -r--r--r--  1 root  wheel   2789725 Jun 11 09:15 game57.tgz
 -r--r--r--  1 root  wheel   8984308 Jun 11 09:15 man57.tgz
 -r--r--r--  1 root  wheel  17060674 Jun 11 09:15 xbase57.tgz
 -r--r--r--  1 root  wheel  39930183 Jun 11 09:15 xfont57.tgz
 -r--r--r--  1 root  wheel  19794709 Jun 11 09:15 xserv57.tgz
 -r--r--r--  1 root  wheel   4519648 Jun 11 09:15 xshares57.tgz
 -8-cut here -8-
 
 Can anyone see where I'm going wrong?

Not immediately obvious, but you're missing the 'index.txt' file[0]:

Note: if you wish to distribute the resultant files by HTTP for use by
the upgrade or install scripts, you will need to add an index.txt
file, which contains the list of all the files in your newly created
release.

[0] http://www.openbsd.org/faq/faq5.html#Release

Regards,

Raf

Re: Autoinstall Failing When Trying to Find Sets (SOLVED)

[Richard Laysell]

On Thu, 11 Jun 2015 12:19:39 +0100
Raf Czlonka rczlo...@gmail.com wrote:

 On Thu, Jun 11, 2015 at 11:58:40AM BST, Richard Laysell wrote:
 
 Hi Richard,
 
  Can anyone see where I'm going wrong?
 
 Not immediately obvious, but you're missing the 'index.txt' file[0]:
 
 Note: if you wish to distribute the resultant files by HTTP for use by
 the upgrade or install scripts, you will need to add an index.txt
 file, which contains the list of all the files in your newly created
 release.
 
 [0] http://www.openbsd.org/faq/faq5.html#Release
 
 Regards,
 
 Raf
 

Hello Raf,

Thanks very much.  This fixed the problem and my system is now doing a
complete autoinstall

Regards,

Richard

Re: Autoinstall without PXE.

[Joshua Smith]

--
Joshua Smith
Lead Systems Administrator WVNET

Montani Semper Liberi 

Sent from my iPhone. 

 On Mar 13, 2015, at 11:39 PM, dan mclaughlin thev...@openmailbox.org wrote:
 
 On Sat, 14 Mar 2015 02:27:56 + Raf Czlonka rczlo...@gmail.com wrote:
 On Fri, Mar 13, 2015 at 09:02:23PM GMT, Joshua Smith wrote:
 
 Hello misc@,
 
 Hi Joshua,
 
 Looking around the man pages for 5.6 and -current it doesn't seem like
 it, but is it possible to perform an autoinstall/autoupgrade with out
 utilizing pxe and an http server.
 
 I would like to put the autoinstall/autoupgrade file on a usbkey or
 embed it on a custom cd.
 
 Well, probably not the way you have in mind (i.e. full autoinstall) as
 you still have to point the installer to the {install,upgrade}.conf
 manually: i.e. choose (A) for autoinstall, it'll then fail, escape to
 shell, mount the disk with your config file, go back to the installer
 and point it to the file - the rest of the installation/upgrade is then
 fully automatic.
 
 I use a 3-line (that includes a keyboard layout) 'upgrade.conf' to
 upgrade to new snapshots.
 
 Regards,
 
 Raf
 
 there is a better way using rdsetroot to actually put the *.conf files in the
 bsd.rd kernel itself. it was discussed previously here:
 
 https://marc.info/?l=openbsd-miscm=141552533922277w=2

Thanks!
This is exactly what I am looking for. 

IMHO being able to provide autoupgrade in / of the existing system would be a 
great addition. 

Re: Autoinstall without PXE.

[dan mclaughlin]

On Sat, 14 Mar 2015 02:27:56 + Raf Czlonka rczlo...@gmail.com wrote:
 On Fri, Mar 13, 2015 at 09:02:23PM GMT, Joshua Smith wrote:
 
  Hello misc@,
 
 Hi Joshua,
 
  Looking around the man pages for 5.6 and -current it doesn't seem like
  it, but is it possible to perform an autoinstall/autoupgrade with out
  utilizing pxe and an http server.
  
  I would like to put the autoinstall/autoupgrade file on a usbkey or
  embed it on a custom cd.
 
 Well, probably not the way you have in mind (i.e. full autoinstall) as
 you still have to point the installer to the {install,upgrade}.conf
 manually: i.e. choose (A) for autoinstall, it'll then fail, escape to
 shell, mount the disk with your config file, go back to the installer
 and point it to the file - the rest of the installation/upgrade is then
 fully automatic.
 
 I use a 3-line (that includes a keyboard layout) 'upgrade.conf' to
 upgrade to new snapshots.
 
 Regards,
 
 Raf
 

there is a better way using rdsetroot to actually put the *.conf files in the
bsd.rd kernel itself. it was discussed previously here:

https://marc.info/?l=openbsd-miscm=141552533922277w=2

Re: Autoinstall without PXE.

[Raf Czlonka]

On Fri, Mar 13, 2015 at 09:02:23PM GMT, Joshua Smith wrote:

 Hello misc@,

Hi Joshua,

 Looking around the man pages for 5.6 and -current it doesn't seem like
 it, but is it possible to perform an autoinstall/autoupgrade with out
 utilizing pxe and an http server.
 
 I would like to put the autoinstall/autoupgrade file on a usbkey or
 embed it on a custom cd.

Well, probably not the way you have in mind (i.e. full autoinstall) as
you still have to point the installer to the {install,upgrade}.conf
manually: i.e. choose (A) for autoinstall, it'll then fail, escape to
shell, mount the disk with your config file, go back to the installer
and point it to the file - the rest of the installation/upgrade is then
fully automatic.

I use a 3-line (that includes a keyboard layout) 'upgrade.conf' to
upgrade to new snapshots.

Regards,

Raf

Re: autoinstall on SGI Indigo

[Sebastian Reitenbach]

On Friday, March 28, 2014 21:01 CET, Sebastian Reitenbach 
sebas...@l00-bugdead-prods.de wrote: 
 
 Hi,
 
 reading the INSTALL.sgi with regard to autoinstall, and also the manpage 
 I find that:
 
 The filename DHCP
 parameter specifies the installer mode, e.g. auto_install.  On
 architectures where this parameter is used for netbooting, create
 a symbolic link named auto_install pointing to the boot program.
 
 due to the old PROM it has, I have to retrieve two files from the
 next-server like this:
 bootp()bootecoff bootp()bsd.rd.IP22
 
 example host entry for the Indigo:
 host excelsior {
 # SGI Irix Indigo (Indy)
 next-server 10.0.0.27;
 # filename auto_install;
 hardware ethernet 08:00:69:06:cc:6f;
 fixed-address 10.0.0.31;
 option host-name excelsior;
 }
 
 then creating a symlink from bootecoff to auto_install, it fails retrieving 
 bsd.rd.IP22,
 ...
 arg 7: OSLoadFilename=/bsd
 Boot: bootp()bsd.rd.IP22
 cannot open /etc/random.seed: Device not configured
 Setting $netaddr to 10.0.0.31 (from server )
 Obtaining bsd.rd.IP22 from server 
 bootp()bsd.rd.IP22: Inappropriate file type or format
 Boot FAILED!
 
 or vice versa, creating a symlink from bsd.rd.IP22 to auto_install, it fails 
 to retrieve 
 bootecoff:
 
  bootp()bootecoff bootp()bsd.rd.IP22
 Setting $netaddr to 10.0.0.31 (from server )
 Obtaining bootecoff from server 
 
 Cannot load bootp()bootecoff.
 Unable to execute bootp()bootecoff
 
 Basically to get both files from the TFTP server, I have to have the
 filename parameter for that host commented out in dhcpd.conf file.
 When then the bsd.rd.IP22 finished booting, and asks me what to do, 
 i.e. install, upgrade, autoinstall etc. then I edit the dhcpd.conf 
 uncommenting
 the filename parameter, and select (A)utoinstall. 
 
 Then it successfully retrieves my autoinstall script file from httpd and goes 
 on
 with the unattended installation. This then fails since the root disk is just 
 too small
 and, as far as I researched, there is no real way yet to edit the disklabel 
 automatically.
 But that's a different story.
 
 So, re-using the next-server parameter to point to the httpd server that hosts
 the installation configuration file, works for me, I have it set up on the 
 same host
 as the TFTP server. But with this host, the filename parameter definitely 
 conflicts
 with booting the kernel from the net.
 Further, I have many different architectures, and this requirement to symlink 
 the
 auto_install file name to the boot file name needed for each architecture also
 prevents to boot different architectures at the same time.
 
 So, instead of re-using the filename dhcp option to define if to do an 
 unattended
 upgrade or installation, maybe a different option could be chosen that is not
 conflicting with other common functionality.
 
 Looking at some options here [1], option 150 (GRUB config path name), 
 209 (Configuration file), or 129 (Kernel options) comes to mind.
 But as far as I can see, the dhcpd doesn't support those custom options (yet)?

just after sending it out, I figured dhcpd seems to support those options, at 
least
specifying them correctly in dhcpd.conf, dhcpd starts up without whining.

 
 cheers,
 Sebastian
 
 [1] 
 https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml

Re: Autoinstall

[Peter Hessler]

On 2013 Nov 04 (Mon) at 17:14:57 -0500 (-0500), Predrag Punosevac wrote:
:I was driving last night so I have not had much sleep. I just want to
:make sure that I am not hallucinating. Then minutes ago when I installed
:the latest snapshot I was presented with an additional installation option
:
:Autoinstall [A]
:
:I picked out of curiosity but since I have not provided configuration
:file I was dropped to the shell.
:
:I think I can see where is this going and I would like to thank you
:everyone involved.
:
:Cheers,
:Predrag
:

Yes, Autoinstall needs some configuration to work.  Documentation is in
progress.


-- 
Anything worth doing is worth overdoing.

Re: Autoinstall

[Marian Hettwer]

Am 2013-11-05 10:06, schrieb Peter Hessler:
On 2013 Nov 04 (Mon) at 17:14:57 -0500 (-0500), Predrag Punosevac 
wrote:

:I was driving last night so I have not had much sleep. I just want to
:make sure that I am not hallucinating. Then minutes ago when I 
installed
:the latest snapshot I was presented with an additional installation 
option

:
:Autoinstall [A]
:
:I picked out of curiosity but since I have not provided configuration
:file I was dropped to the shell.
:
:I think I can see where is this going and I would like to thank you
:everyone involved.
:
:Cheers,
:Predrag
:

Yes, Autoinstall needs some configuration to work.  Documentation is in
progress.


Very glad to see this coming! Thanks a million! :-)

Cheers,
Marian

Re: Autoinstall

[Richard Toohey]

On 11/05/13 11:14, Predrag Punosevac wrote:

I was driving last night so I have not had much sleep. I just want to
make sure that I am not hallucinating. Then minutes ago when I installed
the latest snapshot I was presented with an additional installation option

Autoinstall [A]

I picked out of curiosity but since I have not provided configuration
file I was dropped to the shell.

I think I can see where is this going and I would like to thank you
everyone involved.

I assume it's this?

http://undeadly.org/cgi?action=articlesid=20131029073058mode=expanded


Cheers,
Predrag