Re: Packages for 6.6 mips64el missing from cdn.openbsd.org

2020-02-19 Thread Xiyue Deng
Stuart Henderson writes: > On 2020-02-12, Xiyue Deng wrote: >> --=-=-= >> Content-Type: text/plain >> >> Xiyue Deng writes: >> >>> Hi, >>> >>> It looks like cdn.openbsd.org[1] doesn't sync the 6.6 packages for mips64el >>> from ftp.openbsd.org[2]. >>> >>> [1] http://cdn.openbsd.org/pub/OpenBSD/

Re: Old thread, but wondering if any updates?

2020-02-19 Thread Stuart Henderson
On 2020-02-19, myml...@gmx.com wrote: > I posted this way back in 2017 but i'm wondering if anything has changed... > > https://marc.info/?l=openbsd-misc&m=149613307021262&w=2 > > Is the 16Tb restriction been removed for full disk encryption? The only thing that changed is that the failure is now

setxkbmap cannot completely set compose key

2020-02-19 Thread 陈贤文
Dear OpenBSD users, I run OpenBSD 6.6 amd64. The window manager is fvwm with stock configuration. I am not able to completely set compose key by $ setxkbmap -layout us -variant dvp -option compose:ralt What I meant by *not completely* is that I am able to use _right alt_ as the compose key on f

Re: setxkbmap cannot completely set compose key

2020-02-19 Thread Ingo Schwarze
Hi, Xianwen Chen wrote on Wed, Feb 19, 2020 at 10:37:58AM +: > I run OpenBSD 6.6 amd64. I'm trying to reproduce on OpenBSD-current. > The window manager is fvwm I'm using that, too. > with stock configuration. Well, my configuration is much less bloated than the default (125 rather than

Cannot start conversation using talk

2020-02-19 Thread ben
Hello, everyone; I'm attempting to initiate a conversation via talk(1) however upon executing the command I receive the following error: talk: Couldn't bind to control socket: Can't assign requested address I've uncommented the line in /etc/inetd.conf which corresponds to the talkd daemon, how

Re: Cannot start conversation using talk

2020-02-19 Thread Otto Moerbeek
On Wed, Feb 19, 2020 at 03:38:24PM +, b...@0x1bi.net wrote: > > Hello, everyone; > > I'm attempting to initiate a conversation via talk(1) however upon > executing the command I receive the following error: > > talk: Couldn't bind to control socket: Can't assign requested address > > I've

Re: Cannot start conversation using talk

2020-02-19 Thread ben
I verified the output of rcctl and inetd is running. Ben Raskin.

Re: Cannot start conversation using talk

2020-02-19 Thread Matthew Weigel
On 2020-02-19 9:48, b...@0x1bi.net wrote: I verified the output of rcctl and inetd is running. Did you restart inetd after editing inetd.conf? It has to decide what ports to listen on when it starts up, which means it isn't going to notice edits. -- Matthew Weigel

Re: Cannot start conversation using talk

2020-02-19 Thread ben
>Did you restart inetd after editing inetd.conf? It has to decide what >ports to listen on when it starts up, which means it isn't going to >notice edits. Yes, I restarted inetd. I still receive the 'Couldn't bind to socket: Can't assign requested address' I'm not attempting to talk to another u

Re: Cannot start conversation using talk

2020-02-19 Thread Frederic Cambus
On Wed, Feb 19, 2020 at 06:25:56PM +, b...@0x1bi.net wrote: > >Did you restart inetd after editing inetd.conf? It has to decide what > >ports to listen on when it starts up, which means it isn't going to > >notice edits. > > Yes, I restarted inetd. I still receive the 'Couldn't bind to socket

Re: Cannot start conversation using talk

2020-02-19 Thread ben
> Do you have a correct entry with the machine hostname (full hostname(1) > output) in /etc/hosts? I don't. What should the entry look like? Should the hostname point to 0.0.0.0? Ben Raskin.

Re: Cannot start conversation using talk

2020-02-19 Thread KatolaZ
On Wed, Feb 19, 2020 at 07:13:48PM +, b...@0x1bi.net wrote: > > Do you have a correct entry with the machine hostname (full hostname(1) > > output) in /etc/hosts? > > I don't. What should the entry look like? Should the hostname point to > 0.0.0.0? It should point to 127.0.0.1

Re: Cannot start conversation using talk

2020-02-19 Thread ben
I've set my hostname to point to 127.0.0.1 and I still receive the same error. I tried with and without the domain information. Is there a log for talkd or inetd? I've attempted to use the -d flag for inetd however I receive no error messages or warnings. Ben Raskin.

Re: setxkbmap cannot completely set compose key

2020-02-19 Thread 陈贤文
Dear Ingo, Danke! On 2/19/20, Ingo Schwarze wrote: > Just to make sure it worked, could you please show the output of: > >$ setxkbmap -query The output is: rules: base model: pc105 layout: us variant:dvp options:compose:ralt > What exactly do you mean by "not able to

Re: Cannot start conversation using talk

2020-02-19 Thread Zeljko Jovanovic
On 19.02.2020. 22:08, b...@0x1bi.net wrote: I've set my hostname to point to 127.0.0.1 and I still receive the same error. I tried with and without the domain information. Is there a log for talkd or inetd? I've attempted to use the -d flag for inetd however I receive no error messages or warni

Re: setxkbmap cannot completely set compose key

2020-02-19 Thread NilsOla Nilsson
We had the same problem in this thread: https://marc.info/?l=openbsd-misc&m=156352002210168&w=2 It is working fine for me now, so I can't reproduce it. /NilsOla On Thu, Feb 20, 2020 at 06:03:53AM +, Xianwen Chen (陈贤文) wrote: > Dear Ingo, > > Danke! > > On 2/19/20, Ingo Schwarze wrote: >

Re: suggestions for USB printer (maybe even with scanner)?

2020-02-19 Thread Jordan Geoghegan
On 2020-02-18 21:28, Stuart Longland wrote: On 6/2/20 7:26 am, Adam Thompson wrote: I don't know what you need in a printer, and I don't know what you mean by cheap, so... YMMV. However, I've found Brother **LASER** printers to be very good, and most of them support PCL6 and/or PS3. For exam

Re: setxkbmap cannot completely set compose key

2020-02-19 Thread NilsOla Nilsson
To sum up: It helped by recompile and reinstall xterm. But only for a) newly started xterm's b) the xterm where the recompile/reinstall was run I don't remember if I was running stable or current at the time. /NilsOla On Thu, Feb 20, 2020 at 07:46:35AM +0100, NilsOla Nilsson wrote: > We had the s