Re: mips64el packages deprecated?
On 2017-05-05, Roland Kammerer wrote: > Today I upgraded to OpenBSD 6.1 and saw that none of the mirrors seem to > contain packages for mips64el anymore. > > Are they still building? Yes. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: mips64el packages deprecated?
On 2017-05-19, Roland Kammerer wrote: >> > Today I upgraded to OpenBSD 6.1 and saw that none of the mirrors seem to >> > contain packages for mips64el anymore. >> > >> > Are they still building? >> >> Yes. > > Are we there yet? Are we there yet? ;-). Yes, the packages are finished. They should show up on the mirrors real soon now. > I think for the last 5 or so releases I updated pretty soon after > the official release, so this looks new... Previously, there was a long delay between when the release was finalized and when it was published. This allowed for CD production and for the slow archs to finish building packages. For 6.1, this delay was mostly eliminated, but this also means that the packages for the non-x86 architectures arrive later, according to the time it takes to build them. -- Christian "naddy" Weisgerber na...@mips.inka.de
Configuring unbound(8) for ULA stub zones
Say you use unbound(8) as a validating resolver. And you use IPv6 ULA private address space on your network and you have configured stub zones in unbound(8) to resolve your private host names. Name resolution works fine, but reverse resolution does not. WTF? To save you the hours I wasted on this, here are two things you need to know: 1. By default, unbound(8) internally returns NXDOMAIN for a number of reverse DNS zones for private and reserved addresses. This includes d.f.ip6.arpa. It's actually mentioned in the unbound.conf(5) man page. So if you use fdxx::::/48, you want to add local-zone: "x.x.x.x.x.x.x.x.x.x.d.f.ip6.arpa." transparent to your unbound.conf(5). 2. If you have DNSSEC validation enabled, reverse resolution still fails. At a sufficient verbosity level, unbound(8) says: Could not establish a chain of trust to keys for f.ip6.arpa. DNSKEY IN It greatly helps to add a negative trust anchor for the ULA space to unbound.conf(5): domain-insecure: "d.f.ip6.arpa." PS: Since we're talking about ULA space, the way to generate the digits for your unique prefix is this: openssl rand -hex 5 Ignore the RFC 4193 algorithm. It is intended for people that don't have randomness. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: bioctl crypto size limitation ?
On 2017-05-25, myml...@gmx.com wrote: > fdisk -iy -g sd0 (I left off the "-b 960" because this is not a > bootable partiton) Back in March, Eric Huiban noticed this: | i just performed some remote connection... recreating GPT with an .i EFI | boot partition. The softraid is now 2.7TiB... Grumbl! conclusion : | bioctl needs a mandatory bootable partition to act correctly even on | disks not aimed to be bootable. https://marc.info/?l=openbsd-misc&m=148854591221493&w=2 -- Christian "naddy" Weisgerber na...@mips.inka.de
vesa vs. wsfb?
Between the vesa(4) and wsfb(4) X11 video driver, are there any advantages one has over the other? I have a brand new laptop (Kaby Lake) whose integrated graphics chipset isn't yet supported by inteldrm(4)/intel(4). vesa(4) works if you remember to enable machdep.allowaperture. And since the machine boots through UEFI and efifb(4) attaches, wsfb(4) is also available and can be enabled with a minimal xorg.conf: Section "Device" Identifier "Device0" Driver "wsfb" EndSection I went with wsfb because it doesn't need allowaperture. Any other differences? PS: The FAQ is silent on this topic. I had to dig through old mailing list posts for a reminder to enable allowaperture. I knew there was a wscons-based driver, too, but if you don't know the exact name, wsfb(4) is hard to find. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: xntp mlockall issue patched yet?
On 2017-07-07, Kaya Saman wrote: > I'm running current (6.1 GENERIC.MP#99 amd64) and keep getting this > message when trying to start ntp from @ports: > > ntpd 4.2.8p10@1.3728-o Fri Jun 2 02:18:56 UTC 2017 (1): Starting > > mlockall(): Cannot allocate memory > > fatal out of memory (32 bytes) What exactly is your problem? The ntpd from the net/ntp port runs fine. It logs a harmless error "mlockall(): Cannot allocate memory", but this doesn't affect its operation. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: xntp mlockall issue patched yet?
On 2017-07-07, Kaya Saman wrote: >>> ntpd 4.2.8p10@1.3728-o Fri Jun 2 02:18:56 UTC 2017 (1): Starting > > The exact problem is that the service doesn't start... I have disabled > the ntpd from base in rc.conf then execute the rc.d script and no > service?? - just the error above. > > The service is added in rc.conf.local as such: > > xntpd=YES > xntpd_flags="" That's not the way xntpd is enabled. You may want to use rcctl(8): # rcctl stop ntpd ntpd(ok) # rcctl disable ntpd # rcctl enable xntpd # rcctl start xntpd xntpd(ok) The relevant lines in /etc/rc.conf.local end up being this: ntpd_flags=NO pkg_scripts=xntpd -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: ntpd clock unsynced in vm
On 2017-07-18, tomr wrote: > In playing with vmd, I'm unable to get the guest's ntpd to sync to its > upstream ntp (whether that's the host ntpd or poot.ntp.org). The guest > is losing about 1 second for every 2 that pass. To build a bridge between this question and Mike's reply: This problem has nothing to do with ntpd. ntpd's ability to adjust the clock is limited by adjtime(), which can correct time up to a generous maximum of 5 milliseconds for each second. If your clock drift is worse than that, your clock is broken. Which alas is the case for vm. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: octeon packages
On 2017-07-19, Predrag Punosevac wrote: > I got myself a new toy, Ubiquiti Networks - EdgeRouter Lite. I am a bit > confused about packages for Octeon. I don't see any neither for 6.1 > release nor for 6.1 snapshots. Use the mips64 packages. It's actually explained in INSTALL.octeon. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: AMD64 modern laptop recommendation
On 2017-07-18, Radoslav_Mirza wrote: > To congratulate myself for 2 years of not smoking I want to buy a new medium > to high end laptop and install only OpenBSD on it. > > Does anyone run OpenBSD on a brand new laptop with good support? I recently treated myself to a current (5th gen) Thinkpad X1 Carbon. The principal limitation at the moment, shared by all current laptops with a Kaby Lake CPU, is that there is no inteldrm(4) support yet: * You need to run X11 with wsfb(4). Non-accelerated, but perfectly fine for my use: window manager, xterms, web browser. * No backlight control. * No suspend/resume. Well, suspend works, and resume mostly works, except that there is no video. Beyond that, it just works. In particular, these work: * UEFI boot * nvme(4) for the SSD * em(4), Intel I219-V * iwm(4), 8265; the driver spews various warnings/errors but seems to work in practice * audio, keyboard, trackpoint, trackpad There is so much hardware, I haven't used or tested it all. I don't know about the status of these: * HDMI output * camera, uvideo(4) attaches * LTE modem, umb(4) attaches * fingerprint reader The poorly accessible SD card reader isn't supported. The UEFI BIOS comes with two sets of default settings. The normal ones and "OS Optimized Defaults" for Windows 10. My machine came configured with the latter, so I switched it back to the standard defaults. If you want to disable hyperthreading, you're out of luck: there is no such option. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: iwn0: no link after 6.1 upgrade
On 2017-08-19, Stefan Sperling wrote: >> Yes, I have double-checked, this is what is shown in the Web GUI. >> "Authentication PassPhrase Settings" : "WPA-Personal" >> "WPA Mode" : "WPA2 Only" >> "Cipher Type" : "TKIP" > > Please set Cipher Type to 'AUTO' or 'AES'. Then it should work. > TKIP is used with WPA1 only. The cheat sheet I kept for my DAP-2310 says: ... - Wireless Settings SSID Authentication WPA-Personal WPA ModeWPA2 only Cipher Type AES PassPhrase ... -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Using USB headsets
On 2017-08-16, Norman Golisz wrote:
> I'm trying to figure out how to get my USB headset (Plantronics C310)
> to work.
>
> I can't hear anything, nor does the microphone work. I fiddled with
> different mixerctl settings to no avail, and I'm not even sure my
> headset had been detected at all, as the available options to set
> don't change, while I plug or unplug the device[1].
> dmesg[2] happily reports it detected and configured the device:
>
> uaudio0 at uhub0 port 1 configuration 1 interface 0 "Plantronics Plantronics
> C310" rev 2.00/1.35 addr 2
> uaudio0: audio rev 1.00, 7 mixer controls
> audio1 at uaudio0
My guess is that all your audio commands actually refer to...
> audio0 at azalia0
... instead of audio1. If you want to use only the headset, the
easiest fix may be to switch the /dev/{audio,audioctl,mixer} symlinks
from the *0 devices to the *1 ones.
--
Christian "naddy" Weisgerber na...@mips.inka.de
Re: Problem with key bindings with mutt under OpenBSD 6.1
On 2017-09-02, "C. L. Martinez" wrote: >> > bind index \CO sidebar-open >> > >> > Problem is with "\CO". It doesn't works under OpenBSD but it works >> > without problems under FreeBSD 11 or RHEL7/CentOS7. >> >> $ stty discard undef; mutt > > Perfect!! .. It is working.. Many thanks Anton. That is really odd because FreeBSD also has the discard control character set to ^O by default. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: gtar: ambiguous package
On 2017-10-09, "Todd C. Miller" wrote: >> a 0: >> 1: gtar-1.28p1 >> 2: gtar-1.28p1-static > > Packages with the -static suffix are statically linked and do not > depend on shared libraries. This means that the binary is not > affected by changes in the shared libraries, which can be handy for > development. It can be especially handy for a backup tool, so you can recover even if your shared libraries are messed up. Another potential use for a static flavor is running something in a www chroot. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: 6.2 starts nsd before slaacd binds ipv6 address
On 2017-10-09, lists+m...@ggp2.com wrote: > I don't feel this warrants a bug report, but nevertheless feel that this > behavior is inconsistent with the way dhclient works. I have a vultr > server running nsd/OpenBSD 6.2, and I suspect that the move to slaacd > from kernel code in 6.1 is what has broken my nsd config (it fails to > start on boot now). There definitely are races in the demon startup sequence. It's less clear what to do about them. At home, I have my own stratum 1 NTP server, so my standard ntpd.conf is "server ntp". This seemingly innocuous configuration has revealed _two_ races. (1) slaacd, ntpd I also have "family inet6 inet4" in resolv.conf, and ntp(.mips.inka.de) has both an A and an record. ntpd should thus talk to the server at the v6 address. However, on faster machines it ends up talking to the server's v4 address, because slaacd hasn't successfully configured the local v6 address yet when ntpd starts. (2) nsd, unbound, ntpd On my home gateway I run unbound as caching name server. My private mips.inka.de namespace is configured as a stub-zone supplied by nsd running on the same machine on port 5353. I was quite surprised to find that ntpd on the gateway wasn't talking to ntp.mips.inka.de but instead to ntp.inka.de--a very different machine. Apparently, at the time ntpd starts and queries unbound, nsd isn't ready yet and unbound can't resolve ntp.mips.inka.de, leading to another attempt to resolve "ntp" as ntp.inka.de. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: macppc netboot
On 2017-10-18, Solène Rapenne wrote: > Are you able to fetch /bsd.rd if you use tftp in command line ? How is this relevant? Netbooting is inherently machine-dependent. Firmware aside, there are also at least two OpenBSD bootloader flavors: * pxeboot (amd64, i386) uses TFTP to load the kernel. * netboot (alpha) and ofwboot.net (sparc64) load the kernel from an NFS server. Looking at INSTALL.macppc, I see that macppc's ofwboot works along the lines of alpha and sparc64. If you are trying to give advice based on amd64/i386, then this will be bogus and misleading. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Status of mips64el packages for 6.3
On 2018-05-10, Xiyue Deng wrote: > I noticed that a few days ago (maybe around Monday) the 6.3 release > page[1] has updated mips64el package count: > > mips64el: 8254 Sorry, these are indeed ready, but they haven't been uploaded to the release directory yet. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: ISDN Card /PRI Card support on OpenBSD
On 2018-07-11, Tom Smyth wrote: > this is an odd one but I have a client that needs to > migrate some legacy services > Is there support for ISDN type interfaces in OpenBSD ? No. (Once upon a time there was something called isdn4bsd, but I don't think it was ever officially integrated into OpenBSD, and that's from, oh, twenty years ago.) -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: supported Audio card with SPDIF input
On 2018-07-24, Diana Eichert wrote: > I'm trying to connect to an audio system that only has SPDIF output. > I looked at man pages but nothing obvious regarding supported audio > devices with SPDIF input support. > > Anyone have recommendations? Or is it supported? Your best bet is azalia(4), i.e, it needs to be supported by the motherboard. There are uaudio(4) devices with SPDIF output, however there you may run into issues with our USB support and audio devices. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: autri(4) disabled by default
On 2018-07-31, Janne Johansson wrote: >> I see autri(4) is disabled by default in an amd64 kernel, probably >> others too, and has been for a very long time. > > Seems like it came over with the initial amd64 port from i386, and noone > tested it on amd64, so it never got enabled but remained commented out. It worked on sparc64, where it is enabled by default, back when I still had a Blade 100. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: phonetic alphabet on OpenBSD
On 2018-10-14, Jan Stary wrote: > Are there any phoneticians running on OpenBSD? I still haven't read Ladefoged yet, but I use IPA somewhat regularly. > How do you type the phonetic alphabet in vim? > Is there a standard keyboard layout for the English part of IPA? I don't use vim, but the sad answer is that I copy and paste, principally from Wikipedia's IPA page. If you're only dealing with English, the Help:IPA/English page is more convenient. In general, I use the X11 compose key to enter special characters. See /usr/X11R6/share/X11/locale/en_US.UTF-8/Compose for the available combinations. That's sufficient for entering the letters and diacritics used in all European languages that use the Latin alphabet. However, it does not cover IPA. Vim comes with its own "digraph" system, which uses the RFC1345 digraphs by default. They cover a wide range, including Greek and Cyrillic, but alas, there's another big hole in the Unicode range where the IPA block (U+0250..02AF) is. > but I am looking for a "standard" way. I suspect people use an on-screen keyboard / character picker. In fact, googling for immediately finds a bunch of web-based ones. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: phonetic alphabet on OpenBSD
Chris Bennett: > When I last looked, apparently IPA had two fonts, neither of which > worked for all the characters. Is this still true? You don't need extra fonts. IPA is covered both by Deja Vu that OpenBSD ships as the default TrueType font, as well as xterm's default bitmap font. > I have to ask also, is the audio quality that comes out the speakers (in > general) good enough to learn the proper sounds? Every device I have > seems to have wildly varying qualities and characteristics. > For example, (OK, not OpenBSD but somewhat relevant) if I wanted to > listen to the speech coming out of Google Translate, would a native > speaker of say Spanish, German or Russian consider the sounds "proper"? What a bizarre question. Listen to English dialog from your speaker setup. Does it sound like "proper" English? Anything that plays music in reasonable quality--so *anything*, really--will more than do for human speech. Google Translate's audio is machine-generated text-to-speech output. Again, check what it does for English. > Is there any software that makes proper sounds available (to port, I'm > too poor to buy non-free)? You might find this interactive IPA chart useful: http://www.ipachart.com/ > Haven't yet seen a class offering: > "How to correct your pronunciation years later to sound normal" That's the work of speech therapists and dialect coaches. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Ctrl+4 means SIGQUIT+coredump, where is this documented, what more shortcuts are there?
On 2018-10-31, Stuart Henderson wrote: > No idea how ^4 is mapped to ^\, but for some reason it is, This goes back to the VT220, if not older terminals. Ctrl-3 for ESC aka ^[ is particularly handy if the Esc key is in some inconvenient place as on most PC keyboards. See "Table 3-5 Keys Used to Generate 7-Bit Control Characters" in the VT220 Programmer Reference Manual: https://vt100.net/docs/vt220-rm/table3-5.html -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Which key shortcuts are safe to bind and some Q:s about history and OS diffs Re: Ctrl+4 means SIGQUIT+coredump, where is this documented, what more shortcuts are there?
On 2018-11-01, Tinker wrote: >> > No idea how ^4 is mapped to ^\, but for some reason it is, >> >> See "Table 3-5 Keys Used to Generate 7-Bit Control Characters" in >> the VT220 Programmer Reference Manual: >> https://vt100.net/docs/vt220-rm/table3-5.html > > Historial reasons, a ha. And I'll venture a guess why DEC added those combinations: In order to type ^[ ^\ ^] to produce the ESC, FS, GS characters, you need keys for [ \ ]. If you look at non-English keyboard layouts, you'll see that the corresponding keys have been re-purposed for other characters. In the old days of national ASCII variants, even the characters [ \ ] didn't exist in many national encodings. Later, when extended 8-bit character sets were introduced, [ \ ] were only made available in a secondary mapping reachable with an extra modifier key (AltGr or such). And that's the situation right into the present. By contrast, combinations like ^3, ^4, ^5 were readily available on keyboards. https://en.wikipedia.org/wiki/ISO/IEC_646#ISO_646_national_variants -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: colorls: How to make the blue bright for readability, and a note about its origins
On 2018-11-05, Joseph Mayer wrote:
> This is how to make OpenBSD's colorls show directories bright blue,
> instead of dark blue which may be too dark to be readable on some
> screens:
This is a general problem with the primitive 8/16-color system from
ECMA-48 ("ANSI colors"). Some text colors only work well with a
light background, some only with a dark background.
> The colorls port [1] is interesting, its source [2] seems to be a fork
> of the BSD codebase's ls dating back to 1980, the man page doesn't
> mention any particular authorship, and its code was updated as
> recently as this year.
It's simply OpenBSD's src/bin/ls with a color patch from FreeBSD
on top.
--
Christian "naddy" Weisgerber na...@mips.inka.de
Re: Easiest way to automatically run a script after reboot
On 2018-11-10, Steve Williams wrote: > I have a script that I would like run after all the network is > configured, daemons started, etc. > > I looked at rc.local, but am not sure what is actually started after the > rc.local runs. Let's take a look at /etc/rc: ... [[ -f /etc/rc.local ]] && sh /etc/rc.local # Disable carp interlock. ifconfig -g carp -carpdemote 128 mixerctl_conf echo -n 'starting local daemons:' start_daemon apmd sensorsd hotplugd watchdogd cron wsmoused xenodm echo '.' ... Also, as you can see, cron(8) is started late, and you can put a @reboot entry into crontab(5). -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: No mips64el in 6.4 package
On 2018-11-11, Lingyun Zheng wrote: > There is no "mips64el" directory under > https://cdn.openbsd.org/pub/OpenBSD/6.4/packages/ > Do we have any plan to add it? Once the packages have finished building, yes. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: undefined symbol tgetent
On 2018-11-12, Michael Steeves wrote: > I've updated my system to the latest snapshot, and then upgraded all the > packages (and rebooted for good measure), but I still see these errors. I > assume there's no simple fix for this, and I'd need to either file bugs (and > wait until they're fixed), or else build the ports myself? The problem is known and understood. It's now a matter of either (1) pushing for a general solution in base or (2) fixing all 30+ potentially affected ports individually. We'll just have to wait until somebody gets around to doing either. Building the port yourself will just reproduce the problem. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: riscv
On 2020-03-13, "Peter J. Philipp" wrote: > Any developer working on a riscv port and willing to share their unofficial > work for possible future collaboration? I think I'd have heard by now if somebody was, so I'll go out on a limb and say no, nobody's working on a RISC-V port. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Wine for OpenBSD?
On 2020-04-11, Nikita Stepanov wrote: > Wine for OpenBSD? At hackathons, we typically ask the French developers to pick out a wine from the menu, but they are pretty reluctant to take on this responsibility. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: More than 16 partitions
On 2020-04-23, Ian Darwin wrote: > So: I was able to newfs, mount, and use an OpenBSD partition which > disklabel called 'a' and which had no trace of an fdisk partition around it. > > As Allan pointed out, this is not for booting from - none of those > fdisk partitions looks very healthy. biosboot(8) has an MBR boot signature. If the BIOS doesn't check for a valid MBR partition table--some do, some don't--then it should be able to directly run biosboot(8) from sector 0. installboot(8) tries to prevent such a configuration, but it could be tweaked, or you could try to tweak the disklabel and set the type to floppy, because floppies don't have MBR partitions. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: OpenBSD insecurity rumors from isopenbsdsecu.re
On 2020-05-11, Stuart Longland wrote: > BSD came from the US (University of California), but most of today's > implementations have been very significantly changed since then. BSD built on top of AT&T UNIX, which came from Bell Labs in New Jersey. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Convert ffs1 to ffs2?
On 2020-05-20, Christer Solskogen wrote: > Is that possible? umount, dump, newfs, mount, restore -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Filling a 4TB Disk with Random Data
On 2020-06-01, Justin Noor wrote: > Has anyone ever filled a 4TB disk with random data and/or zeros with > OpenBSD? Yes. > How long did it take? I don't remember. Hours. At a plausible 100 MB/s write speed it will take 11 hours. > What did you use (dd, openssl)? Can you share the command that you used? # dd if=/dev/random of=/dev/rsd1c bs=64k# random data # dd if=/dev/zero of=/dev/rsd1c bs=64k # zeros Take care to pick the proper device corresponding to the drive you want to overwrite. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Issues expanding partition to grow disk
On 2020-06-02, "Darren S." wrote: > I'm dealing with a VPS on KVM with the disk having been recently > expanded from 50 >> 80 GB. > > Disklabel shows reasonable total sectors: > > # disklabel sd0 > total sectors: 167772160 > boundstart: 64 > boundend: 115330635 The upper boundary is still set to 55G. In the disklabel editor use b * to move it to the end of the disk. > Is this something to do with it being a virtual disk in a certain > configuration? And is this a case where I may need to set the disk > boundaries in disklabel(8) as described (although I don't know if this > fits description of "ports with fdisk(8) partition tables where..."): It fits the unmentioned case of a labeled disk later growing. Actual drives don't do that. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Filling a 4TB Disk with Random Data
On 2020-06-05, Roderick wrote: >> I'd think that a degausser would also erase the servo tracks which will make >> the disk irrevocably unusable. If that's what you want then just drill holes >> through the disk - it's quicker. > > Or perhaps to put it on an induction cooktop? I always keep a vat of molten steel at hand so I can easily dispose of old disk drives, killer robots from the future, etc. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: hostname.pppoe0, !/bin/sh when reconnecting
On 2020-06-17, Lévai, Dániel wrote: > I'm trying to run a script whenever I get a new IP address from my ISP over > pppoe0. They disconnect me occasionally and the router reconnects then, eg.: > /bsd: pppoe: GENERIC ERROR: RP-PPPoE: Child pppd process terminated > /bsd: pppoe0: received unexpected PADO > last message repeated 2 times > > I have this as the last line in /etc/hostname.pppoe0: > !/bin/sh /etc/hostname.pppoe0.script pppoe0 0.0.0.1 > > It doesn't seem to be executed when this happens, only when I reboot the > router. /etc/hostname.* is only executed once when the system starts. The PPP disconnect/reconnect is handled entirely by pppoe(4)--well, sppp(4) really--in the kernel. There is no callout to the userland available. It may be possible to use ifstated(8) for this. I haven't tried that, but it's where I would start looking. > Is the culprit here something along the lines of not (re)configuring the > interface with ifconfig up/down (in which case the script would run), Note that ifconfig down/up will not run /etc/hostname.* either. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Cleaning system's old ibraries/files after update to next -release or -current
On 2020-07-14, Ottavio Caruso wrote: >> > After system update I found lots of 'old' libraries versions >> > and possibly binaries from previous releases. >> >> If you need to ask, just don't remove them. Those files eat no bread, >> and in some situations, some of the libs may still be in use. > > What about if one compiles ports? If OpenBSD is anything similar to > NetBSD, on the latter having multiple libs might cause build > breakages. Old versions of libraries are innocuous. They will simply be ignored. Potential sources of trouble are old copies of libraries that no longer exist and header files that no longer exist. OpenBSD hasn't retired a base library in a long time, so that isn't an issue. I recommend cleaning up /usr/include, though. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Upgrade old 6.2 but 6.3 SHA256.sig on mirror different
"Theo de Raadt": > Johan Mellberg wrote: > > and https://ftp.openbsd.org/pub/OpenBSD/6.3/amd64/SHA256.sig > > (Canada, as I like to take them from different sources). I then ran: > > The format of the .sig files was changed in a very small way, intentionally, > way back then. You are hitting that issue. Sorry, no, the file is corrupted. I just downloaded https://ftp.openbsd.org/pub/OpenBSD/6.3/amd64/SHA256.sig and it contains only nul bytes. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: scp host:file* /tmp/nonexistent
On 2020-08-01, Roderick wrote: > It is not documented in 4.4BSD. I suppose this is not original BSD? Public service announcement: The original BSD repository can be browsed here (converted from SCCS): https://svnweb.freebsd.org/csrg/ Wanna know what those hippies at Berkeley really did? You can look it up. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: gcc not on new OpenBSD 6.7 machine, clang problems
"Whiskey T.": > My datacenter installed OpenBSD 6.7 on a new machine: > > # uname -a > OpenBSD machine name 6.7 GENERIC.MP#182 amd64 > > # which gcc > which: gcc: Command not found. > configure:3711: checking whether the C compiler works > configure:3733: ccconftest.c >&5 > ld: error: cannot open crt0.o: No such file or directory Your OpenBSD installation is incomplete. The "comp" set was not installed. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: i386, parallel port permission error?
On 2020-08-19, Doug Moss wrote: > I think the problem in lcdproc is in the code from this file (port.h) > https://github.com/lcdproc/lcdproc/blob/master/server/drivers/port.h > > I am out of my depth with this code. I have never even seen these > calls 'outb' and 'inb' You're saying this as if you never did any MS-DOS or CP/M programming. Which is the mindset with which some of those "drivers" were written. I've had to touch the lcdproc port a bunch of times, because it keeps breaking, and we had to disable ever more of it. It supports a zillion LCD modules--virtually all of them vastly obsolete, I assume--with userland "drivers" that frequently need direct hardware access. The concept is fundamentally broken on Unix. I have no idea if the fraction of functionality that is still available is even useful, and I would be inclined to just remove the port. Apparently there is some newer upstream code available, but there is no port maintainer, nobody cares, it won't fix the fundamental problems, and so the rotting carcass just languishes. No, no, don't remove it, it might still work for somebody somewhere... Oh well, then. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Understanding of keydisk backup for FDE
On 2020-08-27, Andreas Menge wrote: > I try to wrap my head around why the FAQ > (https://www.openbsd.org/faq/faq14.html#softraidFDEkeydisk) says that one > should create a backup of the keydisk with bs=8192 and skip=1. > > From the FAQ: > > # dd bs=8192 skip=1 if=/dev/rsd1a of=backup-keydisk.img > # dd bs=8192 seek=1 if=backup-keydisk.img of=/dev/rsd1a This copies the relevant softraid meta data. > My personal inclination was to just dd the whole disk (like dd if=/dev/rsd1c) > ... That works, but it means the disks will now share the same disklabel with the same size (even if the USB sticks differ in size), the same label, the same "unique" disk ID. That won't matter for their use as keydisk, but if you ever re-use them for something else later, you'll need to remember to recreate the disklabel or weird things may happen. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: iwm0: fatal firmware error on Dell Latitude E5570
On 2020-09-24, Jan Stary wrote: > This is 6.8-beta/amd64 on a Dell Latitude E5570 (dmesg below). > iwm stopped working, saying > > iwm0: hw rev 0x200, fw ver 34.0.1, address e4:a4:71:40:21:08 > iwm0: fatal firmware error > iwm0: could not remove MAC context (error 35) I've been getting a lot of those lately, but my iwm keeps recovering from them eventually. Frankly, I've mostly stopped paying attention. I update my laptop every other week or so, and the reliability of wi-fi keeps fluctuating from kernel to kernel, sometimes it's better, sometimes it's worse, and I don't think it correlates well with commits or firmware updates. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: time_t
On 2020-10-05, "Peter N. M. Hansteen" wrote: > I hadn't looked in a while, but it amazes me that FreeBSD still has > 32-bit time_t. Only on FreeBSD/i386. On all other architectures, time_t is int64_t. See src/sys/*/include/_types.h. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: time_t
On 2020-10-05, Roderick wrote: > The source of my confusion with FreeBSD: > /usr/include/x86/_types.h contains: >typedef __int32_t __time_t; >typedef int __int32_t; $ fgrep time_t /usr/include/x86/_types.h typedef __int64_t __time_t; /* time()... */ typedef __int32_t __time_t; There's an #ifdef __LP64__ ... -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Router advertisements for dynamic IPv6 prefix
On 2020-10-14, Fernando Gont wrote: > Set the VL to 30', and the PL to 15'. You could even set the VL to 15', > and the PL to 7.5', if necessary. How does this influence the lifetime of privacy addresses? Even with rad(8)'s defaults, I already need to specify an originating non-privacy address for all long-running ssh sessions, otherwise they die when the privacy address they're using is forcefully expired after a week or so. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: UNIX printing demystified
On 2020-10-24, Mihai Popescu wrote: > Is there a way to interface LPD directly with GUI apps like Chromium, > mupdf, etc? I mean just to print from GUI menu Print. Those print menus _should_ offer the option to print to lpr. They traditionally did. If they don't now, then this is worth examining. What GUI toolkit does the application use and what does this toolkit do? The GTK+ case is instructive. Once upon a time, the GTK print menu offered printing to lpr. A number of years ago that disappeared. Why? Originally, GTK produced print output in PostScript. The assumption was that you could send this to any lpr printer, since PostScript has effectively been the standard printer language in Unix for decades. The print menu changed, because GTK had switched to producing print output in PDF. The assumption was that random lpr printers could not handle PDF, so the option of printing to lpr was removed. Fast-forward to the present. Virtually all printers that can handle PostScript also accept PDF directly and have been able to do so for years. Finally, two weeks ago (!) the GTK people relented and have marked the lpr backend as capable of accepting PDF. This means that print-to-lpr is going to become available again in GTK applications. On OpenBSD that will most likely happen with the next x11/gtk+3 update. Are there still any GTK+2 applications with a print menu in the ports tree? Let me know, and I'll take a look at what's up there. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: openrsync out of memory
On 2019-08-16, Jan Stary wrote: >> Does that mean openrsync tries to mmap() the entire file? >> The machine only has 256MB of memory, but it does transfer >> a test file of 300MB, so that can't be it. > > I forgot about 1GB swap, so that's why it works > for files up to around 1.2G, but not larger. Why would the size of physical memory + swap matter? mmap() doesn't copy a file into memory, it maps it into the address space. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Why regex doesn't work in while loop's condition?
On 2019-09-06, Andreas Kusalananda Kähäri wrote: >> read x; while [ "$x" != [abc] ]; do echo "Not a, b or c"; break; done > > The shells in the OpenBSD base system do not support matching regular > expressions with that syntax. You may have been thinking of bash, Just to head off crazy rumors: bash doesn't either. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Requesting vi tips
On 2019-10-18, cho...@jtan.com wrote: > I didn't know [how] ! took movement commands. Thanks. I'll have a play > with that one. > > It's not quite M-q (it's M not C) but I'm using vi after all. Since 'q' is unused in nvi, I have this in my .nexrc: map q !}fmt Close enough to emacs's M-q. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Requesting vi tips
On 2019-10-18, Nam Nguyen wrote: >> Since 'q' is unused in nvi, I have this in my .nexrc: >> map q !}fmt > > I just wanted to add that you can Ctrl-v Enter to produce the ^M at the end. > This way it inputs and executes the command for you. > > It could be like this if you want it to press Enter for you: > map q !}fmt^M And upon closer inspection I see that's what I actually have in my .nexrc; less(1) didn't show the ^M and I had forgotten about it. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: vi in ramdisk?
On 2019-11-15, Roderick wrote: >> ed is included in the ramdisk, but if your use case is using vi to fix a > > I imagine, it is there for using it in scripts. Interestingly enough, the installer itself does not use ed, as far as I can tell. * I pretty regularly use ed to perform some configuration tweaks before rebooting a freshly installed system. * I have, rarely, used ed to recover a system from errors in /etc/fstab. * Since the installer itself is just a script, it can be modified with ed in the install environment and then re-run. From time to time I do this when debugging the installer or working on some feature there. If you have some passing familiarity with sed, then ed will feel very familiar. It's just an interactive sed. (Historically, it's the other way around, of course.) > I think, for editing config files, there are sure editors that > are simpler, smaller, not so powerful, but easier to use than ed. By all means, do not keep us in suspense and tell us the names of these editors. How large is a C implementation of TECO? -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: iPXE and UEFI boot
On 2019-12-01, Christer Solskogen wrote: > I've tried sanboot for iso, but it fails. I *can* get BOOTX64.EFI to start, > but it cant find bsd.rd (perhaps BOOTX64.EFI requires tftpd?), No "perhaps". BOOTX64.EFI uses TFTP to load the kernel, just like pxeboot does. With UEFI and PXE I have successfully netbooted * arm64 (OverDrive 1000) with BOOTAA64.EFI * amd64 (Thinkpad X1C5) with BOOTX64.EFI after bluhm@'s recent bootdev_dip fix -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: iPXE and UEFI boot
Christer Solskogen: > > With UEFI and PXE I have successfully netbooted > > * amd64 (Thinkpad X1C5) with BOOTX64.EFI after bluhm@'s recent > > bootdev_dip fix > > Is that already in current? Yes, it was committed five days ago. > I now tried having bsd.rd in tftp root > directory, and BOOTX.EFI does find it (renamed bsd.rd to bsd, just to use > the default settings) > It loads the kernel but I only get a black screen. No kernel messages, what > so ever. I guess there are more bugs waiting to be found. :-( -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: LibreSSL vs. OpenSSL enc command
Dieter Rauschenberger: > This was serveral years ago before Libressl was invented. Now I wanted > to decrypt the docs with: > > openssl enc -aes-256-cbc -d < FOO.aes256 > FOO > > This did not work. The password did not work anymore. The default message digest function used for key derivation changed from MD5 to SHA256 in OpenSSL 1.1.0 and LibreSSL followed suit. openssl enc -aes-256-cbc -d -md md5 < FOO.aes256 > FOO -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: What happened to 6.6/sgi?
On 2019-12-08, Stefan Hagen wrote: > I was browsing around and noticed that there are no files for the SGI > platform on the mirrors. OpenBSD/sgi has been discontinued. No 6.6 release was built. The mips64 CPU architecture remains alive on the octeon platform. > SGI is mentioned in the 6.6/README, That was an oversight. > (snapshot/sgi exists) A several-months-old snapshot that simply hasn't been removed. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: thank you for 6.6 and bsd.rd
On 2019-12-20, "Theo de Raadt" wrote: > well you missed out > > for 6.5 onwards, all you had to was type > > sysmerge > sysupgrade I think that was intended to read syspatch sysupgrade > for 6.6 onwards you'll only need sysupgrade -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: possible SSH algorithm issues?
On 2020-01-08, "lu hu" wrote: > are these real issues? No. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Odd /tmp behavior
On 2020-01-08, Nick Holland wrote: > Weird stuff happens when Softdeps are working as designed. To put it simply: Meta-data writes are delayed. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Low throughput with 1 GigE interface
On 2020-01-30, livio wrote: > I am unable to achieve decent throughput with a 1 GigE interface > (Intel I210) on OpenBSD 6.6. When running iperf3 I get around 145Mbit/s. I get more than 30 Mbytes/s over SSH (!) to an APU2. $ scp -caes128-...@openssh.com /usr/ports/distfiles/texlive-20190410-texmf.tar.xz partoc:/dev/null texlive-20190410-texmf.tar.xz 100% 2714MB 31.8MB/s 01:25 I can't help you, I'm just posting this in the service of squashing rumors. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Low throughput with 1 GigE interface
On 2020-01-30, Jordan Geoghegan wrote: > All you're doing is benchmarking the speed of iperf on that machine. I vaguely remember a thread somewhere that concluded that one of these network benchmark tools degenerated into a benchmark of gettimeofday(2), which apparently is very cheap on Linux and not cheap on OpenBSD. So you end up measuring the performance of this system call. I don't remember whether it was iperf... -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: VLAN or aliases or? best way to isolate untrustable hosts in a small network
On 2020-02-03, Denis wrote: > Some hosts should be limited in internet access and/or local access or > simply be restricted in some way because they are untrusted. > > I'm looking for a possibility to isolate untrusted inside LAN using any > approach applicable. How do people isolate undesirable hosts in their > networks? Put hosts with different trust requirements into different networks at the IP level, connected to a central gateway where you can easily permit/deny traffic between them. Use VLANs to separate the IP networks. For example, my home network is split into three networks: * Trusted hosts. These are allowed to initiate traffic to the Internet and to the other networks. * Untrusted hosts with outside access. These are allowed to initiate traffic to the Internet at large, but not to the other networks. This is mostly my wi-fi. Also a RIPE Atlas probe. * Untrusted hosts without outside access. These cannot initiate traffic to any destination outside their network. Includes my printer and the SIP phone[1] for my "landline". That's three vlan(4) interfaces on my gateway, which provides basic DHCP/SLAAC, DNS, NTP services on all of them and has a small pf(4) ruleset to enforce the restrictions above about who can start talking to whom. [1] A SIP phone that is not allowed to talk to the outside may seem surprising, but it only needs to talk to siproxd on the gateway, and siproxd is required for NAT traversal anyway. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: VLAN or aliases or? best way to isolate untrustable hosts in a small network
Denis, I suspect the fundamental problem is that you don't understand what VLANs are. There should be a lot of articles about this topic on the net; maybe somebody here can recommend a good one. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: VLAN or aliases or? best way to isolate untrustable hosts in a small network
On 2020-02-05, Janne Johansson wrote: >> # /etc/hostname.vlan101 >> description 'WLAN attached untrusted hosts' >> inet 192.168.156.0/24 255.255.255.0 vlandev run0 > > VLANs and wifi sounds like a non-starter. Yep, if you're building your access point with OpenBSD. More generally, though, any AP in the business segment has support for multiple SSIDs that can be assigned to different VLANs on the Ethernet side. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: setxkbmap cannot completely set compose key
Xianwen Chen (陈贤文): > I forgot to report maybe an important piece of information. I use scim > to type in Chinese. I use the default xdm. Here is my .xsession: > > export LC_CTYPE=en_US.UTF-8 > > export XMODIFIERS=@im=SCIM > export GTK_IM_MODULE="scim" > export QT_IM_MODULE="scim" > scim -d I suspect it works as intended for xterm. The compose key handling is a simple input method built into libX11. You are swapping out this default IM for the SCIM one. This area of X11 seems to be virtually undocumented. See XSetLocaleModifiers(3). -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: man to render pure text? (or a pipe in vi macros ?)
Marc Chantreux: > * is there a way to ask man to deliver pure (non-formatted) text ? Pipe its output through "col -b". > * is there a way to introduce a | in vi macros? Yes, by prefixing it with a ^V character. To enter ^V in vi's input mode, press control-V twice. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: man to render pure text? (or a pipe in vi macros ?)
Marc Chantreux: > > > * is there a way to ask man to deliver pure (non-formatted) text ? > > Pipe its output through "col -b". > > what is the gain of using col over fmt ? It's the designated tool for the job. That fmt also happens to replace sequences character1-backspace-character2 with character2 is more of a lucky coincidence. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: man to render pure text? (or a pipe in vi macros ?)
On 2020-03-02, Marc Chantreux wrote: > i felt dumb reading this as i gave a try to the mandoc man. but i just > double checked: > > man mandoc|col -b|grep -w col > > gives me nothing. $ man mandoc|col -b|grep -w col to col(1) -b instead. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: dig and DNSSEC
On 2015-09-26, "Todd C. Miller" wrote: >> As Unbound/nsd are in base now, perhaps it could be easier to get >> drill in and drop dig ? > > That's a great idea. We'd need to add nslookup(1) and host(1) > wrappers though. Vitaly Magerya wrote a ldns-based host(1): http://hg.tx97.net/ldns-host Imported by FreeBSD: https://svnweb.freebsd.org/base/head/contrib/ldns-host/ -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: OpenBSD official reference book ( like FreeBSD handbook / NetBSD Guide )
On 2015-09-28, Ingo Schwarze wrote: >> What I like about the https://www.freebsd.org/doc/handbook/ > > It is intentional that OpenBSD does not have a handbook like FreeBSD. Oh come on, the OpenBSD FAQ serves the same role as the FreeBSD Handbook. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: CD's arrived
On 2015-10-07, M Wheeler <6f84c...@refn.co.uk> wrote: > CD's arrived today UK. Thanks again. Received mine today in Germany and successfully verified the signatures. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Using fsync instead of ioctl(fd, DIOCGFLUSH); (Re: anybody besides me trying to compile gpt-fdisk?)
On 2015-10-21, Joel Rees wrote: > Is fsync an appropriate way to flush writes to the disk device? In the > FreeBSD code, it is > > i = ioctl(fd, DIOCGFLUSH); Dunno, but I'd check what fdisk and disklabel do. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: LPR/LPD does not run filters
On 2015-10-27, Jona Joachim wrote: > Well, specifying 'lp' instead of 'rm' does make it run filters, but the job > is not sent to the printer, even when I use the port@host format from > the man page. As soon as I set 'rm', filters are no longer executed. Yes, that's the way lpd(8) has always worked. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Ntpd(8) in current: server (IP numerical) not used
Gerald Hanuer:
> Ntpd(8) in current: server ("IP numerical") not being used, FQDN works.
>
> ### Works as expected.
> server time1.google.com
>
> ### This does not. ( Numerical of above )
> server 216.239.32.15
I can confirm this. The bug was introduced with this commit:
CVSROOT:/cvs
Module name:src
Changes by: phess...@cvs.openbsd.org2015/10/23 08:52:20
Modified files:
usr.sbin/ntpd : client.c control.c ntp.c ntpd.conf.5 ntpd.h
parse.y
Log message:
Allowing upstream servers of ntp being in multiple routing tables is
non-sensical. The dns lookups happened in the process routing table
(usually '0'), which is very likely to have different results from the
other routing domains. If you do depend on having this behaviour,
you'll need to use pf to cross the rtable boundary.
"listen on * rtable X" is still supported.
Users of "server * rtable X" will need to switch to launching ntpd with
"route -T X exec /usr/sbin/ntpd"
OK deraadt@
Reverting these additional parts that were introduced with the
original rtable commit fixes it:
Index: parse.y
===
RCS file: /cvs/src/usr.sbin/ntpd/parse.y,v
retrieving revision 1.64
diff -u -p -r1.64 parse.y
--- parse.y 23 Oct 2015 14:52:20 - 1.64
+++ parse.y 31 Oct 2015 12:49:44 -
@@ -161,9 +161,7 @@ main: LISTEN ON address listen_opts {
fatal(NULL);
if (p->addr != NULL)
p->state = STATE_DNS_DONE;
- if (!(p->addr))
- TAILQ_INSERT_TAIL(&conf->ntp_peers,
- p, entry);
+ TAILQ_INSERT_TAIL(&conf->ntp_peers, p, entry);
h = next;
} while (h != NULL);
@@ -199,8 +197,7 @@ main: LISTEN ON address listen_opts {
fatal(NULL);
if (p->addr != NULL)
p->state = STATE_DNS_DONE;
- if (!(p->addr))
- TAILQ_INSERT_TAIL(&conf->ntp_peers, p, entry);
+ TAILQ_INSERT_TAIL(&conf->ntp_peers, p, entry);
free($2->name);
free($2);
}
--
Christian "naddy" Weisgerber na...@mips.inka.de
Re: 5.8-release building mutt from ports fails
On 2015-11-05, Tati Chevron wrote: > Or to be more general - what is the best way to manage a local > copy of the distfiles archive? dpb -F2; clean-old-distfiles -- Christian "naddy" Weisgerber na...@mips.inka.de
IPsec: time to drop DES support? (not 3DES)
We would like to remove IPsec support for plain DES. (_Not_ 3DES.) Does anybody still use this? What could it possibly be required for? Note that DES provides no security against a determined attacker. It can be brute-forced in less than a day. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: letsencrypt && https && openbsd.org = https://www.openbsd.org/
On 2015-12-08, szs wrote: > So with letsencrypt here, how about making the main site > default to https? Is this a good idea or is this a great idea? I would like it a lot if www.openbsd.org and cvsweb.openbsd.org switched to https, but I'm not in a position to make it happen. Much of the discussion seems silly: We don't do it because it doesn't provide perfect security? That's exactly the opposite approach to Theo's idea about security in OpenBSD. And encrypting everything makes mass surveillance harder. The true elephant in the room is that I can't get the current OpenBSD source tree securely. (Well, _I_ can if push comes to shove, but the general user community can't.) CVSync? No integrity or authenticity. AnonCVS over SSH? Nope, no integrity or authenticity because the mirror itself got the tree over CVSync. Assuming you trust the mirror in the first place. -- Christian "naddy" Weisgerber na...@mips.inka.de
Cleaning up function prototypes... or not
When you remove code, it's easy to forget function declarations.
That made me wonder how many orphan prototypes there are that refer
to functions that no longer exist.
There is an intriguing gcc option. I'll quote its description in
full, from the info manual:
`-aux-info FILENAME'
Output to the given filename prototyped declarations for all
functions declared and/or defined in a translation unit, including
those in header files. This option is silently ignored in any
language other than C.
Besides declarations, the file indicates, in comments, the origin
of each declaration (source file and line), whether the
declaration was implicit, prototyped or unprototyped (`I', `N' for
new or `O' for old, respectively, in the first character after the
line number and the colon), and whether it came from a declaration
or a definition (`C' or `F', respectively, in the following
character). In the case of function definitions, a K&R-style list
of arguments followed by their declarations is also provided,
inside comments, after the declaration.
I built a kernel with -aux-info. (After make config, edit Makefile
and add something like -aux-info ${@:.o=.X} to NORMAL_C.)
That produces a lot of raw data that can be further processed with
the usual Unix text tools.
To find orphan prototypes, I tried two approaches:
(1) Check the -aux-info output for functions that are declared but
not defined.
(2) Compare the functions that are declared in the -aux-info output
with the kernel symbol table (nm -g bsd).
I then picked a handful of suspect function names turned up by
either scheme and grepped the tree. Unfortunately, both approaches
are subject to false positives. (1) spits out functions that are
actually implemented in assembly. (2) runs into functions that are
defined, but don't show up in the symbol table because they are
inlined. Both approaches turn up function definitions that are
behind various #ifdef guards. There are probably more problems, but
I quickly lost interest when it became obvious that the results
were dominated by false positives.
No, this is not a success story.
Something else fell out of the -aux-info run. We still have tons
of function definitions that aren't ANSI-fied. I wonder whether
it would be worth to clean that up in one final push.
And another pattern showed up:
int func();
int func()
{
...
}
Neither of these is ANSI style. If a function doesn't take parameters,
the parameter list needs to say "void". Looks like somebody forgot
about this--e.g. when ansifying the network code. I thought about
cleaning these up, but then there's little point when we still have
so much unansified code anyway.
Also, as useful as -aux-info is, it requires actual compiling, so
it won't help with MD code for other architectures or drivers that
aren't configured in the kernel.
--
Christian "naddy" Weisgerber na...@mips.inka.de
Re: dpb build box performance suggestions.
On 2015-12-16, Christopher Sean Hilton wrote: > I'm trying to dpb to maintain a small set of packages for a handfull > of OpenBSD boxes that I run. These boxes will all be single purpose > servers of some type or another. Many of them will run with limited > disk space and memory on Soekris hardware. What resources do I want on > my dpb/build box to make it fast? I wouldn't overthink it. The number one limit is CPU. Faster CPU, better. Regarding memory, you want to avoid going into swap. On amd64, the biggest pig in the build is lang/pypy which requires ~4GB. The second biggest ones are the Mozillas, which take ~2GB during linking. (binutils 2.17 may have shaved off a few hundred MB there, I haven't really payed attention.) The vast majority of ports take far, far less memory. So your memory requirements really depend on how many of those big ports you will end up building in parallel. With ncpu*2GB but a minimum of 4GB you should be on the safe side. Disk doesn't matter much. If you run off magnetic disk, you want to use soft updates at least for the work and log directories. Probably the biggest question is how many cores to use for the build. At the low level, our SMP scales poorly. More cores are faster than fewer cores, but also mean that ever more CPU goes into spinning on the big lock instead of compiling. At the high level, dpb's ability to distribute build jobs to all cores is limited by the numer of ports and their interdependencies. It works well for building the whole ports tree, but if you only do a "small set of packages", the build may have to wait for some port that everything else depends on. Probably the biggest hint for building small sets of packages on more than one core is to increase dpb's parallel property (-p flag) to ncpu, from its default of ncpu/2, so you won't see half the cores idling while the build blocks on something like gcc/4.9 or llvm. Anyway, as I said above, don't overthink it. Do an initial build with modest resources, see how it goes. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: dpb build box performance suggestions.
On 2015-12-16, Tati Chevron wrote: > Our couple of build machines are both fairly standard core i5 boxes with > 16 gb of RAM, and Corsair SSDs. The RAM seems to make more difference > than anything else, because you can set the work directory to a ramdisk, > and do the entire build without touching the disk. Have you done actual comparisons? With SSDs, I don't expect a significant difference. (There is none for doing a "make build" of the base system.) -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: IKEDv2 lost tunnel. How to reproduce at will, effects and work around.
There has been zero reaction to this, but I certainly see what looks to be the same problem: After passing a significant amount of traffic (hundreds of MBs, I guess), the iked's lose sync, flows and SAs are in disarray, and it takes a number of minutes before they manage to sync up again. (Yes, that's vague. Start with Daniel's report for details. I haven't gotten around to really looking at what happens.) -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Mg scroll-up issue in xterm
On 2015-12-27, Timo Myyrä wrote: > I noticed issue with mg scroll-up keybinding when "xterm*locale: true" is set > in > ~/.Xresources. > When the above option is set, mg requires that you type C-v C-v to scroll-up > instead of single C-v. I'm not sure if this is bug or feature. That would be a bug, but I can't reproduce this. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Mg scroll-up issue in xterm
On 2015-12-27, Tati Chevron wrote: > ^V is traditionally used on UNIX like systems to 'insert the next character > literally', Only if the IEXTEN flag is set on the tty. Which should obviously not be the case (and in fact isn't) when mg is running. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: How to disable hwfeatures CSUM_TCPv4 on em(4) ?
On 2016-01-10, Denis Fondras wrote: > Can anyone tell me how to disable CSUM_TCPv4 on em(4) please ? There is no way to configure this. You would have to patch the driver. But why would you want to do this in the first place? -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Mg scroll-up issue in xterm
On 2015-12-27, Christian Weisgerber wrote: >> I noticed issue with mg scroll-up keybinding when "xterm*locale: true" is >> set in >> ~/.Xresources. >> When the above option is set, mg requires that you type C-v C-v to scroll-up >> instead of single C-v. I'm not sure if this is bug or feature. > > That would be a bug, but I can't reproduce this. I haven't had time to look into this further, but it happens when luit(1) is run. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Mg scroll-up issue in xterm
On 2016-01-10, Christian Weisgerber wrote: >>> I noticed issue with mg scroll-up keybinding when "xterm*locale: true" is >>> set in >>> ~/.Xresources. >>> When the above option is set, mg requires that you type C-v C-v to scroll-up >>> instead of single C-v. I'm not sure if this is bug or feature. >> > I haven't had time to look into this further, but it happens when > luit(1) is run. I just committed a fix to luit. -- Christian "naddy" Weisgerber na...@mips.inka.de
vmm(4) status?
I was wondering about the status of OpenBSD's vmm(4) hypervisor. Is it ready for some limited use, say, testing a port in an i386 VM on an amd64 host? (TL;DR: nope.) There's little information, so I decided to give it a try after reading the various vmm(4), vm.conf(5), vmd(8), vmctl(8), virtio(4), etc. man pages. First, you need to build a kernel with vmm(4). It is not enabled in GENERIC yet. You also need an up-to-date /dev since vmd opens /dev/vmm and /dev/tap0. Next: Start vmd, create a disk image (can you use a raw partition instead?), spin up a VM with an amd64 bsd.rd kernel I had at hand. # /etc/rc.d/vmd -f start # vmctl create /home/bardioc.img -s 4G # vmctl start -c -k /bsd.rd -m 1G -d /home/bardioc.img -i 1 Something's happening! There's a copyright message. And that's it... I was about to give up when the bsd.rd kernel continued, successfully booted, and allowed to drop me into a (S)hell. Observation: vmd completely hogs one CPU core even if the guest isn't doing anything. Next step: networking. As expected, a vio0 interface showed up inside the VM, but the man pages don't explain how to connect this to the outside. Since I had noticed that vmd opens tap0, I created a bridge on the host and added tap0 and a real interface. I don't know if that's the intended way, but after manually configuring an IP address on vio0, I could ping other machines from the guest. \o/ ping also showed that time was running three times slower in the VM than on the outside. Uh-oh. I deleted the inet configuration from vio0 and started the installer. I got as far as the network configuration, when the guest kernel died with an UVM error--and my patience along with it. So, yeah, interesting but not useful yet. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: vmm(4) status?
On 2016-01-20, Christian Weisgerber wrote: > So, yeah, interesting but not useful yet. That came across all wrong. I already sent some words in private, but I would like to publicly apologize to Mike, too. What I wrote was dismissive of his work in a way that was entirely uncalled for. I failed to consider how this would make feel the people doing the actual work. And I should have done more research and in particular asked the people involved before taking this to a public mailing list. I'm very sorry. Regarding the question in the subject line: vmm(4) is still under construction and not yet enabled FOR A REASON. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: em(4) bad checksums
On 2016-01-23, Pedro Caetano wrote: > The checksum errors are visible in tcpdump. > > pcaetano@soekris $ > doas tcpdump -nnvvr badchecksum.cap > 23:18:56.258991 89.115.7.49.38924 > 129.128.5.194.80: S [bad tcp cksum > e818! -> d08e] 2129156372:2129156372(0) win 16384 1460,nop,nop,sackOK,nop,wscale 3,nop,nop,timestamp 293911467 0> (DF) (ttl > 64, id 62808, len 64) These aren't real errors. You'll note that they concern outgoing packets. em(4) supports hardware checksum offloading. The checksum is filled in only _after_ tcpdump has seen the packet. (I can't comment on your overall problem.) -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: VAX - are we dropping support in 5.9?
On 2016-01-23, "Bryan C. Everly" wrote: > I just noticed that the VAX packages directory was missing on > openbsd.cs.toronto.edu and the other mirrors I checked. I searched the > MARC.info archives and didn't see anything announcing that the VAX was > going away but perhaps I missed something? There hasn't been anything official. Vax is one of several architectures that Theo has had to stop building base snapshots for because the system is too unreliable / the hardware itself is unreliable / the hardware is dead. The last snapshot is dated Oct 31. I assume that sebastia@'s cessation of package builds has related reasons. Going by previous experience, it's conceivable that somebody else will step in to build the release and possibly a few packages. Vax has been on life support with ever more perfunctory package builds for years. Again, from previous experience, it may take several release cycles of hemming and hawing before people face the facts and officially let it die. Armish, socppc, and sparc are also on their death beds. I'm not divulging deep secrets here; you can just check the dates on ftp and see that no recent snapshots have been built. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: VAX - are we dropping support in 5.9?
On 2016-01-23, Bryan Everly wrote: > I hope to add some of my time on these less popular architectures to > try and fix that. It's the comparatively popular platforms like powerpc and sparc64 that are in dire need of help if OpenBSD is not to turn into an amd64-only platform. I obviously can't tell people how to waste their time, but while investing in moribund museum architectures may offer personal satisfaction to some, it does not help in the bigger picture. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: VAX - are we dropping support in 5.9?
On 2016-01-24, "Christoph R. Murauer" wrote: > Quotes taked from Christian Weisgerber : > >> It's the comparatively popular platforms like powerpc and sparc64 >> that are in dire need of help if OpenBSD is not to turn into an >> amd64-only platform. That was a plea for help. Well, a pointer to where help would be actually... helpful. People need to run these platforms, find problems, and fix them. However, I'm afraid you'll find that most of the low hanging fruit has been picked and addressing the problems that matter will require heavy lifting. For instance, landry@'s powerpc package builds are crippled by the unreliability of the build machines. Given the plural, we don't think that the hardware is flakey. Some kernel bug(s) randomly causes processes to die. Vague guesses have been offered. Maybe it's a pmap problem. Somebody with considerable time and skill needs to wade in there. Or looking a bit into the future, I'll mention the elephant in the room and say that architectures without clang support are doomed. >> Going by previous experience, it's conceivable that somebody else >> will step in to build the release and possibly a few packages. That was not a plea for help. I meant to say that some OpenBSD developer may step in and do some builds on their own hardware. I think that happened e.g. for 5.8/sparc. This is really the last stage of an architecture's death, long after it has ceased to be useful. > Let's say someone will build releases and packages, would the project > accept this builds Would you like the project to accept builds from a random stranger? -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: "Available disks are: none" on Sony Vaio SVZ13115GGXI
On 2016-01-30, Paul de Weerd wrote:
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801HBM_AHCI,
> NULL, ahci_intel_attach },
> + { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801HBM_RAID,
> + NULL, ahci_intel_attach },
So this means that switching to non-RAID mode in the Vaio BIOS does
not change the PCI ID as it generally does?
--
Christian "naddy" Weisgerber na...@mips.inka.de
Re: xz: (stdin): Cannot allocate memory
Lampshade: > I have following error: > cat archive.tar | xz -zf --format=xz -9e --threads=2 - > archive.tar.xz > xz: (stdin): Cannot allocate memory You are using the most extreme compression setting, which requires about 674 MB per thread according to the xz(1) man page. This causes you to bump against the data size limit (ulimit -d, see ksh(1)). You need to raise the limit or use a less greedy compression setting. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: xz: (stdin): Cannot allocate memory
On 2016-01-30, Lampshade wrote: > xz: Adjusted the number of threads from 2 to 1 to not exceed the memory > usage limit of 1600 MiB > > 1600 is clearly larger than 674*2=1348 A closer reading of the man page reveals that memory consumption is even higher in multi-threaded mode. In multi-threaded mode about three times _size_ bytes will be allocated in each thread for buffering input and output. The default _size_ is three times the LZMA2 dictionary size or 1 MiB, whichever is more. At -9, the dictionary size is 64 MB, so this adds another 576 MB per thread. A quick check with top(1) confirms that xz in multi-threaded mode allocates 1250 MB per thread at compression level 9. > In the end I can compress, but I think that something is wrong. The last relevant change is that we actually enabled multi-threading. Before that, the -T option was silently ignored. However that change was ten months ago and is already in the 5.8 packages. Anyway, there is nothing wrong, and as I said before: You need to raise the limit or use a less greedy compression setting. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: assigning ipv6 addresses to interfaces
On 2016-01-31, LÉVAI Dániel wrote: > BTW, is there a difference between writing 'inet6 autoconf' or 'rtsol' > in /etc/hostname.pppoe0? If you read /etc/netstart, you can see that "rtsol" translates to ifconfig $if up ifconfig $if inet6 autoconf -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Ntpd's confusing log messages
On 2016-02-06, Lampshade wrote: > Feb 6 17:57:25 host ntpd[7585]: peer 150.254.183.15 now valid > Feb 6 17:58:17 host ntpd[9279]: adjusting local clock by 9.096751s > Feb 6 18:02:02 host ntpd[9279]: adjusting local clock by 7.971861s > I don't think that clock is adjusted "by" that values. It is. > If that would be the case, I guess clock would be far faster synced. The clock isn't set, it is adjusted with adjtime(2). That takes time. The maximum clock skew rate is 5 ms per second. Let's look at the numbers above. From 17:58:17 to 18:02:02, 225 seconds have passed. The clock can be adjusted by 1.125 seconds in that time. Which is the difference in the logged adjustment values. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: 64 Queue Size, ARC routing, MP Networking, OpenBSD 5.9
On 2016-02-07, Andy Lemin wrote: > So I'm deeply saddened to realise that if the MP networking commits do not > make it in to get us above 4Gbps in 5.9 we will have to say goodbye to > OpenBSD for good Just install a snapshot and test how it performs in your environment. There will not be any significant changes in that area between now and 5.9. If it doesn't work out for you, too bad. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Can not get DPB to use _pbuild user
On 2016-02-08, Andreas Kusalananda Kähäri wrote: > I'm trying to get DPB to use the _pbuild user, but I'm failing. I > managed, with "-D FETCH_USER=_pfetch", to use the _pfetch user for > fetching distfiles, but DPB insists on using my personal user account > for actual building, even though I set "-D BUILD_USER=_pbuild". I use this, together with WRKOBJDIR=/usr/obj/ports in /etc/mk.conf: FETCH_USER=_pfetch LOG_USER=naddy STARTUP=install -d -o _pbuild -g _pbuild /usr/obj/ports DEFAULT build_user=_pbuild stuck=4000 localhost ... Possibly -D BUILD_USER doesn't work, I don't quite remember. It took me some experimenting to arrive at a working configuration. -- Christian "naddy" Weisgerber na...@mips.inka.de
