Re: A minimal browser in base

2022-09-12 Thread Jason McIntyre
On Mon, Sep 12, 2022 at 03:43:30PM -0700, Lyndon Nerenberg (VE7TFX/VE6BBM) 
wrote:
> 
> Long ago and far away, the Berkeley distributions used to ship an
> assortment of system documentation in /usr/share/doc, including a
> general-purpose system administrators manual.
> 
> I guess people didn't want to update those, or maybe thought they
> were sacred relics, never to be touched.  But all the *BSDs dropped
> them, years ago.  I thought that was the wrong move; they should
> have been kept, along with a /usr/share/doc/README that noted they
> are historical, and therefore probably out of date.  Although I'm
> sure the vi documentation stands up to this day.
> 

hi.

we stopped installing them because many of them were falling out of date
and there wasn;t really the resources (or motivation) to update them.
however not all of them were removed. although no longer installed, some
of the better ones remain in the source tree. from a quick look:

/usr/src/usr.bin/gprof/PSD.doc
/usr/src/usr.bin/lex/PSD.doc
/usr/src/usr.bin/m4/PSD.doc
/usr/src/usr.bin/make/PSD.doc
/usr/src/usr.bin/yacc/PSD.doc
/usr/src/bin/csh/USD.doc
/usr/src/bin/ed/USD.doc
/usr/src/games/trek/USD.doc
/usr/src/usr.bin/awk/USD.doc
/usr/src/usr.bin/bc/USD.doc
/usr/src/usr.bin/dc/USD.doc
/usr/src/usr.bin/mail/USD.doc
/usr/src/usr.bin/sed/USD.doc
/usr/src/usr.bin/vi/docs/USD.doc
/usr/src/sbin/fsck_ffs/SMM.doc
/usr/src/usr.sbin/lpr/SMM.doc

jmc



Re: A minimal browser in base

2022-09-12 Thread prx
For what it's worth, I keep a downloadable copy of the FAQ : 

=> https://si3t.ch/pub/openbsd-faq/
=> https://si3t.ch/pub/openbsd-faq.tgz

html is dumped to txt to read with any pager.
One can keep it on a disk if necessary.

Regards.



Freeze/hang on arm64 when pushing smsc/usb

2022-09-12 Thread John Verne
(Sending this to misc@ because I'm not sure it falls within the
purview of arm@, but I can repost to there if that would be more
appropriate.)

I've been tracking snapshots on a RaspPi 3+ and it looks like a recent
snapshot may have introduced some issues with the USB bus.

I don't have a lot of detail to offer, unfortunately, because the
failure mode is so sudden and complete. The symptoms are that pushing
the smsc0 ethernet device a little (for example, when fetching sets as
part of a sysupgrade -s) ftp will report "-- stalled--", barf some
messages, and then eventually all ability to interact with the system
halts.

e.g, this is me simulating a sysupgrade download by directly fetching
the current snapshot base72.tgz package:

[...]
fnord# ftp https://openbsd.cs.toronto.edu/pub/OpenBSD/snapshots/arm64/base72.tgz
Trying 128.100.17.240...
Requesting https://openbsd.cs.toronto.edu/pub/OpenBSD/snapshots/arm64/base72.tgz
  3% |**
|  9984 KB02:03 ETAusbd_start_next: error=5
usbd_free_xfer: xfer=0xff8004b6b7e8 not free
smsc0: warning: Failed to write register 0x14
  4% |**
| 12032 KB02:22 ETA^C
fetch aborted.
fnord# sync
[...]

That cntrl-c and sync is a desperate attempt to tell the filesystems
to get their lives in order before their untimely demise. There was no
more console activity after that sync command. In many other attempts
(either with sysupgrade -s, or booting the snapshot bsd.rd and trying
[U]pgrade that way) a cntrl-c does nothing. At most, the fetch can be
aborted but we never get a prompt again.

I'm using the serial console via a USB serial device, and both the
disk and the ethernet is on the USB bus. So I don't know if the device
is actually hung or just inaccessible. It certainly has no network
link to the local DHCP server. A forced reboot always comes with a
long fsck.

If it matters, smsc0 and bwfm0 were trunked, and bwfm0 was forced to
use the lladdr of bwfm0. At one point I pulled the ethernet and tried
a sysupgrade -s with Wi-Fi only. No surprises that this worked without
any errors. But it was too slow to actually try and sysupgrade myself
out of this mess. I'm not sure this info matters, but I'm trying to
disclose anything that was different. This Pi has a third-party touch
HDMI screen attached, but xenodm is disabled (though both work when I
enable X). There is an Apple keyboard and mouse attached as well.

When I booted from the snapshot bsd.rd I also disconnected all the
unnecessary USB devices just in case one of the devices was causing a
problem. But this didn't change anything; once we got to part of the
upgrade where it wanted to fetch sets, the download would stall and
then the entire system appeared to hang.

