Re: No firefox on OpenBSD 7.0 i386?
On Thu, Jan 20, 2022 at 01:46:11AM +0100, Riccardo Mottola wrote: > Crystal Kolipe wrote: > > On Fri, Jan 07, 2022 at 03:38:11PM +, Roderick wrote: > >> I just updated OpenBSD to 7.0. After pkg_add -u, it seems > >> firefox was not updated: > > Firefox no longer builds on i386, since shortly after the release of > > OpenBSD 6.9. > > I noticed that to, it is sad. Wonder why? See the commit log for revision 1.460 of the makefile. I'm sure that it could be fixed, but that requires somebody with an interest in fixing it. Also, just because it compiles and runs, doesn't mean that it's going to be usable for doing useful work.
Re: What password manager do you recommend?
Hi! I use 'Pain Free Passwords', a browser extension from Wladimir Palant. It can regenerate your password from user, website and your password - or store your own ones, locally. I've been using it for years and never thougt about passwords again. https://pfp.works/ Mario On Jan 07 2022, 13:23, Sean Kamath wrote: >> On Jan 7, 2022, at 11:53, fo...@dnmx.org wrote: >> >> Hello. I hope this these types of questions are okay for an mailing list.. >> I completely understand if they are not.. >> >> There's password-store, but it does need some shitty dependencies.. >> Then there's opm, but since it doesn't seem to be popular fuck-knows-who >> if it's secure(ish).. >> >> If I were to use password-store, I'd have dmenu pipe in the query, then >> just pipe the password to `xclip -i -selection clipboard` which is a >> decent setup I guess.. > > gpg < file.gpg > > Sean > > PS OK, it’s more complicated than that, but that’s what it boils down to.
Re: Generating Disk Labels for New Fdisk Partitions
On Wed, Jan 19, 2022 at 10:13:02PM +, thatfatblack...@disroot.org wrote: > After installing OpenBSD I realized I was going to need another > partition, so I went ahead and created it with fdisk. > > Problem is that partition is not showing up like sd0i or sd0j. This is expected behaviour. Since your disk has a 'real' disklabel on it, any other fdisk partitions that you create will not be parsed and added automatically. > I need a way to generate it without having to reinstall OpenBSD. You need to add the details of the new, non-OpenBSD partition to the disklabel manually. This is not difficult. If you invoke disklabel with the -E parameter, you will be able to edit the disklabel partitions in the same way that you did in the installer, so you can use option 'a' to add a partition, and fill in the correct parameters, such as offset, size, etc. If you don't know the parameters, invoke disklabel with the -d parameter. This will show you how the kernel would parse the partitions if there was no disklabel already present. From this information, you should be able to pick out which is your new partition, probably i or j, note the details down, then add them as described above.
Re: ttyflags hangs on Dell PowerEdge R200
Boots fine, dmesg below.
> Index: arch/hppa/dev/com_dino.c
> ===
> RCS file: /cvs/src/sys/arch/hppa/dev/com_dino.c,v
> retrieving revision 1.4
> diff -u -r1.4 com_dino.c
> --- arch/hppa/dev/com_dino.c 15 Jul 2007 19:25:49 - 1.4
> +++ arch/hppa/dev/com_dino.c 18 Jan 2022 18:22:56 -
> @@ -77,7 +77,7 @@
> return (0);
>
> return (1);
> - /* HOZER comprobe1(ca->ca_iot, ca->ca_hpa + IOMOD_DEVOFFSET); */
> + /* HOZER comprobe1(ca->ca_iot, ca->ca_hpa + IOMOD_DEVOFFSET, 1, 0); */
> }
>
> void
> Index: arch/hppa/gsc/com_gsc.c
> ===
> RCS file: /cvs/src/sys/arch/hppa/gsc/com_gsc.c,v
> retrieving revision 1.21
> diff -u -r1.21 com_gsc.c
> --- arch/hppa/gsc/com_gsc.c 15 Jul 2007 19:25:49 - 1.21
> +++ arch/hppa/gsc/com_gsc.c 18 Jan 2022 18:22:53 -
> @@ -69,7 +69,7 @@
> return (0);
>
> return (1);
> - /* HOZER comprobe1(ga->ga_iot, ga->ga_hpa + IOMOD_DEVOFFSET); */
> + /* HOZER comprobe1(ga->ga_iot, ga->ga_hpa + IOMOD_DEVOFFSET, 1, 0); */
> }
>
> void
> Index: dev/acpi/com_acpi.c
> ===
> RCS file: /cvs/src/sys/dev/acpi/com_acpi.c,v
> retrieving revision 1.6
> diff -u -r1.6 com_acpi.c
> --- dev/acpi/com_acpi.c 26 Dec 2021 13:55:36 - 1.6
> +++ dev/acpi/com_acpi.c 18 Jan 2022 18:19:37 -
> @@ -61,14 +61,32 @@
> com_acpi_match(struct device *parent, void *match, void *aux)
> {
> struct acpi_attach_args *aaa = aux;
> + bus_space_handle_t ioh;
> + bus_space_tag_t iot;
> struct cfdata *cf = match;
> + int width = 0, shift = 0, rv;
>
> if (aaa->aaa_naddr < 1 || aaa->aaa_nirq < 1)
> return 0;
> if (cf->acpidevcf_addr != aaa->aaa_addr[0] &&
> cf->acpidevcf_addr != ACPIDEVCF_ADDR_UNK)
> return 0;
> - return acpi_matchhids(aaa, com_hids, cf->cf_driver->cd_name);
> + if (acpi_matchhids(aaa, com_hids, cf->cf_driver->cd_name) == 0)
> + return 0;
> +
> + iot = aaa->aaa_bst[0];
> + if (com_acpi_is_designware(aaa->aaa_dev)) {
> + width = acpi_getpropint(aaa->aaa_node,
> + "reg-io-width", 4);
> + shift = acpi_getpropint(aaa->aaa_node,
> + "reg-shift", 2);
> + }
> +
> + if (bus_space_map(iot, aaa->aaa_addr[0], aaa->aaa_size[0], 0, ))
> + return (0);
> + rv = comprobe1(iot, ioh, width, shift);
> + bus_space_unmap(iot, ioh, aaa->aaa_size[0]);
> + return (rv);
> }
>
> void
> Index: dev/ic/com.c
> ===
> RCS file: /cvs/src/sys/dev/ic/com.c,v
> retrieving revision 1.175
> diff -u -r1.175 com.c
> --- dev/ic/com.c 11 Jan 2022 11:51:14 - 1.175
> +++ dev/ic/com.c 18 Jan 2022 18:19:10 -
> @@ -144,19 +144,34 @@
>
> #ifdef COM_CONSOLE
> int
> -comprobe1(bus_space_tag_t iot, bus_space_handle_t ioh)
> +comprobe1(bus_space_tag_t iot, bus_space_handle_t ioh, int width, int shift)
> {
> int i, k;
>
> - /* force access to id reg */
> - bus_space_write_1(iot, ioh, com_lcr, 0);
> - bus_space_write_1(iot, ioh, com_iir, 0);
> - for (i = 0; i < 32; i++) {
> - k = bus_space_read_1(iot, ioh, com_iir);
> - if (k & 0x38) {
> - bus_space_read_1(iot, ioh, com_data); /* cleanup */
> - } else
> - break;
> + if (width == 4) {
> + /* force access to id reg */
> + bus_space_write_4(iot, ioh, (com_lcr) << shift, 0);
> + bus_space_write_4(iot, ioh, (com_iir) << shift , 0);
> + for (i = 0; i < 32; i++) {
> + k = bus_space_read_4(iot, ioh, (com_iir) << shift);
> + if (k & 0x38) {
> + bus_space_read_4(iot, ioh,
> + (com_data) << shift); /* cleanup */
> + } else
> + break;
> + }
> + } else {
> + /* force access to id reg */
> + bus_space_write_1(iot, ioh, (com_lcr) << shift, 0);
> + bus_space_write_1(iot, ioh, (com_iir) << shift, 0);
> + for (i = 0; i < 32; i++) {
> + k = bus_space_read_1(iot, ioh, (com_iir) << shift );
> + if (k & 0x38) {
> + bus_space_read_1(iot, ioh,
> + (com_data) << shift); /* cleanup */
> + } else
> + break;
> + }
> }
> if (i >= 32)
> return 0;
> @@ -1173,7 +1188,7 @@
>
> if (bus_space_map(comconsiot, comconsaddr, COM_NPORTS, 0, ))
> return;
> - found = comprobe1(comconsiot, ioh);
> + found =
Re: NSD: Could not tcp connect to X Operation timed out
On Wed, Jan 19, 2022 at 11:31:07AM +, Laura Smith wrote: > Hi > > OpenBSD NSD slave is driving me nuts with the following message in the logs > "Could not tcp connect to X Operation timed out". > > The answer sounds obvious, but I can: > > - Ping the IP > - Do a "dig @$auth_server_ip $auth_domain" > > Both respond normally. > > What am I missing here ? Connectivity clearly works ? PF is clearly not > dropping inbound port 53 on the master ? > > THanks > > Laura Hi, you need to use the +tcp option with dig to test TCP functionality. DNS is tcp and udp on port 53 and if the remote end doesn't support it they are breaking the RFC. Hope that helps, -peter
Re: NSD: Could not tcp connect to X Operation timed out
On Wed, Jan 19, 2022 at 11:31:07AM +, Laura Smith wrote: | Hi | | OpenBSD NSD slave is driving me nuts with the following message in the logs "Could not tcp connect to X Operation timed out". | | The answer sounds obvious, but I can: | | - Ping the IP | - Do a "dig @$auth_server_ip $auth_domain" Try "-t AXFR" and/or "+tcp" Ping uses icmp and dig defaults to udp. You can force tcp with "+tcp" and you can do the transfer manually with "-t AXFR". If both work, you may have multiple IPs configured, try with all of them. Cheers, Paul 'WEiRD' de Weerd -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: NSD: Could not tcp connect to X Operation timed out
is pf allowing tcp port53 as well as udp port53 ? On Wed 19 Jan 2022, 11:46 Laura Smith, wrote: > Hi > > OpenBSD NSD slave is driving me nuts with the following message in the > logs "Could not tcp connect to X Operation timed out". > > The answer sounds obvious, but I can: > > - Ping the IP > - Do a "dig @$auth_server_ip $auth_domain" > > Both respond normally. > > What am I missing here ? Connectivity clearly works ? PF is clearly not > dropping inbound port 53 on the master ? > > THanks > > Laura > >
