Re: Some Thoughts on resolv.conf.tail Deprecation
On Fri, Nov 12, 2021 at 02:04:56AM +, beebeet...@posteo.de wrote: > > I am not sure about what problem you are trying to solve. Won't the > > lines added by resolvd be overwritten anyway the first time you use the > > backed up file? > > What I'm trying to solve is that static part of the configuration being > mixed up with configuration generated runtime in a single file, which > leads to a few inconveniences: > - resolv.conf will show up in the diff between backups all the time >even if nothing has really changed; You could backup /var/backups/etc_resolv.conf.current file instead of /etc/resolv.conf (or just all /var/backups files). The backup file seems to be changed only if the content is changed (I only checked mtime on the file on a moving laptop). So you will get the "stable" inode if content is the same. > - when migrating the configuration to a different deployment, for >example, one where IP address is statically assigned, resolvd will >not overwrite the "stale" auto-configured lines, and the old >nameserver info will linger unless manually removed. if the new host doesn't use resolvd(8) it could be a problem as the file will not be rewritten. But in this case you should take a different file for source for your template. OpenBSD isn't a static OS, it is expected to have to adapt the administration task for time to time. Please note that you could also run a simple command-line to "cleanup" resolv.conf: # sed -i -e '/ # resolvd: /d' /etc/resolv.conf (and if you put it in /etc/rc.local, your host with resolvd will recreate it at boot, and your host without resolvd will keep it clean). Thanks. -- Sebastien Marie
Re: Some Thoughts on resolv.conf.tail Deprecation
What I'm trying to solve is that static part of the configuration being mixed up with configuration generated runtime in a single file, which leads to a few inconveniences: - resolv.conf will show up in the diff between backups all the time even if nothing has really changed; Oh come on. Something happened. That is why the contents are different. Yes something happened, but something which I imagine is not typically worth being backed up, yet it lives in the same file as things that are. - when migrating the configuration to a different deployment, for example, one where IP address is statically assigned, resolvd will not overwrite the "stale" auto-configured lines, and the old nameserver info will linger unless manually removed. So what? In cases where one doesn't want reveal what nameserver their other machines were using, a bit more error-prone I guess. I just don't see the reasoning behind removing resolv.conf.tail...
Re: Some Thoughts on resolv.conf.tail Deprecation
beebeet...@posteo.de wrote: > > I am not sure about what problem you are trying to solve. Won't the > > lines added by resolvd be overwritten anyway the first time you use the > > backed up file? > > What I'm trying to solve is that static part of the configuration being > mixed up with configuration generated runtime in a single file, which > leads to a few inconveniences: > - resolv.conf will show up in the diff between backups all the time >even if nothing has really changed; Oh come on. Something happened. That is why the contents are different. > - when migrating the configuration to a different deployment, for >example, one where IP address is statically assigned, resolvd will >not overwrite the "stale" auto-configured lines, and the old >nameserver info will linger unless manually removed. So what? > For now resolv.conf is the only configuration file I know of that gets > mixed up with runtime info, and it's manageable; but imagine if many > more configuration files follow similar principles, the administrative > overhead can quickly become too much. Yes, we are going to do the same thing to lots of other configuration files. We are trying to keep up with systemd. Didn't you get the memo?
Re: Some Thoughts on resolv.conf.tail Deprecation
I am not sure about what problem you are trying to solve. Won't the lines added by resolvd be overwritten anyway the first time you use the backed up file? What I'm trying to solve is that static part of the configuration being mixed up with configuration generated runtime in a single file, which leads to a few inconveniences: - resolv.conf will show up in the diff between backups all the time even if nothing has really changed; - when migrating the configuration to a different deployment, for example, one where IP address is statically assigned, resolvd will not overwrite the "stale" auto-configured lines, and the old nameserver info will linger unless manually removed. For now resolv.conf is the only configuration file I know of that gets mixed up with runtime info, and it's manageable; but imagine if many more configuration files follow similar principles, the administrative overhead can quickly become too much.
Re: OpenBSD 7.0--cron will not run a certain script
W dniu 11.11.2021 o 23:55, Jeff Ross pisze: Hi all, This is on a Raspberry Pi 3B+ (dmesg to follow). Here's my crontab: jross@pi:/home/jross $ crontab -l SHELL=/bin/sh MAILTO="" # #minute hour mday month wday command */2 * * * * /bin/sh /home/jross/upload_latest.sh 2>&1 * * * * * python3 4Kwebcam_loop_no_scp.py 38 * * * * /bin/sh -x /home/jross/sync_to_odroidn2.sh 2>&1 The first 2 scripts work fine. The last one absolutely will not. Here's the very simple script: jross@pi:/home/jross $ cat ./sync_to_ordoidn2.sh #!/bin/sh logger "starting sync to odroidn2" pgrep -x rsync if [ $? -eq 0 ]; then echo "`date` rsync still running...exiting" >> /var/log/rsync_to_odroidn2.out else echo "`date` starting rsync..." >> /var/log/rsync_to_odroidn2.out /usr/local/bin/rsync -avPz /home/jross/webcam/ odroidn2:/samba/starhouse/webcam/ | tee -a /var/log/rsync_to_odroidn2.out echo "`date` finished rsync..." >> /var/log/rsync_to_odroidn2.out fi Here's where cron says it's firing the script: 2021-11-11 15:38:01.305599500 127.0.0.1: cron.info: Nov 11 15:38:01 cron[95324]: (jross) CMD (/bin/sh -x /home/jross/sync_to_odroidn2.sh 2>&1) But, no comment into syslog from the logger line and the script simply does not run. Running the script manually, though, works fine: 2021-11-11 15:47:05.959176500 127.0.0.1: user.notice: Nov 11 15:47:05 jross: starting sync to odroidn2 sending incremental file list 4Kwebcam_2021/ 4Kwebcam_2021/4Kwebcam_1636669302.jpg 2,113,298 100% 6.85MB/s 0:00:00 (xfr#1, to-chk=75/1323) 4Kwebcam_2021/4Kwebcam_1636669333.jpg 2,109,678 100% 1.48MB/s 0:00:01 (xfr#2, to-chk=74/1323) 4Kwebcam_2021/4Kwebcam_1636669357.jpg 2,108,931 100% 1.73MB/s 0:00:01 (xfr#3, to-chk=73/1323) ...and so on I originally had this script running under cron with */10 in the minute column. As a part of debugging I've adjusted the interval to every 5 minutes and then to a set minute in the hour. I'm using full paths everywhere in the script so it can't be that. I do not know what else to try... Jeff dmesg: jross@pi:/home/jross $ dmesg OpenBSD 7.0 (GENERIC.MP) #1332: Thu Sep 30 16:53:51 MDT 2021 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 970907648 (925MB) avail mem = 908574720 (866MB) random: good seed from bootblocks mainbus0 at root: Raspberry Pi 3 Model B Plus Rev 1.3 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 cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4 cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache cpu1: 512KB 64b/line 16-way L2 cache cpu1: CRC32,ASID16 cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4 cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache cpu2: 512KB 64b/line 16-way L2 cache cpu2: CRC32,ASID16 cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4 cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache cpu3: 512KB 64b/line 16-way L2 cache cpu3: CRC32,ASID16 efi0 at mainbus0: UEFI 2.8 efi0: Das U-Boot rev 0x20210700 apm0 at mainbus0 simplefb0 at mainbus0: 656x416, 32bpp wsdisplay0 at simplefb0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-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 bcmintc0 at simplebus0 pluart0 at simplebus0 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 "clocks" at mainbus0 not configured "phy" at mainbus0 not configured "arm-pmu" at mainbus0 not configured agtimer0 at mainbus0: 19200 kHz "leds" at mainbus0 not configured "fixedregulator_3v3" at mainbus0 not configured "fixedregulator_5v0" at mainbus0 not configured "bootloader" at mainbus0 not configured dt: 445 probes usb0 at dwctwo0: USB revision 2.0 scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: removable sd0: 121942MB, 512 bytes/sector, 249737216 sectors uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev 2.00/1.00 addr 1 uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard Microsystems
OpenBSD 7.0--cron will not run a certain script
Hi all, This is on a Raspberry Pi 3B+ (dmesg to follow). Here's my crontab: jross@pi:/home/jross $ crontab -l SHELL=/bin/sh MAILTO="" # #minute hour mday month wday command */2 * * * * /bin/sh /home/jross/upload_latest.sh 2>&1 * * * * * python3 4Kwebcam_loop_no_scp.py 38 * * * * /bin/sh -x /home/jross/sync_to_odroidn2.sh 2>&1 The first 2 scripts work fine. The last one absolutely will not. Here's the very simple script: jross@pi:/home/jross $ cat ./sync_to_ordoidn2.sh #!/bin/sh logger "starting sync to odroidn2" pgrep -x rsync if [ $? -eq 0 ]; then echo "`date` rsync still running...exiting" >> /var/log/rsync_to_odroidn2.out else echo "`date` starting rsync..." >> /var/log/rsync_to_odroidn2.out /usr/local/bin/rsync -avPz /home/jross/webcam/ odroidn2:/samba/starhouse/webcam/ | tee -a /var/log/rsync_to_odroidn2.out echo "`date` finished rsync..." >> /var/log/rsync_to_odroidn2.out fi Here's where cron says it's firing the script: 2021-11-11 15:38:01.305599500 127.0.0.1: cron.info: Nov 11 15:38:01 cron[95324]: (jross) CMD (/bin/sh -x /home/jross/sync_to_odroidn2.sh 2>&1) But, no comment into syslog from the logger line and the script simply does not run. Running the script manually, though, works fine: 2021-11-11 15:47:05.959176500 127.0.0.1: user.notice: Nov 11 15:47:05 jross: starting sync to odroidn2 sending incremental file list 4Kwebcam_2021/ 4Kwebcam_2021/4Kwebcam_1636669302.jpg 2,113,298 100% 6.85MB/s 0:00:00 (xfr#1, to-chk=75/1323) 4Kwebcam_2021/4Kwebcam_1636669333.jpg 2,109,678 100% 1.48MB/s 0:00:01 (xfr#2, to-chk=74/1323) 4Kwebcam_2021/4Kwebcam_1636669357.jpg 2,108,931 100% 1.73MB/s 0:00:01 (xfr#3, to-chk=73/1323) ...and so on I originally had this script running under cron with */10 in the minute column. As a part of debugging I've adjusted the interval to every 5 minutes and then to a set minute in the hour. I'm using full paths everywhere in the script so it can't be that. I do not know what else to try... Jeff dmesg: jross@pi:/home/jross $ dmesg OpenBSD 7.0 (GENERIC.MP) #1332: Thu Sep 30 16:53:51 MDT 2021 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 970907648 (925MB) avail mem = 908574720 (866MB) random: good seed from bootblocks mainbus0 at root: Raspberry Pi 3 Model B Plus Rev 1.3 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 cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4 cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache cpu1: 512KB 64b/line 16-way L2 cache cpu1: CRC32,ASID16 cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4 cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache cpu2: 512KB 64b/line 16-way L2 cache cpu2: CRC32,ASID16 cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4 cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache cpu3: 512KB 64b/line 16-way L2 cache cpu3: CRC32,ASID16 efi0 at mainbus0: UEFI 2.8 efi0: Das U-Boot rev 0x20210700 apm0 at mainbus0 simplefb0 at mainbus0: 656x416, 32bpp wsdisplay0 at simplefb0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-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 bcmintc0 at simplebus0 pluart0 at simplebus0 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 "clocks" at mainbus0 not configured "phy" at mainbus0 not configured "arm-pmu" at mainbus0 not configured agtimer0 at mainbus0: 19200 kHz "leds" at mainbus0 not configured "fixedregulator_3v3" at mainbus0 not configured "fixedregulator_5v0" at mainbus0 not configured "bootloader" at mainbus0 not configured dt: 445 probes usb0 at dwctwo0: USB revision 2.0 scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: removable sd0: 121942MB, 512 bytes/sector, 249737216 sectors uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev 2.00/1.00 addr 1 uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard Microsystems product 0x2514" rev 2.00/b.b3 addr 2 bwfm0 at sdmmc
Re: Some Thoughts on resolv.conf.tail Deprecation
My solution for an static resolv.conf for a long time has been: chattr +i /etc/resolv.conf .. and now disable resovld, of course. If folks use another solution, would be glad to know. -- Fabio Martins On 2021-11-11 17:28, Zé Loff wrote: On Thu, Nov 11, 2021 at 05:36:07PM +, beebeet...@posteo.de wrote: Hi all, I was reading the manual page of resolv.conf(5) today and realized that paragraph on resolv.conf.tail has disappeared since the upgrade to 7.0, so I assume that resolv.conf.tail has been deprecated in response to resolvd being enabled by default. Previously, my backup strategy was to back up the customized system configuration files, which involves backing up resolv.conf.tail, but not resolv.conf. With the new behaviour in 7.0, it appears that my best shot is to back up resolv.conf, which constantly gets edited by resolvd(8). This seems less than ideal. I am not sure about what problem you are trying to solve. Won't the lines added by resolvd be overwritten anyway the first time you use the backed up file? I gave it some thoughts, and came up with an alternative solution to handling resolv.conf: - If resolvd is enabled, then resolv.conf is overidden entirely by resolvd, no more blending of user-edited and auto-configured information is involved. A new resolvd.conf needs to be introduced to instruct resolvd to add static defaults and stuff; - If resolvd is not enabled, then the contents of resolv.conf.tail gets copied to resolv.conf at system start. To me it seems that this is cleaner than the current solution to resolv.conf in that static and dynamic configurations is clearly separated instead of being blended into a one file. What are your thought on this? Thanks!
Re: Some Thoughts on resolv.conf.tail Deprecation
On Thu, Nov 11, 2021 at 05:36:07PM +, beebeet...@posteo.de wrote: > Hi all, > > I was reading the manual page of resolv.conf(5) today and realized that > paragraph on resolv.conf.tail has disappeared since the upgrade to 7.0, so I > assume that resolv.conf.tail has been deprecated in response to resolvd > being enabled by default. > > Previously, my backup strategy was to back up the customized system > configuration files, which involves backing up resolv.conf.tail, but > not resolv.conf. With the new behaviour in 7.0, it appears that my best > shot is to back up resolv.conf, which constantly gets edited by > resolvd(8). This seems less than ideal. I am not sure about what problem you are trying to solve. Won't the lines added by resolvd be overwritten anyway the first time you use the backed up file? > I gave it some thoughts, and came up with an alternative solution to > handling resolv.conf: > > - If resolvd is enabled, then resolv.conf is overidden entirely by >resolvd, no more blending of user-edited and auto-configured >information is involved. A new resolvd.conf needs to be introduced to >instruct resolvd to add static defaults and stuff; > > - If resolvd is not enabled, then the contents of resolv.conf.tail gets >copied to resolv.conf at system start. > > To me it seems that this is cleaner than the current solution to > resolv.conf in that static and dynamic configurations is clearly > separated instead of being blended into a one file. > > What are your thought on this? Thanks! > --
Tiger Lake Intel Xe Graphics inteldrm support?
I got excited with the release of 7.0 listing further support for the Tiger Lake platform, however I have not been successful in configuring the inteldrm driver to gain tearfree accel in X11. Am I missing something in the conf? Is this i5's iGPU model not supported (yet)? Thank you. Hardware is a Lenovo Thinkpad X1 Nano - Intel i5-1130G7 w/ Xe Graphics I've upgraded form the RELEASE to a snapshot of CURRENT, and I've also compiled a kernel from CURRENT cvs src to see if that was any fresher. As for the firmware ``` Installed: iwx-firmware-20210512 vmm-firmware-1.14.0p0 inteldrm-firmware-20211027 uvideo-firmware-1.2p3 ``` inteldrm-firmware-20211027 has been built from CURRENT cvs ports: ports/sysutls/firmware/inteldrm Presently running a snapshot: ``` kern.version=OpenBSD 7.0-current (GENERIC.MP) #85: Tue Nov 9 13:24:56 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP ``` When I go and configure via /etc/X11/xorg.conf.d/20-intel.conf ``` Section "Device" Identifier "Intel Xe Graphics" Driver "intel" Option "TearFree" "true" EndSection ``` Xorg does not launch and exits with errors: ``` [18.866] (--) checkDevMem: using aperture driver /dev/xf86 [18.887] (--) Using wscons driver on /dev/ttyC4 [18.900] X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 [18.900] Build Operating System: OpenBSD 7.0 amd64 [18.900] Current Operating System: OpenBSD x1no.my.domain 7.0 GENERIC.MP#85 amd64 [18.900] Build Date: 09 November 2021 01:42:10PM [18.900] [18.900] Current version of pixman: 0.40.0 [18.900]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [18.900] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [18.900] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 11 12:34:13 2021 [18.902] (==) Using config directory: "/etc/X11/xorg.conf.d" [18.902] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [18.904] (==) No Layout section. Using the first Screen section. [18.904] (==) No screen section available. Using defaults. [18.904] (**) |-->Screen "Default Screen Section" (0) [18.904] (**) | |-->Monitor "" [18.905] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [18.905] (**) | |-->Device "Intel Xe Graphics" [18.905] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [18.905] (==) Automatically adding devices [18.905] (==) Automatically enabling devices [18.905] (==) Not automatically adding GPU devices [18.905] (==) Max clients allowed: 256, resource mask: 0x1f [18.908] (==) 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/ [18.908] (==) ModulePath set to "/usr/X11R6/lib/modules" [18.908] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [18.908] (II) Loader magic: 0x16c48801eb0 [18.908] (II) Module ABI versions: [18.908]X.Org ANSI C Emulation: 0.4 [18.908]X.Org Video Driver: 24.1 [18.908]X.Org XInput driver : 24.1 [18.908]X.Org Server Extension : 10.0 [18.908] (--) PCI:*(0@0:2:0) 8086:9a40:17aa:22c7 rev 1, Mem @ 0x603c00/16777216, 0x40/268435456, I/O @ 0x3000/64 [18.908] (II) LoadModule: "glx" [18.910] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [18.920] (II) Module glx: vendor="X.Org Foundation" [18.920]compiled for 1.20.13, module version = 1.0.0 [18.920]ABI class: X.Org Server Extension, version 10.0 [18.920] (II) LoadModule: "intel" [18.921] (II) Loading /usr/X11R6/lib/modules/drivers/intel_drv.so [18.923] (II) Module intel: vendor="X.Org Foundation" [18.923]compiled for 1.20.13, module version = 2.99.916 [18.923]Module class: X.Org Video Driver [18.923]ABI class: X.Org Video Driver, version 24.1 [18.924] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [18.924] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [18.924] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [18.924] (II) intel: Driver for Intel(R) Iris(TM)
ports/graphics/dcraw MASTER_SITES update
The homepage and distribution site for dcraw changed a long time ago: --- ports/graphics/dcraw/Makefile.dist Thu Nov 11 16:27:45 2021 +++ ports/graphics/dcraw/Makefile Thu Nov 11 16:29:18 2021 @@ -3,11 +3,12 @@ COMMENT = digital camera RAW format conversion tool DISTNAME = dcraw-9.28.0 +REVISION = 1 CATEGORIES = graphics -HOMEPAGE = http://www.cybercom.net/~dcoffin/dcraw/ +HOMEPAGE = https://www.dechifro.org/dcraw/ -MASTER_SITES = http://cybercom.net/~dcoffin/dcraw/archive/ +MASTER_SITES = https://www.dechifro.org/dcraw/archive/ # Some code is completely free, some is under the GPL PERMIT_PACKAGE = Yes
Re: Some Thoughts on resolv.conf.tail Deprecation
No, we will not do what you propose because resolvd so far is working for the majority of people, better than we expected. Luckily we provide all the parts including source, and you can do whatever you want with it. beebeet...@posteo.de wrote: > Hi all, > > I was reading the manual page of resolv.conf(5) today and realized that > paragraph on resolv.conf.tail has disappeared since the upgrade to > 7.0, so I assume that resolv.conf.tail has been deprecated in response > to resolvd being enabled by default. > > Previously, my backup strategy was to back up the customized system > configuration files, which involves backing up resolv.conf.tail, but > not resolv.conf. With the new behaviour in 7.0, it appears that my best > shot is to back up resolv.conf, which constantly gets edited by > resolvd(8). This seems less than ideal. > > I gave it some thoughts, and came up with an alternative solution to > handling resolv.conf: > > - If resolvd is enabled, then resolv.conf is overidden entirely by >resolvd, no more blending of user-edited and auto-configured >information is involved. A new resolvd.conf needs to be introduced to >instruct resolvd to add static defaults and stuff; > > - If resolvd is not enabled, then the contents of resolv.conf.tail gets >copied to resolv.conf at system start. > > To me it seems that this is cleaner than the current solution to > resolv.conf in that static and dynamic configurations is clearly > separated instead of being blended into a one file. > > What are your thought on this? Thanks! >
Some Thoughts on resolv.conf.tail Deprecation
Hi all, I was reading the manual page of resolv.conf(5) today and realized that paragraph on resolv.conf.tail has disappeared since the upgrade to 7.0, so I assume that resolv.conf.tail has been deprecated in response to resolvd being enabled by default. Previously, my backup strategy was to back up the customized system configuration files, which involves backing up resolv.conf.tail, but not resolv.conf. With the new behaviour in 7.0, it appears that my best shot is to back up resolv.conf, which constantly gets edited by resolvd(8). This seems less than ideal. I gave it some thoughts, and came up with an alternative solution to handling resolv.conf: - If resolvd is enabled, then resolv.conf is overidden entirely by resolvd, no more blending of user-edited and auto-configured information is involved. A new resolvd.conf needs to be introduced to instruct resolvd to add static defaults and stuff; - If resolvd is not enabled, then the contents of resolv.conf.tail gets copied to resolv.conf at system start. To me it seems that this is cleaner than the current solution to resolv.conf in that static and dynamic configurations is clearly separated instead of being blended into a one file. What are your thought on this? Thanks!
Re: BiNAT rules not working? Missing information?
W dniu 10.11.2021 o 22:39, Thomas Schweikle pisze:
Hi!
I have to set up a BiNAT address translation for some stuppid hardware
not able to change ip addresses. I've tried with:
Two interfaces:
bge0: 192.168.111.2/24
bge1: 10.160.15.2/24
The default gateway is at 10.160.15.254.
The stupid device with fixed not configurable ip addresses is at
- 192.168.111.{221..225}
The addresses I'd like to map it to 10.160.15.{11..25}
I've set up rules:
set skip on lo
block return
pass
#
tcp_services = "{ ssh }"
sdv_if = bge0
myn_if = bge1
#
sdv_a = 192.168.111.221
sdv_b = 192.168.111.222
sdv_c = 192.168.111.223
sdv_d = 192.168.111.224
sdv_e = 192.168.111.225
#
myn_a = 10.160.15.11
myn_b = 10.160.15.12
myn_c = 10.160.15.13
myn_d = 10.160.15.14
myn_e = 10.160.15.15
#
pass in on egress proto tcp from any to egress \
port $tcp_services keep state
pass out on egress proto { tcp udp icmp } all keep state
#
match out on $myn_if from $sdv_a to any binat-to $myn_a
match out on $myn_if from $sdv_b to any binat-to $myn_b
match out on $myn_if from $sdv_c to any binat-to $myn_c
match out on $myn_if from $sdv_d to any binat-to $myn_d
match out on $myn_if from $sdv_e to any binat-to $myn_e
#
pass on $myn_if from $sdv_a to any binat-to $myn_a
pass on $myn_if from $sdv_b to any binat-to $myn_b
pass on $myn_if from $sdv_c to any binat-to $myn_c
pass on $myn_if from $sdv_d to any binat-to $myn_d
pass on $myn_if from $sdv_e to any binat-to $myn_e
Then reloaded configuration by issuing "sh /etc/netstart" but without
any effect. I can connect to this box using ssh, but trying to connect
to the stupid box behind with "ssh 10.160.15.12" fails.
- Any ideas why? Is the ruleset correct for what I want to achieve?
- Do I have to define address aliases on this box for $myn_{a..e}
to make it work?
Hi,
I have not used binat, but I think that you need to add
10.160.15.{11..25} as IP aliases on bge1, so try adding
inet alias 10.160.15.11 255.255.255.255
inet alias 10.160.15.12 255.255.255.255
inet alias 10.160.15.13 255.255.255.255
inet alias 10.160.15.14 255.255.255.255
inet alias 10.160.15.15 255.255.255.255
to hostname.bge1
Don't forget to enable forwarding:
sysctl net.inet.ip.forwarding=1
Also, the "stupid devices" have to have default gateway pointed at
192.168.111.2, or you have to do SNAT on traffic leaving bge0, since
otherwise "stupid devices" will not know the packet's return path.
Kind regards,
--
Łukasz Moskała
Re: Running redmine on OpenBSD
Hello Radek, I am running Redmine on OpenBSD 6.8 and I just followed the installation instructions posted on the Redmine page which are quite complete: https://www.redmine.org/projects/redmine/wiki/Installation_Guide I installed Postgres and Ruby+Dependencies from the OpenBSD packages. Werner On 11/10/21 00:56, Radek wrote: Hi @misc, Does anyone successfully run redmine[1] on OpenBSD? I'd like to install redmine on 7.0/amd64 with httpd and postgresql. I've never done it before so any advices and hints would be appreciated. There isn't much up to date info in google about it[2][3]. 1. https://www.redmine.org/ 2. https://www.redmine.org/boards/2/topics/496 3. https://web.archive.org/web/20160406041905/http://www.iwebdev.it/blog/?p=229 Thank you!
Re: transparent https proxy with using pf's rdr-to and divert-to
On 2021-11-11, Edward Crawler wrote: > Hi Misc, > > I'm writing a transparent https proxy for tls inspection. This proxy works > fine when I use "rdr-to" in pf. > However, when I try use "divert-to", it's not working.. > > What's the actual difference between the rdr-to and divert-to? What could be > the problem? > rdr-to rewrites the address on the packets so in order to retrieve the original addresses you need write access to /dev/pf so you can use the DIOCNATLOOK ioctl. divert-to does not rewrite them so in that case you use (unprivileged) getsockname. -- Please keep replies on the mailing list.
Re: forum software recommend?
* Paul Wisehart le [10-11-2021 07:58:08 -0500]: > > Hi!, > > Does anyone recommend a forum software that works well with OpenBSD/httpd? > > I installed phpBB, and it seems fine, but I figured I'd ask here before > forging ahead. > > Thanks!, > -- > Paul Wisehart > Hi, I tried MyBB and it works well. However, I prefer FUDforum, much simpler and easier to administer IMHO. Regards.
Re: Support
On Thu, Nov 11, 2021 at 09:19:00AM +0100, Michael Hekeler wrote: > Am 10.11.21 03:57 schrieb Brian O'Loughlin: > > Hi > > > > Further to my support request in September, (...) > > You are refering to an email x weeks ago? > I think you will get more helpful answers if continuing your old thread I doubt it. Have you seen the original thread?
transparent https proxy with using pf's rdr-to and divert-to
Hi Misc, I'm writing a transparent https proxy for tls inspection. This proxy works fine when I use "rdr-to" in pf. However, when I try use "divert-to", it's not working.. What's the actual difference between the rdr-to and divert-to? What could be the problem?
Problem boot cd70.iso and install70.iso on sparc from sparc64 release
Hi,
The release versions of both cd70.iso and install70.iso will not ( at least
for me ) boot my sparc machines. The files from snapshot will boot these
machines! Please see the two machines reports below.
Now I have tried to use a snapshot cd70 boot to install from stable but so
far I have been unable to do this. The snapshot installs fine but of course
uses the files sets from the snapshot directory.
On a working 7.0 snapshot install...
I tried to install the Yubikey tools from packages and also build from
ports. Both failed with some problem with a python conflict. I would like
to be able to install the release ( stable ) version of OpenBSD sparc64 and
build the ports. Any help would be most appreciated. I have posted
regarding the inability to boot sparc from release ( stable ) previously
but have had no replies.
Any help?
Keep safe, kind regards John.
Sun Fire V100
===
ok boot cdrom
Resetti
LOM event: +1h42m22s host reset
ng ...
Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0
Probing upa at 1f,0 pci
Probing upa at 0,0 SUNW,UltraSPARC-IIe (512 Kb)
Loading Support Packages: kbd-translator
Loading onboard drivers:
Probing /pci@1f,0 Device 7 isa dma rtc power SUNW,lomh serial serial
flashprom
Probing /pci@1f,0 Device 3 pmu i2c temperature dimm dimm dimm dimm
i2c-nvram idprom motherboard-fru ppm beep fan-control
lomp
Probing Memory Bank #0 512 Megabytes
Probing Memory Bank #1 512 Megabytes
Probing Memory Bank #2 512 Megabytes
Probing Memory Bank #3 512 Megabytes
Probing /pci@1f,0 Device 7
Probing /pci@1f,0 Device 3
Probing /pci@1f,0 Device c ethernet
Probing /pci@1f,0 Device 5 ethernet
Probing /pci@1f,0 Device a usb
Probing /pci@1f,0 Device d ide disk cdrom
todm5819 Sun Fire V100 (UltraSPARC-IIe 548MHz), No Keyboard
OpenBoot 4.0, 2048 MB memory installed, Serial #56397165.
Ethernet address 0:3:ba:5c:8d:6d, Host ID: 835c8d6d.
Environment monitoring: disabled
Executing last command: boot cdrom
Boot device: /pci@1f,0/ide@d/cdrom@3,0:f File and args:
OpenBSD IEEE 1275 Bootblock 2.1
..>> OpenBSD BOOT 1.21
Trying bsd...
Booting /pci@1f,0/ide@d/cdrom@3,0:f/bsd
4102856@0x100+1336@0x13e9ac8+3247500@0x1c0+946804@0x1f18d8c
OF_map_phys(dfdfc000,8192,fff5a000,-1) failed
no space for symbol table
Program terminated
ok
Sun T5120
=
Oracle(R) Integrated Lights Out Manager
Version 3.0.12.9 r117324
Copyright (c) 2017, Oracle and/or its affiliates. All rights reserved.
sc> console
Enter #. to return to ALOM.
{0} ok boot cdrom
SPARC Enterprise T5120, No Keyboard
Copyright (c) 1998, 2017, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.33.6.h, 16256 MB memory available, Serial #85158202.
Ethernet address 0:21:28:13:69:3a, Host ID: 8513693a.
Boot device: /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/storage@2/disk@0:f
File and args:
OpenBSD IEEE 1275 Bootblock 2.1
..>> OpenBSD BOOT 1.21
ERROR: /iscsi-hba: No iscsi-network-bootpath property
Trying bsd...
Booting /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/storage@2/disk@0
,0:f/bsd
4102856@0x100+1336@0x13e9ac8+3247500@0x1c0+946804@0x1f18d8c
OF_map_phys(ffc6e000,8192,fecea000,-1) failed
no space for symbol table
Program terminated
{0} ok
Re: What language is the bsd.ports.mk file written in?
It's written in BSD make, c.f., https://man.openbsd.org/make .Sent from my Galaxy Original message From: songzongquan Date: 11/11/21 08:28 (GMT+00:00) To: misc Subject: What language is the bsd.ports.mk file written in? What language is the bsd.ports.mk file written in?
What language is the bsd.ports.mk file written in?
What language is the bsd.ports.mk file written in?
Re: Support
Am 10.11.21 03:57 schrieb Brian O'Loughlin: > Hi > > Further to my support request in September, (...) You are refering to an email x weeks ago? I think you will get more helpful answers if continuing your old thread