Since the filesystem was getting a bit ragged from all the unscheduled
restarts (at one point man started returning the wrong pages; "man
ping" returned the page for pflogd, etc.) I decided to boot from
install71 and do a fresh install and all went well with no usb or smsc
log messages.

As a data point, I'm only drawing 8uA/5.6W (not including the USB
drive, which has its own power supply) on a known-good 3A supply. So I
don't think I'm pushing the power limits here.

I saved the last dmesg.boot it made with the snapshot before rebooting
to install a release:

OpenBSD 7.2 (GENERIC) #1747: Sun Sep 11 18:58:53 MDT 2022
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC
real mem  = 970924032 (925MB)
avail mem = 906727424 (864MB)
random: good seed from bootblocks
mainbus0 at root: Raspberry Pi 3 Model B Rev 1.2
cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 512KB 64b/line 16-way L2 cache
cpu0: CRC32,ASID16
apm0 at mainbus0
efi0 at mainbus0: UEFI 2.8
efi0: Das U-Boot rev 0x20211000
simplefb0 at mainbus0: 640x480, 32bpp
wsdisplay0 at simplefb0 mux 1
wsdisplay0: screen 0-5 added (std, vt100 emulation)
"system" at mainbus0 not configured
"axi" at mainbus0 not configured
simplebus0 at mainbus0: "soc"
bcmclock0 at simplebus0
bcmmbox0 at simplebus0
bcmgpio0 at simplebus0
bcmaux0 at simplebus0
bcmdmac0 at simplebus0: DMA0 DMA2 DMA4 DMA5 DMA8 DMA9 DMA10 DMA11
bcmintc0 at simplebus0
pluart0 at simplebus0: rev 2, 16 byte fifo
pluart0: console
bcmsdhost0 at simplebus0: 250 MHz base clock
sdmmc0 at bcmsdhost0: 4-bit, sd high-speed, mmc high-speed, dma
dwctwo0 at simplebus0
bcmdog0 at simplebus0
bcmrng0 at simplebus0
bcmtemp0 at simplebus0
"local_intc" at simplebus0 not configured
sdhc0 at simplebus0
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc1 at sdhc0: 4-bit, sd high-speed, mmc high-speed
"firmware" at simplebus0 not configured
"power" at simplebus0 not configured
"mailbox" at simplebus0 not configured
"gpiomem" at simplebus0 not configured
"fb" at simplebus0 not configured
"vcsm" at simplebus0 not configured
"virtgpio" at simplebus0 not configured
"clocks" at mainbus0 not configured
"phy" at mainbus0 not configured
"arm-pmu" at mainbus0 not configured
agtimer0 at

Re: A minimal browser in base

2022-09-12 Thread Josuah Demangeon
"Lyndon Nerenberg (VE7TFX/VE6BBM)"  wrote:
> Regardless, if someone does write a new "intro to sysadmin" document,

I really like to say to fresh new admins that if they want to learn everything
about system administration, find an OpenBSD system and type "help" in any 
shell,
then start reading from here and keep going.


HELP(1) General Commands ManualHELP(1)

NAME
 help – help for new users and administrators

DESCRIPTION
 This document is meant to familiarize new users and system administrators
 with OpenBSD and, if necessary, UNIX in general.

[...]



Re: A minimal browser in base

2022-09-12 Thread Lyndon Nerenberg (VE7TFX/VE6BBM)
Chris Bennett writes:
> I would instead recommend a new package with the critical newbie
> information included in text form.
> FAQ, anoncvs and ftp addresses, etc.

Long ago and far away, the Berkeley distributions used to ship an
assortment of system documentation in /usr/share/doc, including a
general-purpose system administrators manual.

I guess people didn't want to update those, or maybe thought they
were sacred relics, never to be touched.  But all the *BSDs dropped
them, years ago.  I thought that was the wrong move; they should
have been kept, along with a /usr/share/doc/README that noted they
are historical, and therefore probably out of date.  Although I'm
sure the vi documentation stands up to this day.

Ragardless, if someone does write a new "intro to sysadmin" document,
it should live in /usr/share/doc, and not an external package that
the new sysadmin might need to read to know how to install the
package that contains the documentation she needs to know how to
install the documentation she needs to know how to ... [SIGSEGV --
stack overflow]

--lyndon



Re: A minimal browser in base

2022-09-12 Thread Chris Bennett
I would instead recommend a new package with the critical newbie
information included in text form.
FAQ, anoncvs and ftp addresses, etc.

The first afterboot man page could suggest something like
pkg_add newuser_docs.

If you need or want it, just install it.

Sure, I install Lynx to look at the packages list to see what's new.
But honestly, who is really going to take the time to audit the code
before using it? What are you really going to be getting given all of
the DNS attacks and other risks (some new, never before seen threat
could appear at any time).
I really don't feel that recommending a browser from outside to a first
time user is appropriate. That really does require a lot of effort
better spent elsewhere.

