Re: syntax error in httpd.conf file
"Luca Leone" writes: I could not find much online on how to write these two guys: httpd.conf and relayd.conf On OpenBSD, the first places to check for documentation are: * the man(ual) pages, which can be accessed from the command line, e.g. $ man httpd.conf $ man relayd.conf but which can also be accessed online: https://man.openbsd.org/httpd.conf.5 https://man.openbsd.org/relayd.conf.5 * and the FAQ: https://www.openbsd.org/faq/ and a bit surprinsigly - at least to me - chatgpt didn't get the syntax right either, no matter how detailed my prompt was. Not at all surprising to me, given that ChatGPT and other LLM-based 'AI' systems - essentially Markov chains / glorified autocorrect - are increasingly known for 'hallucinations' and confidently making false claims. i have a boatload of links about this stuff, but here are a couple of examples: * ChatGPT claims that the _whistleblower_ of a bribery scandal was a guilty party: https://www.abc.net.au/news/2023-04-06/hepburn-mayor-flags-legal-action-over-false-chatgpt-claims/102195610 * Meta Chatbot claims to have a child in school: https://www.abc.net.au/news/2024-04-19/meta-releases-llama-3-ai-model/103744538 Alexis.
Re: Fonts for wscons(4)
On Fri Apr 19 15:02:49 2024 Stuart Henderson wrote: > On 2024-04-19, Walter A Iglesias wrote: > > I designed some fonts for wscons(4). Once you decompress the tar file > > you'll find a test.sh script to test the fonts in a fullscreen xterm. I > > include the *.h files to try them in wscons, but you have to recompile > > the kernel for this. > > > > https://en.roquesor.com/Downloads/ape.tar.gz > > Fonts are loadable at runtime, see the terminus-font package for some details. > I thought that wasn't possible under drm(4), but choosing the right size I could load the terminus font (12x24 in my case). What I couldn't do is to correctly convert the bdf file to raw. I've tried first exporting from bdf to psf using gbdfont and then psf2raw, but when I load the font wscons shows garbage. -- To send this message I'm using my patched version of OpenBSD mail(1).
Re: Fonts for wscons(4)
On 2024-04-19, Walter A Iglesias wrote: > I designed some fonts for wscons(4). Once you decompress the tar file > you'll find a test.sh script to test the fonts in a fullscreen xterm. I > include the *.h files to try them in wscons, but you have to recompile > the kernel for this. > > https://en.roquesor.com/Downloads/ape.tar.gz Fonts are loadable at runtime, see the terminus-font package for some details.
Re: syntax error in httpd.conf file
WOW!
it works, super happy right now, after many (interesting) hours trying to make
it work with a lot of not-so-useful help from chatgpt ;)
Maybe then I will not leave openBSD... I simply have to improve my skills :)
Thanks Kirill!!!
Any good resourse you'd like to point me to, to improve on this stuff? I know
you guessed it by now: I have almost zero knowledge on the server side of
things :)
I could not find much online on how to write these two guys: httpd.conf and
relayd.conf, and a bit surprinsigly - at least to me - chatgpt didn't get the
syntax right either, no matter how detailed my prompt was.
On Fri, Apr 19, 2024, at 2:01 PM, Kirill A. Korinsky wrote:
> On Fri, 19 Apr 2024 13:30:47 +0200,
> Luca Leone wrote:
> >
> > I'll keep working on it, but after a couple of days spent on this stuff I'm
> > starting to think that maybe to serve my node app there should be an easier
> > way than openbsd ;)
> >
>
> I guess you mean someting like that?
>
> table { 127.0.0.1 }
>
> http protocol https {
> match request header append "X-Forwarded-For" value "$REMOTE_ADDR"
>
> tls keypair birbi.biz:443
> pass request forward to
> }
>
> relay https {
> listen on egress port https tls
> protocol https
>
> forward to port 3000
> }
>
> --
> wbr, Kirill
>
Re: Fonts for wscons(4)
Interesting, thanks. Could you give us a screenshot to see them? Regards, --ext Walter A. Iglesias írta 2024. ápr.. 19, P-n 14:24 órakor: > I designed some fonts for wscons(4). Once you decompress the tar file > you'll find a test.sh script to test the fonts in a fullscreen xterm. I > include the *.h files to try them in wscons, but you have to recompile > the kernel for this. > > https://en.roquesor.com/Downloads/ape.tar.gz > > > -- > To send this message I'm using my patched version of OpenBSD mail(1). -- --Z--
I betrayed myself :-)
I wanted to show off by sending the message from my patched mail(1) but I forgot that I had just run sysupgrade, ha, ha. Now I am using the patched version of mail(1). ;-)
Fonts for wscons(4)
I designed some fonts for wscons(4). Once you decompress the tar file you'll find a test.sh script to test the fonts in a fullscreen xterm. I include the *.h files to try them in wscons, but you have to recompile the kernel for this. https://en.roquesor.com/Downloads/ape.tar.gz -- To send this message I'm using my patched version of OpenBSD mail(1).
Re: syntax error in httpd.conf file
On Fri, 19 Apr 2024 13:30:47 +0200,
Luca Leone wrote:
>
> I'll keep working on it, but after a couple of days spent on this stuff I'm
> starting to think that maybe to serve my node app there should be an easier
> way than openbsd ;)
>
I guess you mean someting like that?
table { 127.0.0.1 }
http protocol https {
match request header append "X-Forwarded-For" value "$REMOTE_ADDR"
tls keypair birbi.biz:443
pass request forward to
}
relay https {
listen on egress port https tls
protocol https
forward to port 3000
}
--
wbr, Kirill
Re: syntax error in httpd.conf file
wonderful, thanks Omar!
somehow I missed it! my bad.
I wrote a basic relayd.conf, which of course doesn't work.
http protocol "http" {
match request header set "X-Forwarded-For" value "$REMOTE_ADDR"
}
relay "web" {
listen on 0.0.0.0 port 443 tls
protocol "http"
forward to 127.0.0.1 port 3000
tls {
certificate "/etc/ssl/birbi.biz:443.crt"
key "/etc/ssl/private/birbi.biz:443.key"
}
}
I'll keep working on it, but after a couple of days spent on this stuff I'm
starting to think that maybe to serve my node app there should be an easier way
than openbsd ;)
On Fri, Apr 19, 2024, at 12:50 AM, Omar Polo wrote:
> Hello,
>
> On 2024/04/18 22:29:55 +0200, "Luca Leone" wrote:
> > Hi guys!
> >
> > [...]
> >
> > If is change `pass to "http://localhost:3000/"` with a simple `root
> > "/var/www/htdocs"` directive,
> > the syntax check is OK.
> >
> > The reason for the `pass to "http://localhost:3000/"` directive is that I
> > am running a node app on
> > /home/luca/node-app, and I want to forward requests to that server.
> >
> > Any idea on what I am missing?
>
> httpd doesn't support forwarding requests to another HTTP server sadly.
> It only supports FastCGI, or serving static files. `pass to' is not
> part of the httpd' configuration language.
>
> take a look at relayd(8) for proxying requests.
>
>
> Cheers,
>
> Omar Polo
>
Re: multi-package ports make
On 2024-04-18, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> --- =_aa0
> Content-Type: text/plain; charset="us-ascii"
> Content-ID: <53906.171346683...@orthanc.ca>
> Content-Transfer-Encoding: quoted-printable
>
> Can somebody tell me what I'm doing wrong here. When I run
> 'make' against this makefile it blows up with:
>
> Fatal: WRKDIR ends with a slash: /usr/ports/pobj/ (in hush/hush-proxyctl)
> Fatal: WRKDIST ends with a slash: /usr/ports/pobj/ (in hush/hush-proxyctl)
> Fatal: WRKSRC ends with a slash: /usr/ports/pobj/ (in hush/hush-proxyctl)
> Fatal: WRKCONF ends with a slash: /usr/ports/pobj/ (in hush/hush-proxyctl)
> Fatal: WRKBUILD ends with a slash: /usr/ports/pobj/ (in hush/hush-proxyctl=
> )
> *** Error 1 in /usr/ports/hush/hush-proxyctl (/usr/ports/infrastructure/mk=
> /bsd.port.mk:3885 '.BEGIN': @exit 1)
>
> This is my first foray into MULTI_PACKAGE. This make template works
> for other non-MULTI_PACKAGE builds.
This would be better on ports@
That's unrelated to MULTI_PACKAGES, you are missing setting DISTNAME
(which can be done either directly, or indirectly via some other
variables).
go ports are fiddly enough, and there's no big chain of dependencies here
(the usual reason for splitting into multi packages), I think this would
be better as a single package.
> --- =_aa0
> Content-Type: text/plain; name="Makefile"; charset="us-ascii"
> Content-Description: Makefile
> Content-Disposition: attachment; filename="Makefile"
>
> COMMENT-main= DMZ proxy management and control
> COMMENT-server= DMZ proxy management daemon
> MAINTAINER= XXX
>
> V=1.0
> PKGNAME-main= hush-proxyctl-${V}
> PKGNAME-server= hush-proxyctld-${V}
> REVISION-main=0
> REVISION-server= 0
>
> CATEGORIES= hush
>
> MULTI_PACKAGES= -main -server
>
> PERMIT_PACKAGE= Yes
> NO_TEST= Yes
>
> BUILD_DEPENDS=lang/go
>
> pre-configure:
> mkdir -p ${WRKSRC}; cd ${.CURDIR}/files && cp -R . ${WRKSRC}
>
> do-build:
> cd ${WRKSRC}/proxyctl && go build proxyctl
> cd ${WRKSRC}/proxyctld && go build proxyctld
>
> .include
>
> --- =_aa0--
>
>
--
Please keep replies on the mailing list.
Re: OpenBSD Installation Doesn't Detect NVMe SSD, but Detects My USB Drives
On Fri, Apr 19, 2024 at 5:38 AM Stuart Longland wrote: > Not sure there's any such animal when the device is NVMe. NVMe directly > connects to the PCI Express bus, not to a SATA controller. > -- Because some BIOS/UEFI are coded by idiots. I tested fake-raid on one of my "high-end" MSI boards, and the only way for setting it up on NVME drives was to set SATA to RAID.
