Re: bsd.re-config syntax
Received, thnx.. -- Nowarez Market Nov 24, 2023 08:38:37 Peter N. M. Hansteen : > the machine-independent GENERIC config is at > https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/conf/GENERIC?rev=1.291=text/plain, > while what I assume is the most common machine dependent one would be > https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/conf/GENERIC.MP?rev=1.16=text/x-cvsweb-markup > > Lots more under src/sys/arch/$arch/conf where $arch is your architecture.
Re: bsd.re-config syntax
On Fri, Nov 24, 2023 at 08:23:48AM +0100, Capitan Cloud wrote: > Thnx Peter, please can you point me out the path of cvsweb where > to find the resources that you are meaning? the machine-independent GENERIC config is at https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/conf/GENERIC?rev=1.291=text/plain, while what I assume is the most common machine dependent one would be https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/conf/GENERIC.MP?rev=1.16=text/x-cvsweb-markup Lots more under src/sys/arch/$arch/conf where $arch is your architecture. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: bsd.re-config syntax
Thnx Peter, please can you point me out the path of cvsweb where to find the resources that you are meaning? Nov 24, 2023 08:03:00 Peter N. M. Hansteen : > It's a kernel configuration file. There are numerous examples > in the source tree. -- Nowarez Market
Re: bsd.re-config syntax
Thnx Peter, please can you point me out the path of cvsweb where to find the resources that you are meaning? Nov 24, 2023 08:03:00 Peter N. M. Hansteen : > It's a kernel configuration file. There are numerous examples > in the source tree.
Re: bsd.re-config syntax
On Fri, Nov 24, 2023 at 01:14:06AM +0100, Nowarez Market wrote: > I'm in the need to know if /etc/bsd.re-config accepts > comment starting with "#" as normally other file.conf do. It's a kernel configuration file. There are numerous examples in the source tree. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
bsd.re-config syntax
Hello, I'm in the need to know if /etc/bsd.re-config accepts comment starting with "#" as normally other file.conf do. Just to pass my time during the upgrade to 7.4 (and to simplify my life for the next time) .. NB: man could be a little more detailed about the subject. Thnx! == Nowarez Market
Re: OpenBSD alternative setup to ZFS on Linux or FreeBSD
On Fri, Nov 24, 2023 at 08:32:20AM +1000, Stuart Longland VK4MSL wrote: > On 22/11/23 18:25, Crystal Kolipe wrote: > >1. Once data is no longer "work in progress", archive it to write-only > >media and take it out of the regular backup loop. In most cases this > >drastically reduces the volume of data you need to manage. Feel free > >to keep a local on-line copy on a regular disk too for faster access. > > If it's "write only", how does one read it? You try to write each bit a second time, and if the write succeeds then you know that it wasn't already written the first time around. Haven't you ever used magnetic core memory?
Re: OpenBSD alternative setup to ZFS on Linux or FreeBSD
On 22/11/23 18:25, Crystal Kolipe wrote: 1. Once data is no longer "work in progress", archive it to write-only media and take it out of the regular backup loop. In most cases this drastically reduces the volume of data you need to manage. Feel free to keep a local on-line copy on a regular disk too for faster access. If it's "write only", how does one read it? -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: Auto-install over network using UEFI
On 2023-11-23, Nick Owens wrote: > On Tue, Nov 21, 2023 at 7:03 PM Chris Narkiewicz wrote: >> >> I'm experimentin with auto-install over network using linux libvirt >> (qemu). >> >> I managed to load pxeboot in BIOS mode and I'm wondering if UEFI >> is supported. >> >> According to this blog, I should load BOOTX64.EFI instead of pxeboot. >> >> https://eradman.com/posts/autoinstall-openbsd.html >> >> I was skeptical but tried it neverthekess and system immediately reboots >> after >> probing disk: >> >> probing: p0 com0 mem[640K 2029M 9M 3M] >> disk:BS->LocateHandle() returns 14 >> >> >> Is it possible to net-boot installer in UEFI using QEMU? >> >> Cheers, >> Chris >> > > i had some trouble getting PXE set up with dhcpd - see my mail from > april, "dhcpd user-class and vendor-class". > > i think there is also a bug in the EFI loader when run under OVMF as > you experienced, but i never figured it out. With vendor-class the usual way is to react to the class sent by the _client_ and, based on that, send other options as appropriate. You can't do that with dhcpd from base though - it does not support sending different options to different clients via matches - only by setting per-client. It is however possible with ISC dhcpd. Trying to _send_ it from the server like you showed, note that you can only send one vendor-class (so you can't send different boot filenames for different archs) and you can't override another "filename" option (say for a non-UEFI pxeboot loader). As such I think adding it to the manual is likely to create more confusion as people try to use it in the way they've seen in how-to docs for ISC dhcpd, and fail. You don't need this in order to do network installs though. In the simple case where you have only amd64 systems with 64-bit UEFI, you can just copy BOOTX64.EFI to auto_install on your tftp server and use 'filename "auto_install"' in dhcpd.conf. AFAIK that isn't any worse than using "vendor-class" in the way which you showed because you can't cope with multiple archs that way anyway. If you have a mixture of systems, you have several options, in all cases you'll need to make a DHCP assignment for the client's MAC. Note that the boot loader must be named auto_install for the ramdisk's autoinstall functionality to work, *but* it can be in a subdirectory. So either of these are possible: - use tftpd -i and prepare per-IP directories where you copy the relevant boot loader (whichever of pxeboot, BOOTIA32.EFI, BOOTX64.EFI, BOOTAA64.EFI is appropriate) to /tftpboot/11.22.33.44/auto_install - use standard tftpd options, create directories and copy the various loaders across, e.g. BOOTIA32.EFI -> /tftpboot/ia32/auto_install BOOTX64.EFI -> /tftpboot/x64/auto_install BOOTAA64.EFI -> /tftpboot/aa64/auto_install pxeboot -> /tftpboot/pxe/auto_install and in the "host" block in DHCP for each machine, set whichever is appropriate under filename, e.g. 'filename "x64/auto_install"'. We could definitely do with more docs for UEFI network installs but think we need to get a better handle on it before adding them .. -- Please keep replies on the mailing list.
Re: mkdir
all files are present in /bin/ mkdir. Oddly enough after several attempts I was able to create the directory Cdt, Pascal DEVEAUX From: Zé Loff Sent: Thursday, November 23, 2023 4:57:32 PM To: Pascal Deveaux Cc: misc@openbsd.org Subject: Re: mkdir On Thu, Nov 23, 2023 at 12:38:50PM +, Pascal Deveaux wrote: > simple command to create a directories return: > > $ mkdir test > ksh: mkdir: not found > > I don't understand... > > OpenBSD 7.4 - fresh install > > Pascal Is /bin in your PATH, and if so, does /bin/mkdir exist? On an amd64 install /bin should have 41 files. --
Re: And about /bin - Re: mkdir
Got it, many thanks.. -- Nowarez Market Nov 23, 2023 15:23:26 Omar Polo : > On 2023/11/23 14:18:22 +0100, Nowarez Market wrote: >> >> >> Yesterday I was playing around some software and at a the certain >> point in time I launched in the shell: >> >> wiz# rm -Rf * >> ksh: rm: wrong param -3 > > it's quite obvious when you know, yet maybe obscure the first time you > run into it. > > The shell expands * to the list of matching files (i.e. all the files > in the current directory) and pass them to rm(1). Now, what happens if > you have a file called '-3'? (or any file whose first character is a > minus sign) > > it runs `rm -Rf -3 ...other files...' and then rm thinks -3 is an > option. > > This is a "common" issue with globbing, and in fact almost all programs > understand "--" to separate flags from files.
Re: And about /bin - Re: mkdir
On 2023/11/23 14:18:22 +0100, Nowarez Market wrote: > > > Yesterday I was playing around some software and at a the certain > point in time I launched in the shell: > > wiz# rm -Rf * > ksh: rm: wrong param -3 it's quite obvious when you know, yet maybe obscure the first time you run into it. The shell expands * to the list of matching files (i.e. all the files in the current directory) and pass them to rm(1). Now, what happens if you have a file called '-3'? (or any file whose first character is a minus sign) it runs `rm -Rf -3 ...other files...' and then rm thinks -3 is an option. This is a "common" issue with globbing, and in fact almost all programs understand "--" to separate flags from files.
Re: Auto-install over network using UEFI
On Thu, 23 Nov 2023 00:37:37 -0800 Nick Owens wrote: > On Tue, Nov 21, 2023 at 7:03 PM Chris Narkiewicz wrote: > > > > I'm experimentin with auto-install over network using linux libvirt > > (qemu). > > > > I managed to load pxeboot in BIOS mode and I'm wondering if UEFI > > is supported. > > > > According to this blog, I should load BOOTX64.EFI instead of pxeboot. > > > > https://eradman.com/posts/autoinstall-openbsd.html > > > > I was skeptical but tried it neverthekess and system immediately reboots > > after > > probing disk: > > > > probing: p0 com0 mem[640K 2029M 9M 3M] > > disk:BS->LocateHandle() returns 14 > > > > > > Is it possible to net-boot installer in UEFI using QEMU? > > > > Cheers, > > Chris > > > > i had some trouble getting PXE set up with dhcpd - see my mail from > april, "dhcpd user-class and vendor-class". > > i think there is also a bug in the EFI loader when run under OVMF as > you experienced, but i never figured it out. It works with QEMU, it took me around 2 minutes to boot a blank VM in UEFI mode, auto-install it, reboot it and see the login prompt. Error code 14 means "the item was not found", there is probably something wrong with the VM/disk configuration.
And about /bin - Re: mkdir
Yesterday I was playing around some software and at a the certain point in time I launched in the shell: wiz# rm -Rf * ksh: rm: wrong param -3 or something very near. Now, I tried to reproduce it but without enough luck. Maybe from the returned string you can guess something.. == Nowarez Market
Re: mkdir
On Thu, Nov 23, 2023 at 12:38:50PM +, Pascal Deveaux wrote: > simple command to create a directories return: > > $ mkdir test > ksh: mkdir: not found > > I don't understand... > > OpenBSD 7.4 - fresh install > > Pascal Is /bin in your PATH, and if so, does /bin/mkdir exist? On an amd64 install /bin should have 41 files. --
Re: mkdir
On 2023/11/23 12:38:50 +, Pascal Deveaux wrote: > simple command to create a directories return: > > $ mkdir test > ksh: mkdir: not found > > I don't understand... Start off by checking $PATH. mkdir(1) should be in /bin, see if it's listed there. Depending on it, understand either why your $PATH is wrong or why your filesystem is busted.
mkdir
simple command to create a directories return: $ mkdir test ksh: mkdir: not found I don't understand... OpenBSD 7.4 - fresh install Pascal
Re: OpenBSD alternative setup to ZFS on Linux or FreeBSD
Geoff Steckel : > Of course, there's one storage medium verified to last for centuries. > Good ink on rag paper stored dry. Papyrus is good for millenia. > Not entirely a joke. This needs any bullet-proof..
Re: Auto-install over network using UEFI
On Tue, Nov 21, 2023 at 7:03 PM Chris Narkiewicz wrote: > > I'm experimentin with auto-install over network using linux libvirt > (qemu). > > I managed to load pxeboot in BIOS mode and I'm wondering if UEFI > is supported. > > According to this blog, I should load BOOTX64.EFI instead of pxeboot. > > https://eradman.com/posts/autoinstall-openbsd.html > > I was skeptical but tried it neverthekess and system immediately reboots after > probing disk: > > probing: p0 com0 mem[640K 2029M 9M 3M] > disk:BS->LocateHandle() returns 14 > > > Is it possible to net-boot installer in UEFI using QEMU? > > Cheers, > Chris > i had some trouble getting PXE set up with dhcpd - see my mail from april, "dhcpd user-class and vendor-class". i think there is also a bug in the EFI loader when run under OVMF as you experienced, but i never figured it out.
Re: PF Rules for Dual Upstream Gateways
On 2023-11-22, Ian Timothy wrote: > Hello, > > I have two ISPs where one connection is primary and the other is > low-bandwidth for temporary failover only. ifstated handles the failover by > simply changing the default gateway. But under normal conditions I want to be > able to connect via either connection at any time without changing the > default gateway. > > A long time ago under the old pf syntax I had this in /etc/pf.conf which > worked fine, and as far as I can remember was the only thing needed to enable > this desired behavior: > > pass in on $wan1_if reply-to ( $wan1_if $wan1_gw ) > pass in on $wan2_if reply-to ( $wan2_if $wan2_gw ) > > But I’ve not been able to find the right way to do this under the new pf > syntax. From what I’ve been able to find this is supposedly does the same > thing, but no success so far: > > pass in on $wan1_if reply-to ($wan1_if:peer) > pass in on $wan2_if reply-to ($wan2_if:peer) The :peer syntax is for point-to-point interfaces (e.g. pppoe, maybe umb). > What am I missing? Or this there a better way to do this? As long as the gateway is at a known address (not a changing address from DHCP) this should do: pass in on $wan1_if reply-to $wan1_gw pass in on $wan2_if reply-to $wan2_gw You can also have a setup with multiple rtables, but in the simple case, reply-to is often easier. -- Please keep replies on the mailing list.
Re: OpenBSD alternative setup to ZFS on Linux or FreeBSD
On 11/22/23 20:31, j...@bitminer.ca wrote For long-term storage, you have other risks to manage, not the simple technical risk of "will my portable-USB disk be readable in 2038?". Interfaces die - IDE interface cards? Even if you have one the ISA bus might not be available. Parallel SCSI, parallel PCI etc. Archiving data needs regular copy and verify to newer formats/media/attachments and multiple copies stored multiple places. I have files from 1982 which have survived many disasters. Of course, there's one storage medium verified to last for centuries. Good ink on rag paper stored dry. Papyrus is good for millenia. Not entirely a joke.