My 2 cents.

-- 
Chris Bennett



Re: Yet Another Laptop Recommendation Thread

2022-09-12 Thread Christoff Humphries
Just ordered this from eBay after looking at jcs’ list again:
- Lenovo ThinkPad X1 Carbon 7th Gen i7-8565U 16GB RAM 512GB SSD 14" FHD Touch 
2019

Woot, back to OpenBSD as a daily driver again and looking forward to helping 
with ports and stuff.

I’m sure I violated some mailing list formatting rule, my bad. 


> On Sep 12, 2022, at 3:29 PM, Christoff Humphries 
>  wrote:
> 
> Hello all,
> 
>   I know we’ve all searched and I’ve searched a lot but can’t find 
> something reliably said much other than old Thinkpads and which hardware to 
> avoid, or folks suggesting laptops that may work.
> 
>   Can I get a modern recommendation for newer laptop? Looking to replace 
> my daily personal driver (2019 “16 MBP) and don’t want to carry a brick 
> around with me. I want to return back to OpenBSD after years. 
> 
>   I’m just not knowledgeable on computer hardware options and what’s out 
> there. I googled and perhaps looked at most threads by search misc@ archives 
> (2018 thread) and reddit/stackoverflow. 
> 
> 
>   Just looking for a list of laptops that folks personally use as daily 
> drivers that aren’t Thinkpad T420s like I have but is a tank brick. 
> 
>   Please don’t flame me, I’ve been searching the Internet for days and 
> unable to get a solid answer outside of jcs’ site and some other site where 
> people uploaded dmesgs and they were mostly really old Thinkpads.
> 
>   Anything light that “just works”? Price is not a limitation.
> 
> Thanks,
> Christoff



Re: Supermicro SYS-510T-MR PXE issues

2022-09-12 Thread Robert Klein
Does the machine have the correct “filename” set in your DHCP server? I
sometimes forget to change it from the BIOS file to the EFI one and get
about your result.

Best regards
Robert


On Mon, 12 Sep 2022 11:20:46 -0700
"Lyndon Nerenberg (VE7TFX/VE6BBM)"  wrote:

> We have one of the above (X12STH-SYS motherboard) that's refusing
> to PXE boot. It's connecting to DHCP and downloading the pxeboot
> file (according to tftpd), and the bios appears to be printing a
> message saying the boot image was successfully loaded, but it only
> stays on the screen for about 200ms before getting erased, so it's
> hard to be sure.  Anyway, immediately after printing that message
> the system immediately moves on to the next NIC and tries to PXE
> boot from it.
> 
> I'm curious if anyone has run into the same issue.  We're trying
> to figure out "why," and at this stage all we can think of is some
> setting in the BIOS is upsetting the machine to the point where it
> won't run the image.  But I'm stumped.  I've never seen anything
> like this before.
> 
> Anyone have any ideas?
> 
> --lyndon
> 



Yet Another Laptop Recommendation Thread

2022-09-12 Thread Christoff Humphries
Hello all,

I know we’ve all searched and I’ve searched a lot but can’t find 
something reliably said much other than old Thinkpads and which hardware to 
avoid, or folks suggesting laptops that may work.

Can I get a modern recommendation for newer laptop? Looking to replace 
my daily personal driver (2019 “16 MBP) and don’t want to carry a brick around 
with me. I want to return back to OpenBSD after years. 

I’m just not knowledgeable on computer hardware options and what’s out 
there. I googled and perhaps looked at most threads by search misc@ archives 
(2018 thread) and reddit/stackoverflow. 


Just looking for a list of laptops that folks personally use as daily 
drivers that aren’t Thinkpad T420s like I have but is a tank brick. 

Please don’t flame me, I’ve been searching the Internet for days and 
unable to get a solid answer outside of jcs’ site and some other site where 
people uploaded dmesgs and they were mostly really old Thinkpads.

Anything light that “just works”? Price is not a limitation.

Thanks,
Christoff



Supermicro SYS-510T-MR PXE issues

2022-09-12 Thread Lyndon Nerenberg (VE7TFX/VE6BBM)
We have one of the above (X12STH-SYS motherboard) that's refusing
to PXE boot. It's connecting to DHCP and downloading the pxeboot
file (according to tftpd), and the bios appears to be printing a
message saying the boot image was successfully loaded, but it only
stays on the screen for about 200ms before getting erased, so it's
hard to be sure.  Anyway, immediately after printing that message
the system immediately moves on to the next NIC and tries to PXE
boot from it.

I'm curious if anyone has run into the same issue.  We're trying
to figure out "why," and at this stage all we can think of is some
setting in the BIOS is upsetting the machine to the point where it
won't run the image.  But I'm stumped.  I've never seen anything
like this before.

Anyone have any ideas?

--lyndon