Re: S3 Virge support on IBM T23 for 6.6
Den tors 16 apr. 2020 kl 18:24 skrev Paolo Aglialoro : > Thanks Janne for the tech insight. > So, but for routerboards/CLI boxen, considering that this recent move > hinders GUI for most P3s, the really viable ones remain P3s/K7s with > different graphics boards (mostly desktop/tower) and early P4s without > em64t. If there was a huge userbase with tons of GUI i386s needing life support, then perhaps they can form a group and do the heavy lifting, since many hands make work light. If there is one box in a corner with S3 virge, then it can just stop updating and have a $25 box firewall it off the internet so you can get away with having it unpatched where it runs with its GUI. -- May the most significant bit of your life be positive.
Re: Unbound Notice: "sendto failed: No buffer space available"
On 2020-04-16, William Ahern wrote: > I'm no network administrator, but a 3% failure rate would be very high on a > physical interface. vlan4 is presumably the interface your Apple device > passes through, right? Investigate why all the dropped packets. Start with > your queuing rules: examine/enable PF statistics, examine/enable PF logs, or > just disable queueing to rule it out entirely. It's almost certainly the queueing. I would skip queuing for DNS packets or use a separate queue so they aren't affected by bulk transfers, by its nature it drops packets and if you do that to DNS it's going to make the end-user experience of the network very poor.
Re: Regarding randomized times in crontab
Den tors 16 apr. 2020 kl 20:22 skrev Andreas Kusalananda Kähäri < andreas.kah...@abc.se>: > On Thu, Apr 16, 2020 at 11:14:59AM -0600, Theo de Raadt wrote: > > That is a lot of words to cover a simple concept: > > > > The specific random values are selected when cron(5) loads > > the crontab file. New numbers are chosen when crontab -e is used. > > If you understand that, the conclusions are obvious. > > Ah. Good. Then I know the restrictions. The random times are random, > but fixed for the lifetime of the cron daemon (or until the crontab is > reloaded due to being edited). > It would be very weird otherwise, if the 24h random example was used, then it chose 00:01, ran your "bin/true" command and then re-randomized, it would most certainly end up wanting to run again, perhaps twice or more. So if it re-randomized after each execution it would have to keep a 24h timer going (in your example, a per-week, a per-month timer also) to make sure the newly randomized 11:12 time is actually tomorrows 11:12 and not the upcoming one in this day. Also, re-randomization would also mean it could start your one hour backup at 23:59 and once more in 00:01 the next day, which would cause lots of unexpected chaos for anyone expecting a daily one-hour job to not collide with itself. -- May the most significant bit of your life be positive.
Re: Traffic inspection with relayd
On 2020-04-15, Cornelius Jubjub wrote: > Secondly, I'd really like to dump all of > the traffic al la tcpdump but I don't really see a place to do so (no > unencrypted data passes through an interface AFAIK). relayd doesn't do that. Try sslsplit (in packages).
Re: Regarding randomized times in crontab
On Fri, Apr 17, 2020 at 09:06:10AM +0200, Janne Johansson wrote: > Den tors 16 apr. 2020 kl 20:22 skrev Andreas Kusalananda Kähäri < > andreas.kah...@abc.se>: > > > On Thu, Apr 16, 2020 at 11:14:59AM -0600, Theo de Raadt wrote: > > > That is a lot of words to cover a simple concept: > > > > > > The specific random values are selected when cron(5) loads > > > the crontab file. New numbers are chosen when crontab -e is used. > > > If you understand that, the conclusions are obvious. > > > > Ah. Good. Then I know the restrictions. The random times are random, > > but fixed for the lifetime of the cron daemon (or until the crontab is > > reloaded due to being edited). > > > > It would be very weird otherwise, if the 24h random example was used, then > it chose 00:01, > ran your "bin/true" command and then re-randomized, it would most certainly > end up wanting > to run again, perhaps twice or more. So if it re-randomized after each > execution > it would have to keep a 24h timer going (in your example, a per-week, a > per-month timer also) > to make sure the newly randomized 11:12 time is actually tomorrows 11:12 > and not the upcoming > one in this day. Also, re-randomization would also mean it could start your > one hour backup at 23:59 > and once more in 00:01 the next day, which would cause lots of unexpected > chaos for anyone expecting > a daily one-hour job to not collide with itself. Well, not weird but unexpected if you didn't think about it when you picked the randomized time intervals. The issue with overlapping jobs could be sorted out fairly easily with manual locking, or with the -s crontab(5) feature that I saw a patch for on the tech list recently. I suppose there is no technical issue with actually re-randomizing the picking of the time whenever a job is about to enter the time frame of when the if would possibly start (not directly after each execution, obviously). That would have the same effect as delaying the job with sleep and $RANDOM. > > -- > May the most significant bit of your life be positive. :-) -- Andreas (Kusalananda) Kähäri SciLifeLab, NBIS, ICM Uppsala University, Sweden .
ieee80211 panic on athn reconfig
This is current/i386 on an ALIX (dmesg below) with athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9 athn0: AR9280 rev 2 (2T2R), ROM rev 22, address 04:f0:21:01:d6:86 # cat hostname.athn0 inet 192.168.33.1 255.255.255.0 NONE media autoselect mode 11g mediaopt hostap chan 2 nwid stare.cz wpakey hovnoPrdel123 After changing the password, or the channel, or the mode, and doing # sh /etc/netstart athn0 the machine reproducibly panics (cereal script below). I have no idea why it panics in ieee80211_encrypt(). It happens both with clients associated and not. Is this known with athn(4)? How can I help debug this? Jan ddb> show panic ieee80211_encrypt: key unset for sw crypto: 0 ddb> trace db_enter() at db_enter+0x4 panic(d0b83788) at panic+0xcc ieee80211_encrypt(d194e030,d195bc00,d194eb00) at ieee80211_encrypt+0x70 ar5008_tx(d194e000,d195bc00,d19a,2) at ar5008_tx+0x9a ar5008_swba_intr(d194e000) at ar5008_swba_intr+0x238 ar5008_intr(d194e000) at ar5008_intr+0x12f intr_handler(f3b1d67c,d1945480) at intr_handler+0x18 Xintr_legacy9_untramp() at Xintr_legacy9_untramp+0xf7 end of kernel ddb> ps PID TID PPIDUID S FLAGS WAIT COMMAND *51886 239363 46526 0 7 0x3ifconfig 46526 94296 51119 0 30x10008b pause sh 51119 210938 1 0 30x10008b pause ksh 4074 355325 1 0 30x100098 poll cron 26296 319573 67907 74 30x100092 bpf pflogd 67907 395783 1 0 30x80 netio pflogd 78788 338207 1 79 30x100090 kqreadtftpd 64936 466062 45121 95 30x100092 kqreadsmtpd 78617 19784 45121103 30x100092 kqreadsmtpd 89735 422787 45121 95 30x100092 kqreadsmtpd 40031 127196 45121 95 30x100092 kqreadsmtpd 3003 366634 45121 95 30x100092 kqreadsmtpd 67429 418102 45121 95 30x100092 kqreadsmtpd 45121 87978 1 0 30x100080 kqreadsmtpd 892939339 1 77 30x100090 poll dhcpd 32523 33766 1 0 30x80 selectsshd 16723 521208 1 0 30x100080 poll ntpd 41803 404697 97594 83 30x100092 poll ntpd 97594 270290 1 83 30x100092 poll ntpd 27672 104019 1 53 30x90 kqreadunbound 85121 72700 81754 97 30x100090 kqreadnsd -81754or133366 40270 97 30x100090 poll nsd 40270 98718 1 97 30x100090 kqreadnsd 2198 36071 55390 74 30x100092 bpf pflogd 55390 372523 1 0 30x80 netio pflogd 82531 87748 87247 73 30x100090 kqreadsyslogd 87247 309403 1 0 30x100082 netio syslogd 98924 510112 35334115 30x100092 kqreadslaacd 93418 61048 35334115 30x100092 kqreadslaacd 35334 428553 1 0 30x100080 kqreadslaacd 5139 163288 0 0 3 0x14200 bored smr 22383 413035 0 0 2 0x14200zerothread 77055 99704 0 0 3 0x14200 aiodoned aiodoned 61899 379872 0 0 3 0x14200 syncerupdate 81836 124433 0 0 3 0x14200 cleaner cleaner 55117 45992 0 0 3 0x14200 reaperreaper 50811 60573 0 0 3 0x14200 pgdaemon pagedaemon 15077 352797 0 0 3 0x14200 bored crynlk 6357 442984 0 0 3 0x14200 bored crypto 45388 138131 0 0 3 0x14200 usbtskusbtask 45899 192598 0 0 3 0x14200 usbatsk usbatsk 77300 116231 0 0 3 0x14200 bored sensors 36473 508486 0 0 3 0x14200 bored softnet 73636 394873 0 0 3 0x14200 bored systqmp -64894or356410 0 0 3 0x14200 bored systq 4636 461286 0 0 3 0x40014200 bored softclock 59424 288681 0 0 3 0x40014200idle0 19281 244490 0 0 3 0x14200 kmalloc kmthread 1 431117 0 0 30x82 wait init 0 0 -1 0 3 0x10200 scheduler swapper OpenBSD 6.7-beta (GENERIC) #108: Thu Apr 9 11:00:54 MDT 2020 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC real mem = 267931648 (255MB) avail mem = 247336960 (235MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 11/05/08, BIOS32 rev. 0 @ 0xfd088 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last b
Re: ieee80211 panic on athn reconfig
On Fri, Apr 17, 2020 at 12:08:39PM +0200, Jan Stary wrote: > This is current/i386 on an ALIX (dmesg below) with > > athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9 > athn0: AR9280 rev 2 (2T2R), ROM rev 22, address 04:f0:21:01:d6:86 > > # cat hostname.athn0 > inet 192.168.33.1 255.255.255.0 NONE > media autoselect mode 11g mediaopt hostap chan 2 > nwid stare.cz wpakey hovnoPrdel123 > > After changing the password, or the channel, or the mode, and doing > > # sh /etc/netstart athn0 > > the machine reproducibly panics (cereal script below). > > I have no idea why it panics in ieee80211_encrypt(). > It happens both with clients associated and not. > > Is this known with athn(4)? No, but it is definitely a bug. > How can I help debug this? Could you try to find a short sequence of 'ifconfig athn0' commands that will trigger it, instead of /etc/netstart? That would help me already.
iked and rdomain
Good afternoon, is it possible to have only traffic which is routed through a specific rdomain being encryped, i.e. have an enc interface in another rdomain and only the whole traffic that runs in that rdomain gets encryped? Thank you for your help. Best regards, Florian
[www] broken link - rpki-client/index.html
Hello, yet another broken link: page: https://www.openbsd.org/rpki-client/index.html link to: https://www.openbsd.org/rpki-client/txt/release-6.6p1.txt Cheers, Alex
chattr on OpenBSD???
I noticed that chattr exists on OpenBSD. The man page says it applies to Linux file systems (ext* etc). Two questions: 1. Does this also apply to OpenBSD's fast file system? (The man page would suggest not.) 2. If not, is it of any use on OpenBSD? -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond
Re: chattr on OpenBSD???
On Fri, 17 Apr 2020 09:11:15 -0600, "Raymond, David" wrote: > I noticed that chattr exists on OpenBSD. The man page says it applies > to Linux file systems (ext* etc). Two questions: > > 1. Does this also apply to OpenBSD's fast file system? (The man page > would suggest not.) No. > 2. If not, is it of any use on OpenBSD? Not unless you are using one of the Linux ext* file systems on OpenBSD. For native OpenBSD file systems you can use the BSD chflags(8) command. - todd
pthreads, C and guacamole [Was: Reduce attack surface - Tomcat and guacamole...]
Hi,
I am looking into guacamole's use of pthread_mutexattr_setpshare.
(an aside, if I comment out the 4 lines of code invoking
pthread_mutexattr_setpshare, it compiles with gcc on OpenBSD 6.6
(GENERIC.MP) )
I am an experienced C programmer, but I've never looked in threading in
C before so it has required quite a bit of reading. I haven't been able
to find a comprehensive "architecture" document, just various man pages,
some with sample code.
For example:
https://linux.die.net/man/3/pthread_mutexattr_init
In the above documentation, it states:
...the possibility that an application may allocate the
synchronization objects from this section in memory that is accessed
by multiple processes (and therefore, by threads of multiple processes).
That is the purpose of the guacamole's pthread_mutexattr_setpshared(foo,
PTHREAD_PROCESS_SHARED) , to permit multiple threaded processes to
access the resource protected by the MUTEX.
However, from my reading of the code, the MUTEX is only protecting
malloc'd memory, which as far as I know, isn't a resource that can be
accessed by multiple processes.
It is my newby (to pthreads) interpretation of the code that in all 4
cases, the code is malloc'ing memory that is being protected by the
MUTEX. For example:
src/libguac/pool.c:
...
guac_pool* guac_pool_alloc(int size) {
pthread_mutexattr_t lock_attributes;
guac_pool* pool = malloc(sizeof(guac_pool));
^^^
Allocate memory that will only be accessible by this process
/* If unable to allocate, just return NULL. */
if (pool == NULL)
return NULL;
/* Initialize empty pool */
pool->min_size = size;
pool->active = 0;
pool->__next_value = 0;
pool->__head = NULL;
pool->__tail = NULL;
/* Init lock */
pthread_mutexattr_init(&lock_attributes);
pthread_mutexattr_setpshared(&lock_attributes, PTHREAD_PROCESS_SHARED);
pthread_mutex_init(&(pool->__lock), &lock_attributes);
This codes saves the MUTEX in the locally allocated memory
No other process can find this MUTEX in malloc'd memory, so setting it
to PTHREAD_PROCESS_SHARED seems totally irrelevant.
If so, I *think* it's OK to just comment out that code as OpenBSD's
pthread implementation will work fine within a process, just not
multiple processes.
Is this a correct assessment of the code and OpenBSD's pthread environnment?
Thanks,
Steve W.
On 15/04/2020 10:19 a.m., Stuart Henderson wrote:
On 2020-04-14, Steve Williams wrote:
Guacamole (I believe) needs to run under something like tomcat to serve
up the java war file & application.
I looked at this before - it also requires guacamole-server to be built
(written in C), it requires mutexes shared between different processes
(pthread_mutexattr_setpshared(foo, PTHREAD_PROCESS_SHARED) which
isn't supported in OpenBSD's thread library.
But what you can do is run guacamole elsewhere and have a reverse http
proxy running on OpenBSD doing http auth and feeding connections across.
So, I was thinking of using some form of authpf to open up pf rules when
I needed to access systems remotely.
But, I don't want to open up Tomcat to the world when I'm using
guacamole, so is it possible to have authpf tweak pf rules so that the
originating IP address of the ssh session would be the only one that
could access Tomcat?
That is exactly what authpf normally does anyway.
I was thinking even httpd in front of tomcat with httpd authentication,
but that doesn't seem to make sense to me at a high level.
I was looking at relayd but it doesn't seen to have any authentication
mechanism built in.
httpd can't proxy connections to another http server. relayd can but as
you say doesn't have a way to add http authentication. You can do this
with nginx, haproxy or Apache httpd though.
Re: chattr on OpenBSD???
On Fri, Apr 17, 2020 at 09:11:15AM -0600, Raymond, David wrote: > I noticed that chattr exists on OpenBSD. The man page says it applies > to Linux file systems (ext* etc). Two questions: No. You have e2fsprogs installed. e2fsprogs-1.42.12p5:sysutils/e2fsprogs:/usr/local/man/man1/chattr.1 ..bottom of chattr(1): E2fsprogs version 1.42.12 August 2014CHATTR(1) -Bryan.
Re: chattr on OpenBSD???
Hmm... Why would I want e2fsprogs on OpenBSD??? Oh, I see, libreoffice drags it in. One more thing I wish I could dispense with. Dave On 4/17/20, Bryan Steele wrote: > On Fri, Apr 17, 2020 at 09:11:15AM -0600, Raymond, David wrote: >> I noticed that chattr exists on OpenBSD. The man page says it applies >> to Linux file systems (ext* etc). Two questions: > > No. You have e2fsprogs installed. > > e2fsprogs-1.42.12p5:sysutils/e2fsprogs:/usr/local/man/man1/chattr.1 > > > ..bottom of chattr(1): > > E2fsprogs version 1.42.12 August 2014CHATTR(1) > > -Bryan. > > -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond
Re: chattr on OpenBSD???
On Fri, 17 Apr 2020 15:27:33 -0600, "Raymond, David" wrote: > Hmm... Why would I want e2fsprogs on OpenBSD??? Oh, I see, > libreoffice drags it in. One more thing I wish I could dispense with. A bunch of ports pull it in for its uuid code. - todd
Help debugging slow nfs (40kB/s); linux client
Hello, I am trying to get an Intel atom mini itx board running as an OpenBSD 6.6 NAS. I've got the necessary daemons running on the mini itx board: > doas rcctl ls started cron httpd mountd nfsd ntpd pflogd portmap slaacd smtpd sndiod sshd syslogd and exports is set up: > cat /etc/exports /home/nathan/shared -alldirs -ro I am mounting this from my laptop which runs on arch linux at the moment. On the linux client machine, this is the relevant line from mount: 192.168.1.4:/home/nathan/shared on /home/nathan/mnt type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.4,mountvers=3,mountport=997,mountproto=udp,local_lock=none,addr=192.168.1.4) I can copy small files over nfs, but anything large takes way too long. I've read rsync isn't necessarily the best way to gauge transfer speed, but rsync shows I'm getting about 38kB/s transfer speed. For comparison, I tried using sshfs to mount the same directory on the itx to the same location on the linux system and I get ~1.1MB/s, wow! Even that isn't great, but I'm the laptop is on wifi and I figure I can get to more tuning later. It seems clear I'm not (just) dealing with hardware limitations in this nfs mount. What else can I do to debug this? Thanks, Nathan
Re: iked and rdomain
On Fri, Apr 17, 2020 at 02:37:57PM +0200, Florian Weber wrote: > Good afternoon, > > is it possible to have only traffic which is routed through a specific > rdomain being encryped, i.e. have an enc interface in another rdomain and > only the whole traffic that runs in that rdomain gets encryped? > > Thank you for your help. > > Best regards, > > Florian > Currently the only thing that should work out of the box is having iked running in a non-default rdomain and then use ipsec only in this rdomain. However, I have been working on better rdomain integration for ipsec/iked lately and a working diff that should solve your problem is currently waiting for testing over at tech@: https://marc.info/?l=openbsd-tech&m=158677212723896&w=2 Feedback welcome ;)
Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic
On 4/10/20 4:51 AM, Martin wrote: I'm looking for relatively cheap VPS with OpenBSD installation support and with ~1Tb of unfiltered traffic. In any words all in/out VPS ports must be opened by default. Any recommendations? Ohai. Co-founder of Cyberia Computer Club here - we're a US-based nonprofit - part of our deal is providing good & open services. We host our own hardware in a US datacenter, and offer OpenBSD VMs for decent prices. You can see the whole shtick at https://capsul.org No filtering or snooping, you just get a box on a public IPv4 and that's it. Just wanted to toss my own hat in the ring! j3s
Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic
On Fri, Apr 10, 2020 at 09:51:41AM +, Martin wrote: > I'm looking for relatively cheap VPS with OpenBSD installation support and > with ~1Tb of unfiltered traffic. In any words all in/out VPS ports must be > opened by default. > Any recommendations? Hetzner has some cheap VPS plans and they do support OpenBSD. Best regards, Chris Narkiewicz signature.asc Description: PGP signature
ATI Mobility 1 support on Dell Latitude L400
Hello,
considering that 6.6 nuked X for my T23 as mentioned in previous recent
post, I decided to refresh my old Dell L400, which was lagging behind at
6.2, with a fresh 6.6 install.
Unfortunately X crashes. The first error in the log file was about setting
machdep.allowaperture=1 and rebooting (I always used 2 before). After
changing its value in sysctl.conf to 1, this is the new error in the log
file:
X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
[ 206.190] Build Operating System: OpenBSD 6.6 i386
[ 206.190] Current Operating System: OpenBSD argento.local 6.6 GENERIC#6
i386
[ 206.192] Build Date: 12 October 2019 11:55:53AM
[ 206.192]
[ 206.192] Current version of pixman: 0.38.4
[ 206.192] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 206.192] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 206.193] (==) Log file: "/home/pasha/.local/share/xorg/Xorg.0.log",
Time: Sat Apr 18 03:10:40 2020
[ 206.365] (==) Using system config directory
"/usr/X11R6/share/X11/xorg.conf.d"
[ 206.424] (==) No Layout section. Using the first Screen section.
[ 206.424] (==) No screen section available. Using defaults.
[ 206.424] (**) |-->Screen "Default Screen Section" (0)
[ 206.424] (**) | |-->Monitor ""
[ 206.448] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 206.448] (==) Automatically adding devices
[ 206.449] (==) Automatically enabling devices
[ 206.449] (==) Not automatically adding GPU devices
[ 206.476] (==) Max clients allowed: 256, resource mask: 0x1f
[ 207.101] (==) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[ 207.101] (==) ModulePath set to "/usr/X11R6/lib/modules"
[ 207.101] (II) The server relies on wscons to provide the list of input
devices.
If no devices become available, reconfigure wscons or disable
AutoAddDevices.
[ 207.101] (II) Loader magic: 0x351fe000
[ 207.101] (II) Module ABI versions:
[ 207.101] X.Org ANSI C Emulation: 0.4
[ 207.101] X.Org Video Driver: 24.0
[ 207.101] X.Org XInput driver : 24.1
[ 207.101] X.Org Server Extension : 10.0
[ 207.121] (EE)
Fatal server error:
[ 207.122]
*(EE) xf86OpenConsole: No console driver found Supported drivers: wscons
Check your kernel's console driver configuration and /dev entries*(EE)
[ 207.122] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 207.122] (EE) Please also check the log file at
"/home/pasha/.local/share/xorg/Xorg.0.log" for additional information.
[ 207.122] (EE)
[ 207.170] (EE) Server terminated with error (1). Closing log file.
As far as I know from https://www.openbsd.org/faq/upgrade66.html the ATI
driver shouldn't be in the recently killed ones, as I get from dmesg:
OpenBSD 6.6 (GENERIC) #6: Thu Mar 12 09:36:01 MDT 2020
r...@syspatch-66-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem = 267862016 (255MB)
avail mem = 247291904 (235MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 05/09/03, BIOS32 rev. 0 @ 0xfd7a0, SMBIOS rev. 2.3
@ 0xdc010 (28 entries)
bios0: vendor Quanta Computer version "A09(Q3J01)" date 05/09/2001
bios0: Dell Computer Corp. Latitude L400
acpi0 at bios0: ACPI 1.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP BOOT
acpi0: wakeup devices PCI0(S3) COMA(S3) CRD0(S3) MDEM(S3) LID_(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpicpu0 at acpi0: !C3(@20 io@0x8015), !C2(@10 io@0x8014), C1(@1 halt!)
acpitz0 at acpi0: critical temperature is 97 degC
"PNP0A03" at acpi0 not configured
acpicmos0 at acpi0
acpibtn0 at acpi0: LID_
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT1 model "SI-QT17" serial type LION oem "SANYO"
acpibtn1 at acpi0: SBTN
bios0: ROM list: 0xc/0x1 0xd/0x800! 0xdc000/0x4000!
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 698 MHz, 06-08-0a
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PSE36,MMX,FXSR,SSE,PERF,MELTDOWN
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
intelagp0 at pchb0
*agp0 at intelagp0: aperture at 0xf800, size 0x400*
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
*vga1 at pci1 dev 0 function 0 "ATI Mobility 1" rev 0x64wsdisplay0 at vga1
mux 1: console (80x25, vt100 emulation)wsdisplay0: screen 1-5 added (80x25,
vt100 emulation)*
piixpcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
Re: ATI Mobility 1 support on Dell Latitude L400
Paolo Aglialoro writes: > considering that 6.6 nuked X for my T23 as mentioned in previous recent > post, I decided to refresh my old Dell L400, which was lagging behind at > 6.2, with a fresh 6.6 install. > > Unfortunately X crashes. The first error in the log file was about setting > machdep.allowaperture=1 and rebooting (I always used 2 before). After > changing its value in sysctl.conf to 1, this is the new error in the log > file: Are you using xenodm instead of startx? Beginning in 6.5, "Xorg(1), the X window server, is no longer installed setuid. xenodm(1) should be used to start X." https://www.openbsd.org/65.html
Updating a Nextcloud instance installed via package
Hello, I have a running installation of Nextcloud, installed via the OpenBSD package and set up according to the various pkg-readmes. The section about updating is kept very short, so I wanted to ask here before doing something unwise out of my lack of experience: When trying to use the NC updater (after working around the chroot), it complains that there is an additional file in the directory, namely ".htaccess.dist". The installation also fails the integrity check (unrelated to upgrade), I assume because of modifications that were made by the maintainers. I am not aware of what these modifications are and whether they are needed for NC to run properly on OpenBSD, so I was wondering how the update process would work using "pkg-add -u" to simply update the package. Would that replace the entire directory, or does it just fetch the newest version of Nextcloud, after which I would just need to run `occ upgrade`? Is there a better, recommended way to update in this case? I'd be very thankful for some guidance and advice before I accidentally break something or end up with a bad hack. :) Regards, Unicorn
Re: Help debugging slow nfs (40kB/s); linux client
Hello, Try these options: sudo mount.nfs -o wsize=8192,rsize=8192 IPADDRESS:/shara /home/myuser/shara/ Play with wsize and rsize to achieve better speed. These are mines. 18.04.2020 02:31, Nathan Clement пишет: Hello, I am trying to get an Intel atom mini itx board running as an OpenBSD 6.6 NAS. I've got the necessary daemons running on the mini itx board: doas rcctl ls started cron httpd mountd nfsd ntpd pflogd portmap slaacd smtpd sndiod sshd syslogd and exports is set up: cat /etc/exports /home/nathan/shared -alldirs -ro I am mounting this from my laptop which runs on arch linux at the moment. On the linux client machine, this is the relevant line from mount: 192.168.1.4:/home/nathan/shared on /home/nathan/mnt type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.4,mountvers=3,mountport=997,mountproto=udp,local_lock=none,addr=192.168.1.4) I can copy small files over nfs, but anything large takes way too long. I've read rsync isn't necessarily the best way to gauge transfer speed, but rsync shows I'm getting about 38kB/s transfer speed. For comparison, I tried using sshfs to mount the same directory on the itx to the same location on the linux system and I get ~1.1MB/s, wow! Even that isn't great, but I'm the laptop is on wifi and I figure I can get to more tuning later. It seems clear I'm not (just) dealing with hardware limitations in this nfs mount. What else can I do to debug this? Thanks, Nathan -- С уважением, Родин Максим
