On Jan 11 01:35:20, p...@jbechtel.de wrote:
> TL;DR - maybe the reason is some bad interaction between Linux mount
> with wrong -o ufstype=old with following BSD auto-fsck on boot?
I don't suppose linux's mount of a wrong type
or obsd's autofsck would wipe the filesystem clean.
> > > What also ma
Hello,
On 2024/01/10 11:41:01 +, Ioan Samarul wrote:
> Hello to you all!
>
> I am trying to define mappings in cwmrc for some of my scripts. If I
> use the full path (/home/user/bin/someScript) they work as expected,
> but if I use something like $HOME/bin/someScript cwm does not
> recognize
On Thu, Jan 11, 2024 at 02:39:45PM +0100, Jan Stary wrote:
> I don't think you rm-rf'd your directory;
> I suspect you simply newfs'd a new FS in its place.
You can probably answer that question with a good degree of certainty by
checking whether it's now FFS1 or FFS2.
The old filesystem original
Has anyone tried these HUNSN mini pcs/routers with multiple interfaces?
I'm thinking of getting one for home routing. Does it work with OpenBSD?
(dmesg?)
Performance? Will it route/firewall at 1Gbps? Intel N100 seems to be low on TDP
and gives numbers.
Any problems with I226? I've read about i
> Jan 9 07:10:24 stable relayd[29792]: relay wwwtls, session 1 (1 active),
> fqdn1, 127.0.0.1 -> 127.0.0.1:8080, done, GET -> 127.0.0.1:8080;
> Jan 9 07:10:25 stable relayd[28442]: relay wwwtls, session 1 (1 active),
> fqdn2, 127.0.0.1 -> 127.0.0.1:8081, done, GET -> 127.0.0.1:8081;
> Jan 9 07
>
>
> On 12/28/23 12:30, Michael Hekeler wrote:
> >
> > I try to install OpenBSD on netcup ARM, too...
> >
> > > I disabled the pluart driver in the ramdisk kernel (on a other machine
> > > with
> > > config -e -f /bsd.rd and copied the ramdisk kernel over to the nectup
> > > server) and got a
On Wed, Jan 10, 2024 at 7:44 PM Jonas Bechtel wrote:
> After mounting with right ufstype, I saw right data. (Probably this is
> what I remember. Files in root directory looked well there)
>
> In installation I went to manual disklabel edit. One of the steps there
> was to assign the mount point /
Em qui., 11 de jan. de 2024 às 13:35, Michael Hekeler
escreveu:
>
> > Jan 9 07:10:24 stable relayd[29792]: relay wwwtls, session 1 (1 active),
> > fqdn1, 127.0.0.1 -> 127.0.0.1:8080, done, GET -> 127.0.0.1:8080;
> > Jan 9 07:10:25 stable relayd[28442]: relay wwwtls, session 1 (1 active),
> > f
> Take a look at the example in man relayd.conf. You have to set the X-header
> like:
>
> match header set "X-Forwarded-For" \ value "$REMOTE_ADDR"
> match header set "X-Forwarded-By" \ value
> "$SERVER_ADDR:$SERVER_PORT"
This has nothing to do with relayd's forwarding r
9 matches
Mail list logo
