old nslookup binary found?
Hello, I accidentally found a possibly old nslookup binary from 2019 in /usr/sbin when I ran nslookup as root: root ~ # echo $PATH /sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/sbin:/usr/local/bin root ~ # which nslookup /usr/sbin/nslookup root ~ # nslookup openbsd.org Bad system call (core dumped) root ~ # ls -lA /usr/sbin/nslookup -r-xr-xr-x 1 root bin 1499352 Oct 12 2019 /usr/sbin/nslookup But a working nslookup binary is there: root ~ # ls -lA /usr/bin/nslookup -r-xr-xr-x 3 root bin 403056 Mar 25 19:15 /usr/bin/nslookup Is it really just the old official binary which could remain after an upgrade? This is the 7 year old OpenBSD installation which is regularly upgraded. -- Maksim Rodin
Re: ixl not seeing SFP+ modules ?
On 2023-04-14, deich...@placebonol.com wrote: > The Intel 710 only works with Intel brand optics. It is possible you can > find optics which will report as Intel, though I've never tried. > > I do use FlexOptix programmable optics in various network devices. When I > get to the office I'll plug in the programmer and see if it can code Intel > optic info. I have FS and FlexOptix SFP and SFP+ (various LX, SR, LR) in X710-based cards, I don't remember what they're vendor-coded as (probably either Intel or Cisco for the FS, and either Intel or generic for the FlexOptix). It might vary between card firmware too, I don't recall having problems with these (they've been installed for a while though - still running 7.0 on some of them).
Re: old nslookup binary found?
On 2023 Apr 15 (Sat) at 09:33:51 +0300 (+0300), Maksim Rodin wrote: :Hello, :I accidentally found a possibly old nslookup binary from 2019 :in /usr/sbin when I ran nslookup as root: :root ~ # echo $PATH :/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/sbin:/usr/local/bin :root ~ # which nslookup :/usr/sbin/nslookup :root ~ # nslookup openbsd.org :Bad system call (core dumped) :root ~ # ls -lA /usr/sbin/nslookup :-r-xr-xr-x 1 root bin 1499352 Oct 12 2019 /usr/sbin/nslookup : :But a working nslookup binary is there: :root ~ # ls -lA /usr/bin/nslookup :-r-xr-xr-x 3 root bin 403056 Mar 25 19:15 /usr/bin/nslookup : :Is it really just the old official binary which could remain after an :upgrade? :This is the 7 year old OpenBSD installation which is regularly :upgraded. : :-- :Maksim Rodin : The upgrade from 6.6->6.7 guide did tell you to delete these files. https://www.openbsd.org/faq/upgrade67.html#RmFiles -- Living on Earth may be expensive, but it includes an annual free trip around the Sun.
Re: ixl not seeing SFP+ modules ?
Sent with Proton Mail secure email. --- Original Message --- On Friday, April 14th, 2023 at 21:14, Stuart Henderson wrote: > ixl can be vendor locked in firmware. also iirc they can be funny about when > the module was plugged in, if it was hotplugged try rebooting, though vendor > lock is more likely. > Interesting tid-bit, thanks for that. I think my ixl is a pure Intel one, but I'll need to go back through my orders ... I'll give the box a reboot later today just incase !
Re: ixl not seeing SFP+ modules ?
--- Original Message --- On Saturday, April 15th, 2023 at 08:37, Stuart Henderson wrote: > I have FS and FlexOptix SFP and SFP+ (various LX, SR, LR) in X710-based cards, > I don't remember what they're vendor-coded as (probably either Intel or Cisco > for the FS, and either Intel or generic for the FlexOptix). > Unfortunately I don't have any spare Flexoptix hanging around but sounds like it might well be worth a go.
selling off some used OpenBSD routers within EU
Hi, https://blog.centroid.eu/c?article=1681550055 Please send me mail privately off list, as I'm not subscribed to misc@. Best Regards, -peter
Re: old nslookup binary found?
Thank you very much! I must have missed it during that upgrade. On Sat Apr 15 09:41:13 2023, Peter Hessler wrote: > On 2023 Apr 15 (Sat) at 09:33:51 +0300 (+0300), Maksim Rodin wrote: > :Hello, > :I accidentally found a possibly old nslookup binary from 2019 > :in /usr/sbin when I ran nslookup as root: > :root ~ # echo $PATH > :/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/sbin:/usr/local/bin > :root ~ # which nslookup > :/usr/sbin/nslookup > :root ~ # nslookup openbsd.org > :Bad system call (core dumped) > :root ~ # ls -lA /usr/sbin/nslookup > :-r-xr-xr-x 1 root bin 1499352 Oct 12 2019 /usr/sbin/nslookup > : > :But a working nslookup binary is there: > :root ~ # ls -lA /usr/bin/nslookup > :-r-xr-xr-x 3 root bin 403056 Mar 25 19:15 /usr/bin/nslookup > : > :Is it really just the old official binary which could remain after an > :upgrade? > :This is the 7 year old OpenBSD installation which is regularly > :upgraded. > : > :-- > :Maksim Rodin > : > > The upgrade from 6.6->6.7 guide did tell you to delete these files. > > https://www.openbsd.org/faq/upgrade67.html#RmFiles > > > -- > Living on Earth may be expensive, but it includes an annual free trip > around the Sun. -- С уважением, Родин Максим
ftp.fr down
Hi. ftp.fr is down for an unknown amount of time. sysupgrade(8) seems to have failed. I don't have direct access to the console and I am waiting for someone to revive it. I'll keep you posted as soon as the service is back. Sorry for the inconvenience. -- Antoine
File system is full after using dd
Hello, I've run the dd command to wipe the data of an SD card:dd if=/dev/zero of=/dev/rsdb1c bs=1MAfter quite some time it crashed saying that the / filesystem is full and even after a reboot the same happens. Now I can't even run xorg because the fs is full. Any idea on why this happened? I have a 1TB NVME SSD as root disk and I have only a root partition as well as the efi partition on the root disk.Lorenzo Torres (https://sagittarius-a.org)
Re: File system is full after using dd
On Sat, Apr 15, 2023, at 9:14 AM, Lorenzo Torres wrote: > Hello, I've run the dd command to wipe the data of an SD card:dd > if=/dev/zero of=/dev/rsdb1c bs=1MAfter quite some time it crashed > saying that the / filesystem is full and even after a reboot the same > happens. Now I can't even run xorg because the fs is full. Any idea on > why this happened? Yes, you filled up your / partition with a garbage file. Run `ls -lS /dev/|head` and you will surely find it. /dev/rsdb1c is not a valid drive and partition/slice combination. You probably meant rsd1c, but be careful to verify that when wiping. Brian Conway Lead Software Engineer, Owner RCE Software, LLC
Re: File system is full after using dd
Thanks, that was the issue, I'll pay more attention in the future.Lorenzo Torres (https://sagittarius-a.org)
Re: File system is full after using dd
Am 15.04.2023 um 16:14 schrieb Lorenzo Torres: Hello, I've run the dd command to wipe the data of an SD card:dd if=/dev/zero of=/dev/rsdb1c bs=1MAfter quite some time it crashed saying that the / filesystem is full and even after a reboot the same happens. Now I can't even run xorg because the fs is full. Any idea on why this happened? You most likely wrote into a file and not onto the SD card. Just delete the file.
Re: File system is full after using dd
On Sat, Apr 15, 2023 at 04:14:08PM +0200, Lorenzo Torres wrote: > Hello, I've run the dd command to wipe the data of an SD card:dd if=/dev/zero > of=/dev/rsdb1c bs=1MAfter quite some time it crashed saying that the / > filesystem is full and even after a reboot the same happens. Now I can't even > run xorg because the fs is full. Any idea on why this happened? I have a 1TB > NVME SSD as root disk and I have only a root partition as well as the efi > partition on the root disk.Lorenzo Torres (https://sagittarius-a.org) This sounds to me that you mistyped and created a huge file in your /dev/ directory. identify that file and delete it. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: File system is full after using dd
On 4/15/23 10:14, Lorenzo Torres wrote: Hello, I've run the dd command to wipe the data of an SD card:dd if=/dev/zero of=/dev/rsdb1c bs=1MAfter quite some time it crashed ^^ bzzzt. game over. saying that the / filesystem is full and even after a reboot the same happens. Now I can't even run xorg because the fs is full. Any idea on why this happened? I have a 1TB NVME SSD as root disk and I have only a root partition as well as the efi partition on the root disk ^ game took a while to be over, didn't it? As people have already said, you created a file, you didn't zero your SD card. But...what wasn't said (yet? as I'm typing this? Probably twenty people will respond about this two seconds after I hit "SEND") was pointing out this is one of many reasons NOT to create a huge root partition and nothing else. Granted, OpenBSD has lots of OpenBSD-only reasons, too, but one big root partition is Bad Unix Administration. If you had an appropriate sized root partition, perhaps 1G (default), you would have quickly discovered something was wrong, probably in a few seconds. Instead, it took a while, and you assumed you had accomplished your mission of zeroing an SD card. So not only did you fill root, your sensitive data is still on the card. Many system administrators can tell you stories about thinking they were backing up every night to tape, only to find out that they were dumping a big backup *file* in their /dev directory rather than putting their data to tape...and find this when they realize their tape has never been written when they need a restore. $DAYJOB involves helping maintain a bunch of systems that regularly fill their root partitions. Not always by bad initial design, but often because there was "plenty of space" on the root partition, so someone started dropping data or applications there. And then, one day...boom. Partition your system. And / should be as small as you can sanely get away with. That isn't to say it should be super-tiny. But if you have 1GB to spare, it is probably too big. I did learn to regret a 200MB root because OpenBSD grew a lot over around ten years that I used that install. Nick.
Re: ftp.fr down
Hi. Everything is back :-) On Sat, 2023-04-15 at 16:30 +0200, Antoine Jacoutot wrote: > Hi. > > ftp.fr is down for an unknown amount of time. > sysupgrade(8) seems to have failed. > I don't have direct access to the console and I am waiting for someone to > revive > it. > I'll keep you posted as soon as the service is back. > > Sorry for the inconvenience. > -- Antoine
Re: intermittent keyboard freezes
(cc'ing bugs@) On Sat, 15 Apr 2023, at 00:45, Allan Streib wrote: > I've had this problem for a while, over several releases. > > Keyboard will freeze up (key presses do nothing). Mouse pointer > can be moved but clicks do nothing. Only solution was to reboot > using the power button, which does trigger a clean shutdown. > I have a similar issue since the last few releases. It seems pretty random, sometimes I can go several days without this happening. It generally only happens several hours after booting and using various programs. Playing a file with mpv is almost always the trigger for it. The file will start playing for a split second, then the video will freeze. Keyboard is unresponsive, and the mouse cursor will still move, but can't do anything. I can usually still ssh into the machine from a different computer. My assumption was that there is a bug in the amdgpu drm code somewhere. This is the hardware: amdgpu0: CARRIZO 6 CU rev 0x01
Re: pkg_info -Q confusion
> I'm generally interested in what is available for the exact machine I am > running on. You could use `pkg_info -a -Q` which searches all the repositories. >From the pkg_info man page: -Q substring Show the names of all packages in the first repository of the package search path containing the substring in the stems of their package names. A stem is a package name with all version and flavor suffixes removed; see pkg_add(1) for more details on stems. If -a is also specified, show the names of all matching packages in all repositories instead.
Re: pkg_info -Q confusion
> Am 15.04.2023 um 23:44 schrieb Antun Matanović : > >> I'm generally interested in what is available for the exact machine I am >> running on. > > You could use `pkg_info -a -Q` which searches all the repositories. >> From the pkg_info man page: > -Q substring > Show the names of all packages in the first repository of the > package search path containing the substring in the stems of > their package names. A stem is a package name with all version > and flavor suffixes removed; see pkg_add(1) for more details on > stems. If -a is also specified, show the names of all matching > packages in all repositories instead. So simple and so perfect! Thanks for that hint. I’ll still keep pkglocate around for more complicated partial name searches but for most of my use cases pkg_info -aQ name is exactly what I need. Mike
Re: File system is full after using dd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 15 Apr 2023 12:49:47 -0400 Nick Holland wrote: > if you have 1GB to spare, it is probably too big. I did learn to > regret a 200MB root because OpenBSD grew a lot over around ten I learned to regret setting / to under 1 mb once upon a time. Now I just assume such rulz are all transients Dhu > years that I used that install. > > Nick. > > -- Je suis Canadien. Ce n'est pas Francais ou Anglais. C'est une esp`ece de sauvage: ne obliviscaris, vix ea nostra voco;-) Duncan Patton a Campbell -BEGIN PGP SIGNATURE- iQGzBAEBCAAdFiEEqge1PVqb4YiiKJRjW+0jaAWoWygFAmQ7bWoACgkQW+0jaAWo WygGQwwAu9L/0r21FF0ynNswkaWJe7I+qgeNQ3PzTDJ1JiSGuld2WsUfgsfTzYsY +8L9jzLPQKYf/3AKaP7hFjG78b/KfvZ9KRtVpnp8VCwBG9p6mQyE/Y5fFlke+c8E VVgsDvcLn3Pmm6NeJpP5YnWTvr1G1t3yN4hjxuSR77m45MFnyEMEIWwiPpoL50E1 Yh05QDfKFDMCDEhBhbwZS020CIvthKGqJzC/xnOZA3qjY/EFhRmHQWGjsmQmGr5e Y1YCB4ejO3uHxMweODEkkQ1zWdaDFVlD6/XZlDTT1flRb8swtWNiLjhpj/szWt6F DewWXIjPlJww6E+AlTyixfkaqZHldGwTfuzd4fNKwGZjI3cV3XKJdXTuFUVHW4Nk DLTqyKfy2PFPCJdhJBRhFZWhStokv3yyi9iX5jdAbRKD/S1OzXuS7l9p/kVBnIpR mW6flpNx5sCjEsfoSwsdGTvOd2yJQ1+hva+kUYcFjNHxk4jRnSaNr5Kt8xWlSrsa QzVoQvaO =iSaR -END PGP SIGNATURE-