Re: pkg_info
On Tue, Jun 28, 2016 at 08:29:23PM -0500, Edgar Pettijohn wrote:
> On 16-06-29 03:16:02, Theo Buehler wrote:
> > On Tue, Jun 28, 2016 at 08:09:02PM -0500, Edgar Pettijohn wrote:
> > > This doesn't seem possible, but maybe I'm missing something.
> > >
> > > I would like pkg_info to tell me where to find a package in
> > > the ports tree. For example:
> > >
> > > If I go to /usr/ports and do make search key=wget I can find
> > > the following.
> > >
> > > Port: wget-1.16.3p0
> > > Path: net/wget
> > > Info: retrieve files from the web via HTTP, HTTPS and FTP
> > > Maint: The OpenBSD ports mailing-list
> > > Index: net lang/python
> > > L-deps: STEM->=0.10.38:devel/gettext converters/libiconv devel/libidn
> > > devel/pcre net/libpsl
> > > B-deps: STEM->=0.10.38:devel/gettext archivers/xz devel/gettext-tools
> > > R-deps: STEM->=0.10.38:devel/gettext
> > > Archs: any
> > >
> > > Which tells me to go to /usr/ports/net/wget. Is there currently
> > > a way to achieve this with any of the pkg_ tools?
> >
> > Use the -P option:
> >
> > $ pkg_info -P wget
> > Information for inst:wget-1.18
> >
> > Pkgpath:
> > net/wget
> >
> I can't believe I missed that. Beats the hell out of my alternative.
>
> pkg_info -f wget | grep pkgpath | awk '{print $2}' | cut -f 2 -d =
In that case, you'll want to add the -q option:
$ pkg_add -Pq wget
net/wget
Re: pkg_info
On 16-06-29 03:16:02, Theo Buehler wrote:
> On Tue, Jun 28, 2016 at 08:09:02PM -0500, Edgar Pettijohn wrote:
> > This doesn't seem possible, but maybe I'm missing something.
> >
> > I would like pkg_info to tell me where to find a package in
> > the ports tree. For example:
> >
> > If I go to /usr/ports and do make search key=wget I can find
> > the following.
> >
> > Port: wget-1.16.3p0
> > Path: net/wget
> > Info: retrieve files from the web via HTTP, HTTPS and FTP
> > Maint: The OpenBSD ports mailing-list
> > Index: net lang/python
> > L-deps: STEM->=0.10.38:devel/gettext converters/libiconv devel/libidn
> > devel/pcre net/libpsl
> > B-deps: STEM->=0.10.38:devel/gettext archivers/xz devel/gettext-tools
> > R-deps: STEM->=0.10.38:devel/gettext
> > Archs: any
> >
> > Which tells me to go to /usr/ports/net/wget. Is there currently
> > a way to achieve this with any of the pkg_ tools?
>
> Use the -P option:
>
> $ pkg_info -P wget
> Information for inst:wget-1.18
>
> Pkgpath:
> net/wget
>
I can't believe I missed that. Beats the hell out of my alternative.
pkg_info -f wget | grep pkgpath | awk '{print $2}' | cut -f 2 -d =
--
Edgar Pettijohn
Re: pkg_info
On Tue, Jun 28, 2016 at 08:09:02PM -0500, Edgar Pettijohn wrote: > This doesn't seem possible, but maybe I'm missing something. > > I would like pkg_info to tell me where to find a package in > the ports tree. For example: > > If I go to /usr/ports and do make search key=wget I can find > the following. > > Port: wget-1.16.3p0 > Path: net/wget > Info: retrieve files from the web via HTTP, HTTPS and FTP > Maint: The OpenBSD ports mailing-list > Index: net lang/python > L-deps: STEM->=0.10.38:devel/gettext converters/libiconv devel/libidn > devel/pcre net/libpsl > B-deps: STEM->=0.10.38:devel/gettext archivers/xz devel/gettext-tools > R-deps: STEM->=0.10.38:devel/gettext > Archs: any > > Which tells me to go to /usr/ports/net/wget. Is there currently > a way to achieve this with any of the pkg_ tools? Use the -P option: $ pkg_info -P wget Information for inst:wget-1.18 Pkgpath: net/wget
Re: pkg_info
Edgar Pettijohn wrote: > I would like pkg_info to tell me where to find a package in > the ports tree. For example: > > If I go to /usr/ports and do make search key=wget I can find > the following. > > Port: wget-1.16.3p0 > Path: net/wget > Info: retrieve files from the web via HTTP, HTTPS and FTP > Maint: The OpenBSD ports mailing-list > Index: net lang/python > L-deps: STEM->=0.10.38:devel/gettext converters/libiconv devel/libidn > devel/pcre net/libpsl > B-deps: STEM->=0.10.38:devel/gettext archivers/xz devel/gettext-tools > R-deps: STEM->=0.10.38:devel/gettext > Archs: any > > Which tells me to go to /usr/ports/net/wget. Is there currently > a way to achieve this with any of the pkg_ tools? I don't know about pkg_info, but "cd ports/*/wget" usually gets the job done.
pkg_info
This doesn't seem possible, but maybe I'm missing something. I would like pkg_info to tell me where to find a package in the ports tree. For example: If I go to /usr/ports and do make search key=wget I can find the following. Port: wget-1.16.3p0 Path: net/wget Info: retrieve files from the web via HTTP, HTTPS and FTP Maint: The OpenBSD ports mailing-list Index: net lang/python L-deps: STEM->=0.10.38:devel/gettext converters/libiconv devel/libidn devel/pcre net/libpsl B-deps: STEM->=0.10.38:devel/gettext archivers/xz devel/gettext-tools R-deps: STEM->=0.10.38:devel/gettext Archs: any Which tells me to go to /usr/ports/net/wget. Is there currently a way to achieve this with any of the pkg_ tools? Thanks, -- Edgar Pettijohn
Re: Interesting error message from disk testing
On Tue, 28 Jun 2016, STeve Andre' wrote: I am testing some new 8TB disks. I've taken to doing dd if=/dev/zero of=/dev/rsd3c bs=64k and dd if=/dev/rsd3c of=/dev/null bs=64k as a first test. It's depressing how often I've found problems on big disks. Today, the read test produced an error in the messages file I've not seen before: Jun 28 16:17:39 paladin /bsd: sd3(umass0:1:0): Check Condition (error 0x70) on opcode 0x28 Jun 28 16:17:39 paladin /bsd: SENSE KEY: Aborted Command Jun 28 16:17:39 paladin /bsd: ASC/ASCQ: Information Unit iuCRC Error Detected So it isn't a soft read error -- what is it? It might be useful to indicate where the error occurred? This is the second of three disks to be tested. It's connected to a Thermaltake USB 3.0 disk enclosure. I have seen CRC errors number of times when working with different USB enclosures. My guess is that either the connectors inside the boxes aren't 100% tight, the electronics is not shielded properly or it has some flaws. If I am not mistaken, it is the transfer between the HDD electronics and the controller (ie. the bridge chip) that failed. Also see this thread: http://marc.info/?t=10989807768&r=1&w=2 I would also monitor the drive with smartctl from sysutils/smartmontools. Regards, David
Interesting error message from disk testing
I am testing some new 8TB disks. I've taken to doing dd if=/dev/zero of=/dev/rsd3c bs=64k and dd if=/dev/rsd3c of=/dev/null bs=64k as a first test. It's depressing how often I've found problems on big disks. Today, the read test produced an error in the messages file I've not seen before: Jun 28 16:17:39 paladin /bsd: sd3(umass0:1:0): Check Condition (error 0x70) on opcode 0x28 Jun 28 16:17:39 paladin /bsd: SENSE KEY: Aborted Command Jun 28 16:17:39 paladin /bsd: ASC/ASCQ: Information Unit iuCRC Error Detected So it isn't a soft read error -- what is it? It might be useful to indicate where the error occurred? This is the second of three disks to be tested. It's connected to a Thermaltake USB 3.0 disk enclosure. Thanks for any pointers. --STeve Andre'
Re: Different unbound configurations pr interface?
On Tue, Jun 28, 2016 at 07:22:46PM +0200, Tor Houghton wrote: > Hello, > > I'm looking for the best/easiest way to run unbound on different interfaces > but with different configuration files (well, what I actually want is to > specify different forward-addr: configurations for each interface). > > I also would like to control the unbound daemon(s?) using rcctl. > > Should I go about this by making multiple unbound entries in /etc/rc.d > pointing to different configuration files? Or is there a more elegant way > (e.g. /etc/rc.d/unbound_em0 /etc/rc.d/unbound_em1 and corresponding > rc.conf.local entries)? See 'EXAMPLES' section in rcctl(8). j.
Mac mini acpiec(4) panic with Unsupported RegionSpace
I have two different Macmini7,1 systems (the late 2014 and most recent Mac mini model). On one of them, I was using OpenBSD -current in April but haven't used the system or upgraded it to a newer snapshot. I purchased another similar system and went to install OpenBSD -current on it from the June 22 and found that I had a panic early in the boot process. The panic is from below which I hand copied. This is from bsd.rd but the panic is identical with bsd.mp as well. I did not get far enough to get a full dmesg with the recent kernels but could pull an old one as well if needed. Also, this is using EFI boot from a USB stick which has worked fine in the past. real mem = 17032085504 (16243MB) avail mem = 16514179072 (15749MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x88d1 (49 entries) ... (snip) ... ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpiec0 at acpi0 Unsupported RegionSpace panic: aml_die aml_rwfield:2475 The operating system has halted. Press press any key to reboot. rebooting... I believe the panic stems from revision 1.53 of acpiec.c. I can try reverting that commit on -current now and see if I can avoid the issue but there may be more to it than that. Any idea how to resolve this? There is also a separate issue that I will report in another message with "halt -p" causing a panic related to aml but that has been around for quite a while including in the April snapshot I am running on one of those systems. It isn't as important since reboot works fine. Bryan
Different unbound configurations pr interface?
Hello, I'm looking for the best/easiest way to run unbound on different interfaces but with different configuration files (well, what I actually want is to specify different forward-addr: configurations for each interface). I also would like to control the unbound daemon(s?) using rcctl. Should I go about this by making multiple unbound entries in /etc/rc.d pointing to different configuration files? Or is there a more elegant way (e.g. /etc/rc.d/unbound_em0 /etc/rc.d/unbound_em1 and corresponding rc.conf.local entries)? Kind regards, Tor
