ProtectLi w/ OpenBSD
Is there any newer information than this: https://OpenBsdMailBox.blogspot.com/2023/05/protectli-vp2420-with-dasharo.html Looking for a newer faster firewall ... Want headless, and obviously OpenBSD. So is CoreBoot not an option? Or is there a way to make it work?
Re: Cannot PXE Boot PC Engines APU.1D4
--- On Monday, January 1, 2024 at 06:10:57 AM EST, Stefan Sperling wrote: > Booting 7.4 or -current kernels with an old pxeboot binary won't work. > Make sure that both the kernel image and pxeboot originate from the > 7.4 release or -current. I was using pxeboot and bsd.rd from 7.4.
Cannot PXE Boot PC Engines APU.1D4
Note: trying to boot/install from OpenBSD 7.4 PXE. Cannot PXE Boot PC Engines APU.1D4 Have tried both i386 and amd64. Verified that my tftpd server is working. This used to work. Now fails. Hardware is about 10 years old. Do I need new hardware?? What is recommended? Need minimum of 3 ethernet ports. Thanks in advance. PS Having great difficulty signing up and posting to the mailing list. Just not working.
ProtectLi.com
> I used these now because they support Core Boot. > https://ProtectLi.com/ Which model? Does the VP2420 model work well with OpenBSD?
Re: Cannot PXE Boot PC Engines APU.1D4
Note: trying to boot/install from OpenBSD 7.4 PXE. Cannot PXE Boot PC Engines APU.1D4 Have tried both i386 and amd64. Verified that my tftpd server is working. This used to work. Now fails. Hardware is about 10 years old. Do I need new hardware?? What is recommended? Need minimum of 3 ethernet ports. Thanks in advance. PS Having great difficulty signing up and posting to the mailing list. Just not working.
Cannot PXE Boot PC Engines APU.1D4
Cannot PXE Boot PC Engines APU.1D4 Have tried both i386 and amd64. Verified that my tftpd server is working. This used to work. Now fails. Hardware is about 10 years old. Do I need new hardware?? What is recommended? Need minimum of 3 ethernet ports. Thanks in advance. PS Having great difficulty signing up and posting to the mailing list. Just not working.
Cannot PXE Boot PC Engines APU.1D4
Cannot PXE Boot PC Engines APU.1D4 Have tried both i386 and amd64. Verified that my tftpd server is working. This used to work. Now fails. Hardware is about 10 years old. Do I need new hardware?? What is recommended? Need minimum of 3 ethernet ports. Thanks in advance. PS Having great difficulty signing up and posting to the mailing list. Just not working.
Cannot PXE Boot PC Engines APU.1D4
Cannot PXE Boot PC Engines APU.1D4 Have tried both i386 and amd64. Verified that my tftpd server is working. This used to work. Now fails. Hardware is about 10 years old. Do I need new hardware?? What is recommended? Need minimum of 3 ethernet ports. Thanks in advance.
subscribe misc@openbsd.org
subscribe misc@openbsd.org
Cannot PXE Boot PC Engines APU.1D4
Cannot PXE Boot PC Engines APU.1D4 Have tried both i386 and amd64. Verified that my tftpd server is working. This used to work. Now fails. Hardware is about 10 years old. Do I need new hardware?? What is recommended? Need minimum of 3 ethernet ports. Thanks in advance.
subscribe misc@OpenBSD.org
subscribe misc@OpenBSD.org
subscribe misc@OpenBSD.org
subscribe misc@OpenBSD.org
Re: keyboad left ALT not working on console - thinkpad t410
What does xev say? On Tuesday, February 7, 2023, 05:54:58 AM EST, Luca Ferrari wrote: Hi all, running 7.2, I don't understand how to configure wscons because my left alt key does not work on console. wsconsctl reports keyboard.type=pc-xt When I press ALT it seems it turns UTF-8 on to print a codepoint. I'm using a lenovo thinkpad t410. Any idea? Thanks, Luca
Re: CyberPower cp1500PPFCLCD
--- On Sunday, November 13, 2022, 01:56:12 PM EST, Peter Fraser wrote: > I replace it with a new CyberPower cp1500PPFCLCD. You poor bastard. If this company has anything to do with the CyberPower PC that I bought a PC from a few years ago, you made a big mistake in buying from them. The motherboard on my PC started failing about 6 months after I bought it. The first video slot failed. Then later, the other video slot failed. In order to "honor their warranty", the company was going to make me go without my computer for 3 months. About a week (or maybe two) to ship it to California, a couple of months for them to repair it and test it, and another week (or maybe two) *at my expense* to ship it back to me. I bought another motherboard and fixed it myself. If you look at the comments online about this company, about half of them say this is the best company ever. The other half are horror stories like mine. I think the first half are all false and astro-turfed. The best response is never to have anything to do with this company ever again, and spread the word about just how horrible they are. Sorry to hear about your horrible experience. PS Don't believe any positive reviews. Nobody goes out of their way to post a positive review when things are working. On the other hand, they will post a negative review when things don't go well. Those are the believable reviews.
OpenBSD 6.8 Errata 019 Failed
configure: error: source directory already configured; run "make distclean" there first *** Error 1 in . (/usr/X11R6/share/mk/bsd.xorg.mk:158 'config.status') *** Error 2 in /usr/xenocara/lib/libX11 (/usr/X11R6/share/mk/bsd.xorg.mk:196 'build') I don't understand what the error message is telling me to do. Nothing I have tried has worked. My source tree is up to date. What directory do I have to run `make distclean' in? Thanks, Ken
Re: 6.8 Install Issue
--- On Saturday, February 27, 2021, 12:09:45 AM EST, wrote: > I'm confused as to how you're capable of sending emails when you haven't > installed your system. I have more than one computer.
Re: 6.8 Install Issue
I physically removed the SSD mSATA disk, and re-inserted it.
Then I started the install procedure again, and partitioned it, and disklabeled
it.
It is now working, wanting to install the sets.
So apparently, I had some type of hardware failure.
On Friday, February 26, 2021, 10:09:14 PM EST, Kenneth Hendrickson
wrote:
Another 6.8 install failure.
What specifically does "disklabel: DIOCWDINFO: Device busy" mean at the end of
disklabel???
Does it mean I have hardware failure???
When I let OpenBSD 6.8 partition the disk and use the default disklabel, I get:
Available disks are: sd0 sd1.
Which disk is the root disk? ('?' for details) [sd0]
Disk: sd0 geometry: 15566/255/63 [250069680 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
---
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: DA 0 1 1 - 7782 254 63 [ 63: 125033832 ]
*3: A6 7783 1 1 - 15565 254 63 [ 125033958: 125033832 ] OpenBSD
Use (W)hole disk MBR, whole disk (G)PT, (O)penBSD area or (E)dit? [OpenBSD] W
Setting OpenBSD MBR partition to whole sd0...done.
The auto-allocated layout for sd0 is:
# size offset fstype [fsize bsize cpg]
a: 1.0G 64 4.2BSD 2048 16384 1 # /
b: 4.2G 2097216 swap
c: 119.2G 0 unused
d: 4.0G 10912064 4.2BSD 2048 16384 1 # /tmp
e: 11.9G 19300640 4.2BSD 2048 16384 1 # /var
f: 6.0G 44270336 4.2BSD 2048 16384 1 # /usr
g: 1.0G 56853248 4.2BSD 2048 16384 1 # /usr/X11R6
h: 17.3G 58950400 4.2BSD 2048 16384 1 # /usr/local
i: 2.0G 95245440 4.2BSD 2048 16384 1 # /usr/src
j: 6.0G 99439744 4.2BSD 2048 16384 1 # /usr/obj
k: 65.8G 112022656 4.2BSD 2048 16384 1 # /home
Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a]
disklabel: DIOCWDINFO: Device busy
Disk: sd0 geometry: 15566/255/63 [250069680 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
---
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
*3: A6 0 1 2 - 15565 254 63 [ 64: 250067726 ] OpenBSD
Use (W)hole disk MBR, whole disk (G)PT, (O)penBSD area or (E)dit? [OpenBSD] W
Setting OpenBSD MBR partition to whole sd0...done.
The auto-allocated layout for sd0 is:
# size offset fstype [fsize bsize cpg]
a: 1.0G 64 4.2BSD 2048 16384 1 # /
b: 4.2G 2097216 swap
c: 119.2G 0 unused
d: 4.0G 10912064 4.2BSD 2048 16384 1 # /tmp
e: 11.9G 19300640 4.2BSD 2048 16384 1 # /var
f: 6.0G 44270336 4.2BSD 2048 16384 1 # /usr
g: 1.0G 56853248 4.2BSD 2048 16384 1 # /usr/X11R6
h: 17.3G 58950400 4.2BSD 2048 16384 1 # /usr/local
i: 2.0G 95245440 4.2BSD 2048 16384 1 # /usr/src
j: 6.0G 99439744 4.2BSD 2048 16384 1 # /usr/obj
k: 65.8G 112022656 4.2BSD 2048 16384 1 # /home
Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] a
disklabel: DIOCWDINFO: Device busy
Disk: sd0 geometry: 15566/255/63 [250069680 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
---
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
*3: A6 0 1 2 - 15565 254 63 [ 64: 250067726 ] OpenBSD
Use (W)hole disk MBR, whole disk (G)PT, (O)penBSD area or (E)dit? [OpenBSD]
On Friday, February 26, 2021, 09:26:40 PM EST, Theo de Raadt
wrote:
Kenneth Hendrickson wrote:
> Thanks again Theo.
>
> > WARNING: / was not properly unmounted
>
> That is true for the disk in that system.
You don't understand the OpenBSD installed. That / is the root filesystem
of the install-tool fileysystem inside the bsd.rd
It is corrupt. Someone wrote to it. Whatever happpened to the bsd.rd
you used is outside our control, because it has been modified.
Re: 6.8 Install Issue
Another 6.8 install failure.
What specifically does "disklabel: DIOCWDINFO: Device busy" mean at the end of
disklabel???
Does it mean I have hardware failure???
When I let OpenBSD 6.8 partition the disk and use the default disklabel, I get:
Available disks are: sd0 sd1.
Which disk is the root disk? ('?' for details) [sd0]
Disk: sd0 geometry: 15566/255/63 [250069680 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
---
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: DA 0 1 1 - 7782 254 63 [ 63: 125033832 ]
*3: A6 7783 1 1 - 15565 254 63 [ 125033958: 125033832 ] OpenBSD
Use (W)hole disk MBR, whole disk (G)PT, (O)penBSD area or (E)dit? [OpenBSD] W
Setting OpenBSD MBR partition to whole sd0...done.
The auto-allocated layout for sd0 is:
# size offset fstype [fsize bsize cpg]
a: 1.0G 64 4.2BSD 2048 16384 1 # /
b: 4.2G 2097216 swap
c: 119.2G 0 unused
d: 4.0G 10912064 4.2BSD 2048 16384 1 # /tmp
e: 11.9G 19300640 4.2BSD 2048 16384 1 # /var
f: 6.0G 44270336 4.2BSD 2048 16384 1 # /usr
g: 1.0G 56853248 4.2BSD 2048 16384 1 # /usr/X11R6
h: 17.3G 58950400 4.2BSD 2048 16384 1 # /usr/local
i: 2.0G 95245440 4.2BSD 2048 16384 1 # /usr/src
j: 6.0G 99439744 4.2BSD 2048 16384 1 # /usr/obj
k: 65.8G 112022656 4.2BSD 2048 16384 1 # /home
Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a]
disklabel: DIOCWDINFO: Device busy
Disk: sd0 geometry: 15566/255/63 [250069680 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
---
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
*3: A6 0 1 2 - 15565 254 63 [ 64: 250067726 ] OpenBSD
Use (W)hole disk MBR, whole disk (G)PT, (O)penBSD area or (E)dit? [OpenBSD] W
Setting OpenBSD MBR partition to whole sd0...done.
The auto-allocated layout for sd0 is:
# size offset fstype [fsize bsize cpg]
a: 1.0G 64 4.2BSD 2048 16384 1 # /
b: 4.2G 2097216 swap
c: 119.2G 0 unused
d: 4.0G 10912064 4.2BSD 2048 16384 1 # /tmp
e: 11.9G 19300640 4.2BSD 2048 16384 1 # /var
f: 6.0G 44270336 4.2BSD 2048 16384 1 # /usr
g: 1.0G 56853248 4.2BSD 2048 16384 1 # /usr/X11R6
h: 17.3G 58950400 4.2BSD 2048 16384 1 # /usr/local
i: 2.0G 95245440 4.2BSD 2048 16384 1 # /usr/src
j: 6.0G 99439744 4.2BSD 2048 16384 1 # /usr/obj
k: 65.8G 112022656 4.2BSD 2048 16384 1 # /home
Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] a
disklabel: DIOCWDINFO: Device busy
Disk: sd0 geometry: 15566/255/63 [250069680 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
---
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
*3: A6 0 1 2 - 15565 254 63 [ 64: 250067726 ] OpenBSD
Use (W)hole disk MBR, whole disk (G)PT, (O)penBSD area or (E)dit? [OpenBSD]
On Friday, February 26, 2021, 09:26:40 PM EST, Theo de Raadt
wrote:
Kenneth Hendrickson wrote:
> Thanks again Theo.
>
> > WARNING: / was not properly unmounted
>
> That is true for the disk in that system.
You don't understand the OpenBSD installed. That / is the root filesystem
of the install-tool fileysystem inside the bsd.rd
It is corrupt. Someone wrote to it. Whatever happpened to the bsd.rd
you used is outside our control, because it has been modified.
Re: 6.8 Install Issue
This does not look normal to me: PcEngines2# ls -Fla / total 12564133706863018 drwxr-xr-x 11 root wheel 512 Oct 5 00:17 ./ drwxr-xr-x 11 root wheel 512 Oct 5 00:17 ../ -rw-r--r-- 1 root wheel 1480 Oct 5 00:17 .profile lrwxr-xr-x 1 root wheel 11 Oct 5 00:17 autoinsb drwxr-xr-x 2 root wheel 512 Oct 5 00:17 bin/ drwxr-xr-x 2 root wheel 2048 Feb 27 02:41 dev/ drwxr-xr-x 5 root wheel 512 Feb 27 02:39 etc/ lrwxr-xr-x 1 root wheel 11 Oct 5 00:17 installb -rw-r--r-- 1 root wheel 2906 Oct 5 00:17 installd -rwxr-xr-x 1 root wheel 59228 Oct 5 00:17 install* crw-rw-rw- 1 root wheel 0, 0 Jan 1 1970 mnt drwxr-xr-x 2 root wheel 512 Oct 5 00:17 mnt2/ drwxr-xr-x 2 root wheel 1024 Oct 5 00:17 sbin/ drwxrwxrwt 4 root wheel 512 Feb 27 02:42 tmp/ lrwxr-xr-x 1 root wheel 11 Oct 5 00:17 upgradeb drwxr-xr-x 6 root wheel 512 Oct 5 00:17 usr/ drwxr-xr-x 6 root wheel 512 Oct 5 00:17 var/ How did mnt become a character device?? Note: This was after the failed install, and I said "no", do not continue. On Friday, February 26, 2021, 09:32:42 PM EST, Kenneth Hendrickson wrote: Thanks again. Here is the sha256 of bsd.rd: 106 King$ sha256sum bsd.rd 9fb54e358cbc716b86acff277af176d534a039257c81b802bdc74c93ca48adf3 bsd.rd 47 PcEngines1# sha256 bsd.rd SHA256 (bsd.rd) = 9fb54e358cbc716b86acff277af176d534a039257c81b802bdc74c93ca48adf3 On Friday, February 26, 2021, 09:26:40 PM EST, Theo de Raadt wrote: Kenneth Hendrickson wrote: > Thanks again Theo. > > > WARNING: / was not properly unmounted > > That is true for the disk in that system. You don't understand the OpenBSD installed. That / is the root filesystem of the install-tool fileysystem inside the bsd.rd It is corrupt. Someone wrote to it. Whatever happpened to the bsd.rd you used is outside our control, because it has been modified.
Re: 6.8 Install Issue
Thanks again. Here is the sha256 of bsd.rd: 106 King$ sha256sum bsd.rd 9fb54e358cbc716b86acff277af176d534a039257c81b802bdc74c93ca48adf3 bsd.rd 47 PcEngines1# sha256 bsd.rd SHA256 (bsd.rd) = 9fb54e358cbc716b86acff277af176d534a039257c81b802bdc74c93ca48adf3 On Friday, February 26, 2021, 09:26:40 PM EST, Theo de Raadt wrote: Kenneth Hendrickson wrote: > Thanks again Theo. > > > WARNING: / was not properly unmounted > > That is true for the disk in that system. You don't understand the OpenBSD installed. That / is the root filesystem of the install-tool fileysystem inside the bsd.rd It is corrupt. Someone wrote to it. Whatever happpened to the bsd.rd you used is outside our control, because it has been modified.
Re: 6.8 Install Issue
Thanks again Theo. > WARNING: / was not properly unmounted That is true for the disk in that system. But I booted from the 6.8 bsd.rd via PXE. On Friday, February 26, 2021, 09:21:21 PM EST, Theo de Raadt wrote: Kenneth Hendrickson wrote: > Thanks Theo. > > Here is what happened beforehand: > > Welcome to the OpenBSD/amd64 6.8 installation program. > WARNING: / was not properly unmounted I have no idea what is going on here, but this never happens with an OpenBSD install image. The mr.fs inside the bsd.rd is always clean. This is not normal, and hints that you have changed something.
Re: 6.8 Install Issue
(enter '?' for help at any prompt) sd0> p OpenBSD area: 125033958-250067790; size: 125033832; free: 28 # size offset fstype [fsize bsize cpg] a: 2104480 133435904 4.2BSD 2048 16384 1 b: 8401932 125033958 swap c: 250069680 0 unused d: 2104512 135540384 4.2BSD 2048 16384 1 e: 4209024 137644896 4.2BSD 2048 16384 12960 f: 4209056 141853920 4.2BSD 2048 16384 12960 g: 4209024 146062976 4.2BSD 2048 16384 1 h: 5365696 244702080 4.2BSD 2048 16384 12960 i: 125033832 63 unknown j: 2104512 150272000 4.2BSD 2048 16384 12960 k: 10490432 152376512 4.2BSD 2048 16384 12960 l: 2104512 162866944 4.2BSD 2048 16384 12960 m: 2104544 164971456 4.2BSD 2048 16384 12960 n: 58733632 167076000 4.2BSD 2048 16384 12960 o: 16787904 225809632 4.2BSD 2048 16384 12960 p: 2104544 242597536 4.2BSD 2048 16384 12960 sd0> n a mount point: [none] / sd0> n e mount point: [none] /tmp sd0> n f mount point: [none] /var sd0> n h mount point: [none] /home sd0> n j mount point: [none] /root sd0> n k mount point: [none] /var/crash sd0> n l mount point: [none] /var/log sd0> n m mount point: [none] /var/mail sd0> n n mount point: [none] /usr sd0> n o mount point: [none] /usr/obj sd0> n p mount point: [none] /usr/local/src sd0> p OpenBSD area: 125033958-250067790; size: 125033832; free: 28 # size offset fstype [fsize bsize cpg] a: 2104480 133435904 4.2BSD 2048 16384 1 # / b: 8401932 125033958 swap c: 250069680 0 unused d: 2104512 135540384 4.2BSD 2048 16384 1 e: 4209024 137644896 4.2BSD 2048 16384 12960 # /tmp f: 4209056 141853920 4.2BSD 2048 16384 12960 # /var g: 4209024 146062976 4.2BSD 2048 16384 1 h: 5365696 244702080 4.2BSD 2048 16384 12960 # /home i: 125033832 63 unknown j: 2104512 150272000 4.2BSD 2048 16384 12960 # /root k: 10490432 152376512 4.2BSD 2048 16384 12960 # /var/crash l: 2104512 162866944 4.2BSD 2048 16384 12960 # /var/log m: 2104544 164971456 4.2BSD 2048 16384 12960 # /var/mail n: 58733632 167076000 4.2BSD 2048 16384 12960 # /usr o: 16787904 225809632 4.2BSD 2048 16384 12960 # /usr/obj p: 2104544 242597536 4.2BSD 2048 16384 12960 # /usr/local/c sd0> ? Available commands: ? | h - show help n [part] - set mount point A - auto partition all space p [unit] - print partitions a [part] - add partition q - quit & save changes b - set OpenBSD boundaries R [part] - resize auto allocated partition c [part] - change partition size r - display free space D - reset label to default s [path] - save label to file d [part] - delete partition U - undo all changes e - edit drive parameters u - undo last change g [d|u] - [d]isk or [u]ser geometry w - write label to disk i - modify disklabel UID X - toggle expert mode l [unit] - print disk label header x - exit & lose changes M - disklabel(8) man page z - delete all partitions m [part] - modify partition Suffixes can be used to indicate units other than sectors: 'b' (bytes), 'k' (kilobytes), 'm' (megabytes), 'g' (gigabytes) 't' (terabytes) 'c' (cylinders), '%' (% of total disk), '&' (% of free space). Values in non-sector units are truncated to the nearest cylinder boundary. sd0> w sd0> q No label changes. newfs: /dev/rsd0a is mounted on /mnt /dev/rsd0h: 2620.0MB in 5365696 sectors of 512 bytes 13 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0j: 1027.6MB in 2104512 sectors of 512 bytes 6 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0e: 2055.2MB in 4209024 sectors of 512 bytes 11 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0n: 28678.5MB in 58733632 sectors of 512 bytes 142 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0p: 1027.6MB in 2104544 sectors of 512 bytes 6 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0o: 8197.2MB in 16787904 sectors of 512 bytes 41 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0f: 2055.2MB in 4209056 sectors of 512 bytes 11 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0k: 5122.3MB in 10490432 sectors of 512 bytes 26 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0l: 1027.6MB in 2104512 sectors of 512 bytes 6 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0m: 1027.6MB in 2104544 sectors of 512 bytes 6 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each Available disks are: sd1. Which disk do you wish to initialize? (or 'done') [done] On Friday, February 26, 2021, 09:05:52 PM EST, Theo de Raadt wrote: Kenneth Hendrickson wrote: ... > No label changes. > newfs: /dev/rsd0a is mounted on /mnt ^^^ Well you had that partition mounted, probably with a different disklabel and sizes, so it was not newfs'd. You did something manual earlier. You didn't show that which created the problem.
6.8 Install Issue
After making the filesystems, I get error messages: sd0> p OpenBSD area: 125033958-250067790; size: 125033832; free: 28 #size offset fstype [fsize bsize cpg] a: 2104480133435904 4.2BSD 2048 16384 1 # / b: 8401932125033958swap c:2500696800 unused d: 2104512135540384 4.2BSD 2048 16384 1 e: 4209024137644896 4.2BSD 2048 16384 12960 # /tmp f: 4209056141853920 4.2BSD 2048 16384 12960 # /var g: 4209024146062976 4.2BSD 2048 16384 1 h: 5365696244702080 4.2BSD 2048 16384 12960 # /home i:125033832 63 unknown j: 2104512150272000 4.2BSD 2048 16384 12960 # /root k: 10490432152376512 4.2BSD 2048 16384 12960 # /var/crash l: 2104512162866944 4.2BSD 2048 16384 12960 # /var/log m: 2104544164971456 4.2BSD 2048 16384 12960 # /var/mail n: 58733632167076000 4.2BSD 2048 16384 12960 # /usr o: 16787904225809632 4.2BSD 2048 16384 12960 # /usr/obj p: 2104544242597536 4.2BSD 2048 16384 12960 # /usr/local/c sd0> ? Available commands: ? | h- show help n [part] - set mount point A- auto partition all space p [unit] - print partitions a [part] - add partition q- quit & save changes b- set OpenBSD boundariesR [part] - resize auto allocated partition c [part] - change partition size r- display free space D- reset label to defaults [path] - save label to file d [part] - delete partition U- undo all changes e- edit drive parameters u- undo last change g [d|u] - [d]isk or [u]ser geometry w- write label to disk i- modify disklabel UID X- toggle expert mode l [unit] - print disk label header x- exit & lose changes M- disklabel(8) man page z- delete all partitions m [part] - modify partition Suffixes can be used to indicate units other than sectors: 'b' (bytes), 'k' (kilobytes), 'm' (megabytes), 'g' (gigabytes) 't' (terabytes) 'c' (cylinders), '%' (% of total disk), '&' (% of free space). Values in non-sector units are truncated to the nearest cylinder boundary. sd0> w sd0> q No label changes. newfs: /dev/rsd0a is mounted on /mnt /dev/rsd0h: 2620.0MB in 5365696 sectors of 512 bytes 13 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0j: 1027.6MB in 2104512 sectors of 512 bytes 6 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0e: 2055.2MB in 4209024 sectors of 512 bytes 11 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0n: 28678.5MB in 58733632 sectors of 512 bytes 142 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0p: 1027.6MB in 2104544 sectors of 512 bytes 6 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0o: 8197.2MB in 16787904 sectors of 512 bytes 41 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0f: 2055.2MB in 4209056 sectors of 512 bytes 11 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0k: 5122.3MB in 10490432 sectors of 512 bytes 26 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0l: 1027.6MB in 2104512 sectors of 512 bytes 6 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each /dev/rsd0m: 1027.6MB in 2104544 sectors of 512 bytes 6 cylinder groups of 202.50MB, 12960 blocks, 25920 inodes each Available disks are: sd1. Which disk do you wish to initialize? (or 'done') [done] /dev/sd0a on /mnt type ffs (local, read-only) mkdir: /mnt: Not a directory mount: realpath /mnt/home: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/root: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/tmp: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/usr: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/usr/local/src: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/usr/obj: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/var: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/var/crash: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/var/log: Not a directory mkdir: /mnt: Not a directory mount: realpath /mnt/var/mail: Not a directory WARNING! The following filesystems were not properly mounted: /mnt/home (de5701386a9f9155.h) /mnt/root (de5701386a9f9155.j) /mnt/tmp (de5701386a9f9155.e) /mnt/usr (de5701386a9f9155.n) /mnt/usr/local/src (de5701386a9f9155.p) /mnt/usr/obj (de5701386a9f9155.o) /mnt/var (de5701386a9f9155.f) /mnt/var/crash (de5701386a9f9155.k) /mnt/var/log (de5701386a9f9155.l)
Build and Install Userland on -stable ??
I have installed 6.7. I have `cvs up'dated to the stable 6.7 branch (-rOPENBSD_6_7). I have rebuilt and installed a new kernel, and rebooted. I have rebuilt everything with errata, installed it, and rebooted. I would now like to re-build and install all of userland. But, I do not want to install anything in /etc, /var, or /dev. I am following the instructions in Step 2 of https://man.OpenBSD.org/release The instructions are not entirely clear to me. Will `make build' install all of userland, without modifying anything in /etc, /var, or /dev ? Will `make install', after `make build', do that? Thanks, Ken
Build Problem in Unbound
What happened previously: Installed 6.7 Installed firmware Fetched source from 6.7 stable Built everything in syspatch 001-013 Installed everything in syspatch 001-013 Rebooted Built kernel Rebooted In trying to build userland, I encountered the following: ... ===> usr.sbin/trpt ===> usr.sbin/unbound make make: don't know how to make config.h (prerequisite of: dns.lo) Stop in usr.sbin/unbound/obj *** Error 2 in usr.sbin/unbound (Makefile.bsd-wrapper:49 'gnu') *** Error 2 in usr.sbin (:48 'all': @for entry in ac accton acme-client acpidump adduser amd apm apmd arp authpf bgpctl bgpd...) *** Error 2 in /usr/src (:48 'all': @for entry in lib include bin libexec sbin usr.bin usr.sbin share games gnu sys; do set ...) How do I get past this? What did I do wrong? Thanks, Ken
