Re: Bitmap fonts
Hi, On 20/08/2018 21:36, Cág wrote: and under the impression bitmap fonts are guaranteed to look bad by design Bitmap fonts are considered superior by some, and are used by a lot of people. Go search for some tiling WM's screenshots, and you'll see :) Also, if you don't like old-school-looking X11 default fonts, maybe try Terminus, Dina or Tamsyn. It is a matter of taste probably, but for User-interface elements I prefer a good bitmap font without AA. I use WindowMaker and GNUstep and especially on a good display, Helvetica bitmap is far more readable and consistent than anti-aliased and scalable ones. The same goes for me for terminal and Code Editors. For text display in reading like in a Browser or a PDF, a scalable font with AA might be more pleasant. However... if bitmap fonts are available in the correct text and header sizes, they look really good! Riccardo
Re: Smooth ThinkPad installation
Riccardo Mottola wrote: > Hi, Hi, > yes... it is using the "high res" console. > Can't we fix the fonts inside DRM? I don't think so, there must be a need for a new console driver... Take a look at the code though, maybe there's a mention of the font somewhere: https://github.com/NetBSD/src/tree/trunk/sys/external/bsd/drm2/dist/drm/i915 -- caóc
Re: port-arm/53537: typo in src/sys/arch/arm/sunxi/sunxi_thermal.c
> I realize that I've maybe made a mistake by assigning a category > matching a non-existing (ever? http://www.netbsd.org/ports/history.html) > port to this PR. Would it make sense to offer just existing ports as > port categories in PR submission form? No, port-arm is a legitimate category. It is meant for all the ARM ports, of which evbarm is just one. > I've also noticed that there is no maintainer listed for the evbarm port > on the "port maintainers" web page > (http://www.netbsd.org/people/port-maintainers.html). This seems > surprising to me as the port is listed among the "Tier I" ports. Does > this port have a maintainer? I cannot comment on who the official portmaster is, but the evbarm port is fairly active. jmcneill@ does quite a bit of work, for example. -- Benny
Re: port-arm/53537: typo in src/sys/arch/arm/sunxi/sunxi_thermal.c
Hi, gnats-ad...@netbsd.org wrote: It has the internal identification `port-arm/53537'. The individual assigned to look at your report is: port-arm-maintainer. Category: port-arm Responsible:port-arm-maintainer Synopsis: typo in src/sys/arch/arm/sunxi/sunxi_thermal.c Arrival-Date: Sat Aug 18 14:05:00 + 2018 I realize that I've maybe made a mistake by assigning a category matching a non-existing (ever? http://www.netbsd.org/ports/history.html) port to this PR. Would it make sense to offer just existing ports as port categories in PR submission form? I've also noticed that there is no maintainer listed for the evbarm port on the "port maintainers" web page (http://www.netbsd.org/people/port-maintainers.html). This seems surprising to me as the port is listed among the "Tier I" ports. Does this port have a maintainer? Thanks, r.
Re: Smooth ThinkPad installation
Hi, Cág wrote: Well, old VGA fonts could be modified with pcvt-utils, at least that's what the guide says. This "high-res" font is kinda built-in into drm(4) (correct me if I'm wrong), that's why you can't change it with wsfontload(8). yes... it is using the "high res" console. Can't we fix the fonts inside DRM? Riccardo
Re: git https issue
On Aug 19, 2018 2:06 PM, matthew sporleder wrote: > > On Sun, Aug 19, 2018 at 4:26 AM, Riccardo Mottola > wrote: > > Hi, > > > > > > On 19/08/2018 02:26, Matt Sporleder wrote: > >> > >> > >> Can you do curl -vvv to GitHub? > > > > > > hmm, if you mean just to the homepage like below, we have an issue :( > > > > narsil$ curl -vvv https://github.com/ > > * Trying 192.30.253.113... > > * TCP_NODELAY set > > * Connected to github.com (192.30.253.113) port 443 (#0) > > * ALPN, offering http/1.1 > > * Cipher selection: > > ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH > > * successfully set certificate verify locations: > > CAfile: none > > CApath: /etc/openssl/certs > > * TLSv1.2 (OUT), TLS header, Certificate Status (22): > > * TLSv1.2 (OUT), TLS handshake, Client hello (1): > > * TLSv1.2 (IN), TLS handshake, Server hello (2): > > * TLSv1.2 (IN), TLS handshake, Certificate (11): > > * TLSv1.2 (IN), TLS handshake, Server key exchange (12): > > * TLSv1.2 (IN), TLS handshake, Server finished (14): > > * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): > > * TLSv1.2 (OUT), TLS change cipher, Client hello (1): > > [1] Illegal instruction (core dumped) curl -vvv https://github.com/ > > > > gdb tells me: > > * TLSv1.2 (OUT), TLS change cipher, Client hello (1): > > > > Thread 1 received signal SIGILL, Illegal instruction. > > 0xb66f3d50 in gcm_ghash_4bit_mmx () from /usr/lib/libcrypto.so.12 > > > > > > (gdb) bt > > #0 0xb66f3d50 in gcm_ghash_4bit_mmx () from /usr/lib/libcrypto.so.12 > > #1 0x in ?? () > > > > very nice :) > > > > now I don't remember if this CPU has MMX or not... > > cpu0 at mainbus0 > > cpu0: Intel 586-class, 232MHz, id 0x581 > > cpu0: package 0, core 0, smt 0 > > > > It should though, according to: https://www.thinkwiki.org/wiki/Category:600 > > > > > > Riccardo > > Looks like you found the issue. There was a thread on tech I believe talking about something very similar not too long ago. Might be worth looking through the archives.
Re: git https issue
Hi Matthew, On 19/08/2018 21:06, matthew sporleder wrote: gdb tells me: * TLSv1.2 (OUT), TLS change cipher, Client hello (1): Thread 1 received signal SIGILL, Illegal instruction. 0xb66f3d50 in gcm_ghash_4bit_mmx () from /usr/lib/libcrypto.so.12 (gdb) bt #0 0xb66f3d50 in gcm_ghash_4bit_mmx () from /usr/lib/libcrypto.so.12 #1 0x in ?? () very nice:) now I don't remember if this CPU has MMX or not... cpu0 at mainbus0 cpu0: Intel 586-class, 232MHz, id 0x581 cpu0: package 0, core 0, smt 0 It should though, according to:https://www.thinkwiki.org/wiki/Category:600 Riccardo Looks like you found the issue. Well, what is the issue actually? We have a clue... but no details do you think git has the same issue but does not coredumps? Anyway, curl should work, I found a bug for sure. /usr/lib/libcrypto.so.12 is part of base though. What now? a PR? Riccardo
