I'm currently facing a situation where auoinstall pauses until I tell it the
correct port number :
Fetching http://10.0.2.2/52:54:00:12:34:56-install.conf?path=7.5/amd64
Fetching http://10.0.2.2/openbsd-vm-install.conf?path=7.5/amd64
Fetching http://10.0.2.2/install.conf?path=7.5/amd64
Response f
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.
Hello,
I was able to auto-install OpenBSD/amd64 except full disk encryption
(FDE). Is FDE supported in autoinstall?
Thanks much!
Boj
Hello,
I was able to auto-install OpenBSD/amd64 except full disk encryption
(FDE). Is FDE supported in autoinstall?
Thanks much! J.
k (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
>
ver = 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 ha
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
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
On Tue, Jun 02, 2020 at 01:48:33PM +, RT wrote:
> I have already gone through the autoinstall man page but I didn't understand
> how to do that using local(offline without the TFTP server) file(do I need to
> write rewrite the bsd.rd and include the install.conf file?
Hey
I have no prior experience with BSD.
I am planning to perform non interactive installation of OpenBSD with some
params(like the default root password, network etc) as host on Fedora(guest)
using virt-install any suggestions for that?
I have already gone through the autoinstall man page but
Autoinstall(8) and its ability to automate the trivial but time
consuming task of typing info like keyboard layout and network setup -
not to mention encrypted passwords and ssh keys! - by supplying the
information in a response file, is great. Add the ability to supply a
template for disklabel
t 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 co
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 inst
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
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
> 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 with
ig 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'
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, bu
> 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-INTERACTIV
> 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 serve
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
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, bu
> 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
> > f
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
> fi
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
> fi
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?
--
Edw
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 supp
Experimenting with autoinstall(8) and predefined partition layout
templates, I was a little surprised to find that disklabel(8) apparently
does not support specifying partition sizes givin in sectors, only in
units (b,c,k,m,g,t) and/or percentages? Am I missing out on something
obvious here?
My
is (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 o
is (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 installatio
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 fo
Thanks, Jiri
I wasn't worried about the stability at this very moment. More about the
way to get me to from release to stable/current.
Regards,
Lysemose
On Thu, Aug 6, 2015 at 10:24 AM, Jiri B wrote:
> > Ahh, I didn't see the snapshot before now.
> > I thought that I needed to re-compile the wh
> Ahh, I didn't see the snapshot before now.
> I thought that I needed to re-compile the whole thing to get me on -current.
>
> I will try the snapshot and report back!
Well, if you do not have your own testing and build process,
you do not need stable ABI/API for your production apps,
then just
Ahh, I didn't see the snapshot before now.
I thought that I needed to re-compile the whole thing to get me on -current.
I will try the snapshot and report back!
Thanks,
Lysemose
On Thu, Aug 6, 2015 at 2:40 AM, wrote:
> > Thanks, that's it!!
> > I'm not running current-release... I'll guess I h
Hi Laurent
Thanks, that's it!!
I'm not running current-release... I'll guess I have to wait for 5.8 then...
Regards,
Lysemose
On Aug 5, 2015 18:45, "Laurent Salle" wrote:
> On 05/08/15 11:58, Heine Lysemose wrote:
>
>> Hi
>>
>> I'm
On 05/08/15 11:58, Heine Lysemose wrote:
Hi
I'm trying to get my autoinstall to autopartition my disk.
My system is a VirtualBox server and client with OpenBSD 5.7
Are you running 5.7 current ?
I've been bitten myself. Autopartitionning is not available in 5.7
release or stable
On Wed, 05 Aug 2015 05:14:35 -0700, Heine Lysemose
wrote:
Are there any order the questions/answers should appear in, in the file
install.conf?
I don't know if the email system mangled your install.conf contents, but
is the autopartition URL on the same line as the question?
As far as I
Maybe this is useful? The answer is in the second message of the thread.
Code example is included also.
http://marc.info/?l=openbsd-misc&m=143402045705775&w=2
On Wed, Aug 5, 2015 at 1:06 PM, Jiri B wrote:
> On Wed, Aug 05, 2015 at 11:58:55AM +0200, Heine Lysemose wrote:
> > Hi
> >
> > I'm trying to get my autoinstall to autopartition my disk.
> >
> > My system is a VirtualBox server and client with OpenBSD 5.7
On Wed, Aug 05, 2015 at 11:58:55AM +0200, Heine Lysemose wrote:
> Hi
>
> I'm trying to get my autoinstall to autopartition my disk.
>
> My system is a VirtualBox server and client with OpenBSD 5.7
>
> So far I can boot from PXE it runs through the autoinstall just
Hi
I'm trying to get my autoinstall to autopartition my disk.
My system is a VirtualBox server and client with OpenBSD 5.7
So far I can boot from PXE it runs through the autoinstall just fine but
fails to do the autopartitioning and therefore creates a default layout of
the disk.
Here my
q/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
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
>
Hello,
I'm trying to do an autoinstallation of OpenBSD 5.7. The system PXE
boots OK and most of the installation works as expected, but the
install system is unable to find the installation sets and stops
I'm using the bsd.rd from snapshots as this supports the auto
partitioning (which works gre
:
>>>
>>> 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.
On Sat, 14 Mar 2015 02:27:56 + Raf Czlonka 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
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.
>
>
Hello misc@,
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.
T
Hi,
i am using pxe boot with autoinstall and a hostname specific tgz file
in the sets to deploy many similar Firewalls.
i tell the installer how to configure at least one nic, to download
the sets. i use dhcp for that.
after that everything works as expected until the install is done and
machine
On 12/16/14 22:06, Adriaan wrote:
> On Tue, Dec 16, 2014 at 8:26 AM, Raf wrote:
>>
>> On Tue, Dec 16, 2014 at 01:01:51AM EST, Adriaan wrote:
>>
>> > An initial interactive install was succesful. A next autonstall using
>> > bsd,rd gave a "Cannot determine prefetch area" after selecting the
>> > se
http://www.openbsd.org/faq/faq4.html#site
>
Thanks, it has been a while since I read those sections. But it indeeds
mentions the "Cannot determine prefetch area" error that I had never seen
before.
Adding the following to the install.conf file makes an autoinstall with
the auto layout su
On Tue, Dec 16, 2014 at 7:35 AM, Ted Unangst wrote:
>
> On Tue, Dec 16, 2014 at 07:01, Adriaan wrote:
> > OpenBSD 5.6-current (RAMDISK_CD) #573: Sun Dec 14 20:08:49 MST 2014
> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
> >
> > An initial interactive install was succesful.
On Tue, Dec 16, 2014 at 01:01:51AM EST, Adriaan wrote:
> An initial interactive install was succesful. A next autonstall using
> bsd,rd gave a "Cannot determine prefetch area" after selecting the
> sets.
> [...]
> Cannot determine prefetch area. Continue without verification? [no] no
I see that t
On Tue, Dec 16, 2014 at 07:01, Adriaan wrote:
> OpenBSD 5.6-current (RAMDISK_CD) #573: Sun Dec 14 20:08:49 MST 2014
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
>
> An initial interactive install was succesful. A next autonstall using
> bsd,rd gave a
> "Cannot determine pre
OpenBSD 5.6-current (RAMDISK_CD) #573: Sun Dec 14 20:08:49 MST 2014
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
An initial interactive install was succesful. A next autonstall using
bsd,rd gave a
"Cannot determine prefetch area" after selecting the sets.
(Complete dmes
Le 2014-05-08 13:03, Kenneth Westerback a écrit :
On 8 May 2014 05:33, Xavier Claude wrote:
Hello,
I'm trying to use autoinstall with OpenBSD 5.5 but the Server line
in
the configuration file is not read set according to the install.conf
and instead is used for the ntp server.
Here
On 8 May 2014 05:33, Xavier Claude wrote:
> Hello,
>
> I'm trying to use autoinstall with OpenBSD 5.5 but the Server line in
> the configuration file is not read set according to the install.conf
> and instead is used for the ntp server.
>
> Here is my install.co
Hello,
I'm trying to use autoinstall with OpenBSD 5.5 but the Server line in
the configuration file is not read set according to the install.conf
and instead is used for the ntp server.
Here is my install.conf file:
System hostname = testbsd
Password for root = $2a$06$8APgDGjoEAAq85b3S.
On Friday, March 28, 2014 21:01 CET, "Sebastian Reitenbach"
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. "
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
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,
:Pred
:
: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 configurati
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
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 pro
64 matches
Mail list logo
